Closed ericwaraujo closed 9 years ago
to backup, enter the chroot:
sudo enter-chroot
navigate to your /home dir
cp -avr /home/myusername/myfoldername ~/Downloads
Where,
-a : Preserve the specified attributes such as directory an file mode, ownership, timestamps, if possible additional attributes: context, links, xattr, all. -v : Explain what is being done. -r : Copy directories recursively.
then after you're sure it all copied correctly to Downloads, move it to usb and/or cloud storage as /Downloads may not always remain permanent storage.
That's one way to backup, another way is to use edit-chroot
outside the chroot:
sudo edit-chroot -b trusty
That will save a compressed tarball in ~/Downloads by default.
You might want to re-download crouton (https://goo.gl/fd3zc) and then attempt to update your chroot one more time, the latest version of crouton is more forgiving when encountering update errors and that might be just enough to get you going.
I noticed a couple of problems -
W: GPG error: http://star-www.st-andrews.ac.uk trusty/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 51716619E084DAB9
WARNING: The following packages cannot be authenticated! r-base-core r-cran-boot r-cran-cluster r-cran-foreign r-cran-mass r-cran-kernsmooth r-cran-lattice r-cran-nlme r-cran-matrix r-cran-mgcv r-cran-survival r-cran-rpart r-cran-class r-cran-nnet r-cran-codetools r-base r-recommended r-base-dev r-doc-html r-base-html
They could be related but I'm not familiar with them. If you could remove them I think your update would complete successfully.
Will try both solutions. Knowing I can back up my files is already super awesome. Thank you so much for the help!!!
I have the same issue as ericwaraujo. Did the solution work for you?
These files mentioned are the R programming language packages through a ppa. Somehow the public key was corrupted in the latest update of chrome OS.
When you say 'remove' these files, can you describe this method more in detail. These are packages that are part of a ppa source and integral to an application I use.
Hi mathewarndt,
Last night I only had time to do the backup, following tedm suggestion and I have my backup now. Sweet!
Later I realized the packages are from R, but I had no time to remove them. (I have R installed but don't need it anymore, so removing them would work for me).
I also appreciate suggestions on how to remove these packages. Should I do
sudo enter-chroot
and then
apt-get remove
the packages?
By the way, I did try to update chroot as suggested by DennisLfromGA before removing the packages but it did not work.
@ericwaraujo I'd use:
apt-get remove --purge packagename
so you remove the config files as well.
YES! Back in business! Thank you very much @tedm @DennisLfromGA !!!
What worked:
Enter chroot:
sudo enter-chroot
List all installed packages (the r troublemaking packages will be listed there):
dpkg --get-selections | grep -v deinstall
Remove the problematic packages:
apt-get remove --purge packagename
where packagename will r-base then r-base-core then r-base-html and any other r- packages (see list above). Remove them one by one, after the first few all will be gone. Tab complete works, fyi.
Do another inspection:
dpkg --get-selections | grep -v deinstall
If all r packages are removed, exit chroot:
exit
Get the latest crouton to update chroot: Follow the link above provided by @DennisLfromGA, or/and follow Common issues and reporting instructions
I guess if you need R you could still install it again after updating chroot, but that is just my guess, I have not tested this.
Hi,
chroot had been running great for months until I had the power run out on me and could not restart anymore.
I unsuccessfully tried to update chroot, and the output can be found below.
I don’t mind reinstalling everything, BUT I do have a dir in my home that I really want to backup. If anybody could help me either get chroot up and running again or back up the dir I would be super appreciative!
Thank you so much!
Terminal outputs:
I unsuccessfully tried to update chroot:
Despite the error, I tried to startunity again: