Red Hat Bugzilla – Bug 827651
dracut fails to load lvm root
Last modified: 2013-07-04 13:05:15 EDT
Created attachment 588605 [details]
Description of problem:
I've upgraded an up to date F16 installation on my laptop using the installation image. Unfortunately, I'm dropped into a dracut shell when the lvm root fails to load. Activating the pertinent volumes allows the system to boot without further issues.
I've ran grub2-mkconfig from the new installation to rule out grub configuration issues, the result appears to be correct.
Version-Release number of selected component (if applicable):
Name : dracut
Version : 018
Release : 40.git20120522.fc17
Name : grub2
Epoch : 1
Version : 2.0
Release : 0.25.beta4.fc17
Name : lvm2
Version : 2.02.95
Release : 6.fc17
Boot system with configuration as described in attachments.
User is required to manually activate logical volumes from dracut shell.
System boots without user intervention.
I don't suspect it's related, but this was a PXE installation that took several attempts due to a flaky broadcom NIC. Anaconda resumed the upgrade seamlessly to complete the process.
Created attachment 588606 [details]
device tree as described with `dmsetup ls --tree`
Created attachment 588607 [details]
attached filesystems as described in /etc/fstab
Created attachment 588608 [details]
boot configuration from /etc/grub2/grub.cfg
Created attachment 588609 [details]
output of `lvm lvdisplay`
Created attachment 588610 [details]
output of `lvm pvdisplay`
Created attachment 588611 [details]
output of `lvm vgdisplay`
Created attachment 588613 [details]
Created attachment 588614 [details]
please boot with "rd.debug" appended to the kernel command line and "rhgb" removed
when you are dropped to the dracut shell save /run/initramfs/init.log and the output of dmesg to a USB stick and attach the files here.
you might also want to try to boot without the "rd.lvm.lv=" parameter
suggested line (yes one line, bugzilla might split it) in /etc/grub2/grub.cfg:
linux /vmlinuz-3.3.7-1.fc17.x86_64 root=UUID=ed9a5ba0-5e95-4a1f-87a2-56c929752826 ro rd.md=0 rd.dm=0 KEYTABLE=us rd.lvm.vg=vg_mercury rd.luks=0 LANG=en_US.UTF-8 quiet
Created attachment 589189 [details]
init.log with boot line as before
Created attachment 589190 [details]
init.log with boot parameters as suggested
The suggested line does not resolve the issue. I've attached /run/initramfs/init.log for both the 'factory' appendages and the suggested boot line, hope it's useful. Thanks for the attention,
are the attached files with the blkid and lvm calls from the dracut shell or from the running system? If they are not from the dracut shell, can you please do the same from the dracut shell?
# ls -l /dev/mapper
Oh, and please post from the booted system the output of:
# rpm -qa 'dracut*'
# cat /etc/dracut.conf.d/*
the same problem here
preupgrade from Fedora 16 to 17.
on boot i'm dropped into dracut shell with info the root (lvm) was not found.
on manual mounting lvm system boots.
I instructions on mounting lvm root from dracut I got from :
now on Fedora 17:
* kernel 3.3.7-1.fc16.x86_64 boots fine.
* kernel 3.3.7-1.fc17.x86_64 drops me into dracut shell.
try to regenerate the dracut initramfs:
# dracut -f '' 3.3.7-1.fc17.x86_64
This solved my problem. Now 3.3.7-1.fc17.x86_64 boots as fine as 3.3.7-1.fc16.x86_64 did :)
Thanks a lot :)
I guess now the only remaining issue is why it doesn't happen out-of-box with fc17 kernels.
(In reply to comment #18)
> This solved my problem. Now 3.3.7-1.fc17.x86_64 boots as fine as
> 3.3.7-1.fc16.x86_64 did :)
> Thanks a lot :)
> I guess now the only remaining issue is why it doesn't happen out-of-box
> with fc17 kernels.
That is a very good question, which I also would like to know! Maybe a recent lvm2 update fixed some issues.
Created attachment 590331 [details]
blkid; lvm *display from dracut shell
(In reply to comment #17)
> try to regenerate the dracut initramfs:
> # dracut -f '' 3.3.7-1.fc17.x86_64
I haven't been able to pull this off, unfortunately. I see there's dracut 018-55.git20120606.fc16 is in -testing, I'll give it a spin.
I didn't end up installing the -testing dracut for F16 on my F17 box, naturally...
However, this issue was resolved in subsequent updates to dracut and/or the kernel. Sorry that I can't provide more information than that, and that I left this open with out comment for so long.