[pkg-cryptsetup-devel] Bug#767832: Initramfs provided in initramfs-tools_0.118_all won’t automount luks partitions at boot

[Simon McVittie]

On Thu, 27 Nov 2014 at 10:02:34 +0000, Simon McVittie wrote:
> On Sun, 02 Nov 2014 at 22:21:16 +0100, zer0 divide wrote:
> > My system does not start automatically after I enter the password for
> > unlocking the root partition. I have to unlock manually /usr (from initramfs
> > ), and then do "CTRL + D".

Steps to reproduce what I think is the same bug:

Install jessie on a virtual machine in this arrangement:

    /dev/vda1: ext4 /boot, 200M
    /dev/vda2: LUKS encrypted (volume named vda2_crypt), 1.5G
        containing ext4 / (root filesystem), 1.5G
    /dev/vda3: LUKS encrypted (volume named vda3_crypt), 1.5G
        containing ext4 /usr, 1.5G

Reboot from the installer into the real system. The root filesystem is
decrypted and mounted by the initramfs; the /usr filesystem is decrypted
and mounted after systemd starts, with a visibly different passphrase
prompt.

Upgrade to current jessie and reboot. The same things happen.

Upgrade initramfs-tools (only) to the version from sid, 0.118, and reboot.
The initramfs unlocks and fscks vda2_crypt, then after a delay:

    Gave up waiting for /usr device.  Common problems:
    ...
    ALERT!  /dev/mapper/vda3_crypt does not exist. Dropping to a shell!
    ...
    (initramfs)

To recover: type at the initramfs prompt

    cryptsetup luksOpen /dev/vda3 vda3_crypt
    exit

and the system boots.

    S