The backup GPT table is not on the end of the device

Rocky Linux Help & Support
1

Hello,

I installed Rocky Linux 9.6 on a server with six physical disks: two SAS, two SATA SSD and two NVMe.

The SAS and SATA SSD disks are connected to a physical RAID controller. I created two RAID groups for these disks and installed the OS.
The NVMe disks have a RAID group created based on Intel VROC.

After installing the OS, I ran the ‘fdisk -l’ command, and the results are as follows:

The backup GPT table is not on the end of the device.
Disk /dev/nvme0n1: 2.91 TiB, 3200631791616 bytes, 6251233968 sectors
Disk model: INTEL SSDPF2KE032T1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 967E9FC1-7912-4ABB-B183-6507AA3E6273

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 4294977535 4294975488 2T Linux LVM
The backup GPT table is not on the end of the device.

Disk /dev/nvme1n1: 2.91 TiB, 3200631791616 bytes, 6251233968 sectors
Disk model: INTEL SSDPF2KE032T1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 967E9FC1-7912-4ABB-B183-6507AA3E6273

Device Start End Sectors Size Type
/dev/nvme1n1p1 2048 4294977535 4294975488 2T Linux LVM
Disk /dev/sdb: 558.41 GiB, 599584145408 bytes, 1171062784 sectors
Disk model: SAS3916
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: 23E66FBF-E562-4B7A-8D56-9F9F20413C81

Device Start End Sectors Size Type
/dev/sdb1 2048 1230847 1228800 600M EFI System
/dev/sdb2 1230848 3327999 2097152 1G Linux filesystem
/dev/sdb3 3328000 772999167 769671168 367G Linux LVM

Disk /dev/sda: 1.75 TiB, 1919816826880 bytes, 3749642240 sectors
Disk model: SAS3916
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: E900C318-A6AF-40F6-A32F-C1F17C935573

Device Start End Sectors Size Type
/dev/sda1 2048 2147493887 2147491840 1T Linux LVM

Disk /dev/mapper/vg–os-root: 200 GiB, 214748364800 bytes, 419430400 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/vg–os-swap: 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

Disk /dev/md126: 2.77 TiB, 3040599867392 bytes, 5938671616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 967E9FC1-7912-4ABB-B183-6507AA3E6273

Device Start End Sectors Size Type
/dev/md126p1 2048 4294977535 4294975488 2T Linux LVM

Disk /dev/mapper/vg–index-commvault_index: 1 TiB, 1099511627776 bytes, 2147483648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes

Disk /dev/mapper/vg–os-var_tmp: 15 GiB, 16106127360 bytes, 31457280 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/vg–os-var_log: 30 GiB, 32212254720 bytes, 62914560 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/vg–os-home: 20 GiB, 21474836480 bytes, 41943040 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/vg–os-tmp: 30 GiB, 32212254720 bytes, 62914560 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/vg–os-var: 30 GiB, 32212254720 bytes, 62914560 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/vg–os-var_log_audit: 10 GiB, 10737418240 bytes, 20971520 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/vg–ddb-commvault_ddb: 2 TiB, 2199023255552 bytes, 4294967296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

I found the following article, but I’m not sure if this is normal behaviour when RAID is configured based on Intel VROC: After building RAID in RSTe mode (IMSM), there will be an error when executing partprobe - Red Hat Customer Portal

Thank you in advance for your help!