Basically as the title says. System doesn't boot because the the root volume doesn't come up. If I drop into a rescue shell I can activate it manually, but for some reason dracut just won't do it. dracut 050 or 051 are working fine. Can't debug this further right now, just wanted to report the issue so that devs are aware that 053 is probably not ready for stable. Reproducible: Always
For the record, my LVM-root, that contains a LUKS2 container, gets activated by initrd produced by dracut-053 just fine. So this might be an issue that does not affect all LVM2 users.
(In reply to Victor Mataré from comment #0) > Basically as the title says. System doesn't boot because the the root volume > doesn't come up. If I drop into a rescue shell I can activate it manually, > but for some reason dracut just won't do it. > > dracut 050 or 051 are working fine. > > Can't debug this further right now, just wanted to report the issue so that > devs are aware that 053 is probably not ready for stable. > > Reproducible: Always Same problem here.
I also cannot reproduce, so we need your help to debug this problem. Please append "rd.debug" to the kernel cmdline. When you are dropped to an emergency shell, the file /run/initramfs/rdsosreport.txt is created. Copy this file to some persistent storage and attach to this bug report.
Same issue for me, fixed with the following patch https://github.com/dracutdevs/dracut/commit/ba4bcf5f4f11ad624c647ddf4f566997186135e7 See more info at the bug from RH bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1945596
Oups, wrong link for the RH related bug. The good one is here: https://bugzilla.redhat.com/show_bug.cgi?id=1946074 I know that the patch is related to a NetworkManager service, and seems not related with the LVM issue, but it strangely fix my setup (SD -> LUKS -> lvm-root). Hope it will fix the issue for you too.
As you said, that patch has nothing to do with LVM, and would only affect network booting with systemd. I would guess your issue is sporadic and this did not actually resolve the root cause. If anyone is experiencing difficulty with LVM and dracut-053, I would suggest giving dracut-055 a try.
I was able to reproduce this bug by just including "network" module into initramfs. And patch from comment #4 indeed fixes it.
(In reply to Alexander Tsoy from comment #7) > I was able to reproduce this bug by just including "network" module into > initramfs. And patch from comment #4 indeed fixes it. It made it upstream in 054: https://github.com/dracutdevs/dracut/commit/ba4bcf5f4f11ad624c647ddf4f566997186135e7.
I suppose a dependency loop might cause the boot process to fail without mounting the root filesystem.
Ok, I think the common point is the network plugin indeed. I use it for unlocking my root LUKS volume remotely. As Mike said, LVM volumes are not activated because of this dependency issue with the network plugin after the LUKS volume unlocking.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1e5c3786ee37ebca4e26bc2df7ce32541a46146a commit 1e5c3786ee37ebca4e26bc2df7ce32541a46146a Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2021-06-17 15:01:51 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2021-06-17 15:01:51 +0000 sys-kernel/dracut: backport fix for Network Manager Closes: https://bugs.gentoo.org/775671 Signed-off-by: Mike Gilbert <floppym@gentoo.org> .../{dracut-053.ebuild => dracut-053-r1.ebuild} | 1 + sys-kernel/dracut/files/053-network-manager.patch | 24 ++++++++++++++++++++++ 2 files changed, 25 insertions(+)
