** Description changed: 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 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 "mountall" functionality related:" about determining the md devices that the devices mentioned in fstab depend on.) + + + --- + + The possibility that large server RAIDs may take minutes until they come + up, but regular ones are quick, can be handled nicely: + + + "NOTICE: /dev/mdX didn't get up within the first 10 seconds. + + We continue to wait up to a total of xxx seconds complying to the ATA + spec before attempting to run the array degraded. + (You can lower this timeout by setting the rootdelay= parameter.) + + <counter> seconds to go. + + Press escape to stop waiting and to enter a rescue shell.
-- degraded NON-root raids never --run 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
