Okay. Things are a bit confusing in the cloud. The new Grub 2 is not being used, and the cloud loader reads /boot/grub/menu.lst entries directly (you can't use update-grub to regenerate menu.lst anymore, as the new way is the grub.cfg file, which however is not used in the cloud).
So all this confused me a bit and I also wasn't running update-initramfs to reflect my changes in /etc/initramfs-tools/conf.d/mdadm. The root of my issue was that I was creating a RAID5 array (without the --force option), which automatically puts the array into "degraded, rebuilding" state, which then fails to reboot (in the cloud) due to the BOOT_DEGRADED defaulting to "false" (in /etc/initramfs- tools/conf.d/mdadm). Please close this bug, but hopefully this helps others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1060417 Title: mdadm BOOT_DEGRADED setting is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1060417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
