Machine is running x86 snv_94 after recent upgrade from opensolaris 2008.05. ZFS and zpool reported no troubles except suggesting upgrade for from ver.10 to ver.11. seemed like a good idea at the time. system up for several days after that point then took down for some unrelated maintenance. now will not boot the opensol, drops to grub prompt, no menus. zfs was mirrored on two disks c6d0s0 and c7d0. I never noted the GRUB commands for booting and not really familiar with the nomenclature. at this point I am hoping that a burn of SXCE snv_94 will give me access to the zfs pools so I can try "update-grub" but at this point it will be about 9 hours to download the .iso and I kinda need to work on data residing in that system any suggestions thanks, sgk This message posted from opensolaris.org
Seymour Krebs wrote:> Machine is running x86 snv_94 after recent upgrade from opensolaris 2008.05. ZFS and zpool reported no troubles except suggesting upgrade for from ver.10 to ver.11. seemed like a good idea at the time. system up for several days after that point then took down for some unrelated maintenance. > > now will not boot the opensol, drops to grub prompt, no menus. > > zfs was mirrored on two disks c6d0s0 and c7d0. I never noted the GRUB commands for booting and not really familiar with the nomenclature. at this point I am hoping that a burn of SXCE snv_94 will give me access to the zfs pools so I can try "update-grub" but at this point it will be about 9 hours to download the .iso and I kinda need to work on data residing in that system > >I''ll try to help, but I''m confused by a few things. First, when you say that you upgraded from OpenSolaris 2008.05 to snv_94, what do you mean? Because I''m not sure how one "upgrades" an IPS-based release to the older SVR4 packages-based release type. Do you mean that you did an initial install using snv_94? If so, did you select a zfs root or a ufs root? At what point were you presented with the suggestion to upgrade the pool from ver.10 to ver.11? Also, you write that you are doing a burn of SXCE snv_94, but how did you do the "upgrade" (or whatever) to snv_94 in the first place without a snv_94 install medium? Lori> any suggestions > > thanks, > sgk > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >
-- Via iPhone 3G On 04-ao?t-08, at 19:46, Lori Alt <Lori.Alt at Sun.COM> wrote:>> >> >> > I''ll try to help, but I''m confused by a few things. First, when > you say that you upgraded from OpenSolaris 2008.05 to snv_94, > what do you mean? Because I''m not sure how one "upgrades" > an IPS-based release to the older SVR4 packages-based > release type. Do you mean that you did an initial install > using snv_94? >> >> >> >>
The first attempt at this went well... Anyway, he meant updating to the latest Indiana repo, which is based on snv_94. Regards, -mg -- Via iPhone 3G On 04-ao?t-08, at 19:46, Lori Alt <Lori.Alt at Sun.COM> wrote:> Seymour Krebs wrote: >> Machine is running x86 snv_94 after recent upgrade from opensolaris >> 2008.05. ZFS and zpool reported no troubles except suggesting >> upgrade for from ver.10 to ver.11. seemed like a good idea at the >> time. system up for several days after that point then took down >> for some unrelated maintenance. >> >> now will not boot the opensol, drops to grub prompt, no menus. >> >> zfs was mirrored on two disks c6d0s0 and c7d0. I never noted the >> GRUB commands for booting and not really familiar with the >> nomenclature. at this point I am hoping that a burn of SXCE snv_94 >> will give me access to the zfs pools so I can try "update-grub" but >> at this point it will be about 9 hours to download the .iso and I >> kinda need to work on data residing in that system >> >> > I''ll try to help, but I''m confused by a few things. First, when > you say that you upgraded from OpenSolaris 2008.05 to snv_94, > what do you mean? Because I''m not sure how one "upgrades" > an IPS-based release to the older SVR4 packages-based > release type. Do you mean that you did an initial install > using snv_94? If so, did you select a zfs root or a ufs root? > At what point were you presented with the suggestion > to upgrade the pool from ver.10 to ver.11? > > Also, you write that you are doing a burn of SXCE snv_94, > but how did you do the "upgrade" (or whatever) to snv_94 > in the first place without a snv_94 install medium? > > Lori >> any suggestions >> >> thanks, >> sgk >> >> >> This message posted from opensolaris.org >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >> > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Did you do the extra required grub step between the ''pkg image-update'' and rebooting? If I recall correctly, it needs to happen once between snv_86 (which I think is stock OS2008.05 and snv_89+ I think the grub step is documented at opensolaris.org in the downloads section where it talks about work on OS 2008.11, but I can''t seem to load opensolaris.org right now to send a link. I believe there is also a workaround to get you back out of the situation you''re in now, but I''m not sure. I''ve included the email with the procedure, but I think the solution to your current problem might be in the instructions on os.org.. Hope this helps. --Kris> ---------- Forwarded message ---------- > Date: Fri, 6 Jun 2008 22:46:31 -0700 > From: Alan Steinberg <Alan.Steinberg at Sun.COM> > Reply-To: "mailer at opensolaris.org" <mailer at opensolaris.org> > To: "indiana-discuss at opensolaris.org" <indiana-discuss at opensolaris.org>, > "opensolaris-announce at opensolaris.org" > <opensolaris-announce at opensolaris.org> > Subject: [osol-announce] pkg.opensolaris.org repository update: snv_90 > > The pkg.opensolaris.org repository has been updated to the snv_90 level. > This update also includes snv_89 packages. > > PAY ATTENTION TO THE ATTACHED UPDATE PROCEDURE!!! Failure to do so will > prevent your system from rebooting. > > Please see the attached for instructions for updating from OpenSolaris > 2008.05, as well as a list of changes incorporated into the snv_90 update. > > -- Alan Steinberg > OpenSolaris Release Engineering >Instructions to update OpenSolaris 2008.05 to build 89 or later =============================================================== The command "pkg image-update" can be used to update an OpenSolaris 2008.05 system to build 89 or later. However due to changes in the GRUB boot system, one must manually update the Master Boot Record (MBR) to include these latest changes. When "pkg image-update" completes successfully, it will print a message of the form A clone of opensolaris exists and has been updated and activated. On next boot the Boot Environment opensolaris-1 will be mounted on ''/''. Reboot when ready to switch to this updated BE. The name of the newly created clone can also be seen by looking for the "Active on reboot" entry in the output of the "beadm list" command $ beadm list BE Active Active on Mountpoint Space Name reboot Used ---- ------ --------- ---------- ----- opensolaris-1 no yes - 17.06M opensolaris yes no - 33.92M First, mount the clone under the /mnt directory $ pfexec mount -F zfs rpool/ROOT/opensolaris-1 /mnt Next, update the GRUB configuration on your ZFS boot device(s) using $ pfexec /mnt/boot/solaris/bin/update_grub -R /mnt When you''re ready to boot into the updated boot environment, you can reboot(1M) or init(1M) as usual. Today at 10:18, Seymour Krebs <seymour.krebs at gmail.com> wrote:> Machine is running x86 snv_94 after recent upgrade from opensolaris 2008.05. ZFS and zpool reported no troubles except suggesting upgrade for from ver.10 to ver.11. seemed like a good idea at the time. system up for several days after that point then took down for some unrelated maintenance. > > now will not boot the opensol, drops to grub prompt, no menus. > > zfs was mirrored on two disks c6d0s0 and c7d0. I never noted the GRUB commands for booting and not really familiar with the nomenclature. at this point I am hoping that a burn of SXCE snv_94 will give me access to the zfs pools so I can try "update-grub" but at this point it will be about 9 hours to download the .iso and I kinda need to work on data residing in that system > > any suggestions > > thanks, > sgk > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >-- Thomas Kris Kasner Qualcomm Inc. 5775 Morehouse Drive San Diego, CA 92121 (858)658-4932 But rushing around seems what''s wrong with the world Don''t lose the dreams inside your head... -- Dave Matthews "You Never Know"
So, it looks like only snv94 is capable of understanding the
"upgraded" zfs pool.
jack at opensolaris:~# zpool history
no pools available
jack at opensolaris:~# zpool import
pool: rpool
id: 17601658646371843627
state: UNAVAIL
status: The pool was last accessed by another system.
action: The pool cannot be imported due to damaged devices or data.
see: http://www.sun.com/msg/ZFS-8000-EY
config:
rpool UNAVAIL newer version
mirror ONLINE
c5d0s0 ONLINE
c6d0 ONLINE
jack at opensolaris:~# uname -a
SunOS opensolaris 5.11 snv_93 i86pc i386 i86pc Solaris
This message posted from opensolaris.org
thanks for the help folks esp. Mikee who had experienced a similar problem and provided a concise solution basically, after an excruciating download of the sxce_b94.iso, I was able to boot from the dvd, "zpool import -f rpool". this gave me failures to mount x4 "unable to create mount point". so i was kinda worried about the loss of the whole file system, but scrubbed and it was ok and "zfs list" showed all teh requisite zfs directories. so finally, I gathered up some courage and "installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c2d0s0" seemed to write out what I assume is a new MBR. tried to also installgrub on the other disk in the mirror c3d0 and failed over several permuations"cannot open/stat /dev/rdsk/c3d0s2" was the error msg. however a reboot from dsk/c2dos0 gave me a healthy and unchanged grub stage2 menu and functioning system again . whew Although I cannot prove causality here, I still think that the zpool upgrade ver.10 -> ver.11 borked the MBR. indeed, probably the stage2 sectors, i guess. I also seem to also only have single MBR between the two disks in the mirror. is this normal? This message posted from opensolaris.org
Luca Morettoni reported a similar behavior (i.e. a perfectly running system that drops into grub on reboot) on indiana-discuss. I wonder if the issue is that installgrub is updating the MBR on one disk. If the second disk does not have an updated grub menu, that would explain what you are seeing. If this indeed is the issue, then what is puzzling is why did the BIOS change the boot order ? Was the BIOS updated and the values got reset to some default values ? Lori Alt wrote:> Seymour Krebs wrote: > >> Machine is running x86 snv_94 after recent upgrade from opensolaris 2008.05. ZFS and zpool reported no troubles except suggesting upgrade for from ver.10 to ver.11. seemed like a good idea at the time. system up for several days after that point then took down for some unrelated maintenance. >> >> now will not boot the opensol, drops to grub prompt, no menus. >> >> zfs was mirrored on two disks c6d0s0 and c7d0. I never noted the GRUB commands for booting and not really familiar with the nomenclature. at this point I am hoping that a burn of SXCE snv_94 will give me access to the zfs pools so I can try "update-grub" but at this point it will be about 9 hours to download the .iso and I kinda need to work on data residing in that system >> >> >> > I''ll try to help, but I''m confused by a few things. First, when > you say that you upgraded from OpenSolaris 2008.05 to snv_94, > what do you mean? Because I''m not sure how one "upgrades" > an IPS-based release to the older SVR4 packages-based > release type.In the IPS world, one upgrades using the command pkg image-update. pkg commands link with beadm libraries. rpool is snapshotted, then cloned. It is mounted on a temporary mountpoint and then the contents are upgraded. Very similar to live upgrade for zfs. -Sanjay> Do you mean that you did an initial install > using snv_94? If so, did you select a zfs root or a ufs root? > At what point were you presented with the suggestion > to upgrade the pool from ver.10 to ver.11? > > Also, you write that you are doing a burn of SXCE snv_94, > but how did you do the "upgrade" (or whatever) to snv_94 > in the first place without a snv_94 install medium? > > Lori > >> any suggestions >> >> thanks, >> sgk >> >> >> This message posted from opensolaris.org >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >> >> > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >
You can try to boot from Opensolaris CD, import rpool, mount the root filesystem and upgrade the grub. Regards, Andre W. Seymour Krebs wrote:> Machine is running x86 snv_94 after recent upgrade from opensolaris 2008.05. ZFS and zpool reported no troubles except suggesting upgrade for from ver.10 to ver.11. seemed like a good idea at the time. system up for several days after that point then took down for some unrelated maintenance. > > now will not boot the opensol, drops to grub prompt, no menus. > > zfs was mirrored on two disks c6d0s0 and c7d0. I never noted the GRUB commands for booting and not really familiar with the nomenclature. at this point I am hoping that a burn of SXCE snv_94 will give me access to the zfs pools so I can try "update-grub" but at this point it will be about 9 hours to download the .iso and I kinda need to work on data residing in that system > > any suggestions > > thanks, > sgk > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >
Almost. I did exactly the same thing to my system -- upgrading ZFS. The 2008.11 development snapshot CD I found is based on snv_93 and doesn''t yet suport ZFS v.11 so it refuses to import the pool. My system doesn''t have a DVD drive, so I cannot boot the SXCE snv_94 DVD. I guess I have to track down or wait for a >= snv_94 based development snapshot live CD. Should be any day now, right? This message posted from opensolaris.org
> so finally, I gathered up some courage and > "installgrub /boot/grub/stage1 /boot/grub/stage2 > /dev/rdsk/c2d0s0" seemed to write out what I assume > is a new MBR.Not the MBR - the stage1 and 2 files are written to the boot area of the Solaris FDISK partition.> tried to also installgrub on the other > disk in the mirror c3d0 and failed over several > permuations"cannot open/stat /dev/rdsk/c3d0s2" was > the error msg.This is because installgrub needs the "overlap" slice to be present as slice 2 for some reason. The overlap slice, also called the "backup" slice, covers the whole of the Solaris FDISK partition. If you don''t have one on your second disk, just create one.> > however a reboot from dsk/c2dos0 gave me a healthy > and unchanged grub stage2 menu and functioning system > again . whew > > Although I cannot prove causality here, I still think > that the zpool upgrade ver.10 -> ver.11 borked the > MBR. indeed, probably the stage2 sectors, i guess.No - upgrading a ZFS pool doesn''t touch the MBR or the stage2. The problem is that the grub ZFS filesystem reader needs updated to understand the version 11 pool. This doesn''t (yet) happen automatically.> > I also seem to also only have single MBR between the > two disks in the mirror. is this normal?Not really normal, but at present manually creating a ZFS boot mirror in this way does not set the 2nd disk up correctly, as you''ve discovered. To write a new Solaris grub MBR to the second disk, do this: installgrub -m /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c3d0s0 The -m flag tells installgrub to put the grub stage1 into the MBR. Cheers Andrew. This message posted from opensolaris.org
On Wed, Aug 06, 2008 at 10:19:45PM -0700, andrew wrote:> > > > I also seem to also only have single MBR between the > > two disks in the mirror. is this normal? > > Not really normal, but at present manually creating a ZFS boot > mirror in this way does not set the 2nd disk up correctly, as you''ve > discovered. To write a new Solaris grub MBR to the second disk, do > this: > > installgrub -m /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c3d0s0 > > The -m flag tells installgrub to put the grub stage1 into the MBR.I had a similar situation. Starting with a single disk containing the root pool, I added a second disk and mirrored them manually into the same zpool. Then I created a second boot environment in the same pool and did a live upgrade from build 94 to build 95. That operation seems to have written the GRUB stages onto both disks. I can boot either one to get the same GRUB menu and the same default Nevada build. I''m very impressed with how well ZFS and Live Upgrade work together. -- -Gary Mills- -Unix Support- -U of M Academic Computing and Networking-
I have a similar situation and would love some concise suggestions: Had a working version of 2008.05 running svn_93 with the updated grub. I did a pkg-update to svn_95 and ran the zfs update when it was suggested. System ran fine until I did a a reboot, then no boot, only grub command line shows up.>From this post it appears that I''ll have to install another disk to import the rpool and resurrect the system. Is this true? I''m downloading sol-nv-b97-x86-dvd.iso now. Can I use this?Any guided suggestions would be wonderful. Thanks. -- This message posted from opensolaris.org
Nils Goroll
2008-Sep-18 12:00 UTC
[zfs-discuss] Procedure to follow after zpool upgrade on rpool (was: zpool upgrade wrecked GRUB)
(not sure if this has already been answered)> I have a similar situation and would love some concise suggestions: > > Had a working version of 2008.05 running svn_93 with the updated grub. I did a pkg-update to svn_95 and ran the zfs update when it was suggested. System ran fine until I did a a reboot, then no boot, only grub command line shows up.IMHO, after a ZFS upgrade an easy way to fix this is: touch /etc/system # make bootadm re-create archive bootadm update-archive /boot/solaris/bin/update_grub If you''re already lost after an upgrade (commands from memory, no syntax guarantee) * Boot from a current snv CD (needs to support the zpool version you have upgraded to) ISOs available at http://www.genunix.org/ * Import your rpool mkdir /tmp/rpool zpool import -R /tmp/rpool rpool - if this fails, get the pool ID with zpool import, then use zpool import -f -R /tmp/rpool <ID> * Mount your root-fs mount -F zfs rpool/opensolaris-X /mnt (now same as above, but with mounted on /mnt) * update boot-archive touch /mnt/etc/system bootadm update-archive -R /mnt * update grub /mnt/boot/solaris/bin/update_grub * umount, export umount /mnt zpool export rpool At least this has worked for me. Would it be a good idea to put this into indiana release notes? Nils
Nils Goroll
2008-Sep-18 12:15 UTC
[zfs-discuss] Procedure to follow after zpool upgrade on rpool
Not knowing of a better place to put this, I have created http://www.genunix.org/wiki/index.php/ZFS_rpool_Upgrade_and_GRUB Please make any corrections there. Thanks, Nils
Pablo Méndez Hernández
2008-Sep-19 08:08 UTC
[zfs-discuss] Procedure to follow after zpool upgrade on rpool (was: zpool upgrade wrecked GRUB)
Hi: On Thu, Sep 18, 2008 at 13:00, Nils Goroll <slink at schokola.de> wrote:> (not sure if this has already been answered) > > > I have a similar situation and would love some concise suggestions: > > > > Had a working version of 2008.05 running svn_93 with the updated grub. I > did a pkg-update to svn_95 and ran the zfs update when it was suggested. > System ran fine until I did a a reboot, then no boot, only grub command line > shows up. > > IMHO, after a ZFS upgrade an easy way to fix this is: > > touch /etc/systemWhy is needed this step (the "touch" one) ? # make bootadm re-create archive> bootadm update-archive > /boot/solaris/bin/update_grubRegards. -- Pablo M?ndez Hern?ndez -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080919/ae03bd2d/attachment.html>
Nils Goroll
2008-Sep-19 08:43 UTC
[zfs-discuss] Procedure to follow after zpool upgrade on rpool
Hi Pablo,> Why is needed this step (the "touch" one) ? > > > # make bootadm re-create archive > bootadm update-archive > /boot/solaris/bin/update_grubThis is just an easy way to make sure bootadm will write new archive files. You could also use rm /platform/i86pc/amd64/boot_archive \ /platform/i86pc/boot_archive I am not absolutely sure if or why it is necessary to recreate the archive, but this has solved boot problems for me. I suspect that when the ZFS on disk format is changed, the updated grub zfs code expects all files to be written in that format. There are other issues related to the fact that the GRUB zfs implementation is lightweight, for instance it cannot read a boot archive which is created with compression=gzip enabled on the filesystem (or at least it could not a couple of months ago, have not re-checked recently). Nils