WORKS2011
asked on
Accessing GPT Protected Disk and Preserving Data
ASKER
This isn't true, it's connected to a WIN10 Pro computer and I don't believe you understand my question. GPT vs GPT Protected.
ASKER
From the article,
...a GPT disk will be supported (GPT Protective Partition will not appear) by all computers with 64-bit operating systems, including Windows XP Professional and Windows Server 2003.
Can a disk be both GPT and MBR?https://docs.microsoft.com/en-us/previous-versions/windows/hardware/design/dn640535(v=vs.85)#gpt_faq_why_mbr_with_gpt
No. However, all GPT disks contain a Protective MBR.
What is a Protective MBR?
The Protective MBR, beginning in sector 0, precedes the GPT partition table on the disk. The MBR contains one type 0xEE partition that spans the disk.
Why does the GPT have a Protective MBR?
The Protective MBR protects GPT disks from previously released MBR disk tools such as Microsoft MS-DOS FDISK or Microsoft Windows NT Disk Administrator. These tools are not aware of GPT and do not know how to properly access a GPT disk. Legacy software that does not know about GPT interprets only the Protected MBR when it accesses a GPT disk. These tools will view a GPT disk as having a single encompassing (possibly unrecognized) partition by interpreting the Protected MBR, rather than mistaking the disk for one that is unpartitioned.
Why would a GPT-partitioned disk appear to have an MBR on it?
If this occurred, you must have used an MBR-only-aware disk tool to access the GPT disk.
EASUS does have a procedure to recover your files https://www.easeus.com/resource/recover-data-from-gpt-protective-partition-windows-10.html
I'd rather use gparted https://gparted.org/
Probably got a 32 bit version of Windows 10.
As far as Win2003 and XP GPT support was introduced in a servicepack for the 64 bit versions.
As far as Win2003 and XP GPT support was introduced in a servicepack for the 64 bit versions.
ASKER
WIN10 is 64 bit. I'm aware of the drive history and how they were converted to protected GPT. I pulled them from a RAID controller. If this helps they were never read from a workstation or server without a RAID controller. They come from a RAID1 configuration.
If they cone from a hardware RAID controller then the RAID metadata will be on the first few sectors so the partition data will be offset from sector zero. That's why Windows can't cope with it. There are several programs that can allow for that offset - captain nemo from runtime.org etc.
ASKER
As stated,
Is there a faster way to access the data?Please see original question. As many of you have posted threads how GPT works, etc, it's not what I'm looking for.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>Please see original question.
Why? You didn't provide the essential information that it was from a RAID controller until today. Captain Nemo would work fine, it can cope with offset sectors since it is used in conjunction with RAID reconstructor.
Why? You didn't provide the essential information that it was from a RAID controller until today. Captain Nemo would work fine, it can cope with offset sectors since it is used in conjunction with RAID reconstructor.
https://www.partitionwizard.com/partitionmagic/gpt-protective-partition.html