I got the solution from A.Stecker but I forgot to cc the list, sorry... The fix was to add the kernel -r option on boot, as described in http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6923585
Thanks, Didier -- This message posted from opensolaris.org On 24 Mar 2010, at 22:21, Mark Wedel wrote: > On 03/19/10 01:15 AM, Didier Carlier wrote: >> Hello, >> The machine is an Sun Ultra 24, I'm trying to replace the original SATA boot >> disk (250G) with a a mirror of 2 250GB slices on 2 1TB disks. >> I inserted the first new disk which I labeled, sliced, attached to rpool, >> resilvered and finally installed grub on it. >> >> I then stop the machine, boot it and go the bios to select the new drive and >> boot from it. >> It works and I doubled check once booted that it actually booted from the >> new disk using the "prtconf -v|sed -n '/bootpath/,/value/p'" stanza. >> >> Next step in my plan was to remove the original boot disk, insert the second >> new 1TB disk and repeat the steps above so that I would end up with intended >> rpool consisting of a mirror of the 2 slices 0 on the 2 new disks. >> So I remove the original disk and reboot. >> Grub takes control, it starts to boot but stops after printing the line >> "Hostname: xxx". Normally the line after that is something like "Reading ZFS >> configuration". >> With the -v boot option, the last message printed is >> pseudo-device: srn0 >> srn0 is /pseudo/s...@0 >> >> When I put back the original boot disk, it completes the boot again. >> >> So it seems the system it actually booting fine from both disks, but only as >> long as the original disk is still there. >> Does this ring a bell ? >> Thanks for any hint... > > Have you tried doing a zpool detach on the disk you want to remove before > rebooting it? > > I've seen similar problems at boot with missing root mirrors (in my case, the > external device was a USB drive that I was planning to use for an offsite > copy) - if that device was turned off, I was unable to boot. If it was on, > able to boot. If I detached it, it didn't matter the state. > > It may be that the uninitialized data on that new device is confusing things. _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
