Problems with linux vdisks

[Midas]

I have been trying to follow the setup detailed in https://www.ventoy.net/en/plugin_vtoyboot.html, but I always get stuck with the same errors.





I've been mostly trying this to setup 'linuxmint-20-mate-64bit.iso' and have tried booting the vdi.toy created with VirtualBox in Ventoy v1.0.41, v1.0.32, etc.

I have working VHDs with Windows in the same locations that boot alright before that -- i.e., when I get such errors, nothing boots anymore and I have to reboot.

What am I doing wrong?

[longpanda]

The photo is not clear enough.

[Midas]

You mean the error messages? Or the graphics?

How can I make it clearer? Is there a log somewhere?

BTW, this happened in two different computers.

[longpanda]

The graphics is too small and I can't see the error message.

[Midas]

Pictures are 900x600 pixels, but here's a transcript:

1st image
error: hd0 cannot get C/H/S values.
error: can't open file (hd0,1)/_BOOTIMAGES/mintl.vhd.vtoy
.
error: hd0 cannot get C/H/S values.
error: you need to load the kernel first.

Press any key to continue...

2nd image
error: hd0 cannot get C/H/S values.
error: you need to load the kernel first.
error: you need to load the kernel first.

Press any key to continue...

[longpanda]

Does a normal ISO file boot fine? (e.g. /_BOOTIMAGES/ubuntu.iso)

[Midas]

Yes. The Mint ISO mentioned in OP that was used to create the vdisk resides there and boots fine.

[longpanda]

press c to enter grub shell and run some commands:
ls
ls -l
ls (hd0,1)/_BOOTIMAGES/mintl.vhd.vtoy

[Midas]

Sorry for the delay, but the suitable computer wasn't readily available...

Here's the result of the prescribed commands (the vdisk name has changed, but the result remains the same):

   

If however I try to boot this vdisk, it fails and afterwards the commands result is this:

1. (proc)
   
2. Device proc: Filesystem type procfs - sector size 512B - Total size 0KiB
   
3. error: hd0 cannot get C/H/S values.
   

This is a Dell laptop PC which has Ventoy v1.0.32 installed on its main SSD.

---

EDIT: ages later, I finally managed this by using a VHD instead of VDI...

For details, check https://www.q4os.org/forum/viewtopic.php?id=3909