My external hard drive suddenly stopped mounting on my Mac, and I need to recover important files from it as soon as possible. It shows up inconsistently, but I can’t open it or access my data. I’m looking for help with Mac external hard drive not mounting, possible fixes, and safe file recovery steps before I make things worse.
I’ve hit this Mac drive mess more than once, usually when I needed the disk right then. The annoying part is the drive often isn’t dead. A lot of the time, macOS refuses to mount it because the file system got a little messy, and the Mac decides to stop talking to it.
Before you do anything bigger, check the boring stuff first. I know, everyone skips it. I did too. Then it turned out to be a bad cable.
Start here:
1. Swap the USB cable.
2. Plug the drive straight into the Mac, not a hub.
3. Try another port.
4. Open Finder settings and make sure external disks are set to show under General and Sidebar.
If the drive light is on or you hear it spin up, the hardware still has a shot.
The fastest fix is erasing the drive, but that wipes everything. So if the files matter, stop thinking about repair for a minute. Pull the data off first. I learned this one the hard way years ago with a project folder I thought was safe. It was not lol.
macOS tends to reject drives with even small file system errors. When that happens, recovery tools sometimes read the disk even when Finder and Disk Utility won’t mount it properly. I’ve had the best luck with Disk Drill. It usually spots drives sitting there unmounted, grayed out, or marked uninitialized.
If you use it, make a byte-to-byte backup first. Do not skip it if the files matter. A full clone gives you a safer copy to scan, so you aren’t hammering the original drive over and over. After scanning, preview the files and recover them to your Mac or to another disk. Once the data is safe, then mess with repairs.
What I try first in Disk Utility
One thing trips people up. They click the broken volume, not the full physical disk above it.
Do this:
1. Open Disk Utility.
2. Click View in the top left.
3. Pick Show All Devices.
4. Select the top-level drive, usually labeled with the brand name like WD or Seagate.
5. Run First Aid there.
If the partition map was the issue, the drive sometimes mounts right after.
When fsck gets stuck
If the drive was yanked without ejecting, macOS might still be running a file system check in the background. I’ve seen this block mounting with no clear warning.
Steps:
1. Open Terminal.
2. Run sudo pkill -f fsck
3. Enter your password.
If fsck was hung, the drive often appears a few seconds later.
Intel Mac only, reset the controllers
This one helped me on an older Intel MacBook when USB got flaky for no obvious reason. On Apple silicon, a normal restart handles this sort of reset on its own.
NVRAM reset:
1. Shut the Mac down.
2. Turn it back on.
3. Hold Option + Command + P + R for around 20 seconds.
SMC reset:
1. Shut it down.
2. Unplug power for 15 seconds.
3. Plug it back in.
4. Wait 5 seconds.
5. Turn it on.
On some Intel MacBooks, you hold Shift + Control + Option + Power for 10 seconds instead.
Manual mount in Terminal
When Disk Utility acts dumb, Terminal sometimes gives a cleaner answer.
1. Open Terminal.
2. Run diskutil list
3. Find your drive identifier, something like disk4s1
4. Run diskutil mount /dev/disk4s1 with your own identifier
If it mounts, Terminal says so. If it fails, the error text often points to the real problem, which is more useful than Disk Utility’s vague nonsense.
If none of it works
At that point I usually stop fighting it and format the drive, but only after recovery is done.
In Disk Utility:
1. Select the drive.
2. Click Erase.
3. Pick APFS if the drive stays with Macs only.
4. Pick exFAT if you need Mac and Windows both.
This fixes most logical corruption issues. The big rule is simple. Recover first, erase second. If you reverse those steps, you’ll hate yourself later. I did.
2 Likes
If the drive shows up off and on, I would stop trying random mounts and focus on reading SMART and system logs first. I disagree a bit with @mikeappsreviewer on one point, killing fsck is not where I’d start. If the disk is unstable, interrupting checks over and over can make the situation messier.
Do this instead.
- Open System Information, go to USB or Thunderbolt, see if the enclosure appears every time you reconnect it.
- Open Terminal and run:
diskutil list
diskutil info /dev/diskX
Replace X with your disk number. - Check S.M.A.R.T. status if the bridge exposes it. If it says failing or unsupported, note it.
- Open Console and filter for I/O error, diskarbitrationd, or eject. Repeated I/O errors usually point to hardware, not file system damage.
- If it is a desktop external, test a diff power supply if you have one. Undervoltage causes weird mount issues more oftne than people think.
- If it is in a cheap USB enclosure, remove the bare drive and connect it with a different SATA to USB adapter. I’ve seen the enclosure fail while the disk itself was fine.
For recovery, Disk Drill is still a solid pick when Finder refuses to open the volume. I’d scan only after you confirm the connection is stable for more than a few minutes.
If the data matters a lot, skip erase and skip repeated First Aid runs.
Also, this thread has solid Mac-specific troubleshooting for unreadable externals:
best fixes for an external hard drive not mounting on Mac
If it’s showing up inconsistently, I’d treat this like a failing connection or enclosure before assuming the file system is the only problem. @mikeappsreviewer covered the usual mount/repair path, and @espritlibre is right about checking logs, but I’d add one thing people miss all the time: test the drive on another Mac before doing more scans on this one. That instantly tells you if your Mac is being weird or the drive/enclosure is.
Also, if the external has a removable case, the USB bridge board may be the actual problem. I’ve had “dead” externals come back the second I pulled the bare SATA drive and connected it with a different adapter. Super annoying, but very real.
Another angle: if the drive is NTFS formatted, macOS may see it but act flaky with third-party NTFS drivers installed. I’d uninstall or disable any old NTFS helper tools first. Those can cause strange mount failures.
If your files matter, don’t keep forcing First Aid over and over. One pass, maybe. Ten passes, nope. That’s how people turn “recoverable” into “welp.”
For recovery, Disk Drill is still one of the better options on Mac because it can often read drives that won’t mount normally. If you want a simple walkthrough, this Disk Drill recovery tutorial for Mac external drives is worth a look.
My order would be:
- Test on another Mac
- Try a different enclosure/adapter
- Check whether it’s NTFS + bad driver conflict
- Recover with Disk Drill
- Repair or erase only after data is safe
Do not format it yet. Seriously, dont.
I’m slightly less sold on repeated SMART/log digging as the next move if the drive is only appearing intermittently. Useful, yes, but if the bridge chip is browning out or the partition table is half-readable, you can burn a lot of time collecting clues without getting files off.
What I’d do that complements what @espritlibre, @sonhadordobosque, and @mikeappsreviewer already covered:
- Check Disk Utility for whether the physical device appears with 0 bytes, wrong capacity, or “Not Initialized.” That points more toward enclosure/bridge or serious media trouble than a simple mount issue.
- In Terminal, try read-only verification instead of repair-first thinking:
diskutil verifyDisk /dev/diskXdiskutil verifyVolume /dev/diskXsY
Verification is lower risk than jumping straight into repair.
- If the drive ever mounts for even 30 seconds, copy the irreplaceable small stuff first. Docs, photos, work files. Don’t start with giant video folders.
- If the disk clicks, spins down, disappears, or remounts itself, stop. That’s where DIY gets expensive.
On recovery apps, Disk Drill makes sense here if the drive can stay visible long enough to image or scan.
Pros
- Good at seeing unmounted/lost partitions on Mac
- Easy preview of recoverable files
- Byte-to-byte backup option is actually useful
Cons
- Deep scans can be slow
- Recovery quality drops hard if hardware is unstable
- Not magic if the enclosure or drive keeps disconnecting
If it were mine: verify, grab critical files immediately, then use Disk Drill on a clone if possible. Repair later, never first.