Package: cryptsetup-initramfs Version: 2:2.0.3-2 Severity: critical --- Please enter the report below this line. --- Hi,
I have a full disk-encryption set up with LUKS. After upgrading from 2.0.3-1 to 2.0.3-2 my last (and current) kernel is unbootable. Fortunately, the previous one has still a valid initramfs, so I can boot my system (many thanks for that backup system). Here are the log (copied manually): ===== Please unlock disk sda3_crypt: [ 14.107558] device-mapper: table: 253:0: crypt: Error allocating crypto tfm device-mapper: reload ioctl on failed: No such file or directory Failed to setup dm-crypt key mapping for device /dev/sda3. Check that kernel supports aes-xts-plain64 cipher (check syslog for more info). cryptsetup: ERROR: sda3_crypt: cryptsetup failed, bad password or options? Please unlock disk sda3_crypt: ===== Obviously, I cannot check the syslog for more info. But for now I don't want to run any update until I am sure I can boot the system. However, after setting MODULES from dep to most in /etc/initramfs-tools/initramfs.conf and re-generating the initramfs, the system can boot. Maybe the refactoring lost this feature, but I'd like to see it back, since it allows for faster initramfs generation, and kind of faster boot also. I'm available for some more tests if needed. Adrien --- System information. --- Architecture: Kernel: Linux 4.16.0-1-amd64 Debian Release: buster/sid 500 unstable ftp.fr.debian.org 500 testing download.jitsi.org 1 experimental ftp.fr.debian.org --- Package information. --- Depends (Version) | Installed =======================================-+-=============== cryptsetup-run (>= 2:2.0.3-2) | 2:2.0.3-2 busybox | 1:1.27.2-2 OR busybox-static | initramfs-tools (>= 0.129) | 0.130 OR linux-initramfs-tool | Recommends (Version) | Installed ============================-+-=========== console-setup | 1.184 kbd | 2.0.4-3 Package's Suggests field is empty. --- Output from package bug script ---
