Bug 485274

Summary:	mount: could not find filesystem '/dev/root' - again
Product:	[Fedora] Fedora	Reporter:	keith <keith.allcock>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	rawhide	CC:	anaconda-maint-list, hdegoede
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-02-12 18:25:57 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 keith 2009-02-12 18:06:15 UTC

Description of problem:
Booted the new release of Fedora 11 Alpha, used the install option from the desktop. 
I have two disks, installation was on sda, sdb is my data store and home partition. Other than the config of sdb device config was default (logical volume for /)
All installation went well.
On reboot, I can see plymouth start, then got the following error after the logical volume successful message:
mount: could not find filesystem '/dev/root'

In searching found a similar previous bug for F9 of # 431778 (https://bugzilla.redhat.com/show_bug.cgi?id=431778)

Unlike F9 Alpha, I had no additonal messages

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

How reproducible:
On first install so far

Steps to Reproduce:
1. Install alpha
2. Reboot
3.
  
Actual results:
failed to boot on first usage

Expected results:
Boot into Fedora 11

Additional info:

Comment 1 Hans de Goede 2009-02-12 18:25:57 UTC

Known issue, to workaround this you need to specify your root on the kernelcmdline (grub) not as UUID= or LABEL=, but directly, see the F11 alpha release notes.

Once you've booted this way do:
yum update mkinitrd

Followed by
yum update kernel

And booting by UUID should work again.

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