unetbootin VS Ventoy

Use a tool like Rufus or UNetbootin to create a live USB stick.

format your USB drive and then you can retry with your software again, or you can try with a piece of software I know works successfully. https://unetbootin.github.io/

Linux on a USB large enough to hold your files. Linux does not care what OS made the file. You mat be able to Boot from the USB. Access the BIOS and try it. UNetbootin can also be used to load various system utilities. https://unetbootin.github.io/

I think UNetbootin could create a bootable installer directly from your current drive.

This is what you want. Bootcamp is the old way to do it. You want to use This for making a usb

use rufus or unetbootin to make setup the drive

You want to test out? Get a live image. You can put it on a bootable flash drive, too (e.g., unetbootin). Changes to the computer then require your explicit consent. (If the Ubuntu partition is encrypted, you might not access the data from an other Linux except with the credentials, though.)

Link to installing: Ventoy

Ventoy is an open-source tool to create a bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. Using Ventoy, we can create live USB for multiple distros in one flash disk. This is a revolutionary feature compared to other tools, e.g., Etcher, Rufus, etc, that can only create one live USB at a time. This tool is so important. Don't call yourself a distro hopper if you don't know this tool.

I'm thinking you mean Ventoy? They say they can load vhd and img files, though I've only tried ISO's myself.

https://www.ventoy.net/

View on GitHub

I faced it too. There is a PR on the ventoy GitHub repository that fixes Proxmox boot.

https://github.com/ventoy/Ventoy/actions/runs/7088423200

> While this works, I find this method a bit tedious to use, at least compared to Ventoy [0].

I find ventoy more tedious, because you can't use it on your hard drive with a sane partitioning scheme.

The only reason is because of how the ventoy detection hardcode the partition boundaries in its checks, and it means Ventoy can only run with the partitions set in a way that may lead to alignment issues like write-amplification: I've detailed that in https://github.com/ventoy/Ventoy/issues/1342

Ideally I'd have a 10G partition after the EFI (or it could even be the EFI itself) with a few ISOs for rescue purposes + a UEFI entry to avoid having to use a bootable USB, but that's not possible with Ventoy unless I accept Ventoy choices of partition boundaries:

                (pMBR->PartTbl[0].StartSectorId != 2048 ||