Ventoy icon indicating copy to clipboard operation
Ventoy copied to clipboard

[issue]: Linux Mint .vtoy not booting on Lenovo IdeaPad 300

Open steve6375 opened this issue 1 year ago • 4 comments

Official FAQ

  • [X] I have checked the official FAQ.

Ventoy Version

1.0.80

What about latest release

Yes. I have tried the latest release, but the bug still exist.

Try alternative boot mode

Yes. I have tried them, but the bug still exist.

BIOS Mode

UEFI Mode and Legacy/BIOS

Partition Style

MBR

Disk Capacity

128GB

Disk Manufacturer

Sandisk Extreme Pro

Image file checksum (if applicable)

No response

Image file download link (if applicable)

https://1drv.ms/u/s!AqlrQcdsFA-K8UBsEV3DhdWok6wD?e=CRcBNI

What happened?

Booting same .vtoy in Legacy Mode on Asus Z87 PC works. Booting same .vtoy in Legacy Mode on VBox 5 VM works OK (but only if boot USB set as IDE or SCSI in VM .vmdk - does not work under a SATA controller in VBox, get black screen + flashing cursor hang) Booting same .vtoy in Legacy Mode on IdeaPad300 fails. When .vtoy file is selected and hit ENTER, get message:

error: hd0 cannot get C/H/S values
The OS in the vdisk was created in UEFI mode, but the current is BIOS mode.

Note that the IdeaPad 300 requires GRUB2 mode to even Legacy boot Ubuntu64.iso file - will not boot as 'normal' mode - but OK in UEFI64. Also, same .vtoy will not boot on IdeaPad300 in UEFI mode - error message is 'reset system' and then notebook resets. But works OK in VBox and Asus Z87 PC.

steve6375 avatar Sep 28 '22 10:09 steve6375

P.S. vdi.vtoy uses MBR partitions. It was created using Legacy install and then UEFI boot files added after install complete.

sudo  apt-get  install  grub-efi-amd64-bin
sudo  grub-install  --force  --removable  --target=x86_64-efi --efi-directory=/boot/efi  --bootloader-id=Ubuntu
sudo  update-grub

steve6375 avatar Sep 28 '22 10:09 steve6375

  1. The OS in the vdisk was created in UEFI mode, but the current is BIOS mode. This message should only print when the vtoy file is in GPT partition style. use vtdebug on to get more details.

  2. 'reset system' may be the same with https://github.com/ventoy/vtoyboot/issues/30 https://github.com/ventoy/vtoyboot/issues/19

  3. What about you follow the official instruction to make the vtoy file? (Create VM and boot in UEFI mode, install OS(should be GPT partition style) and finally run the vtoyboot.sh)

ventoy avatar Sep 28 '22 16:09 ventoy

I created a vdi using UEFI. vtoy_vdi_gpt_ptns vdi-vtooyboot_gpt

If I UEFI-boot on the IdeaPad300 it resets. If I Legacy boot using grubfm on the IdeaPad300 it hangs after "Booting 'vDiskChainLoad'" (or the error: hd0 cannot get C/H/S values message if legacy boot using Ventoy).

So same.

vtdebug on - legacy boot to Ventoy 1.0.79

part type GPT
part 2 is grub_bios part
image trim head 4096
ventoy_cmd_acpi_param 0x838283e0 512
error: hd0 cannot get C/H/S values
The OS in the vdisk was created in UEFI mode, but the current is BIOS mode.

There is something odd about the IdeaPad - VBOX and Asus Z87 PC are booting OK.

Note: Under VBox, the vdi.vtoy Linux file crashes if USB boot drive is configured as a SATA disk in VM, but boots OK if configured as a SCSI or IDE disk!

steve6375 avatar Sep 29 '22 09:09 steve6375

P.S. I re-checked the first vdi.vtoy file usin gparted and it seems LinuxMint created a GPT disk even though I legacy booted and used a blank raw vdi. No matter what I do, the Mint installer always creates a GPT disk if the disk is blank.

steve6375 avatar Sep 29 '22 12:09 steve6375