My Oracle Support Banner

Oracle Linux: Beginning Disk Data Could Be Potentially Destroyed Accidentally If Using GPT Partitions (Doc ID 2063720.1)

Last updated on MAY 06, 2021

Applies to:

Linux OS - Version Oracle Linux 5.10 to Oracle Linux 6.6 [Release OL5U10 to OL6U6]
Oracle Cloud Infrastructure - Version N/A and later
Information in this document applies to any platform.

Symptoms

There are several symptoms which may be caused by broken data at the beginning of the disk:

  1. /dev/mdX (raid device) can not be mounted.
  2. Raw data on the disk is destroyed.
  3. LVM can not be configured.
  4. MS-DOS type MBR and partition tables are replaced to GPT.
  5. This is not an exhaustive list.

When the disk has/had a GPT (GUID partition table) like: 

 

Changes

A "perfect storm" where all the following occur could cause data loss at the beginning of the disk:

  1. The disk had had GPT and the beginning of the disk was changed by commands like dd(10), mdadm(8), pvcreate(8) or fdisk(8)
  2. The disk now has both of GPT and other data on the top
  3. Someone runs parted(8) command on the disk; simply attempting a read (such as "parted --script --list") is sufficient.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.