Bug 744679

Summary:	newly installed kernel (made wrong line in grub? and) bring user into recovery mode.
Product:	[Fedora] Fedora	Reporter:	Fidtiriadi H. <fid3adi>
Component:	grub2	Assignee:	Peter Jones <pjones>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	dennis, mads, pjones
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-11 11:07:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Fidtiriadi H. 2011-10-10 07:17:32 UTC

Description of problem:
- Kernel update (3.1.0-0.rc9.git0.0.fc16) generate one new line in grub to select during boot that started with "fedora" whereas all the other lines is "Linux, with linux ....."
- selecting that line will brings to recovery mode. have to boot into old kernel and do sudo grub2-mkconfig -o /boot/grub2/grub.cfg

Version-Release number of selected component (if applicable):
1.99-7.fc16

How reproducible:
not sure

Steps to Reproduce:
1.Do update (or maybe even possible when install new kernel??)
2.restart
3.select newly created line of option in grub during boot up
  
Actual results:
user going into recovery mode

Expected results:
Boot up into normal desktop

Additional info:

Comment 1 Mads Kiilerich 2011-10-24 15:50:28 UTC

Can you attach the bad grub.cfg?

Comment 2 Fidtiriadi H. 2011-11-11 02:10:02 UTC

Sorry for the (very) late reply, and sorry, unable to attach it, ext HDD where i install all of the distro is broken. 

Now i have no choice but to end my distro hopping and take the risk "breaking the company rules by installing debian sid in my workstation for my daily use".

However,even if my ext HDD is not broken, since the problem is fixed by doing sudo grub2-mkconfig -o /boot/grub2/grub.cfg, isn't that will generate the new grub.cfg thus the bad grub.cfg is replaced?

Comment 3 Mads Kiilerich 2011-11-11 11:07:51 UTC

Yes, grub2-mkconfig can be used to create a new working config.

Without the bad config file there is nothing we can do. Nobody else has reported problems like this.