search

ventoy / vtoyboot

Work with ventoy to support boot Linux distros in a vdisk file (vhd/vdi/raw ...)
GNU General Public License v3.0
275 stars 23 forks source link

Error: Unsupported vtoy type unknown #48

Open Sitolam opened 2 years ago

Sitolam commented 2 years ago

I have an external SSD. That's where I set up Ventoy. I then followed the instructions of linux vdisk but I got this error.

FJIMG_20220604_110814.jpg FJIMG_20220604_110828.jpg

ventoy commented 2 years ago

  1. Did you use fixed size vdi type or dynamic size vdi type? Ventoy only support fixed size vdi type. That is to say, if you create a 16GB virtual disk in the VM then the vdi file must be exactly 16GB size.

  2. You can compress and share me the vdi file for analyze

Sitolam commented 2 years ago

  1. Did you use fixed size vdi type or dynamic size vdi type? Ventoy only support fixed size vdi type. That is to say, if you create a 16GB virtual disk in the VM then the vdi file must be exactly 16GB size.

  2. You can compress and share me the vdi file for analyze

I used fixed size. My vdi file is 400gb so that was difficult to forward. So I made a smaller one of 16gb and it worked. I would like to have a vdi file of 400gb how can I solve this? With the 400gb vdi file I already had the vdi file on my ventoy ssd during installation with virtualbox could that be the problem?

ventoy commented 2 years ago

It has been highlighted in the document : https://www.ventoy.net/en/plugin_vtoyboot.html The virtual hard disk must be newly created, do not use the existing ones.

So you can delete the current VM and vdi file and make a new one from scratch. I don't think there is any difference between 16GB vdi file and 400GB vdi file.

Sitolam commented 2 years ago

It has been highlighted in the document : https://www.ventoy.net/en/plugin_vtoyboot.html The virtual hard disk must be newly created, do not use the existing ones.

So you can delete the current VM and vdi file and make a new one from scratch. I don't think there is any difference between 16GB vdi file and 400GB vdi file.

Ok, I will try

Sitolam commented 2 years ago

It has been highlighted in the document : https://www.ventoy.net/en/plugin_vtoyboot.html The virtual hard disk must be newly created, do not use the existing ones.

So you can delete the current VM and vdi file and make a new one from scratch. I don't think there is any difference between 16GB vdi file and 400GB vdi file.

I have recreated the 400gb vdi file. And when I boot it I get the same error.

Sitolam commented 2 years ago

It has been highlighted in the document : https://www.ventoy.net/en/plugin_vtoyboot.html The virtual hard disk must be newly created, do not use the existing ones.

So you can delete the current VM and vdi file and make a new one from scratch. I don't think there is any difference between 16GB vdi file and 400GB vdi file.

I have recreated the 400gb vdi file. And when I boot it I get the same error. The vdi file is on my ventoy ssd during the installation of the 400gb vdi file because I don't have enough space on my computer for a 400gb file. At the 16gb it was on my computer. Could that be the problem?

ventoy commented 2 years ago

Please do more test for 64GB/100GB/200GB/300GB... to see which is the smallest capacity that get the error. You don't need to really boot the VM and install OS into it. Just after you create the vdi file, then you can boot it by Ventoy, because we just want to see that whether it will report the Unsupported vtoy type error and the content inside the vdi file has no relationship with this error.

Sitolam commented 2 years ago

Please do more test for 64GB/100GB/200GB/300GB... to see which is the smallest capacity that get the error. You don't need to really boot the VM and install OS into it. Just after you create the vdi file, then you can boot it by Ventoy, because we just want to see that whether it will report the Unsupported vtoy type error and the content inside the vdi file has no relationship with this error.

Ok I will try that

Sitolam commented 2 years ago

I did what you suggested but then even with the 16gb I got the same error message.

ventoy commented 2 years ago

That is to say if you create the 16GB vdi file in your local disk and copy to Ventoy, then it boot OK. But if you create the 16GB vdi file in the Ventoy disk, then it boot fail?

ventoy commented 2 years ago

Create a new an empty 16GB vdi file in your local disk and copy to Ventoy and boot. If it can boot OK. then compress the two 16GB vdi files and share with me for analyze. The two 16GB vdi files are empy, so they should be very small after compress.

Sitolam commented 2 years ago

I created the local vdi file and tried to boot it but then I also got the error. Could it be that I need to turn on EFI first? https://mega.nz/file/FopDlTKR#utsN7ShylR2YcvSZTm5fuyj8SZ_N3dNH_DvxFAEnBUchttps://mega.nz/file/0hQDiAYD#Fq3ouzHTgerXdwPuwOqIwpT7jIyQodSIRXLnpRG8SjE

Sitolam commented 2 years ago

Must I try VHD?

trymeouteh commented 1 year ago

I have the same issue and have tried the following...

Linux Mint - VDI - Fixed - 50GB Linux Mint - VDI - Fixed - 100GB Linux Mint - VDI - Fixed - 200GB Linux Mint - VDI - Fixed - 300GB Linux Mint - VDI - Fixed - 460GB Linux Mint - VDI - Fixed - 920GB

The only ones that booted up were 200GB and lower. Anything above 200GB will not boot. However I was able to created fixed VHD drives and they will work no matter the size it will seem. I was able to make a 920GB VHD which did boot in Ventoy.

There is something wrong with ventoy when it comes to booting large VDI drives.

HaroMeng commented 9 months ago

i have the same problem.400GB

ObiKeahloa commented 6 months ago

Same issue, 24gb vdi

peri0d commented 3 months ago

i also have the same problem. And i made a 35GB VDI and the only difference between it and the 400GB is that the size is different The 35GB VDI boot up successfully

OneShz commented 3 months ago

i have the same problem,and i have another error :error disk hd1,1 not found unspported vtoy type unknown.i found i have another disk so the system can recognize it , i unplug the USB flash drive and it is ok.