Short summary ... ... the UUID and other "cryptic error messages" are consequences of the raid1 devices not being assembled. Thus, the corresponding UUID:s are never created and the result is fail in later stages.
An example: scripts/local-top/cryptroot , line 272 if /sbin/cryptsetup isLuks $cryptsource > /dev/null 2>&1; then This fails since isLuks returns faluse, since the $cryptsource is the md1 array that never was assebmled and does not exist at all and it then fallbacks to default cryptsetup asking for passphrase that is guaranteed to fail. Another example: cryptsetup: evms_activate is not available This was the first error text I got which was pretty cryptic (no pun intended!) error message of UUID device not existing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659899 Title: Degraded boot fails when using encrypted raid1 with lvm -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
