This is a somewhat old LP bug, but for completeness it worth mentioning
here that recently some patches were merged on initramfs-tools and
cryptsetup, that allow a good experience booting with LUKS-encrypted
rootfs on top of a degraded RAID1 array; for details, please check:
https://bugs.launchpad.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: debian-installer (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/659899
Tit
Reproduced in a Vmware virtual machine running Zentyal 3.3 (Ubuntu 12.04
LTS based) tried with two vmdisks in raid1 also, 3 partition as physical
volumes for raid, one as /boot and two others as physical volumes for
encryption used as swap and /. Grub installed on both disks, and
confirmed positive
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 $cry
Similar problem hit me when I installed Ubuntu Server 10.10 and wanted
to confirm that both disks were capable of booting alone (in order to
simulate a disk failure "2 years from now" (since previous installations
always had problems with the MBR only being written to /dev/sda))
I do not use LVM o
