Bug 969984 - dracut host only fails to mount default lvm
Summary: dracut host only fails to mount default lvm
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: dracut-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-03 09:10 UTC by Simon Putt
Modified: 2013-06-18 06:20 UTC (History)
4 users (show)

Fixed In Version: dracut-029-1.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-18 06:20:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
working log (with nohostonly installed) (321.56 KB, application/x-gzip)
2013-06-03 16:20 UTC, Simon Putt
no flags Details
broken dracut log with default settings (hostonly) (244.46 KB, application/x-gzip)
2013-06-03 16:23 UTC, Simon Putt
no flags Details

Description Simon Putt 2013-06-03 09:10:45 UTC
Description of problem:

With the newest dracut (dracut-027-81.git20130531.fc19)

it fails to make the initrd to load the lvm components and on creation says something about dm-0 and dm-1 not being found. boot does not complete as missing root.


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


How reproducible:


Steps to Reproduce:
1.install new dracut
2.make new initrd with dracut -f
3.no boot

Actual results:

failed boot

Expected results:

to boot as normal

Additional info:

Comment 1 Harald Hoyer 2013-06-03 09:19:30 UTC
Can you provide either the output of:

# dracut -f --debug

or the sosreport.txt, when dracut falls back to the rescue shell?

Comment 2 Simon Putt 2013-06-03 15:32:45 UTC
how do i pipe the debug output to a file?

Comment 3 Harald Hoyer 2013-06-03 15:59:46 UTC
(In reply to Simon Putt from comment #2)
> how do i pipe the debug output to a file?

# dracut -f --debug 2>debug.log

Comment 4 Simon Putt 2013-06-03 16:20:33 UTC
Created attachment 756402 [details]
working log (with nohostonly installed)

Comment 5 Simon Putt 2013-06-03 16:23:47 UTC
Created attachment 756403 [details]
broken dracut log with default settings (hostonly)

Comment 6 Harald Hoyer 2013-06-12 11:05:54 UTC
commit 437a56dc6bdda0f985eb86e3e51f01d787da15b8
commit 66ed711ccf6698da4bbc3420c15bfedd186b6f87

Comment 7 Harald Hoyer 2013-06-12 13:05:12 UTC
It would really be helpful, if you could provide /run/initramfs/sosreport.txt from the unsuccessful boot.

- determine your /boot partition device

$ findmnt -nr -o SOURCE /boot

- reboot with the hostonly initramfs
- get dropped to a shell
- mount /boot
  Replace "/dev/sda1" with your /boot partition device
 
# mkdir /boot
# mount /dev/sda1 /boot

- copy /run/initramfs/sosreport.txt to /boot

# cp /run/initramfs/sosreport.txt /boot
# umount /boot

Then reboot to your working kernel+initramfs.

# reboot

Now, you can attach /boot/sosreport.txt to this bug report.

Thanks for your collaboration!

Comment 8 Fedora Update System 2013-06-12 13:57:24 UTC
dracut-028-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/dracut-028-1.fc19

Comment 9 Fedora Update System 2013-06-13 18:08:09 UTC
Package dracut-028-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dracut-028-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-10777/dracut-028-1.fc19
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2013-06-14 13:59:52 UTC
dracut-029-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/dracut-029-1.fc19

Comment 11 Fedora Update System 2013-06-18 06:20:07 UTC
dracut-029-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.