[sles-beta] LVM startup issues...

[Joel Barbieri]

I am having issues with LVM startup on boot.  My autoyast profile creates a traditional disk layout, and automatically creates an LVM volume.  On system reboot after installation [or anytime] it cannot successfully mount the volume it created.  It instead times out waiting for the device [dev-vg00-lv_emageon].

All volumes are done by name and not by UUID or anything more exotic.

Logging in shows the device to be available from via vgs and lvs, and active, but it is not available via /dev [e.g. /dev/vg00/lv_emageon].

/dev/mapper is empty...

Running journalctl tells me...

/var/lock/lvm/V_vg00:aux: open failed: No such file or directory
Can't get lock for vg00
Failed to read Volume Group "vg00" (xkrW06-vHO2-12OW-DX...) during autoactivation.
Starting Activation of VM2 logical volumes...
Lvmetad is active, skipping direct activation during sysinit...
...
Looks like attempts to start encrypted, lvm2, remote, with all LVM "skipping direct activation"...

Followed by the timeout and fail...

Anyone have any great hints?  I may be ablet o workaround with some autoyast profile changes, or by using uuid, but possibly not.

It seems similar to prior lvm systemd startup issues that occurred in OpenSuSE.

This does not occur in SLES12SP0 with the same autoyast profile.

Bug?  Or is it more likely I'm doing something not quite supported any longer with systemd?

-Joel

Joel Barbieri
Merge Healthcare
900 Walnut Ridge Drive
Hartland, WI 53029
262-369-3118
joel.barbieri at merge.com