Bug 1115591

Summary:	Booting with init=/bin/sh does not work
Product:	Red Hat Enterprise Linux 7	Reporter:	Denys Vlasenko <dvlasenk>
Component:	plymouth	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED DUPLICATE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.0	CC:	harald, initscripts-maint-list, jstephen, lnykryn, mkovarik
Target Milestone:	rc	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-29 14:51:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Denys Vlasenko 2014-07-02 16:56:06 UTC

Description of problem:
Booting with init=/bin/sh does not work

Steps to Reproduce:
1. Press 'e' in grub boot menu, append "init=/bin/sh" to kernel command line
2. Boot the system

Actual results:
After initramfs stage finishes, "sh-4.2#" prompt does appear, but it is unusable: tty is in wrong mode: <enter> results in the prompt re-printed on the same line, not next line.
about half of the entered chars are "eaten": typing "ls<enter>" results in "sh: l: command not found".

Expected results:
Usable shell

Comment 2 Lukáš Nykrýn 2014-07-07 08:18:37 UTC

This has nothing to do with initscripts.

Comment 5 Harald Hoyer 2014-08-14 12:06:36 UTC

(In reply to Denys Vlasenko from comment #0)
> Description of problem:
> Booting with init=/bin/sh does not work
> 
> Steps to Reproduce:
> 1. Press 'e' in grub boot menu, append "init=/bin/sh" to kernel command line
> 2. Boot the system
> 
> Actual results:
> After initramfs stage finishes, "sh-4.2#" prompt does appear, but it is
> unusable: tty is in wrong mode: <enter> results in the prompt re-printed on
> the same line, not next line.
> about half of the entered chars are "eaten": typing "ls<enter>" results in
> "sh: l: command not found".
> 
> Expected results:
> Usable shell

Does it help to disable plymouth?

Add "rd.plymouth=0 plymouth.enable=0" to the kernel cmdline.

Comment 6 Harald Hoyer 2014-08-14 12:14:02 UTC

Anyway, you better use runlevel 1 or "s" for a rescue shell.

Add "1" or "s" to the kernel cmdline.

Comment 7 Harald Hoyer 2014-10-29 12:28:50 UTC

even better add "emergency" to the kernel command line

Comment 8 Michal Kovarik 2014-10-29 12:38:01 UTC

'emergency' will ask you for root password. It cannot be used for root password change.

init=/bin/sh is working if rhgb is removed.

Comment 9 Harald Hoyer 2014-10-29 13:05:43 UTC

reassigning to plymouth, which had code to detect "init=/bin/sh", IIRC

Comment 10 Ray Strode [halfline] 2014-10-29 14:51:50 UTC


*** This bug has been marked as a duplicate of bug 1098332 ***