Hide Forgot
Description of problem: When booting my kernel.org (3.9.8 or so) only the root-lv is activated. it appears that vgchange -ay is not executed Version-Release number of selected component (if applicable): Fedora current How reproducible: Boot See dracut shell happen do `lvm vgchange -ay` `exit` and see boot continue (but is stuck on encrypted swap partition job...) Expected results: No lvm issue Additional info:
What info do you need to fix this bug?
(In reply to udo from comment #1) > What info do you need to fix this bug? Boot with "rd.debug" on the kernel command line. Do your lvm vgchange -ay, boot. # journalctl -ab --no-pager -o short-monotonic > /tmp/sosreport.txt and attach /tmp/sosreport.txt
Created attachment 770479 [details] sosreport.
your kernel command line is missing "rd.lvm.vg=my_vg" or "rd.lvm.lv=my_vg/usrlv" , because you seem to have a split /usr- Please add "rd.lvm.vg=my_vg" to your kernel command line.
Thanks for your quick reply. rd.lvm.vg=my_vg did indeed help! Where is this documented for me and others to read as change for Fedora 18? Please give us a link so we can be informed. THANKS!
https://fedoraproject.org/wiki/Upgrading_from_EOL_Fedora_using_yum#Fedora_16_-.3E_Fedora_17 ... If you have /usr on LVM, MD raid or DM raid, make sure the kernel command line has either all settings like "rd.lvm.lv=..." to ensure the /usr device is accessible in dracut or just remove all restrictions like "rd.lvm...", "rd.md...", "rd.dm...". Either way, you should probably use anaconda to update, if you are experiencing problems with a separate /usr. ... The problem here is, that you had root=/dev/mapper/... which turned into "rd.lvm.lv=", but without the /usr LV.
In Fedora 19, this will be solved with the host-only initramfs, because dracut does parses your /etc/fstab and knows what to activate and wait for.
Thanks for explaining! For a perhaps related issue: https://bugzilla.redhat.com/show_bug.cgi?id=979695 does that also require extra kernel commandline parameters in Fedora 18?