AFAICS this bug is still relevant as the check is still in place and putting CRYPTSETUP=y in /etc/initramfs-tools/initramfs.conf is still not enough.
I try to boot a btrfs on a RAID1 (dm) inside an encrypted partition. For some reason, update-initramfs is not able to determine the "canonical device of /dev/md0" which in turn probably makes it not include the cryptsetup binary. The hack mentioned in comment #4 seems to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1256730 Title: /usr/share/initramfs-toos/hooks/cryptroot does not honour the CRYPTSETUP variable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1256730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs