https://bugzilla.novell.com/show_bug.cgi?id=862076 https://bugzilla.novell.com/show_bug.cgi?id=862076#c0 Summary: use_lvmetad = 1 in lvm.conf triggers systemd to get into emergency target on boot Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: thomas.blume@suse.com ReportedBy: thomas.blume@suse.com QAContact: qa-bugs@suse.de CC: systemd-maintainers@suse.de Found By: Development Services Priority: 1000 Blocker: --- lvm2-2.02.98-0.28.5.1.x86_64 introduced the following change in lvm.conf: - set use_lvmetad = 1 as default of lvm.conf(bnc#854413) This creates a failure on activating non-root lvm mounts. In my test system I'm using lvm devices for /home and /var: [ ***] (1 of 2) A start job is running for dev-nonroot-var.device [** ] (2 of 2) A start job is running for dev-mapper-nonroot\x2dhome.device systemd tries for a while to mount them, then times out and starts the emergency target: Job dev-nonroot-var.device/start finished, result=timeout [ TIME ] Timed out waiting for device dev-nonroot-var.device. Job var.mount/start finished, result=dependency [DEPEND] Dependency failed for /var. Job local-fs.target/start finished, result=dependency [DEPEND] Dependency failed for Local File Systems. Triggering OnFailure= dependencies of local-fs.target. Trying to enqueue job emergency.target/start/replace Installed new job emergency.target/start as 125 Installed new job emergency.service/start as 126 But the emergency target doesn't provide a shell either, it seems to loop somewhere. The reason why the start jobs fail, is apparently that lvmetad is not runnig. I've tried to enable it (it was disabled) via: systemctl enable lvm2-lvmetad.service but it didn't have any effect on the behaviour. As a workaround, one can mount system root via, e.g. the rescue system and set: use_lvmetad = 0 in lvm.conf. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.