I agree. I don't really think the problem is with mdadm - but instead
with the order that the disk and controller drivers are loaded in
feisty. Don't know what module controls that though. Hopefully this
bug will be addressed before release!
- Original Message -
From: "marcw" <[EMAIL PR
Tried it, no joy. If I get time tomorrow I'm going to experiment with
manual changes to the initrd to see if I can work around the module
problem that way. I looked, and while I thought I remembered an mdadm
mailing list, it seems my memory was faulty or it no longer exists. If
you have any othe
I think I may have found it. Attempting to boot from RAID,
/proc/ide/ide0/hda/driver is "ide-default version 0.9.newide" whereas
booting successfully via non-RAID, /proc/ide/ide0/hda/driver is "ide-
disk version 1.18".
Googling "ide-default ide-disk" reveals some bugs/race conditions that
were su
I had a XenExpress 3.2 cd handy to boot in this same machine, and one
thing I note is that it assigns the same hardware/drives significantly
differently.
XenExpress 2.6.16.38 Feisty 2.6.20.13
hd[a-d] Promise Controller 1 hd[a-d] Onboard VIA controller
