May please the following wiki: LiveUsbPersistence please be perused.

I have installed Ventoy on one of my HDDs. I then partitioned the rest space and can boot different ISOs from Ventoy. So far so good.

Could Ventoy be used to boot a Debian Live Persistent set up?

There are certain aspects in the said page that needs to be addressed. For example,

Quote:We can use:

• FAT partition with boot flag,
  
• ext4 partition with label persistence. The label "persistence" is mandatory.
  

Hi,

I've successfully expanded the DAT file for the persistence of my Linux Mint distro. Before the expansion, everything was working correctly. I used the default caspar-rw 4GB DAT file provided by Ventoy, hosted on an 64GB USB stick. Note that all hardware remained the same in this whole issue.

To do the expansion, I used the "expansion script" provided by Ventoy, targeting the existing DAT file. The expansion took quite a while -- about 30 mins -- as I brought the DAT from 4GB to 24GB. It completed successfully, although I remember there was some warning about "unmatching sectors" or something like that, but then the script prompted me for a final verification, after which it returned a "success" message.

After the expansion, I can boot to Linux Mint, but it immediately crashes to Fallback mode. LM immediately asks if I want to restart the GUI, and if I do, it immediately crashes again to fallback mode. If I keep using fallback mode, I can see that the persistence seems to have retained all my data and programs, but I cannot access basic system settings and the experience is far from ideal.

What's the best course of action here? I don't have any important data in the persistence, so I would be ok with starting from scratch, but I do need a DAT larger than the default ones -- I only wonder if I won't end up in the same situation if I try again the expansion. Is there a way to recover the existing persistence DAT to a working state (I don't have time snapshots unfortunately)? What's the best way to start with a stable, large DAT file targeting Linux Mint?

will there be suppiort for proxmox 8.2 on ventoy

已架设好iventoy，unraid新建Legacy启动模式的虚拟机，网络启动引导正常。其他条件不变的情况下，改成 UEFI模式，网络启动引导进入系统后就重影花屏。尝试多次，pe和window引导盘都是花屏，Fedora倒是可以正常启动。

On Ventoy GHub CI release on 3 April , it always shows ‘‘Alloc magic broken’’ somewhy, but i expect that to install FreeBSD 14.x-STABLE and that Ventoy release is the minimum Ventoy release in order to boot the FreeBSD installer that release in order of that FreeBSD to be installed

Hello guys

for the most part ventoy did work very fine but there is a weird issue and I am unable to track it down further. 

If I connect the stick to the computer I created it with the Ventoy volume takes a long time to appear and something USB related is delayed until it's there. For example I pulled the wire from my mic while it was "hanging" and it still showed as connected device until the USB drive was properly recognized. Also the Windows disk management hangs. It takes pretty much the same time every time - about a minute and then working fine as far I can see.

It's only happening to the Ventoy USB stick and only on my main computer. I tried it on a couple of other machines no problem.

I am getting the following events logged in event viewer after connecting the Ventoy stick.

17.04.2024 22:27:51 Der E/A-Vorgang an der logischen Blockadresse "0x773ad288" für den Datenträger "3" (PDO-Name: \Device\0000016c) wurde wiederholt.
17.04.2024 22:28:07 Ein Zurücksetzen auf Gerät "\Device\RaidPort11" wurde ausgegeben.
17.04.2024 22:28:07 Der E/A-Vorgang an der logischen Blockadresse "0x800" für den Datenträger "3" (PDO-Name: \Device\0000016c) wurde wiederholt.
17.04.2024 22:28:21 Das Zeitlimit (30000 ms) wurde beim Warten auf eine Transaktionsrückmeldung von Dienst WSearch erreicht.
17.04.2024 22:28:21 Das Zeitlimit (30000 ms) wurde beim Warten auf eine Transaktionsrückmeldung von Dienst Backupper Service erreicht.

after these it takes additional 20 seconds but then I can use it without a problem

Since I am using ventoy for a long time I cannot really tell when it was the first time. Also it sometimes does not happen. I have absolutely no idea how to troubleshoot further.

Ideas very much appreciated. Thank you 

When boot an iso made with microsoft mdt , iventoy 1.0.20 don't mount y: drive.
Attachment: ventoy.log

Attached Files

Thumbnail(s)
   

Hi!
I want to install the Windows 11 23h2+Office 21 build, but after downloading the files, the error "Windows installation files were not found!" appears. If you mount this image on a USB flash drive, then everything works. The installer tries to run the file "JInn\WinSetup\boot 11 x64.wim", but cannot find it. This file is available in the image. If we take the official image of win 11 from Microsoft, then it also works.
System: Debian 11, IVentoy 1.0.20 (1.0.19)
Posted this topic on GitHub: https://github.com/ventoy/PXE/issues/62
Has anyone encountered this problem? Sorry for my English)

Attached Files

Thumbnail(s)
               

Hi there, as other people have been posting the same error, I can't seem to find a way around it, I've followed all the advice in other posts with the same issue  

First my setup... I have iventoy  1.0.20 on a Linux server, I've forwarded port 26000 in my router, I added a fresh iso of windows 11 from Microsoft, I tested iventoy first in a virtual machine and the install of windows 11 worked fine but when it comes to my 2 other main systems the install fails saying it needs to load a missing driver, I can ping the server and get a reply and see the install pc's network mac address in iventoy


This is my first system

Gigabyte Z590 AORUS PRO AX
Intel Core I5 11600k
Intel i225v LAN
Kingston SNVS250G NVME

My other system is based on an Intel 12th gen cpu and that fails in the same way

I even tested the windows version and that fails in exactly the same way, I've also tried disabling windows firewall and temporarily disabled firewall rules in the unifi router but still do luck.

I really appreciate the help and this is an amazing piece of software thank you. 

 

Good day, is it possible to define in ventoy.json custom menu entries in grub2 format, such like cloning some options from /dev/sda3/boot/grub/grub.cfg?