Created attachment 1012260 [details] output of journalctl -a Description of problem: Sometimes happens that the system on usb (either netinst and live) doesn't boot and falls to dracut (I've seen it only on UEFI boot so far). It doesn't find usb device (usb is missing in /dev/). Messages before dracut emergency shell is run: dracut-initqueue[433]: Warning: Could not boot. systemd[1]: Received SIGRTMIN+20 from PID 434 (plymouthd). dracut-initqueue[433]: Warning: /dev/disk/by-uuid/D7D2-A15E does not exist dracut-initqueue[433]: Warning: /dev/mapper/live-rw does not exist systemd[1]: Starting Dracut Emergency Shell... Version-Release number of selected component (if applicable): kernel-4.0.0-0.rc5.git4.1.fc22.x86_64 Fedora Beta RC1 - happened with Server DVD and Workstation Live How reproducible: It doesn't happen everytime, but it happened three times in a row now and happens to me on one machine in about 25% of cases. Steps to Reproduce: 1. put image to usb (I used livecd-iso-to-disk last time) 2. try to boot (Happens to me with UEFI) 3. Actual results: usb isn't found and boot falls to dracut emergency shell Expected results: normal boot Additional info: I propose this as beta blocker. It violates the alpha criterion: "All release-blocking images must boot in their supported configurations."
Created attachment 1012261 [details] generated sos report
I've been doing quite a lot of USB boots to test the FW RAID fixes and haven't seen this once. Is this always on the same system or with the same USB stick?
If nobody else have seen it than it is probably problem of that particular pc. So I'm canceling blocker bug propose. New information. It happened to me even with non uefi boot of usb.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.