[issue]: Fresh install of Ventoy wont boot

tps800 commented 3 years ago

Official FAQ

[X] I have checked the official FAQ.

Ventoy Version

1.0.55

What about latest release

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

BIOS Mode

Both

Partition Style

GPT

Disk Capacity

500GB

Disk Manufacturer

Intenso

Image file checksum (if applicable)

Yes.

Image file download link (if applicable)

https://github.com/ventoy/Ventoy/releases/download/v1.0.55/ventoy-1.0.55-linux.tar.gz

What happened?

Installing Ventoy 1.0.55 onto a fresh device this device will not boot. Tested with

VMware Workstation 16.2.0
Qemu running on Ubuntu Impish
Lenovo T490, T460, T450

A closer look at the device installed reveals there is no boot code for x86/x86_64 installed on the device (grub or other). Going back to version 1.0.23, then installing, next upgrading to 1.0.55 will make the device bootable.

ventoy commented 3 years ago

Which method did you use to install Ventoy? CLI/GUI/WebUI
Please upload the log.txt for check
Can some version between 1.0.43 ~ 1.0.55 work ?

tps800 commented 3 years ago

Which method did you use to install Ventoy? CLI/GUI/WebUI

All of them.

Can some version between 1.0.43 ~ 1.0.55 work ?

Tried with 1.0.23. This worked, but only for SATA SSD. NVMe SSD will not boot in any case.

Please upload the log.txt for check

############# Ventoy2Disk -I -r 2048 -g -s -L BCKPSN_A /dev/sdb [x86_64] ################
Do 21. Okt 08:54:54 CEST 2021
no need to decompress tools
User will reserve 2048 MB disk space
MODE=install FORCE=Y RESERVE_SPACE=YES RESERVE_SIZE_MB=2048
hexdump test ok ...
mkexfatfs test ok ...
vtoyfat test ok ...
tool check success ...
check tool work ok
root permission check ok ...
install Ventoy ...
/dev/sdb1 not exist
format_ventoy_disk_gpt 2048 /dev/sdb parted ...
modsector:7 need to be aligned with 4KB
part1_start_sector=2048  part1_end_sector=995955335
part2_start_sector=995955336  part2_end_sector=996020871
format disk by parted ...
test uuid: 00000000  3d 39 b2 ec 17 54 4d 83  b9 ba 7c f7 26 a4 e2 2e  |=9...TM...|.&...|
00000010

Trying to boot this newly written device with qemu (BIOS, UEFI) will only tell about no boot device available. Same for VMware Workstation or real hardware.

ventoy commented 3 years ago

Let's take focus on Ventoy-1.0.55 and this NVMe SSD. Please reinstall 1.0.55 with GUI version and upload the full log.txt file for check. Besides:

Please run parted /dev/sdb p after install and give the result.
Can 1.0.55 work OK on SATA SSD?

ventoy commented 3 years ago

After install. /dev/sdb should be divided into 2 partitions. and /dev/sdb2 is a 32MB FAT partition with label VTOYEFI. Can you see this partition after install? If this FAT partition exist, you can try to boot into UEFI shell firstly and find this partition and run \EFI\BOOT\BOOTX64.EFI file in the partition manually to see what happen.

tps800 commented 3 years ago

Please run parted /dev/sdb p after install and give the result.

# LANG=C parted /dev/sdb p
Model: Intenso Portable SSD (scsi)
Disk /dev/sdb: 512GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name     Flags
 1      1049kB  510GB  510GB                Ventoy   msftdata
 2      510GB   510GB  33,6MB  fat16        VTOYEFI  hidden, msftdata

Can 1.0.55 work OK on SATA SSD?

Yes.

After install. /dev/sdb should be divided into 2 partitions. and /dev/sdb2 is a 32MB FAT partition with label VTOYEFI. Can you see this partition after install?

Yes.

If this FAT partition exist, you can try to boot into UEFI shell firstly and find this partition and run \EFI\BOOT\BOOTX64.EFI file in the partition manually to see what happen.

The system hangs, just doing nothing.

I had the time trying (the Intenso-Disk is an USB 3.1 device with PCIe disk build in):

Install Ubuntu 21.10, UEFI-Mode -> installs fine, but wont boot afterwards.
fedora 34, UEFI-Mode -> installs fine, but wont boot afterwards.

Tested against an USB 3.1 device with SATA emulation NVMe SSD: Ventoy 1.0.55, Ubuntu 21.10, Fedora 34 all install well and boot. The very same device equipped with an PCIe NVMe SSD wont boot any more (DeLock 42004 -- allows both: SATA and PCIe NVMe SSD). I could even try out to boot these USB-Installed devices directly within a Laptop having two slots: one for SATA NVMe SSD and an other one for PCIe NVMe SSD. Both boot installed directly.

tps800 commented 3 years ago

USB 3.1/3.2 devices seem not recognized by qemu. In a efi-shell without any other connected devices than one USB-PCIe-SSD there are no mappings available. Same for VMware Workstation 16 and some real hardware: Lenovo T490, T460, T450. Seams there are some problems with such devices ...

steve6375 commented 3 years ago

Connect the device using a USB 2 cable (to test).

tps800 commented 3 years ago

Tested. Same result: drive not recognized.

ventoy / Ventoy