This bug is easy to reproduce without possibility for the user to make an error resulting in issues:
- acquire the lastest netinstall image as of 2025-03-14. - partition for lvm - create lvm - create 2 lvs - set those lv for encyption - encrypt both with password - set 1 for /, set the other for /home etc. On first boot after install the passphrase for / will be asked. Decryupting /home later on will fail since there is no interaction to ask the passphrase for it. Since I don't want to use passphrases appart from /, I create a key for /home and add it to luks. Edit /etc/crypttab to use the key instead of passphrase. update initrd and reboot. Second boot will still fail, the key was never used to decrypt. Manually running cryptdisks_start on the home_crypt works and it can be mounted so that startup can be completed. Only after installing the package systemd-cryptsetup the boot process can conclude without user intervention. So my conclusion is that this bug isn't due to a user error, it is an installer error since at least when the users partition with encrypted devices systemd-cryptsetup should be installed. The easy fix for this bug: ALWAYS install systemd-cryptsetup package.
