After upgrading to dracut-034-18.git20131018.fc20 my system does not boot. Regenerating the initramfs with the previous dracut build (dracut-034-8.git20131008.fc20) fixes the problem. My root filesystem is on an LVM logical volume. A diff between the working and the broken initramfs shows this suspicious hunk: diff -Nurp good/etc/cmdline.d/90lvm.conf bad/etc/cmdline.d/90lvm.conf --- good/etc/cmdline.d/90lvm.conf 2013-10-19 09:56:37.000000000 +0200 +++ bad/etc/cmdline.d/90lvm.conf 2013-10-19 10:03:03.000000000 +0200 @@ -1 +1 @@ - rd.lvm.lv=nonraidvg/swap rd.lvm.lv=nonraidvg/F-root + rd.lvm.lv=nonraidvg/swap nonraidvg/F-root This line seems to be generated by the looped touched by the fix for bug 1013767, so I suspect that this is what caused the regression. (Seems that "$line" now contains all the values from get_host_lvs at once, instead of being assigned one after another in the loop.) As a workaround I can add "rd.lvm.lv=nonraidvg/F-root" to the kernel command line and boot successfully. Version-Release number of selected component (if applicable): dracut-034-18.git20131018.fc20
I'm unable to reproduce this in qemu/kvm: 1. Boot Fedora-Live-Desktop-x86_64-20-Beta-TC5.iso, and install using guided partitioning default (conventional LVM); and reboot. 2. yum update dracut 3. dracut -f 4. reboot. System does reboot.
dracut-034-19.git20131021.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/dracut-034-19.git20131021.fc20
Package dracut-034-19.git20131021.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dracut-034-19.git20131021.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-19603/dracut-034-19.git20131021.fc20 then log in and leave karma (feedback).
dracut-034-19.git20131021.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.