Restoring a volume encounters GPT disk initialization failure in the CentOS-based boot environment

Summary

When booting into the CentOS-based environment and restoring a volume to a bare metal disk, the disk is initialized as MBR instead of GPT, even when GPT is chosen. This leads to the failure of the recovery task.

Causes

This issue arises when conducting Volume Recovery to a bare metal disk. 

Workaround

GPT disk initialization works correctly in the WinPE-based boot environment. For Volume Recovery from a Windows image to a bare metal disk, perform it after booting into the WinPE-based boot environment. When restoring from a Linux image, follow specific initialization steps before starting Volume Recovery, except when restoring a disk (no additional operation required).

1) GUI — Utilities — Open Terminalく
2) Use “lsblk” command to check the device to restore a backup image

[root@AIPBE ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 1.1G 1 loop loop1 7:1 0 6G 1 loop ├─live-rw 253:0 0 6G 0 dm / └─live-base 253:1 0 6G 1 dm loop2 7:2 0 32G 0 loop └─live-rw 253:0 0 6G 0 dm / sda 8:0 0 40G 0 disk sr0 11:0 1 1.3G 0 rom

3) In this example, since "sda" represents the device, execute the command to inspect the partition table. 

[root@AIPBE ~]# parted -l Error: /dev/sda: unrecognised disk label Model: VMware Virtual disk (scsi) Disk /dev/sda: 42.9GB Sector size (logical/physical): 512B/512B Partition Table: unknown Disk Flags:

Initialize to GPT.

[root@AIPBE ~]# parted /dev/sda mklabel gpt

Display the partition table again and make sure [gpt] is indicated.

[root@AIPBE ~]# parted -l Model: VMware Virtual disk (scsi) Disk /dev/sda: 42.9GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags:

After initializing the partition table, perform Volume Recovery.

Target Product

– Every released (CentOS-based) boot environment

(13451118539673)