Your message dated Sun, 1 Jun 2025 18:01:02 +0200 with message-id <56ac62e2-87c3-4fdd-9487-8b47a4819...@plouf.fr.eu.org> and subject line Re: Bug#1092968: debian-installer: LUKS encrypted installation does not use /etc/crypttab to decrypt other drives has caused the Debian Bug report #1092968, regarding debian-installer: LUKS encrypted installation does not use /etc/crypttab to decrypt other drives to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1092968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: debian-installer Severity: important X-Debbugs-Cc: veltf...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I did a full-disk luks encrypted installation using trixie-DI-alpha1 _Trixie_ - Official Alpha amd64 NETINST with firmware 20241230-11:26. * What exactly did you do (or not do) that was effective (or ineffective)? I edited my /etc/crypttab to include other encrypted drives and partitions. The drives had keyfiles that had been added with cryptsetup using "luksAddKey UUID=WhaEver321 /someplace/keyfile-somename" as I normally do. However when rebooting I was dropped to an emergency shell because the partitions had not been decrypted. Adding the partitions to the keyfiles and double-checking the crypttab did not help. I was forced to mark the encrypted mounts in my fstab as "noauto" in order to boot to the GUI. I checked /usr/lib/systemd/system-generators/ and found there was no unit called systemd-cryptsetup-generator as there was in other Debian installations with encrypted partitions. I installed the package 'systemd-cryptsetup' & a couple of others that probably were not necessary (cryptmount, pmount) and checked again and found there was now a unit: /usr/lib/systemd/system-generators/systemd-cryptsetup-generator I removed the 'noauto' options from my fstab and was able to boot normally with my drives properly mounted. * What was the outcome of this action? I was able to boot normally. * What outcome did you expect instead? Any installed system with luks encryption support should be able to read and decrypt entries in /etc/crypttab with properly processed keyfiles without installing additional packages. *** End of the template - remove these template lines *** -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.6-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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
--- End Message ---
--- Begin Message ---Fixed in partman-crypto 132: * Install systemd-cryptsetup alongside cryptsetup-initramfs. While the latter is sufficient if one picks guided partitioning with an encrypted LVM layout, other use cases might require the former, originally bundled together within systemd (Closes: #1092977).
--- End Message ---
