[pkg-cryptsetup-devel] Bug#591626: Unable to boot from encrypted Luks volume after upgrade

[Derrick Karpo]

For those of you experiencing this bug I've run into a similar
situation with udev + lvm + cryptsetup/LUKS in that any of my newly
generated initramfs images fail to boot my system as they just spin
after entering either a valid or invalid cryptsetup passphrase.  A
blank passphrase returns to the "enter passphrase" prompt.

A current workaround I'm using to boot this particular system is to
manually kill udev as follows.  Does it work for anyone else?

  o boot your linux image with the 'break=mount' option
  o once in (initramfs) check the running processes
  o kill all the udev processes
  o `exit'
  o enter your cryptsetup passphrase
  o system boots normally and udev re-starts on boot

I have two older 2.6.33 initramfs images, one that works (older), and
one that is broken which was generated with the latest
initramfs-0.98.3.  All of my newer initramfs images fail to boot
unless I manually kill udev as per above.  If you are interested, I've
attached a diff of the 2 initramfs images.  Perhaps something
obviously wrong with my configuration will be apparent to someone out
there.

Derrick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.6.33.bad.vs.good.initramfs.txt.gz
Type: application/x-gzip
Size: 17875 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20100924/c02cc588/attachment.bin>