[issue]: update seems to have wiped the entire drive or at least the partition table #248

New issue

Open

opened 2025-10-14 18:12:15 -06:00 by navan · 0 comments

navan commented

2025-10-14 18:12:15 -06:00

Owner

Originally created by @dev-jam on 2/21/2025

Official FAQ

I have checked the official FAQ.

Ventoy Version

1.1.03

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

Both

Partition Style

GPT

Disk Capacity

2TB

Disk Manufacturer

Transcend

Image file checksum (if applicable)

Yes.

Image file download link (if applicable)

No response

What happened?

Updating from 1.1.01 to 1.103 seems to have wiped the entire disk or at least the partiton table.
The disk had 1 exfat ventoy partition, 1 EFI partition and 1 luks partition.
After this update the partition table changed to 'Unknown (PMBR)' in gnome disk.

I downgraded to 1.1.01 which was possible but did not fix the problem.
Ventoy still sees the installed version but gparted and gnome disk do not recognize the partition table.

Seems it even damaged the backup partition table.

Repair with gdisk seems to be successful. I can mount Ventoy and the luks partition again and on first sight, all the files seem to be there.

gdisk report:

GPT fdisk (gdisk) version 1.0.9

Caution! After loading partitions, the CRC doesn't check out!
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.

Warning! One or more CRCs don't match. You should repair the disk!
Main header: OK
Backup header: OK
Main partition table: ERROR
Backup partition table: ERROR

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged

*Originally created by @dev-jam on 2/21/2025* ### Official FAQ - [x] I have checked the official FAQ. ### Ventoy Version 1.1.03 ### 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 Both ### Partition Style GPT ### Disk Capacity 2TB ### Disk Manufacturer Transcend ### Image file checksum (if applicable) Yes. ### Image file download link (if applicable) _No response_ ### What happened? Updating from 1.1.01 to 1.103 seems to have wiped the entire disk or at least the partiton table. The disk had 1 exfat ventoy partition, 1 EFI partition and 1 luks partition. After this update the partition table changed to 'Unknown (PMBR)' in gnome disk. I downgraded to 1.1.01 which was possible but did not fix the problem. Ventoy still sees the installed version but gparted and gnome disk do not recognize the partition table. Seems it even damaged the backup partition table. Repair with gdisk seems to be successful. I can mount Ventoy and the luks partition again and on first sight, all the files seem to be there. gdisk report: GPT fdisk (gdisk) version 1.0.9 Caution! After loading partitions, the CRC doesn't check out! Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables. Warning! One or more CRCs don't match. You should repair the disk! Main header: OK Backup header: OK Main partition table: ERROR Backup partition table: ERROR Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged