[Bug 862086] New: No keyboard in emergency boot mode
https://bugzilla.novell.com/show_bug.cgi?id=862086 https://bugzilla.novell.com/show_bug.cgi?id=862086#c0 Summary: No keyboard in emergency boot mode Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: rschweikert@suse.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=577068) --> (http://bugzilla.novell.com/attachment.cgi?id=577068) Attempt to enter emergency boot mode When the system enters emergency boot mode a message is displayed with instruction on how to proceed. However, no keyboard input is accepted by the system. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c1
Thomas Wagner
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c
Xiyuan Liu
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c2
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c3
--- Comment #3 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c4
--- Comment #4 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c5
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c6
--- Comment #6 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c7
Hagen Fuchs changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
CC| |code@hfuchs.net
InfoProvider|rschweikert@suse.com |
--- Comment #7 from Hagen Fuchs
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.
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c8
Thomas Blume
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c9
Hagen Fuchs changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|code@hfuchs.net |
--- Comment #9 from Hagen Fuchs
2014-05-09 07:35:48 UTC ---
Can you try with plymouth.enable=0?
I did (having reverted the system to pristine state with the exception of the garbled fstab) and it changed nothing. Actually, I was thrown into the "Welcome to emergency mode"-loop a little earlier (quite a few services didn't seem to have been started), but it still wasn't usable. Thanks! -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c10
--- Comment #10 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c11
--- Comment #11 from Hagen Fuchs 2014-05-09 09:39:01 UTC ---
Thank you, yes, that did the trick. Installing 'systemd-sysvinit' and
'systemd'
from the repository you suggested fixed the problem. This upgraded
systemd from version 208 to 210.
Just for the record: the problem appeared on many different machines,
specifically x86_64 workstations and vmware guests.
Will systemd 210 be included in the regular 13.1 update channels?
Thanks 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.
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c12
--- Comment #12 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c13
--- Comment #13 from Hagen Fuchs 2014-05-09 10:05:48 UTC ---
(In reply to comment #12)
I tried to get the gist of #854884 and came back with the impression that
a) it isn't entirely clear what caused the issue;
b) the systemd version under consideration was also 208; and
c) the original poster seemed satisfied with the progress, even motioning to
close the report.
Hence, I'd vote for closing /both/ bug reports at once and including v210 into
the 13.1 update pipeline.
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c14
--- Comment #14 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=862086
https://bugzilla.novell.com/show_bug.cgi?id=862086#c15
--- Comment #15 from Hagen Fuchs 2014-07-14 11:06:24 UTC ---
(In reply to comment #14)
I concur, if solely for the fact that the fix over there
seems to be the same as here, namely
Upgrade to systemd-210
Thus, we could close 5 bugs at once (all duplicates of #832220).
--
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.
participants (1)
-
bugzilla_noreply@novell.com