Exadata dom0 no longer able to boot after fixing partition table using parted (Doc ID 2470999.1)

Last updated on SEPTEMBER 27, 2021

Applies to:

Symptoms

We added disk expansion kit to Virtualized Exadata X6-2 system and RAID rebuild happened automatically.

Then we followed steps from documentation "5.14.3 Expanding /EXAVMIMAGES on Management Domain on Releases Earlier than 12.2.x" to finish the setup.

After re-starting the dom0 it was no longer able to boot:

Intel(R) Boot Agent XE v2.3.34
Copyright (C) 1997-2014, Intel Corporation

CLIENT MAC ADDR: 00 10 E0 B3 B0 78 GUID: 080020FF FFFF FFFF FFFF 0010E0B3B078
PXE-E53: No boot filename received

PXE-M0F: Exiting Intel Boot Agent.

Intel(R) Boot Agent XE v2.3.34
Copyright (C) 1997-2014, Intel Corporation

CLIENT MAC ADDR: 00 10 E0 B3 B0 78 GUID: 080020FF FFFF FFFF FFFF 0010E0B3B078
PXE-E53: No boot filename received

PXE-M0F: Exiting Intel Boot Agent.

Intel(R) Boot Agent XE v2.3.34
Copyright (C) 1997-2014, Intel Corporation

CLIENT MAC ADDR: 00 10 E0 B3 B0 78 GUID: 080020FF FFFF FFFF FFFF 0010E0B3B078
DHCP.....-

Changes

Fixed the partition table as described in above documentation section "6 Run parted to verify the partition size. If you see a request to fix the GPT, respond with F."

[root@#####dm01 db]# parted /dev/sda print
Error: The backup GPT table is not at the end of the disk, as it should be. This might mean that another operating system
believes the disk is smaller. Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? Fix
Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all of the space (an extra
4679680000 blocks) or continue with the current setting?
Fix/Ignore? Fix

Then the "Error. The backup GPT table is not at the end..." is gone:

[root@#####dm01 db]# parted -s /dev/sda print

Model: LSI MR9361-8i (scsi)
Disk /dev/sda: 4193GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 32.8kB 537MB 537MB ext3 primary boot
2 537MB 123GB 122GB primary lvm
3 123GB 1797GB 1674GB primary

Cause