Re: after systemd upgrade, cryptdisks won't start except with systemctl start cryptdisks.service but that doesn't work if boot goes to failsafe

["Kevin P. Fleming" <lists.systemd-devel@xxxxxxxxxxxxx>]

On Mon, Oct 28, 2024, at 12:58, Marc MERLIN wrote:
> From there, I finally realized that there is a seperate
> systemd-cryptsetup package that somehow
> was missing from my system after the upgrade. No idea why :-/

This was an intentional change on the part of the Debian systemd package maintainers, and has caused problems for other users too. I believe it is listed in the release notes of the package which presumably would have been displayed during the upgrade process, but of course many (most?) users don't read those thoroughly.

The TL;DR is that if you are using LUKS with systemd on Debian, ensure you have the systemd-cryptsetup package installed manually (not just automatically as a dependency). I don't know how this is supposed to work for people upgrading from Bullseye or Bookworm though.