Solved Create UEFI bootable USB from Fedora
-
I just use Fedora Media Writer (it's built in the Fedora Workstation version) to burn all ISOs... they are UEFI bootable, that's all I use anymore, and I even use Fedora Media Writer on Windows as well.
-
@dbeato said in Create UEFI bootable USB from Fedora:
Have you tried Unebootin?
https://unetbootin.github.io/That worked, but I have already uninstalled it
-
@tim_g said in Create UEFI bootable USB from Fedora:
I just use Fedora Media Writer (it's built in the Fedora Workstation version) to burn all ISOs... they are UEFI bootable, that's all I use anymore, and I even use Fedora Media Writer on Windows as well.
I usually used that also, but I made a 1803 USB this morning and it would not show up in the UEFI section of the Dell boot menu.
-
@jaredbusch said in Create UEFI bootable USB from Fedora:
@tim_g said in Create UEFI bootable USB from Fedora:
I just use Fedora Media Writer (it's built in the Fedora Workstation version) to burn all ISOs... they are UEFI bootable, that's all I use anymore, and I even use Fedora Media Writer on Windows as well.
I usually used that also, but I made a 1803 USB this morning and it would not show up in the UEFI section of the Dell boot menu.
No idea why then. I use it to create bootable USB keys all the time, and I always have legacy BIOS disabled on all workstations and servers, leaving UEFI the only option. I haven't tried anything with 1803, though.
-
-
@stacksofplates said in Create UEFI bootable USB from Fedora:
@jaredbusch said in Create UEFI bootable USB from Fedora:
So does anyone know an easy way to do this?
Google gives me some answers that are all manual, including have to copy the data out of the ISO and onto the USB after it is properly prepared.Man what a pain. On Windows I just use Rufus.
Fedora Media Writer only makes legacy boot versions.
I use the disks application in GNOME. Choose "Restore disk image" from the menu and choose the ISO.
Ok. Did this, but the USB does not show up.
Looking back at Disks, I see why. It is UDF. UEFI requires FAT32 I do believe.
-
Compared to this one made with UNetbootin
-
@tim_g said in Create UEFI bootable USB from Fedora:
@jaredbusch said in Create UEFI bootable USB from Fedora:
@tim_g said in Create UEFI bootable USB from Fedora:
I just use Fedora Media Writer (it's built in the Fedora Workstation version) to burn all ISOs... they are UEFI bootable, that's all I use anymore, and I even use Fedora Media Writer on Windows as well.
I usually used that also, but I made a 1803 USB this morning and it would not show up in the UEFI section of the Dell boot menu.
No idea why then. I use it to create bootable USB keys all the time, and I always have legacy BIOS disabled on all workstations and servers, leaving UEFI the only option. I haven't tried anything with 1803, though.
-
@Tim_G I just used Fedora Media Writer to burn the Fedora 28 Workstatino NetInst ISO and that appears like it will work. Testing now.
-
@jaredbusch said in Create UEFI bootable USB from Fedora:
@Tim_G I just used Fedora Media Writer to burn the Fedora 28 Workstatino NetInst ISO and that appears like it will work. Testing now.
Yup, worked. Shows in the UEFI section.
-
I've always used Fedora Media Writer for my UEFI USB boot sticks.
-
@fateknollogee said in Create UEFI bootable USB from Fedora:
I've always used Fedora Media Writer for my UEFI USB boot sticks.
That is what I did this morning and had the problem that resulted in this post.
As you can see using the NetInst ISO for Fedora worked just fine.
But the Windows 10 1803 ISO does not.
-
Still an issue today. I wanted to make a Windows 10 1903 USB stick and it wilil not boot after writing the USB with Fedora Media Writer.
Creating a Fedora 30 USB worked just fine.
-
FYI This is what I have been using: WoeUSB.
Just thought I would try again.
-
I just use
dd
after getting rid of the partitions on the USB drive, but that's probably more manual than you want.Edit (after reading the rest of the thread): I haven't used my method of
dd
with a Windows ISO. I'll try it if I get a chance to tonight and let you know how it goes. -
Try using WoeUSB via command line. Here's what I did with my USB drive.
sudo umount /dev/sdb1 sudo woeusb --tgt-fs NTFS --device Win10_1903_V1_English_x64.iso /dev/sdb
After running the command.
WoeUSB v3.2.12 ============================== Mounting source filesystem... Wiping all existing partition table and filesystem signatures in /dev/sdb... /dev/sdb: 2 bytes were erased at offset 0x000001fe (dos): 55 aa /dev/sdb: calling ioctl to re-read partition table: Success Ensure that /dev/sdb is really wiped... Creating new partition table on /dev/sdb... Creating target partition... Making system realize that partition table has changed... Wait 3 seconds for block device nodes to populate... Cluster size has been automatically set to 4096 bytes. Creating NTFS volume structures. mkntfs completed successfully. Have a nice day. --2019-06-05 19:28:36-- https://github.com/pbatard/rufus/raw/master/res/uefi/uefi-ntfs.img Resolving github.com (github.com)... 192.30.253.113 Connecting to github.com (github.com)|192.30.253.113|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://raw.githubusercontent.com/pbatard/rufus/master/res/uefi/uefi-ntfs.img [following] --2019-06-05 19:28:37-- https://raw.githubusercontent.com/pbatard/rufus/master/res/uefi/uefi-ntfs.img Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.0.133, 151.101.64.133, 151.101.128.133, ... Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.0.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 524288 (512K) [application/octet-stream] Saving to: ‘/tmp/WoeUSB.JXhyoC.tempdir/uefi-ntfs.img’ uefi-ntfs.img 100%[===================>] 512.00K 2.70MB/s in 0.2s 2019-06-05 19:28:37 (2.70 MB/s) - ‘/tmp/WoeUSB.JXhyoC.tempdir/uefi-ntfs.img’ saved [524288/524288] 1024+0 records in 1024+0 records out 524288 bytes (524 kB, 512 KiB) copied, 0.293463 s, 1.8 MB/s Mounting target filesystem... Applying workaround to prevent 64-bit systems with big primary memory from being unresponsive during copying files. Copying files from source media... 1% Installing GRUB bootloader for legacy PC booting support... Installing for i386-pc platform. Installation finished. No error reported. Installing custom GRUB config for legacy PC booting... Resetting workaround to prevent 64-bit systems with big primary memory from being unresponsive during copying files. Unmounting and removing "/media/woeusb_source_1559784507_8150"... Unmounting and removing "/media/woeusb_target_1559784507_8150"... You may now safely detach the target device Done :) The target device should be bootable now
-
@black3dynamite never looked into the CLI since I am always doing it from my laptop. handy to know.
-
I confirmed my dd method did not result in a functional USB for a windows install.
-
WoeUSB is the only convenient way I've been able to make bootable (UEFI) USB Windows medium. Usually purge all the partitions on the USB device prior, using Gnome Disks application.
I use Gnome Disks application - restore (or DD), for Linux
-
I went through this fiasco recently. I did not know about WoeUSB so I tried everything like DD and gnome disks, but they dont create a bootable UEFI disk. You have to turn on legacy boot which I did not want.
It seems the solution was right in front of me, and I didnt even know it. Gnome has a startup disk utility that is specifically for creating startup disks. Works with UEFI right out of the box