When restoring a volume, initialization to GPT disk fails in (CentOS-based) boot environment
After booting into (CentOS-based) boot environment and when restoring a volume to bare metal disk, the disk is initialized to MBR though GPT is selected. As a result recovery task fails.
This known issue occurs when performing Volume Recovery to bare metal disk.
Initialization to GPT disk is correctly performed in (WinPE-based) boot environment. Please perform Volume Recovery from Windows image to bare metal disk after booting into (WinPE-based) boot environment.
When restoring from Linux image, please take the following initialization procedures before starting Volume Recovery.
* When restoring a disk, this operation is not 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, as “sda” indicates the device, run the following command.
Check 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.
– Every released (CentOS-based) boot environment