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
hd[e-h] Promise Controller 2 sd[ab] Promise Controller 1
hd[i-j] Onboard VIA controller sd[cd] Promise Controller 2
The boards BIOS has on option to set the hard disk order, and it is set
with as follows:
onboard master: 1st
onboard slave: 2nd
promise1 master: 3rd
promise1 slave: 4th
promise2 master: 5th
promise2 slave: 6th
Don't know if this helps, but thought I would provide it as additional
info. Is there a chance that perhaps the kernel code in the newer
Feisty kernel that reads the BIOS drive order is provided as a module
and somehow isn't included in my initrd image??? If so, what is the
name of that module please???
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
