Re: new install

[lsorense@csclub.uwaterloo.ca (Lennart Sorensen)]

On Wed, Apr 19, 2006 at 10:51:26PM -0400, Anthony DeRobertis wrote:
> That really shouldn't matter. The RAID superblocks for all RAID levels
> contain a UUID for a reason.
> 
> With
> 	DEVICE partitions
> in /etc/mdadm/mdadm.conf, mdadm will check /proc/partitions for all
> partitions and scan each for your raid disks.
> 
> [Not sure how to make mkinitramfs do this, though.]

The problem I get is that on some boots I get:

piix: sdc, sdd
/dev/md0 = /dev/sda1+/dev/sdb1 (boot)
/dev/md1 = /dev/sda2+/dev/sdb2 (root)
/dev/md2 = /dev/sda3+/dev/sdb3 (lvm first PV)

promise: sda, sdb
/dev/md3 = /dev/sdc1+/dev/sdd1 (lvm second PV)

and on others I get:

promise: sda, sdb
/dev/md0 = /dev/sda1+/dev/sdb1 (lvm second PV)

piix: sdc, sdd
/dev/md1 = /dev/sdc1+/dev/sdd1 (boot)
/dev/md2 = /dev/sdc2+/dev/sdd2 (root)
/dev/md3 = /dev/sdc3+/dev/sdd3 (lvm first PV)

So now, do I pass root=/dev/md1 or root=/dev/md2?  Seems 50% of the time
it is one, and 50% of the time the other.  Bloody pain really.

I tried passing root=LABEL=ROOT but for some reason, at least with
2.6.15, /dev/disk/.... needed to access by label doesn't exist so at
least with the way initramfs-tools makes the initrd, it can't find root
that way.

So my raid componets always start up just fine, the problem is knowing
which raid md device is the right one to mount as root.

Len Sorensen