Description of problem: Did a fresh F15 install, then yum updated it to F16 Beta. The install was done on /dev/sdc and no raid was involved, just a straight disk on top of LVM. After the yum update, grub boots the FC16 kernel, which then fails in dracut not being able to find the root device. Will attach log files Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 526220 [details] dmsetup output
Created attachment 526222 [details] lvm lvdisplay
Created attachment 526223 [details] lvm pvdisplay
Created attachment 526224 [details] lvm vgdisplay
Created attachment 526227 [details] grub.conf
Created attachment 526228 [details] mdadm.conf
Created attachment 526229 [details] /proc/mdstat Note this was taken when system was booted into the F15 kernel
dracut-013-15.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/dracut-013-15.fc16
-1 blocker, yum upgrades are not part of the release criteria. if this is reproducible with an anaconda upgrade, I'd be +1.
Package dracut-013-15.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing dracut-013-15.fc16' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/dracut-013-15.fc16 then log in and leave karma (feedback).
I have taken a clean F15 install and upgraded to F16 + updates-testing (including dracut-013-15). I had to hard-reboot after upgrade, but system boots and looks ok. Bug fixed.
kamil: the bug is system-specific, by the looks of it, it isn't just a general bug triggered by a yum update. so your test doesn't confirm the fix.
Jens did confirm the fix in Bodhi, though: "Solves BZ#743240 which I reported earlier! Thanks! "
Discussed at 2011-10-07 blocker review meeting. In theory we need more information on the conditions needed to trigger this bug to evaluate its blocker status, but since in practice it'll likely be closed before the next blocker review, you probably don't need to bother giving us that. (it seems to be something to do with having an mdraid array present, at least, as the fix is listed as "fixed mdraid container handling").
dracut-013-15.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.