Alternate GPT header not at the end of the disk.

[jdogcoder]

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!

 

[drackg]

i have same problem , i did clone whole disk from smaller to bigger.. thanks for any advise

 

[leesteken]

Please show the whole command. Also, don't use fdisk for GPT; use gdisk instead. GParted Live might also help sometimes.

 

[drackg]

root@px0:~# gdisk -l
GPT fdisk (gdisk) version 1.0.9

Problem opening -l for reading! Error is 2.
The specified file does not exist!
root@px0:~#

root@px0:~# gdisk
GPT fdisk (gdisk) version 1.0.9

Type device filename, or press <Enter> to exit:


thanks a lot

 

[Kingneutron]

gdisk is not the same as fdisk, you have to give it a device name e.g. /dev/sdX

Usually if you cloned a smaller disk to larger with dd instead of clonezilla or the like, you may just need to rewrite the partition table to the disk from gdisk and it should correct the error message

 

[drackg]

root@px0:~# gdisk /dev/sda -l
GPT fdisk (gdisk) version 1.0.9

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

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Model: Samsung SSD 870
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): D9D52C5C-1868-4824-97BE-BAA05DB1FEAD
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 468862094
Partitions will be aligned on 8-sector boundaries
Total free space is 0 sectors (0 bytes)

Number Start (sector) End (sector) Size Code Name
1 34 2047 1007.0 KiB EF02
2 2048 2099199 1024.0 MiB EF00
3 2099200 468862094 222.6 GiB 8E00

many thanks for help

 

[drackg]

root@px0:~# gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.9

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

Found valid GPT with protective MBR; using GPT.

Command (? for help): i
Partition number (1-3): 1
Partition GUID code: 21686148-6449-6E6F-744E-656564454649 (BIOS boot partition)
Partition unique GUID: B6EB0DB7-9369-4306-A888-BB52B33B04F0
First sector: 34 (at 17.0 KiB)
Last sector: 2047 (at 1023.5 KiB)
Partition size: 2014 sectors (1007.0 KiB)
Attribute flags: 0000000000000000
Partition name: ''

Command (? for help): i
Partition number (1-3): 2
Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI system partition)
Partition unique GUID: 6F7054CC-0F30-4341-927D-1B91F264B5E8
First sector: 2048 (at 1024.0 KiB)
Last sector: 2099199 (at 1025.0 MiB)
Partition size: 2097152 sectors (1024.0 MiB)
Attribute flags: 0000000000000000
Partition name: ''

Command (? for help): i
Partition number (1-3): 3
Partition GUID code: E6D6D379-F507-44C2-A23C-238F2A3DF928 (Linux LVM)
Partition unique GUID: CCE1CD4E-59FB-4BDC-B441-5A98F05EAEC8
First sector: 2099200 (at 1.0 GiB)
Last sector: 468862094 (at 223.6 GiB)
Partition size: 466762895 sectors (222.6 GiB)
Attribute flags: 0000000000000000
Partition name: ''

 

[Kingneutron]

Inside gdisk, enter ' w ' to Write partition table to disk - issue ' ? ' for help

Expanding LVM partition 3 to encompass the rest of the disk is best done from a recovery environment with gparted
https://distrowatch.com/table.php?distribution=systemrescue

After that, you may need to use LVM console commands to expand filesystems