[Bug 1513415] Re: cryptsetup blocks between mountroot and bottom in initramfs

[Encolpe Degoute]

When I break the init during mountroot and I try to decrypt the root it
hangs too:

(initramfs) /sbin/cryptsetup open /dev/sdb3 crypt_root
Enter password for /dev/sdb3:
No key available with this passphrase.
Enter password for /dev/sdb3:

 ^---- Valid password is entered then it hangs.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1513415

Title:
  cryptsetup blocks between mountroot and bottom in initramfs

Status in cryptsetup package in Ubuntu:
  New

Bug description:
  Hello,

  Ubuntu 15.10
  cryptsetup 2:1.6.6-5ubuntu2

  First, I post a question here without any success:
  http://askubuntu.com/questions/693950/impossible-to-boot-on-encrypted-root-partition-after-15-10-upgrade

  With the help of TJ- on IRC, I got more information but no solution.
  This configuration was working since the 14.04 installation.

  The boot sequence is stopped during the initramfs process whitin the
  /usr/share/initramfs-tools/scripts/local-top/cryptroot script, between
  the instant when the good password is validated and the initramfs'
  bottom sequence. At that moment, I can only reboot.

  I can mount and work on my partitions from a 15.10 live dvd.

  My crypt setup:

  /dev/mapper/crypt_root is active and is in use. 
    type:    LUKS1
    cipher:  aes-xts-plain64
    keysize: 512 bits
    device:  /dev/sdb3
    offset:  4096 sectors
    size:    491304960 sectors
    mode:    read/write
  /dev/mapper/crypt_home is active and is in use.
    type:    LUKS1
    cipher:  aes-cbc-essiv:sha256
    keysize: 256 bits
    device:  /dev/sda7
    offset:  4096 sectors
    size:    1130182656 sectors
    mode:    read/write

  
  My /etc/initramfs-tools/modules was empty before the 15.10 upgrade, now it contains:

  cryptoloop
  aes
  sha256
  aes-x86_64
  sha512-ssse3
  dm-mod
  dm-crypt

  My partition should be mounted like this:

  /dev/mapper/crypt_root on / type ext4 (rw,relatime,data=ordered)
  /dev/mapper/crypt_home on /home type ext4 (rw,relatime,data=ordered)
  /dev/sdb2 on /boot type ext4 (rw,relatime,stripe=4,data=ordered)
  /dev/sda2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
  udev on /dev type devtmpfs (rw,nosuid,relatime,size=4039992k,nr_inodes=1009998,mode=755)
  devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
  sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=810576k,mode=755)

  Best regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1513415/+subscriptions