[Bug 1256730] Re: /usr/share/initramfs-toos/hooks/cryptroot does not honour the CRYPTSETUP variable

[Timo Jyrinki]

I upgraded from 14.04 LTS to 16.04 LTS, and _after_ installing the next
new kernel (4.4.0-22) the new kernel's initrd.img did not have
cryptsetup anymore. 4.4.0-21 still had so I have continued to boot to it
for a week now.

I tried a lot of things before finding this bug, but it seems comment #4
finally adds a megabyte or so to the 22's initrd. I still don't get a
password prompt when booting to 22, and the 22 initrd.gz is still 400kB
smaller than 21's.

For possible interest, I'm attaching two diffs:
- Diff from 21 to 22+forcecryptsetup - note that I've removed btrfs package meanwhile since I was getting "Scanning for btrfs filesystems" messages on boot which I thought might be a problem
- Diff from 22 to 22+forcecryptsetup

The diffs are from ls -1R outputs of the initrd contents, with manual
sedding get cleaner diffs, but including (don't let it confuse) all
version numbers were changed to say "4.4.0-21".

Notably while the forcecryptsetup included all the needed kernel modules
and the cryptsetup tool, I'm still missing conf/conf.d/cryptroot on 22
which I guess is the remaining blocker for working. Maybe text.so too?

-- 
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/1256730

Title:
  /usr/share/initramfs-toos/hooks/cryptroot does not honour the
  CRYPTSETUP variable

Status in cryptsetup package in Ubuntu:
  Triaged

Bug description:
  The patch https://launchpad.net/ubuntu/+source/cryptsetup/2:1.4.3-4ubuntu4
  checks via

  +if [ -n "$CRYPTSETUP" ] && [ "$CRYPTSETUP" != "n" ]; then
  +    setup="yes"
  +fi

  whether there is CRYPTSETUP=y has been set.

  The description of the patch says that CRYPTSETUP=y in
  /etc/initramfs-tools/initramfs.conf would be enough.
  But it isn't.

  update-initramfs calls mkinitramfs. CRYPTSETUP is still set to y.
  Then /usr/share/initramfs-tools/hooks/cryptroot is called via
  run_scripts/call_scripts. The variable is still set before the
  cryptroot script is entered, but is unset in the script.

  The problem is that update-initramfs does not put /sbin/cryptsetup
  into initramfs. My root filesystem is unencrypted but I mount an
  encrypted partition during boot, so I need cryptsetup in initramfs.

  Ubuntu 13.10

  Ralf

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