https://bugzilla.novell.com/show_bug.cgi?id=862086 https://bugzilla.novell.com/show_bug.cgi?id=862086#c7 Hagen Fuchs <code@hfuchs.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |code@hfuchs.net InfoProvider|rschweikert@suse.com | --- Comment #7 from Hagen Fuchs <code@hfuchs.net> 2014-03-13 10:54:51 UTC --- We[0] experience the same issue and have a simple, specific procedure to reproduce this behaviour (as well as a solution, see below): 1. Change the /home-entry to a bogus device[1]. 2. reboot 3. Witness the "helpless emergency prompt". This is not dependend on the usage of Plymouth, ie. removing the 'splash' keyword from GRUB's 'linux' line does not change the behaviour. It becomes evident that systemd tries to start other processes (when booting with systemd_debug flags set). Eventually the line "Stopping Emergency Mode" appears and after a while the "helpless prompt" again. This cycle continues. I have experimented quite extensively (also with the changes mentioned in the last bug comment) and have come to the conclusion that, in *our* case at least, emergency mode should be "isolated" (in systemd parlance). In other words, emergency.target should be the only target active. For the local-fs.target fail case (as described above), this can easily be achieved by setting 'OnFailureIsolate=yes'[2] in local-fs.target. The diff is simply: --- a/local-fs.target +++ b/local-fs.target @@ -15 +15 @@ OnFailure=emergency.target -OnFailureIsolate=no +OnFailureIsolate=yes The emergency shell now behaves as expected. Other unit files that specify 'OnFailure=emergency.target' all seem to have this setting. Regards, Hagen [0] Different users, different machines (physical & virtualized) at our institute. [1] Say: /dev/sdx9 /home ext4 acl,user_xattr 1 2 [2] Oddly enough, it seems the keyword has been renamed in systemd - the docs, version 210, don't seem to mention 'OnFailureIsolate' and instead have 'OnFailureJobMode=isolate' - which emphatically does *not* work. -- 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.