Hi, On Wed, 02 Jul 2025 at 01:02:02 +0300, Konstantin Khomoutov wrote: > I've hit a regression after upgrading my Debian 12 laptop to Trixie - > in short, cryptsetup hangs at *early* boot stage when it apparently trying to > create a device mapper node for a LUKS1 device it successfully opened. > LUKS2 devices behave just fine. > […] > 2. Then the boot process hangs for a while and then fails with the message > telling it failed to bring up the /boot partition and hence the > local-fs.target failed to be brought up, as well - bailing into the > emergency mode (which was unusable as I had root account with the locked > password, but this is another story). > […] > The most weird thing is that if I comment out a line for that /boot > partition in /etc/fstab so that it's not attempted to be brought up at boot > and then manually open the device using cryptsetup after the system as > booted - it gets opened just fine.
AFAICT it doesn't hang at early boot (initramfs) stage, but rather after the system has been handed over to systemd. Do you have systemd-cryptsetup installed? (See the NEWS entry for systemd=256-2, which I guess should be in the release notes too.) > 1. https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html I need to review and update this page GRUB can open LUKS2 devices these days. And systemd-cryptsetup should be mentioned there too indeed. -- Guilhem.
signature.asc
Description: PGP signature
