Bug#555676: crypto boot broke due to gnome-vfs=>devicekit-disks which removed dmsetup=>cryptsetup?
I also had the problem of not being able to boot with crypto
disks using the stock kernel, which started recently.
Finally I realized the initramfs cryptsetup scripts were
missing. I remembered gnome-vfs (or something) had
preferentially installed devicekit-disks. devicekit-disks
suggests cryptsetup, but cryptsetup requires dmsetup, which
conflicts with devicekit-disks, so cryptsetup was removed.
Then when the initrd image updated, it no longer booted.
Luckily update-initramfs did not update my custom kernel or
it would have been very inconvenient.
If cryptsetup is not on your system, try installing it
again, and running update-initramfs for the kernels that
I guess I will file a bug report on... cryptsetup? It
should depend on either dmsetup or devicekit-disks? I'll
see what they think.
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org