Comment 63 for bug 1003309

Stefan Tauner (stefanct) wrote :

i had the same problem as the_nipper (robert-wirth-gmx) #58.
i migrated a previous "root in lvm in luks" to "root in lvm in luks in raid1" (by creating new block devices incl. a degraded raid1, copying all data over and changing the configuration of crypttab, fstab etc. and updating the initramfs).

the solution mentioned in (as linked by #61) did not work for me, probably because of plymouth...? the stdin of cryptsetup was not connected so typing the password had no effect whatsoever, yey... but hey canoncial could get a fancy and completely useless boot screen, that's important!

anyway, I resorted to copying lots of the ui logic from /usr/share/initramfs-tools/scripts/local-top/cryptroot into the attached script, which has to be put in /etc/initramfs-tools/scripts/local-top/cryptraid (and made executable!).
it is tailored to open /dev/md1, change cryptsource if needed.
then run update-initramfs -k all -u

it works for me, but it is not much tested, ymmv.