A customer came in last month with a 2TB external drive that macOS refused to read. Three years of project files, all apparently gone. The dialog box was offering to initialise or eject. They nearly clicked initialise. Within about 25 minutes we had the GUID partition table repaired and the drive mounting cleanly, data intact. Knowing how to fix corrupted GPT macOS without reaching for the format button is one of those skills that saves people from genuine disasters, and it's what this guide covers step by step.
TL;DR
To fix corrupted GPT macOS without formatting: start with a different cable and port, then run Disk Utility First Aid on the physical disk (not just the volume), then try diskutil repairDisk /dev/diskX in Terminal. If those fail, boot into macOS Recovery and run First Aid from there. Only format as a last resort.
Key Takeaways
- Fix corrupted GPT macOS is possible without formatting when corruption is mild to moderate
- Always click Eject, never Initialise, when macOS shows the unreadable disk dialog
- Disk Utility First Aid targets the physical disk level, not just the volume
diskutil repairDiskgoes deeper than the GUI and can fix partition-map issues First Aid misses- macOS Recovery mode repairs disks that fail in normal mode because fewer processes are competing for disk access
- If all non-destructive methods fail, data recovery requires third-party tools before reformatting
At a Glance
- Difficulty: Medium to Advanced
- Time Required: 15 to 45 mins
- Success Rate: 40 to 70% depending on GPT damage severity
What Causes Fix Corrupted GPT macOS Situations in the First Place?
The GUID Partition Table lives in the first and last sectors of a drive. macOS writes a primary GPT header near the start and keeps a backup copy at the very end. When both copies are intact and consistent, macOS reads the partition map cleanly and mounts your volumes. When one or both copies get corrupted, macOS sees what looks like an unformatted block device and throws up that familiar "not readable" dialog.
The most common cause, by a long way, is yanking the cable before the drive has finished writing. File copies and Time Machine backups update the GPT metadata as they run. Pull the cable mid-write and you can end up with a partial or inconsistent partition table. This is why the error often appears the morning after a late-night backup that you unplugged in a hurry.
Hardware problems are the second big cause. A dodgy USB cable, a cheap enclosure with a failing bridge chip, or a drive that isn't getting enough power can all produce intermittent disconnects. Each disconnect is a potential partial write. Over time, those accumulate into GPT corruption that looks identical to a software problem but doesn't respond to software fixes.
Less common but worth knowing: some drives ship with vendor-specific encryption (SanDisk Secure Access, WD SmartWare, Seagate Toolkit). macOS sees only the encrypted container, not the underlying GPT, until you unlock it through the vendor's software. This isn't actually GPT corruption, it just looks like it. And then there's the case where someone formatted the drive on Windows using MBR rather than GUID Partition Map, which macOS handles differently and sometimes refuses to mount at all.
Finally, macOS itself occasionally glitches. A USB stack reset or an SMC oddity can prevent a perfectly healthy drive from mounting. This is rare but worth ruling out early, because the fix is just a reboot.
Fix Corrupted GPT macOS: Quick Fixes First
Before you touch Terminal or run any repair commands, work through these. They take five minutes and they solve the problem more often than you'd expect.
Physical Connection and Basic Checks Easy
- Swap the cable and port
Disconnect the drive. Try a different USB-C or Thunderbolt port on your Mac, and use a different cable if you have one. If you're going through a hub, connect directly to the Mac instead. Hubs are surprisingly often the culprit, especially with power-hungry 3.5-inch HDDs. - Check external power
Large HDDs in desktop enclosures need a mains adapter. If the adapter is loose or failing, the drive may spin up but fail to complete the GPT read. Make sure it's properly connected. - Test on another computer
Plug the drive into another Mac or a Windows PC. If it mounts there, the problem is macOS-side (SMC glitch, USB stack issue, Finder settings) rather than actual GPT damage. A reboot of your Mac will often fix this. - Check Finder settings
Open Finder, go to Finder > Settings > General and Sidebar. Make sure "External disks" is ticked. It sounds obvious but this catches people out more than it should. - Restart the Mac
Eject the drive if possible, restart macOS, then reconnect after login. Minor USB stack issues clear with a reboot.
For partition-level work beyond what macOS's built-in tools offer, a dedicated partition manager application can sometimes reconstruct a damaged GPT by reading the backup header at the end of the drive and rebuilding the primary. macOS's own tools don't expose this directly.
Fix Corrupted GPT macOS with Disk Utility
Disk Utility is the right first stop for actual GPT repair. Most people use it wrong though. They select the volume (the indented item in the sidebar) rather than the physical disk. For GPT-level issues you need the top-level physical disk entry.
Disk Utility First Aid on the Physical Disk Medium
- Open Disk Utility with all devices visible
Go to Applications > Utilities > Disk Utility. In the menu bar choose View > Show All Devices. You'll now see the physical disk at the top level with any volumes indented beneath it. If you only see volumes, you're in the wrong view. - Select the physical disk
Click the top-level entry for your external drive. It will show something like "2 TB External" with the manufacturer name. Check the Scheme field at the bottom. It should say GUID Partition Map. If it says Master Boot Record or shows nothing, that tells you something important about what macOS is seeing. - Run First Aid
Click First Aid in the toolbar, then click Run when the confirmation dialog appears. Disk Utility will check the partition map structure, verify the GPT header and backup header consistency, and attempt to repair any issues it finds. This can take anywhere from 30 seconds to several minutes depending on drive size. - Read the result carefully
If First Aid reports success, eject the drive, wait ten seconds, and reconnect it. If it reports errors it could not repair, note the exact message. "Filesystem verify or repair failed" means the partition map is too damaged for Disk Utility to fix via the GUI. Move to the Terminal steps below. - Try manual unmount and remount
If the drive appears in Disk Utility but won't auto-mount, select the volume, click Unmount, wait five seconds, then click Mount. Some volumes with partially intact GPTs won't auto-mount but will respond to a manual mount command.
According to Apple's Disk Utility documentation, First Aid checks both the partition map and the filesystem, and attempts to repair both. But it has limits. The GUI version can't always reconstruct a GPT from the backup header, which is where Terminal comes in.
Advanced Fix Corrupted GPT macOS via Terminal
This is where you get proper control. The diskutil command-line tool performs deeper partition-map inspection and repair than the Disk Utility GUI exposes. It's not scary if you follow the steps carefully. The key rule: identify your disk correctly before running any repair command. Running repairDisk on the wrong disk identifier won't erase data, but it's sloppy and wastes time.
diskutil verifyDisk and repairDisk Advanced
- Open Terminal and list all disks
Go to Applications > Utilities > Terminal. Run:diskutil list
This prints every disk and partition macOS can see. Your external drive will appear as something like/dev/disk2or/dev/disk3. Look for the size and name to confirm which one it is. If the drive shows asGUID_partition_schemewith partitions listed, the GPT is at least partially readable. If it shows as a single entry with no partitions or says "Unknown", the GPT is badly damaged. - Verify the disk first
Run:diskutil verifyDisk /dev/diskX(replace diskX with your actual identifier, e.g. disk2). This scans the partition map and reports errors without changing anything. Read the output. Common messages include "Partition map appears to be OK", "Invalid GPT partition entry size", or "Corrupt partition map". The specific error tells you how bad the damage is. - Attempt partition map repair
If verifyDisk found errors, run:diskutil repairDisk /dev/diskX
This attempts to fix partition-map and structural issues, including some GPT header inconsistencies. It can also repair the protective MBR that macOS uses alongside the GPT. The process usually takes under a minute. After it completes, rundiskutil listagain to see if the partition structure now looks correct. - Repair individual volumes if they're visible
Ifdiskutil listshows volumes (e.g./dev/disk2s1), you can target filesystem-level issues separately. Run:diskutil verifyVolume /dev/disk2s1thendiskutil repairVolume /dev/disk2s1. This addresses APFS or HFS+ corruption that can prevent mounting even when the GPT itself is intact. - Check if the drive mounts
After running repairDisk and repairVolume, rundiskutil listone more time. If the volumes now show correctly, try:diskutil mount /dev/disk2s1to mount the volume manually. If it mounts, back up your data immediately.
diskutil eraseDisk or diskutil partitionDisk at this stage. Those commands will destroy your data. Stick to verifyDisk, repairDisk, verifyVolume, and repairVolume only.macOS Recovery Mode Disk Utility Advanced
- Boot into Recovery
On Intel Macs: restart and hold Command + R until the Apple logo or spinning globe appears. On Apple silicon Macs: shut down completely, then press and hold the Power button until you see "Loading startup options", then click Options > Continue. Recovery mode loads with a stripped-down environment that gives Disk Utility more freedom to make repairs. - Run First Aid from Recovery
Choose Disk Utility from the macOS Utilities screen. Select your external drive's physical disk entry (View > Show All Devices if needed), click First Aid, and run it. Apple's support page on using Disk Utility in Recovery confirms this can repair disks that fail in normal mode because macOS isn't actively using the disk subsystem. - Restart and test
After First Aid completes in Recovery, restart into normal macOS and reconnect the drive. Check whether it mounts. If it does, back up immediately.
If all four solution tiers above have failed, the GPT is likely too damaged for macOS's built-in tools to reconstruct. At that point, dedicated partition manager software can sometimes read the backup GPT header at the end of the drive and rebuild the primary table from it, which is something diskutil doesn't expose directly. Apple's technical note on partition schemes explains how the backup GPT header works and why it's the key to recovery when the primary is gone.
If the data is genuinely critical and nothing has worked, professional data recovery is the next step, not formatting. Formatting at this point makes professional recovery harder and more expensive.
GPT corruption and unreadable external drives are something we fix remotely every week. If you've worked through the Disk Utility and Terminal steps above and the drive still won't mount, connect with us and we'll run the diagnostics live on your Mac.
Get remote helpPreventing Fix Corrupted GPT macOS Problems
Most GPT corruption is preventable. Here's what actually matters, in order of importance.
Always eject properly. This is number one. Finder > Eject, or right-click > Eject, every single time before you unplug. It's not just about flushing the file cache. macOS also writes a clean GPT update on eject. Skip this step and you're gambling every time.
Never unplug during a Time Machine backup or a large file copy. The status bar in Finder shows active copies. Wait for it to finish. This one habit eliminates the majority of GPT corruption cases we see.
Format Mac-only drives as APFS or Mac OS Extended (Journaled) with GUID Partition Map. For cross-platform drives, use exFAT with GUID Partition Map (not MBR). Mixing partition schemes and filesystems creates compatibility headaches that look like corruption but aren't.
Invest in decent cables and enclosures. A cheap no-brand USB-C cable that cuts out intermittently will corrupt a GPT eventually. It's not a matter of if. Quality cables from reputable brands cost a few pounds more and save you hours of repair work.
Keep macOS updated. Point releases regularly include improvements to disk handling, APFS journaling, and USB stack reliability. Running an outdated macOS on a machine that handles external drives regularly is unnecessary risk.
Back up. Time Machine to a separate drive, or any backup strategy you'll actually use. A corrupted GPT on a drive that has a current backup is a minor inconvenience. On a drive with no backup, it's a potential disaster.
Fix Corrupted GPT macOS: What We've Covered
To fix corrupted GPT macOS without formatting, you work through three tiers. Start with physical checks (different cable, port, another computer) because hardware problems masquerade as GPT corruption constantly. Move to Disk Utility First Aid on the physical disk, not just the volume. If that fails, use diskutil verifyDisk and diskutil repairDisk in Terminal for deeper partition-map repair. If that still fails, boot into macOS Recovery and run First Aid from there, where the repair environment is cleaner. Only if all four approaches fail should you consider that the GPT is beyond macOS's built-in repair capability, at which point dedicated partition manager software or professional recovery services are the options left.
The single most important thing: when that "not readable" dialog appears, click Eject. Not Initialise. You've got options to fix corrupted GPT macOS without losing your data, but only if you don't erase it first.
Quick Reference Summary
- Tier 1 (5 mins): Different cable, port, reboot, check Finder settings
- Tier 2 (15 mins): Disk Utility > Show All Devices > select physical disk > First Aid
- Tier 3 (30 mins): Terminal:
diskutil verifyDisk /dev/diskXthendiskutil repairDisk /dev/diskX - Tier 4 (45 mins): Boot Recovery Mode > Disk Utility > First Aid on physical disk
- After any successful repair: Back up data immediately before using the drive further


