dmcrypt + update to kernel 2.6.20-16 fails
Bug #117979 reported by
Jan
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: linux-image-
I am using Feisty and have my home partition encrypted with dmcrypt+LUKS. When booting the system and I lock-in in GNOME, the partition is automatically decrypted and mounted with the same password as the lock-in password. Recently a mandatory update from 2.6.20-15 to 2.6.20-16 took place. Since this upgrade the transparent decryption of the home partition fails. I don't know exactly what goes wrong but it works when starting Ubuntu with 2.6.20-15 which is still installed.
To post a comment you must log in.
I can confirm this bug. Updating from 2.6.20-15 to 2.6.20-16 breaks luks/dmcrypt. I my test setup I used a partition that gets decrypted while booting ("Starting early crypto disks"). With 2.6.20-16 the kernel does not recognize the partition and drops with errors into single user mode.
If I remember correctly when installing the crypto stuff a new personal initrd. img-2.6. 20-15-generic was created for supporting the crypto stuff, probably this step is missing when updating the kernel. This should definitely be done automatically.