Ventoy VS triage

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 ||

I downloaded and made a bootable USB Ventoy (https://www.ventoy.net) with its Windows GUI app in my updated 64-bit W10 Pro PC. However, I couldn't seem to get VirtualBox v7.0.12 to boot it. I read VirtualBox can boot from bootable USB flash sticks so it should work. Am I missing something?

So, yes. The installer will need to install grub to that first partition. You can install ventoy to a usb drive, put a windows iso there and your q4os iso. In case you mess up big time, you can reinstall windows.

There is a known issue on Elementary, system not cleaning automatically old kernel, completely filled the /boot partition.

You can open up an issue here of you’re not sure about the correct repo: https://github.com/elementary/triage

https://github.com/elementary/triage, submit a issue here :))

As described here, sometimes one of my displays sets itself to a lower resolution (on boot) and there's no option to change it. The only "fix" is to reboot my PC. Does anyone has any ideas?

Thank you for the links / your time. I was able to boot 20.04 and 21 ubuntu so am wondering if its something other than this bug on my dell, as i am not getting that error message. I read somewhere that https://github.com/ventoy/Ventoy wrote an iso raw and rufus (which i used) did not, so going to create a new boot disk with ventoy when home tonight and try that. Only have UEFI as its a new laptop and think i cant boot from legacy but hopefully the workarounds here https://github.com/elementary/triage/issues/74 will help some people! Thanks.

I am talking about this issue for example, and the management of it. Of course the eOS developers didn't do anything wrong, Ubuntu devs messed up everything and lets wait for them to fix it. Meanwhile we are going to mix repos to our liking, and blame other devs if some apps wont install or work. The problem is not having bugs or issues with a software, they should be acknowledged and fixed, not blamed on other devs. I am very happy to hack around my system, but please dont try selling a frankensystem that has a 3 yr old ubuntu base as a "capable replacement for macos" because for example it wont even boot for me, although on the front page you can only "purchase" it (I know that if I type in 0usd i can just dl it, not my point)

Looks like it’s an issue facing more than just Neon - this is for Elementary OS, workaround works https://github.com/elementary/triage/issues/74