Bug#1023492: linux-signed-amd64: Cannot boot with message "cryptsetup: Waiting for encrypted source device UUID=xxxx..."
Source: linux-signed-amd64
Version: 6.0.6+2
Severity: important
Dear Maintainer,
I cannot boot my amd64 PC with linux-image-6.0.0-2-amd64, it just shows
"cryptsetup: Waiting for encrypted source device UUID=xxxx" again and again,
then falled down to busybox shell. With 6.0.0-1 works, 6.1~rc3+1~exp1 in
experimental also does not work.
$ LANG=C df -h -x tmpfs
Filesystem Size Used Avail Use% Mounted on
udev 15G 0 15G 0% /dev
/dev/mapper/tiny--vg-system 328G 224G 104G 69% /
/dev/sda2 235M 221M 1.8M 100% /boot
/dev/mapper/tiny--vg-home 559G 391G 168G 70% /home
/dev/nvme0n1p1 256M 34M 223M 14% /boot/efi
$ mount|grep mapper
/dev/mapper/tiny--vg-system on / type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)
/dev/mapper/tiny--vg-home on /home type btrfs (rw,relatime,compress=zstd:3,ssd,space_cache,subvolid=5,subvol=/)
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.0.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Reply to: