Comment 2 for bug 98911

Revision history for this message
Daniel Dehennin (launchpad-baby-gnu) wrote :

I have this problem with my feisty.

I have no md array and the initramfs hook complains about that.

Booting does not work, initramdik created by yaird are OK.

I think a test should be done to see if md are used, and it should honor the /etc/default/mdadm configuration file:
INITRDSTART='none' should by pass the problem.

Here is a verbose output of update-initramfs:

Calling hook mdadm
Adding binary /sbin/mdadm
Adding module /lib/modules/2.6.20-14-generic/kernel/drivers/md/md-mod.ko
Adding module /lib/modules/2.6.20-14-generic/kernel/drivers/md/linear.ko
Adding module /lib/modules/2.6.20-14-generic/kernel/drivers/md/multipath.ko
Adding module /lib/modules/2.6.20-14-generic/kernel/drivers/md/raid0.ko
Adding module /lib/modules/2.6.20-14-generic/kernel/drivers/md/raid1.ko
Adding module /lib/modules/2.6.20-14-generic/kernel/drivers/md/xor.ko
Adding module /lib/modules/2.6.20-14-generic/kernel/drivers/md/raid456.ko
Adding module /lib/modules/2.6.20-14-generic/kernel/drivers/md/raid10.ko
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
W: mdadm: falling back to emergency procedure in initramfs.