Looks like the --scan command might be useless as it seems only to work properly when the array is defined correctly in mdadm.conf. All my devices can be examined with --examine and do not show those odd "failed" lines. While not being able to reproduce the exact issue, removing the array definition from mdadm.conf gets me into a similar problem and mdadm seems not to work right at that point. But that happens with the old -46 and newer -50 kernels.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209423 Title: [STAGING] 2.6.32-47 kernel update on 10.04 breaks software RAID at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1209423/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
