I did, but still the same thing, I think because break=mount doesn't come into play until later in initrd.
FWIW, I reinstalled the first disk with yesterdays daily build, and I still get the same thing (namely when I boot off RAID, /dev/hda* and /dev/hdc* don't show up at all in /proc/partitions which of course keeps the RAID arrays from properly assembling. The partitions on the two promise controllers show up fine. Finally, it dawned on me, why don't you look at the /proc/kmsg and compare RAID versus non-RAID. A few problems showed up: 1. It appears that in the RAID setup, the kernel hangs trying to initialize the onboard vt8237a controller that hda and hdc are attached to (which driver is built into the fesity kernel). I know this, because if I do 'more /proc/kmsg' that is as far as it goes (and in fact, when it gets to the last line, more seems to hang locking the whole initramfs session requiring a hard reboot). 2. A related bug/feature that shows up in either boot case, is that mdadm tries to assemble the arrays twice. It seems that it tries first when all the fake SCSI devices are found, and again later when it finds some IDE devices that also happen to be part of the array. Maybe originally mdadm wasn't intended to work with both IDE and SCSI drives in the same array (but now it seems it must because of the way modern kernels blur the distinction between IDE/SATA/SCSI drives)??? This seems to be nonfatal, but results in unnecessary starting/stopping of the array(s) during boot to add additional member drives. I'm no kernel guy, but it seems there is a conflict somewhere in the modules involved and the built-in vt8237a driver that putting root=/dev/md0 versus root=/dev/hda1 somehow triggers. I'm thinking about posting a link to this thread on the mdadm mailing list unless someone here has some bright ideas. P.S. It also appears intermittent similar to what the first poster was saying. 99% of the time booting of raid, I get /dev/sd[a-d] and no /dev/hda or /dev/hdc, but one time I happened to notice that it was reversed - no sd[a-d] but did get /dev/hda and /dev/hdc. -- Feisty beta1 raid is broken https://bugs.launchpad.net/bugs/96511 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
