I have just done a fresh Proxmox installation, and then installed a single VM (Home Assisant using this install script).
My
What is causing this on such a newly installed system, is it anything to worry about, and how can I fix it?
Here is the full fdisk output:
My
fdisk -l output shows the following error message with regards to the new vm-100-disk-1 partition (which is part of the data LV thin pool):
Code:
The backup GPT table is corrupt, but the primary appears OK, so that will be used.What is causing this on such a newly installed system, is it anything to worry about, and how can I fix it?
Here is the full fdisk output:
Code:
root@proxmox:~# fdisk -l
Disk /dev/sda: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: TOSHIBA THNSNF12
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 49AE1637-198C-4F93-9F85-7975515950C4
Device Start End Sectors Size Type
/dev/sda1 34 2047 2014 1007K BIOS boot
/dev/sda2 2048 2099199 2097152 1G EFI System
/dev/sda3 2099200 250069646 247970447 118.2G Linux LVM
Disk /dev/mapper/pve-swap: 7.58 GiB, 8141144064 bytes, 15900672 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/pve-root: 16 GiB, 17179869184 bytes, 33554432 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/pve-backups_internal: 16 GiB, 17179869184 bytes, 33554432 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/pve-vm--100--disk--0: 4 MiB, 4194304 bytes, 8192 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
Disk /dev/mapper/pve-vm--100--disk--1: 32 GiB, 34359738368 bytes, 67108864 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: 42C47CE3-4843-478A-925D-294B2EB17D52
Device Start End Sectors Size Type
/dev/mapper/pve-vm--100--disk--1-part1 2048 67583 65536 32M EFI System
/dev/mapper/pve-vm--100--disk--1-part2 67584 116735 49152 24M Linux filesystem
/dev/mapper/pve-vm--100--disk--1-part3 116736 641023 524288 256M Linux filesystem
/dev/mapper/pve-vm--100--disk--1-part4 641024 690175 49152 24M Linux filesystem
/dev/mapper/pve-vm--100--disk--1-part5 690176 1214463 524288 256M Linux filesystem
/dev/mapper/pve-vm--100--disk--1-part6 1214464 1230847 16384 8M Linux filesystem
/dev/mapper/pve-vm--100--disk--1-part7 1230848 1427455 196608 96M Linux filesystem
/dev/mapper/pve-vm--100--disk--1-part8 1427456 67108830 65681375 31.3G Linux filesystem
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/sdb: 223.57 GiB, 240057409536 bytes, 468862128 sectors
Disk model: SA400S37240G
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: F9CB94C0-B87F-4FED-98DE-802144BC90EB
Device Start End Sectors Size Type
/dev/sdb1 65535 468862094 468796560 223.5G Linux filesystem
root@proxmox:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
backups_internal pve -wi-ao---- 16.00g
data pve twi-aotz-- 50.00g 12.83 14.28
root pve -wi-ao---- 16.00g
swap pve -wi-ao---- 7.58g
vm-100-disk-0 pve Vwi-aotz-- 4.00m data 0.00
vm-100-disk-1 pve Vwi-aotz-- 32.00g data 20.05