** Description changed: - Binary package hint: mdadm - It is said that the intrepid fix to Bug #120375 re-added support to - mdadm and initramfs-tools for configurable booting degraded RAIDs, but a - systems with /home on a degraded array doesn't come up. + Systems with say /home on raid won't come up booting when raid wasdegraded during downtime. - The particular array needs to be "mdadm --run /dev/md1" after the fsck - fails and before any user is dropped to a console. + An init script like /etc/init.d/mdadm-degrade or because of the already + doing that kind of watchdog functionality "mountall" needs to --run + particular necessary arrays (those with fstab bootwait) degraded if they + don't come up complete after a timeout.. - A regular init script like /etc/init.d/mdadm-degrade (run earlier than - mdadm) is missing that used to run necessary arrays if they are - degraded. + Because the proper mdadm --incremental mode command is not available + (Bug #251646) a workaround needs to be used: - (Within the ubuntu hotplug-scheme /usr/share/initramfs- - tools/hooks/cryptroot contains code that may be usefull to determine - devices that the fstab depends on.) + mdadm --remove <incomplete-md-device> <arbitrary-member-device-of- + incomplete-array> + + mdadm --incremental --run <arbitrary-member-device-of-incomplete-array> + + + (See https://wiki.ubuntu.com/ReliableRaid "How would you decide what + device is needed?" about determining the md devices that the devices + mentioned in fstab depend on.)
** Description changed: - - Systems with say /home on raid won't come up booting when raid wasdegraded during downtime. + Systems with say /home on raid won't come up booting when raid + wasdegraded during downtime. An init script like /etc/init.d/mdadm-degrade or because of the already doing that kind of watchdog functionality "mountall" needs to --run particular necessary arrays (those with fstab bootwait) degraded if they don't come up complete after a timeout.. Because the proper mdadm --incremental mode command 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> - - (See https://wiki.ubuntu.com/ReliableRaid "How would you decide what - device is needed?" about determining the md devices that the devices - mentioned in fstab depend on.) + (See https://wiki.ubuntu.com/ReliableRaid "mountall" functionality + related:" about determining the md devices that the devices mentioned in + fstab depend on.) ** Summary changed: - degraded non-root raids are not run on boot + degraded non-root raids don't appear on boot ** Description changed: - Systems with say /home on raid won't come up booting when raid - wasdegraded during downtime. + Systems with say /home on raid won't come up booting when raid was + degraded during downtime. - An init script like /etc/init.d/mdadm-degrade or because of the already - doing that kind of watchdog functionality "mountall" needs to --run + An init script like /etc/init.d/mdadm-degrade - or because of already + doing that kind of watchdog functionality - "mountall" needs to --run particular necessary arrays (those with fstab bootwait) degraded if they - don't come up complete after a timeout.. + don't come up complete after a timeout. Because the proper mdadm --incremental mode command 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> (See https://wiki.ubuntu.com/ReliableRaid "mountall" functionality related:" about determining the md devices that the devices mentioned in fstab depend on.) ** Also affects: mountall (Ubuntu) Importance: Undecided Status: New -- degraded non-root raids don't appear on boot https://bugs.launchpad.net/bugs/259145 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
