After a system update, I could no longer get my rootfs, which is an LVM logical volume to mount, systemd would just spend hours waiting for it to become available. Tried different kernel versions (gentoo-kernel), dracut versions and lvm2 versions, but in the end it appears to be systemd. Everything is working again with up-to-date versions apart from systemd which I have to pin to 252.6 for now. It's hard to get interesting information when the system fails to boot properly, so guidance welcome if more information is needed. Reproducible: Always
It's a Dracut bug per https://github.com/dracutdevs/dracut/issues/2211#issuecomment-1437592587 and https://github.com/dracutdevs/dracut/issues/2211#issuecomment-1438154826 ... but we can apply a patch to systemd temporarily, see https://github.com/systemd/systemd/issues/26488#issuecomment-1438196977. The patch is https://github.com/systemd/systemd/pull/26494.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bfebeda18b81d781f9dcf8d12c1adddefff6b9a4 commit bfebeda18b81d781f9dcf8d12c1adddefff6b9a4 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2023-02-26 19:26:29 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2023-02-26 19:27:02 +0000 sys-apps/systemd: work around dracut bug with LVM Bug: https://bugs.gentoo.org/896364 Signed-off-by: Mike Gilbert <floppym@gentoo.org> .../files/systemd-253-initrd-generators.patch | 34 ++++++++++++++++++++++ .../{systemd-253.ebuild => systemd-253-r1.ebuild} | 1 + 2 files changed, 35 insertions(+)
Affected systemd versions are no longer in the tree so I think we can close this. Please re-open if it is still relevant.
