After upgrading to sys-apps/systemd-240, my system reboots into emergency mode with my lvm volumes unavailable. I have three volumes in my volume group, swap, root and home. Even though root is correctly mounted in emergency mode, none of the volumes are listed at /dev/mapper. In emergency mode, manually activating the volumes produces the message that all three volumes have been activated, but no volumes are listed at /dev/mapper and none can be mounted. I believe it's related to the following systemd open issue report; https://github.com/systemd/systemd/issues/11255 Downgrading to sys-apps/systemd-239-r2 allows my system to boot correctly.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f61adf54ca7bf3a1da5cd68d58e54f86017099c7 commit f61adf54ca7bf3a1da5cd68d58e54f86017099c7 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2018-12-28 16:37:48 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2018-12-28 16:37:48 +0000 sys-apps/systemd: backport patches Closes: https://bugs.gentoo.org/673852 Package-Manager: Portage-2.3.52_p18, Repoman-2.3.12_p30 Signed-off-by: Mike Gilbert <floppym@gentoo.org> sys-apps/systemd/Manifest | 1 + sys-apps/systemd/{systemd-240.ebuild => systemd-240-r1.ebuild} | 3 ++- 2 files changed, 3 insertions(+), 1 deletion(-)
Thanks! Following up, emerging sys-apps/systemd-240-r1 does indeed work correctly on my system.
