Legacy mode works fine

with 1.0.12 Uefi works on some machines.

with 1.0.13 and 1.0.14 no success with Uefi


i have posted some pictures with debug output
and output of blkid at:
https://github.com/ventoy/Ventoy/issues/187

[url=https://github.com/ventoy/Ventoy/issues/187][/url]

Hi

Ventoy is a great tool. Unfortunately I'm experiencing something strange, Ubuntu 20.04 LTS. When removing iso's from usb and adding new the menu i ventoy seems not to update accordingly. Information on already removed iso still remains in the boot option. Sometimes showing up twice when I add and remove the same iso file. Is this a known issue? Ho can I fix it?

https://github.com/ventoy/Ventoy/issues/266

I have a 4TB HDD which I want to use for VENTOY. And rest partition I could keep for some other purpose.

So can VENTOY use GPT since MBR only supports upto 2TB?

Hello friends, 

I can't use WINDOWS XP and WINDOWS 7, I tested it on 3 flash drives and the same thing happens

Attached Files

Thumbnail(s)
       

So tested my iso's I keep handy with a fresh install of 1.0.14.  Testing hardware if relevant is a HP Chromebook 13G1 (Core M7-6Y75/16GB/32GB eMMC) that uses mr. chromebox full rom instead of ChromeOS firmware (pure EFI boot).

Here's the list of iso's tested:
anarchy-1.2.1-x86_64.iso
debian-10.4.0-amd64-netinst.iso
endeavouros-2020.05.08-x86_64.iso
Fedora-Workstation-Live-x86_64-32-1.6.iso
FuryBSD-12.1-KDE-2020042001.iso
GhostBSD-20.04.1.iso
gparted-live-1.1.0-1-amd64.iso
haiku-r1beta2-hrev54154_111-x86_64-anyboot.iso
Mageia-7.1-Live-Plasma-x86_64.iso
OpenMandrivaLx.4.1-2020.05-plasma.x86_64.iso
q4os-3.11-x64-tde.r2.iso
ROSA.FRESH.PLASMA5.R11.x86_64.uefi.iso
sparkylinux-5.11-x86_64-lxqt.iso
void-live-x86_64-20191109.iso


All those tested with 1.0.13 are unchanged.  If they were working with 1.0.13, they worked with 1.0.14.  If they were not working with 1.0.13, they didn't work here.

Changed/new:


haiku-r1beta2-hrev54154_111-x86_64-anyboot.iso


q4os-3.11-x64-tde.r2.iso (newer iso)
not working, error same as r1 iso however.

Archuser iso does not start in Uefi mode
I would be very happy if someone would add support for it
It is very important for me to install Arch linux
Thanks a lot


https://github.com/laurent85v/archuseriso
http://dl.gnutux.fr/live/

I have a 256GB drive that I want to use as a full "digital toolbox" with Ventoy and PortableApps, but I would like to do so with 2 partitions so I can encrypt the non-ventoy partition with BitLocker. I built the drive with Ventoy and tested it, then used DiskGenius to split the volume. However, now when I boot it is going to a "Minimal BASH-like line editing is supported." I know the boot partition is still there because I'm getting that far, and all 3 partitions are visible in Windows. I know EXFat is wacky and doesn't really support splitting like that.

The second question, I also tried with the new version where they say on the front page where they say "Reserved USB space supported" which to me sounds like we will have an opportunity to slice some space off, but I don't see that.

Does anyone have any suggestions to get this setup working before I start over and try again?

So far soooooooooo GOOD.

Since the MBR partition is opted considering the Old PCs which is a good thought indeed.

But it could be wise and flexible (if possible) to give user the choice to choose whether to go for MBR or GPT partition format.

Likewise, if I have 1 USB-HDD & 1 Pen Drive; so the USB-HDD I want to use as GPT Partition with VENTOY in it for modern PCs. And the Pen Drive one I could use for MBR Partition with VENTOY for Backward Compatibility.

In this scenario if VENTOY allows me to choose the Partition Format prior Formatting (as it now lets us choose the Partition Configuration), it could be great advantage for us.

Thank you for your Hard work towards Smart output.

-From India with Love.

Hello,

I would like to mount (read-write) the ventoy partition from a live linux distribution that booted from ventoy. I tried 2 different versions but I have the same problem.

I type as root :
# mount -t auto -o rw /dev/sdb1 /mnt/newlycreatedmountpoint

It does not work. The message is : already mounted or mount point busy

The partition is not already mounted, of course, and the mount point has been created manually and is not busy.