https://bugzilla.novell.com/show_bug.cgi?id=725622 https://bugzilla.novell.com/show_bug.cgi?id=725622#c0 Summary: systemd breaks startup (crypted home?) Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: koenig@linux.de QAContact: qa@suse.de Found By: --- Blocker: --- last "zypper dup" of my 12.1-beta notebook installed systemd-sysvinit-37-2.1.x86_64 and sysvinit-2.88+-65.1.x86_64 (before it was running fine with old style sysvinit-2.88-37.47.1). now the system startup hangs, maybe due to my crypted home ?! /home passphrase gets requested, but then after timeout I end in "emergency mode" and /home is not mounted. exiting "emergency mode" asks again for /home passphrase, and I end in "emergency mode" again -- looks like ground hog day :-((( this is the console output: unused Waiting for udev to settle... Scanning for LVM volume groups... Reading all physical volumes. This may take a while... Found volume group "system" using metadata type lvm2 Activating LVM volume groups... 7 logical volume(s) in volume group "system" now active done [ 1791.563301] systemd[1]: Job tmpfs.device/start timed out. [ 1791.598992] systemd[1]: Job remote-fs.target/start failed with result 'dependency'. [ 1791.634034] systemd[1]: Job local-fs.target/start failed with result 'dependency'. [ 1791.669280] systemd[1]: Triggering OnFailure= dependencies of local-fs.target. [ 1791.704659] systemd[1]: Job var-run-nscd.mount/start failed with result 'dependency'. [ 1791.740064] systemd[1]: Job fsck@tmpfs.service/start failed with result 'dependency'. [ 1791.775067] systemd[1]: Job tmpfs.device/start failed with result 'timeout'. Welcome to emergency mode. Use "systemctl default" or ^D to activate default mode. Give root password for login: [ 1792.062344] dhcpcd[5680]: wlan0: exiting Can't deactivate volume group "system" with 5 open logical volume(s) skipped Not shutting down MD RAID - reboot/halt scripts do this. missing [ 1792.323473] systemd[1]: md.service: control process exited, code=exited status=3 [ 1792.364160] systemd[1]: Unit md.service entered failed state. I'm totally new to systemd -- now to I debug/test/workaround/... (or just get rid of systemd and use sysvinit again) ?!? -- 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.