Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#38729 - [lvm2] Systemd timeout waiting for LV when booting into single user mode
Attached to Project:
Arch Linux
Opened by David Rosenstrauch (darose) - Thursday, 30 January 2014, 15:40 GMT
Last edited by Thomas Bächler (brain0) - Wednesday, 26 February 2014, 22:37 GMT
Opened by David Rosenstrauch (darose) - Thursday, 30 January 2014, 15:40 GMT
Last edited by Thomas Bächler (brain0) - Wednesday, 26 February 2014, 22:37 GMT
|
DetailsWhen I boot into single user mode (i.e., kernel /boot/vmlinuz-linux root=/dev/sda6 ro single) the LVM volumes in my fstab are not found (systemd times out while trying to access them - "Timed out waiting for device dev-vg1-lvabs.device"), fail to mount, and cause the boot process to fail.
Apparently making the following changes to the systemd configuration fixes the issue: sudo mkdir /etc/systemd/system/sysinit.target.wants cd /etc/systemd/system/sysinit.target.wants/ sudo ln -s /usr/lib/systemd/system/lvmetad.socket This causes the lvmeta daemon to be active at system init, and so makes the lvm volumes available on a single user boot. Perhaps these changes should be part of the LVM package? Booting into single user mode seems to me to be a common enough use case, and I would think it shouldn't fail just because you have LVM volumes. |
This task depends upon
Closed by Thomas Bächler (brain0)
Wednesday, 26 February 2014, 22:37 GMT
Reason for closing: Fixed
Additional comments about closing: lvm2 2.02.105-2
Wednesday, 26 February 2014, 22:37 GMT
Reason for closing: Fixed
Additional comments about closing: lvm2 2.02.105-2