Bug 521416

Summary:	dracut doesn't boot LVM root with root=UUID=....
Product:	[Fedora] Fedora	Reporter:	Michael Young <m.a.young>
Component:	dracut	Assignee:	Harald Hoyer <harald>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	harald, kevin, pebolle
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-09-15 14:07:40 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 Michael Young 2009-09-05 16:08:55 UTC

With kernel-2.6.31-0.203.rc8.git2.fc12.x86_64 (dracut-001-2.fc12) my boot fails with an error about not finding the root partition (it does boot with kernel-2.6.31-0.180.rc7.git4.fc12.x86_64 (dracut-0.9-2.fc12) which is the last version I know worked) and has a boot line option of the form root=UUID= . If I replace this with an option like root=/dev/VolGroup00/drive then it does boot. I booted with the rdshell option when the boot failed and the /dev/disk/by-uuid directory only had entries relating to physical partitions (like sda1), so I think dracut is failing to populate this directory with entries from the LVM partition. The logging indicated that LVM was started correctly.

Comment 1 Kevin Fenzi 2009-09-05 21:43:01 UTC

I am seeing this same thing here too. 

2.6.31-0.199.rc8.git2.fc12.x86_64 also failed this same way. 

2.6.31-0.190.rc8.fc12.x86_64 worked fine. 

I have lvm and encrypted root. It asks my passphrase and unlocks the encrypted root, then it says it can't find the root partition and says "sleeping forever"

I'll go try the idea of changing the root= line.

Comment 2 Kevin Fenzi 2009-09-05 22:04:14 UTC

Yep. Passing root=/dev/mapper/VolGroup00-LogVol00 got it booted. 

Happy to provide further info or debugging.

Comment 3 Harald Hoyer 2009-09-07 09:12:57 UTC

please provide the output of:

# lsinitrd <working initrd> | grep dracut
# lsinitrd <not working initrd> | grep dracut

Comment 4 Kevin Fenzi 2009-09-07 17:20:05 UTC

I can attach both those if you like, but the diff is pretty short: 

1,2c1,2
< -rw-r--r--   1 root     root         2205 Aug 14 09:59 lib/dracut-lib.sh
< -rw-r--r--   1 root     root           18 Aug 28 17:05 dracut-0.9-6.fc12
---
> -rw-r--r--   1 root     root         2460 Sep  2 07:54 lib/dracut-lib.sh
> -rw-r--r--   1 root     root           18 Sep  5 18:59 dracut-001-2.fc12

Comment 5 Harald Hoyer 2009-09-07 17:28:31 UTC

ok, >= dracut-001-3 should fix the problem

Download the packages:
http://koji.fedoraproject.org/koji/buildinfo?buildID=130930

Install and rebuild the initrd like with mkinitrd:

# dracut -f /boot/initrd-generic-<kernel version>.img <kernel version>

and boot from it.

Comment 6 Kevin Fenzi 2009-09-07 18:21:00 UTC

I can confirm that version fixes my boot issue here... came up fine (although still with text mode plymouth, but thats another issue). 

Thanks Harald!

Comment 7 Michael Young 2009-09-07 21:17:48 UTC

Yes, an initrd built by dracut-001-3 works for me as well.