iVentoy PXE allows FATDOG v9xx to boot to desktop.

Might want to add this to the list of tested distros tested.

P.S. These versions ALSO boots via Ventoy as well as via iVentoy.

Hey, all. I think I need to chainload (redirect) from my main iPXE server to iVentoy. Basically, there will be a PXE menu entry on Server #1 which needs to direct to Server #2 running iVentoy. I'm not sure what the syntax should be and what specifically within iVentoy I need to be linking to.

Any help would be appreciated.

Is anyone able to boot a FreeBSD 14.0 ISO successfully?

It looks as though there is a problem using the latest release. FreeBSD starts to boot, but then stops. 13.1 and 13.2 booted OK.

I'm using ventoy-1.0.96. I do have a 8TB disk. I'd like
to use it for ventoy and for backup. So I'm trying to execute:

  sudo ./Ventoy2Disk.sh -i  -g -r 7800000 /dev/sdc

This leads to:

  **********************************************
      Ventoy: 1.0.96  x86_64
      longpanda admin@ventoy.net
      https://www.ventoy.net
  **********************************************

  Can't reserve 7800000 MB space from /dev/sdc


Using the GUI gives a similar error.

I can use Ventoy using this procedure:

1. Manually create partitions on the disk:
    1 ... 200GB
    2 ... 100MB
    3 ... remaining space
2. Delete partition 2
3. Do a non-destructive install: sudo ./Ventoy2Disk.sh -i -n /dev/sdc
    Partition 2 is recreated with a size of roughly 32MB
4. Delete partition 3
5. Create partition 3 for the remaining space

Is there any known way to add a chainload entry to the menu?

I have the "Professional" version and have used it to make the boot disk ISO - and added that ISO to Ventoy.

It boots up just fine, it 'sees' the Ventoy Disk but it does not 'see' the fixed SSD with the C\- drive on it.

Any thoughts?

I have an issue that i've documented here: https://github.com/ziggyds/iventoy/issues/8

In escense, there is an issue with iventoy logs when used within a docker container when the logs are mapped to persistant storage outside of the container.

When iVentoy senses an error (Like an ISO is copied to the ISO folder and iventoy dosnt like the ISO) The software crashes within the container and creates an infinite loop cycle of complaining about not being able to find certain log file names that it expects to find.) 

To fix the issue, i have to remove the problematic ISO file from the ISO foler, and then delete or rename the log.txt file and restart. Then iventoy starts again.

It seems that iventoy is referencing individual log file names in its own log output but the log file being created by the container on the persistant storage is being saved as a single file and saved as log.txt.

I understand that this may not be an official way of using iventoy (in a container), but theres no reason i can think of why iventoy shouldnt work where other applications (netboot.xyz etc) work seemlessly.

See the link at the top of the post for a few log screenshots and more detail.

Any advice on mapping the logs externally would be great, a external mapping dosn't seem to cut it...

Hello, I've got a problem with booting Ventoy. My main partition is now unformatted.
I had many ISOs on my installation and now everything is gone.
What should I do to recover my Ventoy USB?
I think it was overwritten somehow by windows commands:
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

Attached Files

Thumbnail(s)
   

Hi.

I have an old pc and i want to install the win11 at this but ventoy doesn't boot correctly.


It bring me that final screen after finish load the usb-hdd i create with the latest version of ventoy.








Can you please fix this?

Hello.

I have recently started using Ventoy with succes.

However there is one very nuisance. A Ventoy prepared USB-stick (under Windows 10), if a extra ISO is to be added, takes maybe 4 minutes before recognized by the PC (with Windows 10). Before recognizing, all USB-related programs (and Windows Explorer), fail to start. After recognizing, all functions well and normal. Even unplugging and replugging the USB-stick gives then no problem (untill replugging in a new started PC).
The are many reports from different peaple about the same problem.

I found that the Ventoy-stick has a FAT16 Ventoy-system partition. 
I have earlier found, on my PC with Windows 10, that memory-cards which are FAT16 formatted (so 2GB or 4GB cards) give serious confusing recognizing problems. Probably because there are several different recognizing ID-'s for FAT16. When I applied FAT32 for those cards all problems were over.

So I suggest to the developer of Ventoy to change the Ventoy-system partition to FAT32, in my expectation that then the long recognizing problem under Windows10 is over.