I found: http://kernel-handbook.alioth.debian.org/ch-initramfs.html#s -initramfs-exam
===== kha...@khaeru-storage:~$ mkdir tmp kha...@khaeru-storage:~$ cd tmp kha...@khaeru-storage:~/tmp$ zcat /boot/initrd.img-2.6.27-11-server | cpio -i 41267 blocks kha...@khaeru-storage:~/tmp$ cat etc/mdadm/mdadm.conf DEVICE partitions ARRAY /dev/md0 level=raid1 num-devices=2 UUID=490f3db6:cea49fa3:345b7477:817747f3 spares=2 ARRAY /dev/md1 level=raid1 num-devices=2 UUID=0726d925:6e4e7a99:bcdab21b:f117ebf9 spares=2 ARRAY /dev/md2 level=raid5 num-devices=4 UUID=9d07bdb8:ede8880b:54422443:48105f18 DEVICE partitions ARRAY /dev/md0 level=raid1 num-devices=2 spares=2 UUID=490f3db6:cea49fa3:345b7477:817747f3 ARRAY /dev/md1 level=raid1 num-devices=2 spares=2 UUID=0726d925:6e4e7a99:bcdab21b:f117ebf9 ARRAY /dev/md2 level=raid5 num-devices=4 UUID=9d07bdb8:ede8880b:54422443:48105f18 MAILADDR root ===== ...so it seems the 2.6.27-11-server kernel was able to boot with this odd mdadm.conf, but the 2.6.28-11-server kernel was not. -- bad mdadm.conf on jaunty upgrade https://bugs.launchpad.net/bugs/366204 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
