Bug#945208: "No such file or directory" when attempting to decrypt LUKS during init

Issue has been resolved. During init, systemd-cryptsetup uses libcryptsetup to perform the actual unlocking of the LUKS partition. libcryptsetup itself requires a few kernel modules to work, or else it fails with -ENOENT, which, through systemd's use of error no -> error message, turns into a gen

Bug#945208: "No such file or directory" when attempting to decrypt LUKS during init

On Thu, 21 Nov 2019 12:38:26 +0100 Michael Biebl wrote: > Am 21.11.19 um 12:22 schrieb Amit Agnani: > > Upstream seems to have a policy to only track bugs against the two most > > recent revisions of systemd, which are 243 and 242 at the moment of writing. > > See: https

Bug#945208: "No such file or directory" when attempting to decrypt LUKS during init

10:57:24 +0100 Michael Biebl wrote: > Am 21.11.19 um 09:35 schrieb Amit Agnani: > > Package: systemd > > Version: 241-7~deb10u2 > > > > When attempting to decrypt LUKS-encrypted volumes under systemd (through > > dracut) during boot/init, I get the following fa

Bug#945208: "No such file or directory" when attempting to decrypt LUKS during init

Package: systemd Version: 241-7~deb10u2 When attempting to decrypt LUKS-encrypted volumes under systemd (through dracut) during boot/init, I get the following failure message:     systemd-cryptsetup[410]: Failed to activate with key file '/run/systemd/cryptsetup/keydev-deviceluks/device-disk.key'