Hi folks, I think that this bug is a regression due to the fix for #784070, which was fairly recently pushed to both unstable and *stable*. We have at least one client server that got bitten by this and failed to boot.
I suspect the incremental assembly, which breaks booting from degraded arrays, was sufficient to start arrays on block devices that take a bit longer to show up than usual. With that now disabled, if the disks haven't showed up by the time mdadm runs in local-top, you're screwed. Adding "rootdelay=15" to the kernel command-line probably fixes this (can't test as we can't just reboot this production server at will) but this isn't a nice fix. It seems like #714155 is also somehow related, but hasn't seen any activity since July 2013. HTH, Chris -- Chris Boot bo...@debian.org GPG: 8467 53CB 1921 3142 C56D C918 F5C8 3C05 D9CE EEEE
