10-01-2021, 06:27 PM
I've noticed that when I reserve space, and then later partition it and save files to it, that partition is not always detected or accessible. I haven't figured out the pattern yet, but I haven't been very rigorous with my effort. And Ventoy is so awesome any way I just keep using it.
My situation is that I I help out high school computer club and I am trying to create USB drives that we can boot on the kids laptops, or the schools desktops. The kids computers are almost always windows (with the occasional mac). The school computers are desktops and a mix of Windows 7-10 and Linux (Ubuntu and Mint). We would like to be able to boot to whatever we have loaded on the first partition - and this always works great! Not a problem at all. But we also sometimes want to use the USB drive to copy files from machine to machine AND read the file when we use Ventoy to boot. But some of the machines can't see partition 3 that was created when we reserved space installing Ventoy. We did also partition that reserved space, labeled it "storage" and added files. Some windows machines can see it, some can't. All the linux machines (I think) can see storage just fine. We created the Ventoy USB drives on both Windows and Linux machines. I think we used the same options for all (we were supposed to). But we get inconsistent results.
This is particularly problematic because often we'll have files and information on a Windows machine that we want to then boot into linux, and use that info/file. But we can't copy it to storage, because Windows doesn't see it. So we copy it to the first partition "Ventoy". But then when we boot into via Ventoy into one of the ISOs, the first partition isn't readable, so we can't see our file.
The other problem that I run into, is that I often want to copy the iso files around, but they're on the first partition which isn't useful... there may be 5 or 10 ISOs (I love Ventoy!) but I can't read any of them... I'm not sure how/why it's mounted like that - I assume it's just part of the way that grub2/linux works. But that points to my holy grail, to be able to read from the first partition while booted into the first partition. Right now my work around is I copy most things to both partition 1 and partition 3. But for ISO files that eats up disk space quite quickly. And I have to commit early on as to how much space I'll reserve.
Is there a way to verify the current state of the disk from Ventoy's perspective - like what the equivalent command line was? I expected the -l switch to do this, but it doesn't give enough info that I can tell. Is there a verbose listing? ;D. I typically create the disks with Ventoy2Disk.sh -i -s -r XXXX /dev/sdX
Am I missing something obvious? Is this just a linux limitation with booting and reading? I definitely blame Windows
My work around is to carry extra USBs but that just seams antithetical to what Ventoy is and makes possible. Ventoy is awesome, it's the best/easiest multiboot I've found. Sorry for sounding greedy and for wanting more.
My situation is that I I help out high school computer club and I am trying to create USB drives that we can boot on the kids laptops, or the schools desktops. The kids computers are almost always windows (with the occasional mac). The school computers are desktops and a mix of Windows 7-10 and Linux (Ubuntu and Mint). We would like to be able to boot to whatever we have loaded on the first partition - and this always works great! Not a problem at all. But we also sometimes want to use the USB drive to copy files from machine to machine AND read the file when we use Ventoy to boot. But some of the machines can't see partition 3 that was created when we reserved space installing Ventoy. We did also partition that reserved space, labeled it "storage" and added files. Some windows machines can see it, some can't. All the linux machines (I think) can see storage just fine. We created the Ventoy USB drives on both Windows and Linux machines. I think we used the same options for all (we were supposed to). But we get inconsistent results.
This is particularly problematic because often we'll have files and information on a Windows machine that we want to then boot into linux, and use that info/file. But we can't copy it to storage, because Windows doesn't see it. So we copy it to the first partition "Ventoy". But then when we boot into via Ventoy into one of the ISOs, the first partition isn't readable, so we can't see our file.
The other problem that I run into, is that I often want to copy the iso files around, but they're on the first partition which isn't useful... there may be 5 or 10 ISOs (I love Ventoy!) but I can't read any of them... I'm not sure how/why it's mounted like that - I assume it's just part of the way that grub2/linux works. But that points to my holy grail, to be able to read from the first partition while booted into the first partition. Right now my work around is I copy most things to both partition 1 and partition 3. But for ISO files that eats up disk space quite quickly. And I have to commit early on as to how much space I'll reserve.
Is there a way to verify the current state of the disk from Ventoy's perspective - like what the equivalent command line was? I expected the -l switch to do this, but it doesn't give enough info that I can tell. Is there a verbose listing? ;D. I typically create the disks with Ventoy2Disk.sh -i -s -r XXXX /dev/sdX
Am I missing something obvious? Is this just a linux limitation with booting and reading? I definitely blame Windows
My work around is to carry extra USBs but that just seams antithetical to what Ventoy is and makes possible. Ventoy is awesome, it's the best/easiest multiboot I've found. Sorry for sounding greedy and for wanting more.