Hi,

I updated to suse 12.3.
With this came the new systemd. Yeehah.
No it does not mount one of my logical volumes any more.
The symptom is that I end up in the emergency shell.
journalctl -b yields:

Code:
Sep 02 21:16:18 vmhost.ts-home.lan systemd[1]: Starting LSB: Start LVM2...
Sep 02 21:16:18 vmhost.ts-home.lan boot.lvm[1151]: Waiting for udev to settle...
Sep 02 21:16:18 vmhost.ts-home.lan boot.lvm[1151]: Scanning for LVM volume groups...
Sep 02 21:16:18 vmhost.ts-home.lan kernel: device-mapper: uevent: version 1.0.3
Sep 02 21:16:18 vmhost.ts-home.lan kernel: device-mapper: ioctl: 4.23.0-ioctl (2012-07-25) initialised: 
Sep 02 21:16:18 vmhost.ts-home.lan boot.lvm[1151]: Reading all physical volumes.  This may take a while...
Sep 02 21:16:18 vmhost.ts-home.lan boot.lvm[1151]: Found volume group "bacshare" using metadata type lvm2
Sep 02 21:16:18 vmhost.ts-home.lan boot.lvm[1151]: Found volume group "vmdata" using metadata type lvm2
Sep 02 21:16:18 vmhost.ts-home.lan boot.lvm[1151]: Found volume group "vmguests" using metadata type lvm2
Sep 02 21:16:18 vmhost.ts-home.lan boot.lvm[1151]: Activating LVM volume groups...
Sep 02 21:16:18 vmhost.ts-home.lan kernel: bio: create slab <bio-1> at 1
Sep 02 21:16:18 vmhost.ts-home.lan boot.lvm[1151]: 1 logical volume(s) in volume group "bacshare" now active
Sep 02 21:16:18 vmhost.ts-home.lan boot.lvm[1151]: 9 logical volume(s) in volume group "vmdata" now active
Sep 02 21:16:18 vmhost.ts-home.lan systemd[1]: Found device /dev/bacshare/stephan.
Sep 02 21:16:18 vmhost.ts-home.lan systemd[1]: Found device /dev/vmdata/vmdatastore.
Sep 02 21:17:15 vmhost.ts-home.lan systemd[1]: Job dev-vmguests-syslogs.device/start timed out.
Sep 02 21:17:15 vmhost.ts-home.lan systemd[1]: Timed out waiting for device dev-vmguests-syslogs.device.
Sep 02 21:17:15 vmhost.ts-home.lan systemd[1]: Dependency failed for /vmadm/syslogs.
Sep 02 21:17:15 vmhost.ts-home.lan systemd[1]: Dependency failed for Local File Systems.
Sep 02 21:17:15 vmhost.ts-home.lan systemd[1]: Dependency failed for Remote File Systems (Pre).
Sep 02 21:17:15 vmhost.ts-home.lan systemd[1]: Job remote-fs-pre.target/start failed with result 'dependency'.
Sep 02 21:17:15 vmhost.ts-home.lan systemd[1]: Job local-fs.target/start failed with result 'dependency'.
Sep 02 21:17:15 vmhost.ts-home.lan systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Sep 02 21:17:15 vmhost.ts-home.lan systemd[1]: Job vmadm-syslogs.mount/start failed with result 'dependency'.
Sep 02 21:17:15 vmhost.ts-home.lan systemd[1]: Job dev-vmguests-syslogs.device/start failed with result 'timeout'.
Please note there are 3 volume groups found (bacshare,vmdata,vmguests) but only in 2 it found devices. In truth the third group (vmguests) contains about 5 logical volumes.
For some reason /dev/vmguests/syslogs times out.

Funnily, when I enter the console this mount is mounted. If I comment this mount out of fstab everything starts up.
In total I mount 3 lv's (one of each group) in fstab, the others work nicely.
I just cant figure out why this happens.

In some posts it is said that this can happen if a device is checked or decrypted too long. So I increased the timeout to 120s. Did not help.

fstab entries look all the same. it did not help to extend the timeout of the mount. To me the mount process of systemd is a bit obscure.

Has anybody run into a similar problem?

Best regards,
Tobi