Alternate GPT header not at the end of the disk.


New Member
Sep 5, 2023
FSDISK shows

GPT PMBR size mismatch (40689663 != 62922751) will be corrected by write.
The backup GPT table is not on the end of the device.
Disk /dev/mapper/pve-vm--110--disk--0: 30 GiB, 32216449024 bytes, 62922752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 8A49268C-6948-4D42-A28B-C234361988B6

Device                                   Start      End  Sectors  Size Type
/dev/mapper/pve-vm--110--disk--0-part1  227328 40689630 40462303 19.3G Linux filesystem
/dev/mapper/pve-vm--110--disk--0-part14   2048    10239     8192    4M BIOS boot
/dev/mapper/pve-vm--110--disk--0-part15  10240   227327   217088  106M EFI System

Partition table entries are not in disk order.

This is on several VMs, preventing boot.

Any help would be GREATLY appreciated!


The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!