You are not logged in.
Hello there,
I've noticed that one of my LVM2 Volume Group is not being activated during boot procedure - what's weird is the fact that it does not happen every boot but rather just randomly, sometimes it boots just fine.
What I see in a journalctl:
Apr 24 19:33:10 cytron2 systemd[1]: Job dev-disk-by\x2duuid-ea4ae576\x2db519\x2d4744\x2d88f1\x2d05081db278ec.device/start timed out.
Apr 24 19:33:10 cytron2 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-ea4ae576\x2db519\x2d4744\x2d88f1\x2d05081db278ec.device.
-- Subject: Unit dev-disk-by\x2duuid-ea4ae576\x2db519\x2d4744\x2d88f1\x2d05081db278ec.device has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dev-disk-by\x2duuid-ea4ae576\x2db519\x2d4744\x2d88f1\x2d05081db278ec.device has failed.
--
-- The result is timeout.
Apr 24 19:33:10 cytron2 systemd[1]: Dependency failed for /var.
-- Subject: Unit var.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit var.mount has failed.
--
-- The result is dependency.
After it fails to recovery shell I can see that all LV from that particular VG that was not activated have 'not available status', for instance:
--- Volume group ---
VG Name Mirroring1TB
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 4
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 931.51 GiB
PE Size 4.00 MiB
Total PE 238466
Alloc PE / Size 238466 / 931.51 GiB
Free PE / Size 0 / 0
VG UUID yGItRe-2DK3-qR01-N2eD-yNai-McgA-YRZZER
--- Logical volume ---
LV Path /dev/Mirroring1TB/lvar
LV Name lvar
VG Name Mirroring1TB
LV UUID WDWAd6-HFK6-idM6-7oc9-oOmv-XF2K-D6QLIo
LV Write Access read/write
LV Creation host, time ,
LV Status NOT available
LV Size 15.00 GiB
Current LE 3840
Segments 1
Allocation inherit
Read ahead sectors auto
After I run `vgchange -ay` and `mount -a` they appear online and I can move on with booting procedure.
My HOOKS:
HOOKS="base udev autodetect modconf block mdadm_udev filesystems keyboard lvm2 usr fsck shutdown"
System is up-to-date (lvm2 2.02.106-1) and lvm.conf has been merged to the latest one (there was important change in lvm.conf - use_lvmetad = 1).
I found similar issue at Red Hat bugzilla - but I don't know how much it's relevant in Arch Linux's configuration.
Any word of advice? Thanks in advance.
EDIT
I also tried to use lvmwait= parameter in kernel, it did not help.
Last edited by Wojo (2014-04-24 18:46:51)
Offline
Same issue as here: https://bbs.archlinux.org/viewtopic.php?pid=1404325
Downgrading to previous lvm2 fixed it for me
Last edited by Darkimmortal (2014-04-26 06:26:28)
Offline