Bug 1089427

Summary:	System boots to rescue mode
Product:	[Fedora] Fedora	Reporter:	Jesús Abelardo Saldívar Aguilar <jasaldivara>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	20	CC:	jasaldivara, johannbg, lnykryn, msekleta, plautrba, s, systemd-maint, vpavlin, zbyszek
Target Milestone:	---	Flags:	jasaldivara: needinfo-
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-17 11:43:45 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 Jesús Abelardo Saldívar Aguilar 2014-04-18 22:53:40 UTC

Description of problem:

Whenever I turn on my computer, system boots to rescue mode intead of graphical session/gdm.

Once in rescue mode, I can press Ctrl-D and the system resumes to start normally to GDM.

This problem started after a software update wich included Kernel 3.13.9-200.fc20.x86_64

Version-Release number of selected component (if applicable):

Fedora 20

How reproducible:

Turn on muy computer, boot to Fedora (Kernel 3.13.9) on GRUB

Steps to Reproduce:
1.
2.
3.

Actual results:

System boots to rescue shell/mode

Expected results:

System should boots to graphicla session/GDM

Additional info:

This problem started after a software update wich included Kernel 3.13.9-200.fc20.x86_64

My system is a Lenovo IdeaPad U310 with core i5 processor

This is the output of uname -a:
Linux ultrabook-lalo 3.13.9-200.fc20.x86_64 #1 SMP Fri Apr 4 12:13:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Comment 1 Lennart Poettering 2014-05-24 11:03:16 UTC

Does journalctl -b show anything interesting when you run it in the rescue shell?

Comment 2 Jesús Abelardo Saldívar Aguilar 2014-05-24 20:32:47 UTC

I don't know what data from journalctl -b is interesting for this. One thing I found that could be related was that rngd.service always failed to start.

Fortunately, this problem stoped happening after a system update wich included Kernel 3.14 among other packages.

Comment 3 Lennart Poettering 2014-06-17 11:43:45 UTC

OK, closing if the problem vanished.