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
Control: forwarded -1 https://github.com/systemd/systemd/issues/14098
Am 21.11.19 um 14:01 schrieb Amit Agnani:
> Bug has been tested with systemd 242-8~bpo10+1 yielding the same error.
>
> An upstream bug has been filed at:
> https://github.com/systemd/systemd/issues/14098
Thanks Amit!
Marking
Processing control commands:
> forwarded -1 https://github.com/systemd/systemd/issues/14098
Bug #945208 [systemd] "No such file or directory" when attempting to decrypt
LUKS during init
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/14098'.
--
945208:
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://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md
>
> But if you insist, I
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://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md
But if you insist, I can do that and link this issue.
On Thu, 21 Nov 2019
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 failure message:
I don't really have any experience with systemd-cryptsetup-generator
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
