SUMMARY: thumper, svm, findroot and dead disk 0.

From: Bryan Hodgson <>
Date: Mon May 11 2009 - 08:08:14 EDT
No responses. Everything just worked.

Installed new disk at c5t0d0.  Apparently thumper's BIOS boot
sequence item 'Hard Disk' is apparently as whatever is in either
bootable disk slot; there is no provision for explicitly booting
from a second disk.  The machine booted from c5t0d4 without
complaint, so it seems 'findroot' did what it is supposed to do.
The rest of the procedure was standard procedure for
re-mirroring; remove the missing metadb's (there were two on each
disk ...), fdisk c5t0d0, prtvtoc c5t0d4 | fmthard -s - c5t0d0,
recreate the mirrors, and installgrub on the new disk.


On Mon, Apr 13, 2009 at 05:46:54PM -0400, Bryan Hodgson wrote:
> One of our research groups has a thumper running 10u6.  The OS
> was installed (not upgraded) on ufs file systems on c5t0d0, and
> manually mirrored to c5t0d4 after the installation was complete
> (including 'installgrub /boot/grub/stage1 /boot/grub/stage2
> /dev/rdsk/c5t0d4s2').  c5t0d0s0 died recently (suddenly and
> entirely); the machine is still running, no reboot yet.  menu.lst
> uses the new 'findroot' syntax, specifically:  "findroot
> (rootfs0,0,a)".  /etc/system includes "set md:mirrored_root_flag=1".
> I'm trying to figure out how 'findroot' is going to play when
> disk 0 isn't present on reboot; that is, whether it would be
> 'better' to swap the c5t0d4 disk into the c5t0d0 spot, or boot
> from the second disk in the BIOS menu, or clone the existing grub
> boot entry to 'findroot (rootfs1,0,a)'.  I don't expect that
> re-establishing the mirrors will be a problem.
> Next time I will talk to my customer about a zfs root mirror, but
> for the present any suggestions / observations would be welcome.
> Will summarize.  TIA.
> Bryan Hodgson
sunmanagers mailing list
Received on Mon May 11 08:09:00 2009

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:14 EST