Comment 25 for bug 778520

michael brenden (mike-brenden) wrote :

There's some race condition now that doesn't give RAID5 (and probably other types) mdadm adequate time, so it shows up with faulty/degraded arrays.

Another problem makes boot process ignore the kernel parm "bootdegraded=true"

This forces people with mdadm software RAID into a "busybox" initramfs shell, basically a blackhole of doom and downage.

Apparently the only recourse is to totally reinstall the system (again), not tell it about the existing RAID5, then go boot and do some fiddling around with udevadm delay, per https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/872220?comments=all

and then cross my fingers, give it a reboot, and hope it boots without race condition incorrectly marking RAID as failed...
and if not then re-install everything and try the next iteration of screwing around.

GOT SOME NEWS FOR YA -- THIS IS THE FSCKING *DEFINITION* OF MICROSOFT.