*** This bug is a duplicate of bug 1302195 ***
https://bugs.launchpad.net/bugs/1302195
** This bug has been marked a duplicate of bug 1302195
System with degraded array boots regardless of BOOT_DEGRADED flag
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060417
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
** Attachment added: AWS Ubuntu Server fail
https://bugs.launchpad.net/bugs/1060417/+attachment/3366147/+files/Screen%20Shot%202012-10-02%20at%2010.17.09%20PM.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, I just realized that the path /conf/conf.d/mdadm is probably a path
inside the initial RAM fs image, so it may be correct.
But I had no luck setting the bootdegraded=true parameter via GRUB kopt=
(plus running update-grub in a chroot) either.
Also there is no way to modify the kernel command
