Bug 478878

Summary:	kernel fails to boot (Asus 900A with ext2 root relatime, no separate /boot)
Product:	[Fedora] Fedora	Reporter:	Matthew Woehlke <mwoehlke.floss>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	10	CC:	james, kernel-maint, quintela
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-04-21 21:28:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthew Woehlke 2009-01-05 20:02:02 UTC

Upon booting, the kernel fails to start with the message "mount: error mounting /dev/root on /sysroot as ext2: Invalid argument".

I don't know exactly at what kernel version this began appearing but it happens with 2.6.27.9-159 and at least one previous kernel. As a result, I am currently stuck on 2.6.27.5-117 (which does not have the problem).

Reproducible always.

My /etc/fstab looks like this (UUID values elided):
UUID=<blah> /         ext2   relatime        1 1
UUID=<blah> /home     ext2   relatime        1 2
tmpfs       /dev/shm  tmpfs  defaults        0 0
devpts      /dev/pts  devpts gid-5,mode=620  0 0
sysfs       /sys      sysfs  defaults        0 0
proc        /proc     proc   defaults        0 0
tmpfs       /tmp      tmpfs  size=30%        0 0

Comment 1 Matthew Woehlke 2009-01-05 21:58:44 UTC

Hmm, apparently this is a duplicate of bug 430280. (If someone can confirm, please close this accordingly.)

How is it that three-year-old bugs are reopening?

Comment 2 Matthew Woehlke 2009-01-07 01:45:38 UTC

...or it might be a duplicate of bug 475495; can't tell without further testing (which I can't do until I get some time to play with the machine in question)

Comment 3 Matthew Woehlke 2009-01-28 19:31:53 UTC

I just did the following:

sed -i 's/norelatime/defaults/' /etc/fstab # actually used vim, but you get the idea
yum update kernel\*
mv /etc/fstab{.bak,} # i.e. undid the above mount option change
reboot

...and I was able to boot the new kernel. Hopefully that narrows down where the problem is.

Comment 4 Matthew Woehlke 2009-04-21 21:28:04 UTC

seems to be working with the latest mkinitrd