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

[Marc F. Clemente]

I don't think this is an isolated bug.  It is happening to me too.

On my system, I notice that /dev/disk/by-uuid does not contain the dm-0 
partition.  On another computer, /dev/disk/by-uuid has dm-0 and dm-1 in 
it.  So maybe when initramfs tries to mount it by UUID, it can't find it 
and it fails.

When I boot, it drops me to the initramfs shell.  To continue the boot 
process, I have to type the following commands at the initramfs prompt:

modprobe dm_mod
modprobe ext3
cryptsetup luksOpen /dev/sda3 root
^D

Some more info...

mc-laptop:~# ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Sep  1 17:50 
2c6f24cc-6e8c-4550-96a7-11fc6627f7b2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Sep  1 17:50 E4D82E3DD82E0E7C -> ../../sda1
lrwxrwxrwx 1 root root 10 Sep  1 17:50 
ebd230c0-b0ef-48a5-aae5-0c20f02bb436 -> ../../sda3


mc-laptop:~# cat /etc/crypttab | grep root
root            /dev/disk/by-uuid/ebd230c0-b0ef-48a5-aae5-0c20f02bb436 
none            luks

mc-laptop:~# grep ext3 /etc/fstab
UUID=2c6f24cc-6e8c-4550-96a7-11fc6627f7b2       /boot           ext3 
         errors=remount-ro       0       1
UUID=231cbe61-54a1-45bf-8c5a-b9456ea11e16       /               ext3 
         errors=remount-ro       0       1