When upgrading to systemd-236 i no longer get any luks password prompt for my setup. I get eventually dropped to shell with services reliant on those luks volumes timing out and failing. Downgrade to systemd-235-r1 immediately resolves the problem. I used a binpkg that links to older cryptsetup, and will test with newer cryptsetup version in a few minutes. I have one volume in /etc/crypttab opened via password, which contains keys for all other luks volumes. Reproducible: Always Steps to Reproduce: 1. Install systemd-236 2. reboot 3. system does not boot up completely 4. downgrade to previous systemd version via recovery mode 5. system works
I have a similar setup that's working fine, but I've only tested with sys-fs/cryptsetup-2.0.0. I'm interested to learn what version of cryptsetup you used that failed and if using 2.0 solves the problem for you.
I'll dig through logs, as i am not sure what was updated first, systemd or cryptsetup. I'll do some rebuilds later on today in all combinations.
Same here, systemd-236, cryptsetup-2.0.0 If noone hit that wall before us, maybe our configs are different? I'm running LUKS1 on LVM volume. Maybe it is in unit order? Already tried rebuilding cryptsetup, AND systemd in that order. Also tried upgrading to LUKS2. Still not working.
What do the logs say? I'm looking through systemd's issue tracker, do any of these look like they could be your issue? https://github.com/systemd/systemd/pull/7688 https://github.com/systemd/systemd/pull/7689 https://github.com/systemd/systemd/issues/7677
https://github.com/systemd/systemd/pull/7688 Out of memory on systemd-cryptsetup-generator.
Edit: After applying patch from https://github.com/systemd/systemd/commit/f189bd8eacd32b38d9566a9e052b164c7ab25cd3.patch (pull 7688), my system asked for password and booted normally :)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c6bf76a0c3f92c9f9d450357e7ee08098cc7988d commit c6bf76a0c3f92c9f9d450357e7ee08098cc7988d Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2017-12-18 22:41:25 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2017-12-19 02:01:31 +0000 sys-apps/systemd: backport crypsetup-generator fix Closes: https://bugs.gentoo.org/641380 Package-Manager: Portage-2.3.19_p1, Repoman-2.3.6_p35 ...generator-Don-t-mistake-NULL-input-as-OOM.patch | 49 ++++++++++++++++++++++ .../{systemd-236.ebuild => systemd-236-r1.ebuild} | 1 + 2 files changed, 50 insertions(+)
*** Bug 641724 has been marked as a duplicate of this bug. ***
