My drive suddenly shows as unallocated in Disk Management, and it was using a GPT partition table. I’m trying to recover the lost GPT partition without formatting or overwriting any data. What’s the safest way to restore the partition and access my files?
When a drive suddenly shows up as “Unallocated” or “RAW,” don’t panic and don’t start clicking repair options right away. With GPT disks, the partition info often has some redundancy, so the files may still be sitting there even if Windows can’t read the partition normally anymore.
The big thing is to stop writing to that drive. Don’t format it. Don’t make a new partition. Don’t run Diskpart clean. Don’t copy anything onto it. Even one bad write can overwrite file system data or partition records that recovery tools might need.
If the data matters, try not to work on the original disk directly.
First, make a sector-by-sector image of the drive if you can. Tools like dd or ddrescue are commonly used for that because they copy the disk at the block level, not just the visible files. That way you can run recovery attempts on the image instead of experimenting on the physical drive. If something goes wrong, you still have the original state to go back to.
After that, recover the files before trying to fix the partition table. For most people, that’s the safer order. Rebuilding GPT first can work, but if you write the wrong partition layout, you can make the mess worse.
A tool like Disk Drill can be a reasonable choice if you want something more straightforward than command-line tools. It can scan for lost partitions, damaged GPT data, and known file signatures, and the scan itself is read-only. Once it finds files, preview them and recover them to a different physical drive. Do not save recovered files back onto the damaged disk.
Once your important files are copied somewhere safe, then it makes sense to look at GPT repair.
TestDisk is a common option for this. It can search for lost partitions and, if it finds the correct one, write the partition table back so the volume shows up again. Just be careful with the “Write” step. That is the point where you are actually changing the disk.
gdisk is another tool worth knowing about. GPT disks keep a backup GPT header at the end of the drive, so if only the main GPT header is damaged, gdisk may be able to rebuild it from that backup.
If Windows shows the disk as a “GPT Protective Partition,” that also doesn’t automatically mean the data is gone. Sometimes that happens because of an older system, a bad USB adapter, or Windows simply not reading the GPT layout correctly.
So the short version is: don’t use Diskpart clean unless you are completely done with the data. Image the disk if possible, scan it with recovery software, copy the files to another drive, and only then think about repairing the partition structure.
1 Like
The drive’s health matters before any GPT repair attempt. If this is a spinning hard drive making odd noises, dropping offline, or showing bad SMART values, don’t run long partition scans on it over and over because that can finish off a failing disk. I agree with the image-first advice, but I’d check SMART status and use a stable direct SATA/USB connection before trusting any results. A bad USB enclosure can make a perfectly good GPT disk look unallocated too, especially with larger drives. Try another cable/port/enclosure first, then image or scan. If the drive is healthy, tools like TestDisk or Disk Drill are fine for finding the old partition, but don’t write a “fixed” GPT until the found start/end sectors actually match the old volume size.
Do not click “Initialize Disk” if Windows offers it. That dialog looks harmless, but it is Windows asking to write a new partition table. If the old GPT is only damaged or being read wrong, initializing can turn a recoverable layout into a harder recovery job.
A detail that gets missed a lot: make sure the disk is being seen with the same geometry as before. If this is an external drive that was removed from its original USB enclosure, dock, NAS, or RAID box, put it back the way it was before you assume the GPT is gone. Some USB bridges translate sector sizes or hide part of the disk. GPT stores a backup header at the end of the disk, so if the reported disk size changes, repair tools can get confused and say the backup GPT is invalid even when the data area is fine.
Before trying to restore anything, I would check these boring details:
- Is this the same machine/adapter where the drive worked before?
- Does the disk size shown in Disk Management match the real size of the drive?
- Does the drive appear in Device Manager without disconnecting/reconnecting?
- Is there any sign it used to be BitLocker, Storage Spaces, dynamic disk, RAID, or part of a NAS?
- Are you looking at the physical disk, not just a missing drive letter?
That last one sounds silly, but Windows sometimes shows a volume as inaccessible for a totally different reason than “the partition is gone.” If the partition exists but has no letter, that is a different fix than rebuilding GPT. If the whole disk is truly unallocated, then yes, you are in recovery territory.
I agree with the earlier advice about imaging first, but I’d be stricter about the order: do not “repair” the GPT just because a tool found something that looks plausible. A found partition starting at the right sector but ending at the wrong place can overlap old metadata, recovery partitions, or another volume. If you had a single NTFS data partition, the start sector is often the clue. If there were multiple partitions, EFI, MSR, Windows, recovery, etc., guessing gets risky fast.
For a safer path, I’d do it like this:
- Disconnect the drive until you have another disk large enough to hold an image or recovered files.
- If the drive is healthy enough, clone/image it sector by sector.
- Scan the image or clone, not the original.
- Recover important files to a third drive.
- Only after that, consider writing a repaired GPT.
TestDisk is useful here, but the dangerous button is still “Write.” The scan is not the scary part. Writing the partition table is. Before writing, compare the found partition size and type with what you remember. For example, if you had a 2 TB data drive and it finds a tiny partition or several strange overlapping ones, don’t accept the first result just because it has files listed.
Disk Drill and similar GUI recovery tools are fine if your goal is to get files out first. The honest caveat is that they are recovery tools, not magic undo buttons. If the file system metadata is damaged, some files may come back without original names or folder structure. That is still better than accidentally writing a bad GPT and reducing your options.
BitLocker is another edge case. If the old partition was encrypted, many recovery scans may look like garbage unless the partition boundary is restored correctly or the tool understands the encrypted volume. In that case, don’t assume “no files found” means the data is gone. It may just mean the tool is scanning encrypted blocks without the right context.
The safest “restore” is really two separate jobs: preserve the current state, then recover data, then repair the partition table if you still want the disk bootable/readable again. If the files are important and you do not already have a clone, I would not make the first write to that disk be a GPT repair attempt. That is the gamble everyone regrets when the partition was almost correct but not quite.
Do not let Windows “fix” it on boot. If this was the system drive, pull it and work from another machine or a live USB, because automatic repair, chkdsk, indexing, and antivirus scans can all write to a disk you are trying to preserve. GPT repair comes after you have a clone or the files copied out, not before.