FS#62302 - [lvm2] [testing] 2.02.184-2 broke boot, hangs after luks passphrase
Attached to Project:
Arch Linux
Opened by William Shuman (wshuman3) - Wednesday, 10 April 2019, 20:06 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 10 February 2021, 10:01 GMT
Opened by William Shuman (wshuman3) - Wednesday, 10 April 2019, 20:06 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 10 February 2021, 10:01 GMT
|
Details
Description: The 2.02.184-2 lvm2/device-mapper update broke
boot on my machine, and causes the system to hang after
entering the luks passphrase
Additional info: * package version(s) 2.02.184-2 * config and/or log files etc. lsblk nvme0n1 disk ├─nvme0n1p1 part /boot └─nvme0n1p2 part └─P17-1933 crypt ├─vol0-lv_swap lvm [SWAP] └─vol0-lv_root lvm / mkinitcpio.conf HOOKS HOOKS="base systemd keyboard autodetect modconf block sd-vconsole sd-encrypt sd-lvm2 fsck filesystems" I'm using systemd-boot. * link to upstream bug report, if any Steps to reproduce: update to 2.02.184-2 lvm2/device-mapper reboot machine and it hangs after asking for luks passphrase. |
This task depends upon
Closed by Christian Hesse (eworm)
Wednesday, 10 February 2021, 10:01 GMT
Reason for closing: Fixed
Additional comments about closing: lvm2 2.02.184-4
Wednesday, 10 February 2021, 10:01 GMT
Reason for closing: Fixed
Additional comments about closing: lvm2 2.02.184-4
If you downgrade to lvm 2.02.184-1 then extract the changed unit files one at a time regenerate the initrd and retest can you determine which one is causing the issue?
It should not be lvm2-activation-generator as that should not produce any units unless use_lvmetad=0 has been set in lvm.conf
diff 1/lvm2-lvmetad.socket 2/lvm2-lvmetad.socket
4,5d3
< DefaultDependencies=no
< Conflicts=shutdown.target
Edit: on a positive note the -2 package with the lvmetad.socket from -1 file fixes my hangs at shutdown
```
Apr 11 08:06:22 able systemd[1]: sysinit.target: Job systemd-tmpfiles-setup.service/start deleted to break ordering cycle starting with sysinit.target/start
Apr 11 08:06:22 able systemd[1]: sysinit.target: Found ordering cycle on systemd-machine-id-commit.service/start
Apr 11 08:06:22 able systemd[1]: sysinit.target: Found dependency on local-fs.target/start
Apr 11 08:06:22 able systemd[1]: sysinit.target: Found dependency on tmp.mount/start
Apr 11 08:06:22 able systemd[1]: sysinit.target: Found dependency on local-fs-pre.target/start
Apr 11 08:06:22 able systemd[1]: sysinit.target: Found dependency on lvm2-monitor.service/start
Apr 11 08:06:22 able systemd[1]: sysinit.target: Found dependency on lvm2-lvmetad.socket/start
Apr 11 08:06:22 able systemd[1]: sysinit.target: Found dependency on sysinit.target/start
```
(a lot more ordering cycles like this, ~8 total I think)
Downgrading lvm2 or overriding `lvm2-lvmetad.socket` for `DefaultDependencies=no` fixes this for me.
P. S.: shouldn't Severity be a tad bit higher? This stuff breaks boot, after all.
Edit:
attached patch to reenable 0a726a7e268b31856615491809af73bda5d4d6f9 and to apply fix 03d6cfdd99fb1c2fd85721ab6faebbb1b6658873