Open steve6375 opened 1 year ago
I have same issue with Ubuntu. I think it is because the VHD or VDI was made using LVM+encryption. I can boot using Ventoy but not using grub2 or grub4dos - does this make sense?
ZorinLite seems to not install via UEFI - even just a simple VBox install to vhd fails when reboot to VHD from UEFI - must be bug in ZornLite 16? I also repeated a LinuxMint install to VDI and now it is working fine! LUKS+UEFI+Legacy+REMOUNT, boots from grub4dos and grub2 and Ventoy. Not sure why it is now working again. Maybe because I started with UEFI install and then added legacy grub files afterwards? You can close this issue if you dont want to keep it open. I still have a VHD that can be run by Ventoy but not by grub4dos/grub2 vdiskchain, but other vtoy files work OK.
Surprisingly, Zorin was working fine for me as in I was able to boot zorin vhd on my hard disk/ssd from grub2 chainloader entry. I had done manual partitioning instead of the auto one in zorin installer.
But i have now replaced it with Elementary OS 6.2 and am facing this identical problem - can't boot from grub2 but any usb with ventoy is able to boot it just fine. On selecting the grub2 chainload entry i get a 2nd grub menu (from the efi partition on the VHD) and on selecting it the display goes blank. Same entry boots just fine when i select it after ventoy boot menu.
I think the post about LVM+Encryption might be on to something. Because i selected auto partitioning while installing and gparted doesnt show me any partitions or the VHD - it only shows my SSD and the ventoy USB used to boot
There's also another issue: when i run the vtoyboot.sh script on elementary after a kernel update it keeps doing its magic for the previous kernel while grub-customizer or just checking out grub.cfg etc show me the newer kernel. Even after i have uninstalled the previous one completely !
I am not quite sure what I have done to the VHDs but I have two zorin legacy-installed VHDs which show the same problem. They were legacy booting OK previously and then I must have done something such as add grub2 uefi files and now they will only boot using the Ventoy menu system. If I use vdiskchain (either under grub4dos or grubfm/grub2) I now get a vdisk parameter not found error.
but they still both boot fine using Ventoy and they were both booting fine yesterday using grub4dos/grub2/ventoy so I must have broken something!
Can you suggest what might be wrong and how to fix please? Is code in vdiskchain same as Ventoy code?
P.S. Ventoy will also UEFI-boot from the vtoy files but it complains about not a uefi disk and also a 10 second Warning - not a Ventoy disk, but then boots OK!