My external hard drive suddenly shows as unallocated in Disk Management, and I believe it was using a GPT partition table. I haven’t formatted it because I need to recover the lost partition and files safely. What’s the best way to restore the GPT partition without making the data harder to recover?
First thing: stop using that drive. Don’t copy anything to it, don’t install recovery tools on it, don’t run Diskpart “clean,” nothing. If it’s your boot drive, power down and use a live USB. If it’s a second drive or external disk, unmount it or unplug it until you’re ready to work on it. The files may still be there, but new writes can overwrite the stuff you’re trying to get back.
You may have a decent shot here because GPT disks keep a backup partition header at the end of the drive. That doesn’t guarantee recovery, but it gives you more to work with than an old MBR-style layout in some cases.
If you have another drive with enough free space, make a full sector-by-sector image first. That’s the safest move. Use dd, ddrescue, or a commercial imaging tool if that’s more comfortable. Then do the recovery work on the image instead of the original disk. If something goes wrong, you still have the untouched source drive.
For a more practical approach, recovery software is usually the least painful option. When the partition table is damaged or deleted, the OS may act like the files are gone, but the actual data is often still sitting on the disk.
Disk Drill is a solid choice for this kind of GPT partition problem. It can scan the physical drive directly, look for lost partitions and file system signatures, and let you preview files before recovering them. It also handles common file systems like NTFS, FAT32, and exFAT, and can work with drives that show up as RAW.
The basic flow is:
- Choose the physical disk, not just a visible volume.
- Run “Search for lost data.”
- Check the “Existing” and “Reconstructed” results.
- Recover anything important to a different drive.
If you want to try repairing the partition table itself, look at TestDisk or gdisk, but be careful. TestDisk can scan for old partition signatures and rewrite the partition entries if it finds the right ones. The scan itself is safe enough, but once you choose “Write,” it changes the disk. Don’t do that unless the detected partition layout clearly matches what you had before.
gdisk is useful for GPT-specific damage. Since GPT stores a backup header at the end of the disk, gdisk can sometimes rebuild the main header from that backup. That can help when the beginning of the disk is what got corrupted.
One more thing: if Windows shows the disk as a “GPT Protective Partition,” don’t immediately convert it, clean it, or initialize it. That can happen after a strange hardware change, a USB dock issue, or a sector-size mismatch. Running “clean” in Diskpart wipes the partition table, which makes recovery harder. Get the files off first with something like Disk Drill, then worry about fixing the disk layout.
8 Likes
Do not initialize the disk just because Windows offers to “fix” it. Before spending hours scanning, I’d rule out the boring hardware side: try a different USB cable, port, and if it is in an enclosure, a different dock/enclosure if possible. Some USB bridges report sector size differently, and that can make a perfectly valid GPT disk look wrong or unallocated. If it still shows the same way, then I agree with the safer approach above: image it first if you can, then scan the image or physical disk with TestDisk/Disk Drill and recover files to another drive. I would not write a rebuilt GPT back to the original until the important files are copied elsewhere.
The first number to check is whether Windows still reports the correct total disk size for the external drive.
If it is a 4 TB drive and Disk Management shows roughly 3.6 TB unallocated, that points more toward a lost or damaged partition map. If it shows 0 bytes, 2 TB, some weird tiny size, or keeps appearing and disappearing, stop treating it like a partition recovery job. That is more likely a USB bridge, enclosure, firmware, or drive health problem, and scanning it for 12 hours may just stress a failing disk.
I agree with the “don’t initialize it” advice, but I’d be careful with another common mistake too: don’t run CHKDSK on it. CHKDSK is for repairing a file system Windows can already understand. On a disk that suddenly shows unallocated, it can make a mess if the partition boundaries or file system metadata are already wrong.
Before trying to rebuild GPT, I’d check these in this order:
- Does the disk show the correct physical size?
- Does it make clicking, disconnect randomly, or freeze Disk Management?
- Can a SMART tool read its health through the USB enclosure?
- Was the drive ever BitLocker encrypted?
- Was it used on a Mac, NAS, Linux box, TV, or game console before Windows saw it as unallocated?
That fourth point gets missed a lot. If the old partition was BitLocker encrypted, some recovery tools may find file signatures but not recover useful filenames or folder structure unless the volume metadata is intact and you have the recovery key. In that case, rebuilding the partition entry correctly matters more than doing a generic file carve.
If the disk size is correct and the drive seems stable, then scanning is reasonable. Pick the physical disk, not a random “unallocated volume,” and preview before paying for anything. Disk Drill, R-Studio, DMDE, UFS Explorer, GetDataBack, and TestDisk all approach this a bit differently. Disk Drill is easier for non-technical users, but I would not buy any tool until it shows you recognizable files in preview. If you’re comparing paid tools, recent Disk Drill user reviews may be worth reading, but the preview result on your actual drive matters more than reviews.
My personal order would be: image first if the data is important, scan the image, recover files to a different disk, then worry about repairing the partition table. Rebuilding the GPT first is tempting because it feels cleaner, but it is the riskier path if you are guessing. A “successful” partition repair that uses the wrong start sector can make Windows ask to format it or show a broken file system, and then people start trying more fixes on top of fixes.
If you use TestDisk, pay close attention to the partition start and end values it finds. Don’t write anything just because it found something with the right file system label. A leftover old partition from a previous format can look convincing. The right result should match the size, file system, and rough layout you remember.
If the drive is noisy, very slow, disconnecting, or throwing read errors, skip the DIY repair attempts and clone with ddrescue or consider a recovery shop. Software recovery assumes the drive can be read reliably enough. When the hardware is failing, every long scan is another pass over damaged media.
Do not create a new simple volume on it to “give Windows something to mount.” That writes fresh partition/file system metadata, and on a recoverable disk it can turn a clean lost-partition case into a partial overwrite case.
A detail I don’t see stressed enough is to separate “partition recovery” from “file recovery.” If the files matter more than making the drive usable again, don’t make the goal “get the old drive letter back.” Make the goal “copy the data off.” After that, you can wipe, repartition, test the drive, or replace the enclosure without worrying about making things worse.
Before writing any repair, take screenshots or notes of what tools report: disk size, sector size, any found partition start/end sectors, file system type, and volume label. This sounds boring, but it helps when two tools find different “lost” partitions. A stale NTFS partition from years ago can look surprisingly valid, especially on a drive that has been reformatted before.
Disk Drill is fine if you want the easier route, but use it as a recovery tool first, not as a “fix my partition table” button. Scan the physical disk, preview real files, then save them to another drive. If it only finds random carved files with no folder names, that usually means it did not reconstruct the original file system well, or the metadata is damaged. In that case I would try a second tool before paying or writing anything back.
For GPT repair specifically, be extra suspicious if the drive was moved between USB enclosures or docks. Some bridges report a slightly different size or sector layout. GPT keeps backup data at the end of the disk, so if the “end” appears to move, repair tools may complain or offer to relocate headers. That can be correct, but it can also be the wrong fix for the wrong enclosure. I’d rather test the drive in the original enclosure if possible, recover the important data, then rebuild the disk from scratch.