Description of problem: unable to boot from USB when root is on a logical volume. Version-Release number of selected component (if applicable): dracut-029-2.fc19.x86_64 How reproducible: always Steps to Reproduce: 1. perform an install with default (LWM) partitioning scheme on a SATA disk connected to a SATA controller, legacy boot (not a UEFI) 2. connect the same disk to a USB<->SATA adapter and attempt to boot from a USB device. Actual results: dracut can't find a root device and drops into a shell. Expected results: successful boot without user interaction. Additional Information: 1. /etc/fstab: /dev/mapper/vg_000-lv_root / ext4 defaults 1 1 UUID=UUID-UUID-etc /boot ext4 defaults 1 2 /dev/mapper/vg_000-lv_home /home ext4 defaults 1 2 /dev/mapper/vg_000-lv_swap swap swap defaults 0 0 2. original installation was done in Dec 2011, then sequentially upgraded, currently Fedora 19 latest.
https://fedoraproject.org/wiki/Features/DracutHostOnly#Release_Notes This Fedora release builds an initramfs tailored especially for your computer hardware. If you change your machine or partitions or significant hardware, you might have to boot with the "Rescue" boot entry and execute "dracut --regenerate-all". If you want your initramfs to be hardware independent, install the "dracut-nohostonly" rpm package. If you don't want rescue images at all (like in virtual machines), install the "dracut-norescue" rpm package.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.