Hide Forgot
Description of problem: Cannot boot when the system drive is attached via USB Version-Release number of selected component (if applicable): systemd-208-9.fc20.x86_64 How reproducible: Persistent Steps to Reproduce: 1. Install Fedora on the internal drive 2. Move the drive to the USB 3 enclosure 3. Actual results: The boot process stops at A job is running for disk/by-id ... Expected results: Normal boot Additional info: UUIDs of the partitions are the same for both internal and external configurations
Well, you apparently configured your mount points/swas in /etc/fstab via /dev/disk/by-id links which will look differently when connected via ata and usb. Use /dev/disk/by-uuid/ links or suchlike to use stable partition identifiers...
Created attachment 836170 [details] fstab of the affected system
The fstab is attached. Everything is mounted via UUIDs. Systemd is awesome, but...
MODIFIED means that an update was released, so nobody would look at this bug report anymore. This should be fixed when systemd-209 is released.
So, are these three fs uuids all on the USB device? UUID=87f23460-fe0a-467b-a2a9-6df5869e6c8d UUID=6d30f509-8d2e-4b4e-8cf0-eff372d53d29 UUID=308cb8c2-344e-41eb-b774-725b0d99d283 What does "ls /usr/disk/by-uuid" show when you try to boot with this?
yes they were. cannot test further at the moment.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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.
I am seeing this bug in Fedora 22... please adjust the version to reflect that it is still a current bug. After grub the screen blanks and gives the Fedora logo. If I hit <escape> I see "[ OK ] Started Show Plymouth Boot Screen" "[ OK ] Reached target Paths." which slowly repeats itself a few times If I wait long enough I get an error message and then a shell that seems to be running in initrd context. When I look in /dev/disk/by-uuid, I notice that none of the USB partitions are listed. They don't seem to have regular /dev entries either. I have discovered a workaround: If after the "[ OK ] Reached target Paths." I unplug and replug the USB drive (this is the very drive it is supposed to be booting from!), then it immediately identifies the drive, prompts me for the password to decrypt partitions, and continues a normal and successful boot. Likewise, if I wait for the initrd shell and look in /dev and /dev/disk/by-uuid, the entries for the USB disk magically pop-up when the device is replugged.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.