1 сентября 2016 г. 4:29:38 CEST, Reginald Beardsley via illumos-discuss <discuss@lists.illumos.org> пишет: > A suggestion: > > Boot a LiveCD > > Mount the existing system drive > > Mount a USB hard drive > > Make a ./ relative tarball of the non-bootable system on the USB drive > > Build a new system and then extract what you want to keep from the > tarball > > Good luck, > Reg > > -------------------------------------------- > On Wed, 8/31/16, Christopher Robinson via illumos-discuss > <discuss@lists.illumos.org> wrote: > > Subject: [discuss] OpenSolaris Boot Failure > To: discuss@lists.illumos.org > Date: Wednesday, August 31, 2016, 5:26 PM > > I am experiencing an inabilty to boot > to the Gnome desktop on OpenSolaris 2009.06. > This was most likely caused by powering off without shutting > down first, although I > have done that many times before with no problems. I can > login to the control con- > sole and I have tried the command "bootadm update-archive", > but that did not work. > I am able to get a live desktop in Gnome using my original > OpenSolaris CD, as well > as OI Hipster. Is there any way to access my files from > either of those? > It was suggested to me on the openindiana discuss-list that > I install OI Hipster and > migrate my files over. However, the installer only allows > one Solaris partition and > warns that it will overwrite the data. I do not have a clone > of my hard disk, so I need > to make sure that there will be no data loss. > Any help with this problem is greatly appreciated. >
Note that not all datasets may be set to mount by default (e.g, alternate rootfs'es, local zones and especially their delegated datasets) so tarballing, cpio'ing etc. on the filesystem tree level might not see all the data there was originally. This is not to say it is a bad offered solution, but one you should be more careful about - e.g. compare `zfs list` and `df` outputs, look at `zfs list -o canmount,mountpoint,zoned,name` for unmountable (by design, yours or vendor's) datasets, etc. See also if `zfs mount -a` reports errors (e.g. some corruption in metadata might be perhaps not handled well, so a read-only pool import or even rollback by a few TXGs if still possible - after you salvage whatever data you can - might be a solution). Also if booting from a livecd, don't forget to import the existing pool into an alternate location so it does not conflict with a livecd filesystem, e.g. `zpool import -R /tmp/mnt rpool` so all the tree is mounted under `/tmp/mnt` (you might need to mkdir it first). Jim -- Typos courtesy of K-9 Mail on my Samsung Android ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
