I have LVM on the top cryptsetup on my Debian unstable amd64. A week ago after upgrade my initramfs changed and now I have to wait few minutes at the beginning of the boot before
cryptsetup asked for password to unlock partition.
There might be some problem with generated images as at the beginning there were just some kernels affected. After proper run of
update-initramfs -u -k all installed kernels are affected.
Wiki instructions don't help much, as
debug kernel option takes too long and nothing happen (booting just stops).
I tried to debug it with
single break=mount kernel options, but nothing found.
I see that in initramfs there is running script
/scripts/init-premount, which starts
dropbear (nothing unusual).
I have no idea what changed. Any idea, how I can debug problem? Any module missing?
-- /proc/cmdline BOOT_IMAGE=/vmlinuz-4.3.0-rc5-amd64 root=/dev/mapper/t61-root ro -- /etc/crypttab sda2_crypt UUID=c524108a-b40f-49b4-8223-23e3441a7409 none luks -- /etc/crypttab sda2_crypt UUID=c524108a-b40f-49b4-8223-23e3441a7409 none luks -- /etc/fstab # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 /dev/mapper/t61-root / ext4 relatime,errors=remount-ro 0 1 UUID=411fe373-ec79-45f7-90f2-e50be400c71d /boot ext4 defaults 0 2 tmpfs /tmp tmpfs nodev,nosuid,size=512M,mode=1777 0 0 /dev/mapper/t61-home /home ext4 defaults,relatime 0 2 /dev/mapper/t61-swap none swap sw 0 0 -- /etc/initramfs-tools/modules dm-crypt aes-x86_64 xts sha256_generic sha512_generic