在学校的希沃一体机上，打开软件，插入U盘，U盘的分区成了CDEF，而CDEF是主硬盘的分区。如附件所示。当时看着设备名称和容量正确，就点了安装，结果系统就崩溃了。（提前做了双系统，现在在Win10，日常使用没问题）
当时是win7 x64 专业版。在win10中也存在同样的问题。在自己的电脑上是正常的，如me.png，做好了去学校电脑上，问题仍存在，如附件seewo.png。
自己排除了分区数量问题，在其他班的电脑上同样有问题。

Attached Files

Thumbnail(s)
       

Hi I install
Ventoy 1.0.29
..
Install iso windows s 7 and 8 and xp and 10   and Linux  and software s.. in flash drive
After boot
..
Boot success windows 10 7 and software s

But not boot windows xp  and not boot working iso Linux
Please help me and fix software

Hi,

配置: 版本1.0.29, EFI引导. 移动硬盘数据分区为ntfs.

尝试了gentoo和debian buster的LiveCD, 启动之后无法挂载数据分区, 错误为Device or resource busy.

现在的Workaround是内核命令行加'toram', 然后启动之后把整个USB Reset一遍 (或者重新插拔).

有没有办法在不加载到ram的情况下也能访问到数据分区的内容 (只读也行) ?

Hi guys,

I am just testing Ventoy and find myself in this situation, for now I just want to be sure this is something that should be working before wasting too much time in something ventoy is not designed to do.

I installed Ventoy on an external HDD using the Linux script. No problems there.

But when I boot in legacy BIOS mode the drive is not listed as an available boot drive. This is how I always set up the system and have used many USB creator in the past.

BIOS settings are correct regarding legacy mode active, boot order, etc. etc. and I was in Legacy mode both times I installed Ventoy on this HDD.

If I switch to UEFI mode the drive is listed and can boot ISO images from there, but only UEFI compatible ones, and that excludes ISOS such as boot-repair-disk and many other tools I normally use.


My question then is if this situation where my drive is not listed on Legacy mode is to be expected or something is going wrong on my side.

Thank you.

I made some changes as per needs in grub.cfg and ventoy.json for better use specially in graphic theme.

thats why i made disk image to acronics and r-image 
nothing worked after successfully restored 
Hang on GR, in Legacy mode and uefi getting warning msg 
what use of customisation and ventoy keeping as open source ? easy2boot aio creator and other few are really looking forward without restriction

I'm not sure whether this is an issue with Ventoy or Linux Live Kit or somehow Mint, but here's what I did:

I customized Linux Mint by making an ISO of my hard drive using Linux Live Kit.  It generated an ISO file and a ZIP file.  I tried placing the ISO file onto my Ventoy drive and booting into it, but it didn't work.  First it booted Ventoy, and then gave me the menu to boot Mint, but when I did, it said that it's may not be compatible with 64-bit EUFI (It's a generic error that I've seen before, and it's common when I try to boot some ISO files on Ventoy but it never happened with Mint before, and why wouldn't it be compatible, considering that it was made from a 64-bit OS which I regularly boot in UEFI mode?).

So then I switched to CSM (Legacy BIOS) mode, and booted it again.  This time it showed a bunch of scrolling text like usual, but then it said:

Live Kit init (followed by a link to their website)
Setting Dynamic RAM compression using ZRAM if available
Probing for hardware
Looking for linux data in /linux.............................................................
Fatal error occurred - Could not locate linux data
Something went wrong and we can't continue.  This should never happen.
Please reboot your computer with Ctrl+Alt+Delete...

It should be noted that when I generated the ISO file, Live Kit told me an error that it couldn't find /linuz, so I went into the config file and changed a line to say /boot/linuz (because that's where it really is), and then it worked fine and created the ISO file without any errors.

Hi.
I would like to know if you can make an image of a bootable usb that is compatible with ventoy.
Thank you

Hello,

Is there any way to access the USB key main partition (where the iso is located) from a linux booted with Ventoy?

I always had a message "unable to mount" when trying to access it and it wasn't in the mounted devices.
It would be really great to have this possibility.

Cheers,
Loceka.

/grub/grub.cfg

Hello,

I tried the .29 version of Ventoy 3 days ago and after booting on linux from ventoy, when I returned to Windows, the usb key was detected as readonly.
To make it readable again I had to go to "Properties/Tools/Check now" (on Windows 7 at least) with admin rights.

I've tried 4 or 5 times on different linux bootable images and it happened every time.

I don't recall every seeing this issue with the previous ventoy versions (the last I tried was the .20).

As for the key creation options I did nothing fancy, just checked "Secure boot support" and chose "MBR" partition table.

Have fun debugging that!
Loceka.