My external hard drive suddenly stopped mounting on my Mac, even though it still shows up in Disk Utility. I have important files on it and really want to avoid formatting if there’s any way to repair it first. I’m looking for safe troubleshooting steps or recovery options that might help without erasing the drive.
I hit this on my Mac with an external drive, and the first few minutes were the worst part. You plug it in, wait for the icon, and nothing shows. No volume on the desktop. No files. It feels bad fast. Still, I would not assume the disk is dead from minute one. A lot of the time, the problem sits between the drive, the cable, and macOS.
Start with the dumb stuff first, because I skipped it once and wasted half my night.
Physical checks matter more than people think. If your drive is connected through a USB hub, unplug it and connect it straight to the Mac. Some hubs do a poor job with power delivery, mostly with older hard drives with spinning platters. Swap the cable too. Swap the port. I had one USB-C cable look fine on the outside and fail only with storage devices. Phone charged, drive did not mount. Annoying.
If the drive powers on, that helps. A light, a hum, a little vibration, any of those signs mean the disk is at least getting power.
Then check Finder, because macOS hides stuff in ways I still find dumb.
Open Finder, then Finder > Settings. On older macOS versions, it says Preferences. Under General, make sure External disks is enabled. Then open Sidebar and make sure external disks are enabled there too. I have seen people think a drive vanished when Finder was simply set not to show it.
If Finder settings look fine, move to Disk Utility.
This is the point where I would slow down. If the files on the drive matter, do not start clicking repair tools at random. I have watched people run First Aid or erase the disk too early and turn a recoverable mess into a clean empty drive. If the drive appears in Disk Utility but refuses to mount, I usually assume file system damage first, not total hardware failure.
When I cared about the data, I treated recovery as step one, not repair.
The reason is simple. macOS wants the file system to look clean enough to mount. Recovery tools do not rely on the normal mount process in the same way. They read the disk more directly and often pull files even when Finder gives you nothing.
I had decent results with Disk Drill for drives in this exact state. Unmounted, corrupted, weirdly half-visible in Disk Utility, stuff like tht. A scan often shows the old folder layout, which makes sorting through the mess easier. The byte-to-byte backup option is worth using if the disk seems unstable. I prefer scanning an image file over poking at failing hardware over and over. If the preview shows your files intact, pull the important data first. Repair comes later.
If your files are safe already, or you do not care about them, then I’d try the rougher fixes.
- Open Terminal and run sudo pkill -f fsck
Sometimes macOS starts a background disk check after an unsafe unplug. That fsck process can hang and block the drive from mounting. I have seen a disk appear right after killing it. Feels stupid, but it works often enough to keep in mind.
- Reset low-level settings if you use an Intel Mac
On Intel models, reset NVRAM or SMC. Those resets clear some hardware-related state and sometimes fix USB weirdness. On Apple Silicon Macs like M1, M2, or M3, a normal restart usually does the same kind of cleanup.
- Reformat the drive if recovery is done and nothing else helped
Go back to Disk Utility. Click View, then Show All Devices. Pick the physical disk, not only the volume underneath it. Hit Erase. If the drive stays on Mac only, use APFS. If you move between Mac and Windows, use exFAT. This wipes the disk and creates a new file system. If the problem was corruption, this often gets the drive usable again. If it still fails after a clean format, I would start suspecting the hardware.
My order is always the same now.
Check power, cable, port, and hub.
Check Finder visibility settings.
Look in Disk Utility.
Recover files first with something like Disk Drill.
Try fsck kill, restart, or reset.
Erase only after the data is handled.
That order saved me once. The drive looked dead, but the files were still there. If yours is showing any sign of life, I would treat it like a recovery job before a repair job.
2 Likes
If it shows in Disk Utility, I’d try mount diagnostics before any repair pass. I differ a bit from @mikeappsreviewer on First Aid. I would not rule it out too early if the drive looks stable and isn’t clicking.
Do this in Terminal first:
diskutil list
Find the external volume identifier, then run:
diskutil info /dev/diskXsY
Look for File System Personality, Read-Only Media, and Mount Point. If macOS says the volume is unmountable but the partition map looks fine, try:
diskutil mountDisk /dev/diskX
If only the volume fails:
diskutil mount /dev/diskXsY
If mount throws an error, note the exact text. Error 49153 often points to file system issues. Error 49218 shows up with APFS damage. Those details matter.
Next, in Disk Utility, select the parent disk and check S.M.A.R.T. status if it appears. If it says Failing, stop writing to it. Clone first.
If the disk is NTFS, macOS often reads it but gets weird after unsafe ejects or Windows Fast Startup. Plug it into a Windows PC and run chkdsk there. Mac repair tools won’t do much for NTFS.
If your files matter, Disk Drill is a solid next move. I’d use it to scan or make a byte-for-byte backup before more tests. Safer route, less risk of makin it worse.
Also useful, this step by step Mac external drive repair video walks through the main fixes in a clean way.
One more thing people miss. Check Console while plugging the drive in. USB or I/O errors there often expose a failing enclosure, not a dead disk. Swap the enclosure if it’s a SATA drive inside. I’ve fixed two drives that way, no format, no data loss.
If it shows in Disk Utility, I’d test whether the volume is broken or the bridge/enclosure is the real problem. That part gets missed a lot in these threads, even by @mikeappsreviewer and @nachtschatten.
A few things I’d do that are different:
- Open System Information > USB and see if the drive identifies normally there. If macOS sees a weird generic USB bridge with missing details, the enclosure may be flaking out.
- If it’s a desktop-style external or a 2.5’ SATA drive in a case, try a different enclosure/dock. I’ve had “dead” drives mount instantly once the cheap USB-SATA board was replaced. Super common.
- Run in Terminal:
log show --last 10m --predicate 'process == 'kernel''
then plug the drive in and look for I/O errors, disconnect loops, or bridge resets. - Boot into Safe Mode once and test mounting there. It can rule out third-party junk interfering with disks.
- If Disk Utility shows the partition but not the filesystem cleanly,
sudo gpt -r show /dev/diskXcan tell you whether the partition map itself is mangled.
I actually disagree a bit with the “don’t touch First Aid at all” vibe. If the drive is stable, not clicking, and you’ve already made a clone or recovered critical stuff with Disk Drill, one careful First Aid pass is reasonable. Not ten passes. One. People love turning a small problem into a bigger one by retrying the same failed repair over and over.
Also, if the drive was ever used with Windows, check whether it was encrypted with BitLocker or had permissions weirdness. Macs can “see” a disk in Disk Utility while Finder still acts clueless. Seen it before, looked like corruption, wasn’t.
If the data matters most, I’d still put Disk Drill near the top because it can scan unmounted external drives on Mac and often pull files before you gamble on repairs.
Also worth reading: more tips for fixing an external hard drive that won’t mount on a Mac
If the drive is making clicking sounds though, stop. At that point every extra minute can make things worse, and DIY fixes get real dumb real fast.
One thing I’d add to what @nachtschatten, @andarilhonoturno, and @mikeappsreviewer covered is to check whether the drive is mounting but being hidden by macOS security rules, not just filesystem damage.
Open Terminal and run:
mount
and
ls /Volumes
Sometimes the volume appears there even when Finder refuses to show it properly. If it does, try copying critical files in Terminal first before doing any repair.
I’d also check permissions/quarantine weirdness with:
diskutil info /dev/diskX
and look for Owners and Writable status. I disagree a little with jumping quickly to resets or repeated mount attempts. If the enclosure is browning out, every retry can make the drive drop offline again.
A good low-risk test is another Mac. If it behaves the same on two machines, the problem is likely on the drive side. If it mounts elsewhere, your Mac’s USB stack or login items may be the culprit.
If the data matters, Disk Drill makes sense before any aggressive repair.
Pros of Disk Drill
- good at scanning unmounted drives
- can preview recoverable files
- byte-to-byte backup is useful if the disk is unstable
Cons
- deep scans can be slow
- recovery quality depends on how damaged the filesystem is
- full recovery usually requires the paid version
My order would be: test on another Mac, check /Volumes, copy anything accessible, then use Disk Drill, then consider First Aid once the important files are safe. If the drive disconnects during reads, stop and suspect hardware.