As long as the proper mdadm --incremental mode command (to start a single array) is not available (Bug #251646) a workaround needs to be used:
mdadm --remove <incomplete-md-device> <arbitrary-member-device-of- incomplete-array> mdadm --incremental --run <arbitrary-member-device-of-incomplete-array> ** Description changed: - Binary package hint: mdadm - - after a timeout mdadm in initrams degrades all arrays instead of just + After a timeout mdadm in initrams degrades all arrays instead of just those required for the rootfs. - The dependencies are not checked and saved to initramfs. Instead the script just looks into /proc/mdstat and uses "mdadm --assemble --scan --run" starting all arrays, if some arrays are incomplete (very likely during initramfs state). - (Additionaly a legacy non-hotplug command.) + This is not good since non-rootfs arrays are likely to be available only + incompletely (due to the early stage during boot) and are getting + desynced by this. - The best way to fix the so many mdadm bugs is probably to adopt the - event driven upstart/mountall init within intiramfs. + When creating the initramfs image the mdadm hook should determine the + dependencies of the rootfilesystem and save a list of the required md + devices in the initramfs. - See https://wiki.ubuntu.com/ReliableRaid + Currently the initramfs boot script just looks for *any* available + incomplete array and calls "mdadm --assemble --scan --run", which starts + all runnable arrays. + + -- + The best way to fix the so many mdadm bugs is probably to adopt the event driven upstart/mountall init within intiramfs. + Bug #491463 upstart init within initramfs -- initramfs' init-premount degrades *all* arrays (not just those required to boot) https://bugs.launchpad.net/bugs/497186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
