Created attachment 846736 [details] rdsosreport.txt generated by the failed boot. Description of problem: Trying to boot an early 2013 retina mac book pro model (15 inch) with fedora 20 from an usb stick fails (last beta version as well as the current release). Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a bootable usb stick. 2. Connect it to the retina mbp. 3. Push 'alt' key while switching on. 4. Select to boot from usb. Actual results: The following is printed to the console: [Firmware Bug]: ioapic 2 has no mapping iommu, interrupt remapping will be disabled pci 0000:00:01.0: ASPM: Could not configure common clock i915 0000:00:02.0: Invalid ROM contents sd 6:0:0:0: [sdb] No Caching mode page found sd 6:0:0:0: [sdb] Assuming drive cache: write through sd 6:0:0:0: [sdb] No Caching mode page found sd 6:0:0:0: [sdb] Assuming drive cache: write through sd 6:0:0:0: [sdb] No Caching mode page found sd 6:0:0:0: [sdb] Assuming drive cache: write through [Nothing happens for quite some time] [ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Paths. [ OK ] Reached target Basic System. dracut-initqueue[398]: Warning: Could not boot. dracut-initqueue[398]: Warning: /dev/disk/by-label/Fedora-Live-Desktop-x86_64-20-1 does not exist Starting Dracut Emergency Shell... Warning: /dev/disk/by-label/Fedora-Live-Desktop-x86_64-20-1 does not exist Warning: /dev/mapper/live-rw does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. Expected results: Additional info:
febootstrap is an obsolete package that was nothing to do with booting. I'm guessing this should be "dracut", but I might be wrong.
Seems like the partitions of the usb stick are not labeled correctly. How did you create the USB stick?
(In reply to Harald Hoyer from comment #2) > Seems like the partitions of the usb stick are not labeled correctly. Seems like the filesystems of the usb stick are not labeled correctly. > > How did you create the USB stick?