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
http://forums.debian.net/viewtopic.php?f=5&t=74232#p506229 (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.

** Attachment added: "cryptraid"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003309/+attachment/3922004/+files/cryptraid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1003309

Title:
  Boot fails after installing updates, error: “cryptsetup: evms_activate
  is not available"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003309/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to