Oracle Linux: Beginning Disk Data Could Be Potentially Destroyed Accidentally If Using GPT Partitions
(Doc ID 2063720.1)
Last updated on JUNE 24, 2020
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.
There are several symptoms which may be caused by broken data at the beginning of the disk:
- /dev/mdX (raid device) can not be mounted.
- Raw data on the disk is destroyed.
- LVM can not be configured.
- MS-DOS type MBR and partition tables are replaced to GPT.
- This is not an exhaustive list.
When the disk has/had a GPT (GUID partition table) like:
A "perfect storm" where all the following occur could cause data loss at the beginning of the disk:
- 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)
- The disk now has both of GPT and other data on the top
- Someone runs parted(8) command on the disk; simply attempting a read (such as "parted --script --list") is sufficient.
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