My external hard drive suddenly stopped mounting on my Mac, even though it was working fine before. It shows power, but I can’t access my files, and Disk Utility isn’t helping much. I’m worried this could mean drive failure or possible data loss, so I need help figuring out what to check next and whether I should be concerned.
I hit this a while back on my Mac, plugged in an external drive, and got nothing. No Finder icon. No volume on the desktop. Dead quiet. It feels bad fast, but I’ve learned not to treat silence like a death notice. A lot of the time the drive is still there, macOS and the drive just aren’t talking cleanly.
First thing I check is the dumb stuff, because the dumb stuff keeps winning. If your drive is connected through a hub, remove the hub and plug it straight into the Mac. Older portable HDDs especially can be picky about power. I also swap the cable and move to a different port. I once burned almost two hours on a “failed” drive and the cause was a bad USB-C cable with a tiny fault inside. If the drive LED comes on, or you feel the disk spin or vibrate, that usually means it’s getting power, which is better than a fully inert brick.
After that, I look at Finder before touching repair tools. macOS sometimes mounts the drive but hides it from view. Open Finder, then Settings, or Preferences on older macOS versions. Under General, make sure External disks is enabled. Then check the Sidebar tab and make sure external disks are allowed there too. I know, it sounds too simple. Still worth checking. I’ve seen people miss this.
If Finder settings look fine and the drive still doesn’t appear, go to Disk Utility. This is the part where I slow down. If the files matter, don’t start clicking random repair options. I’ve seen people go straight to First Aid or, worse, Erase, and turn a recoverable mess into a wiped one. When a drive appears in Disk Utility but won’t mount, I usually assume file system damage before full hardware failure.
At this point I try to get the data off first. That order matters. macOS is strict about mounting. A small file system problem is enough for it to give up. Recovery tools don’t rely on the same mount process, they read the drive at a lower level and pull files directly from the sectors.
I’ve had the best luck with Disk Drill for this kind of case. It handles unmounted, corrupted, and uninitialized drives better than Finder does. On a decent scan, I’ve seen it rebuild most of the folder tree and show files in place instead of dumping nonsense filenames everywhere. The byte to byte backup feature is the part I’d use first if the drive seems unstable. You make an image of the disk, then scan the image instead of stressing the original hardware again and again. Safer move. I also check previews before recovering anything large, because previews tell you fast if the files are intact or half-broken. Once the data is copied out, then I mess with repairs.
If your files are already safe, or you don’t care about them, I’d move on to stronger fixes.
- Open Terminal and run sudo pkill -f fsck
Sometimes macOS starts a background disk check after an unsafe unplug. That fsck process is supposed to help, but I’ve seen it hang and block the drive from mounting. Killing it has made a drive appear right away for me. Feels a bit janky, but it works often enough to keep in mind.
- Reset low-level hardware settings if you’re on Intel
For Intel Macs, I’d try an NVRAM reset or SMC reset. USB weirdness sometimes traces back to system settings at that level. On Apple Silicon, I wouldn’t overthink it. A plain restart fixes a lot of this stuff.
- Reformat the drive if recovery is done and nothing else worked
Back in Disk Utility, click Show All Devices so you see the physical disk, not only the volume under it. Select the actual drive and hit Erase. Pick APFS if the drive stays in the Mac world. Pick exFAT if you move files between macOS and Windows. This wipes the disk and writes a fresh file system. If the issue was corruption, this often clears it. If it still fails after a clean format, I’d start suspecting hardware.
My rule is simple. Save the data first. Repair later. Drives are replaceable. Files aren’t. If the disk still shows signs of life, I’d try recovery with Disk Drill before doing anything destructive. That order has saved me more than once.
3 Likes
Power but no mount does not always mean the drive is dead. It often means macOS sees the hardware but fails at the file system layer.
I’d check System Information, not Finder or Disk Utility first. Apple menu, About This Mac, System Report, then USB or Thunderbolt. If the drive shows there with a model number and capacity, the port bridge is alive. If it does not, I’d suspect the enclosure, adapter board, or cable path before the disk itself.
One thing I disagree with from @mikeappsreviewer, I would not start by killing fsck unless you already know it is stuck. Better to confirm what macOS sees.
Open Terminal and run:
diskutil list
If your external drive appears as something like /dev/disk2, run:
diskutil info /dev/disk2
Look for:
Mounted: No
File System Personality
S.M.A.R.T. status, if shown
Read-Only Media: Yes or No
If the disk appears but the volume will not mount, try:
diskutil mountDisk /dev/disk2
If macOS returns an error like ‘wrong fs type’ or ‘invalid b-tree node size’, you are dealing with file system damage, not full death. At tht point stop forcing mounts.
Also check if the enclosure is the problem. Pull the drive from the USB enclosure only if it is a standard SATA disk and you know what you are doing. I have seen the USB-SATA bridge fail while the bare drive was fine. Put it in a new enclosure or SATA dock and it shows up right away.
If the data matters, clone first or scan with Disk Drill before repair attempts. Disk Drill is one of the better Mac options for an external hard drive that shows in diskutil but will not mount. Better move than poking Disk Utility over and over.
If you want a step by step visual, this Mac external hard drive not mounting video guide walks through the fixes cleanly.
If the drive clicks, spins down, disappears from diskutil, or stalls the Mac when plugged in, thne I’d start thinking hardware failure. At that stage, stop testing it over and over.
Power but no mount does not automatically mean the drive is dead. Sometimes the disk is fine and the thing failing is the file system, the enclosure board, or macOS refusing to mount a dirty volume.
I’d add a couple checks that @mikeappsreviewer and @waldgeist didn’t really lean on:
- Try it on another Mac or even a Windows PC. If another machine sees it, that tells you a lot fast.
- If it mounts there, copy data off imediately and stop troubleshooting on the first Mac.
- In Console.app, plug the drive in and watch live logs. You’ll sometimes see messages like I/O errors, bridge reset failures, or “media not present,” which points more toward hardware/enclosure than filesystem.
- If it’s an older spinning HDD, listen carefully. Repeating clicks, spin-up/spin-down loops, or long pauses are bad signs.
I also wouldn’t assume Disk Utility “First Aid” is harmless. Sometimes it helps, sometimes it makes a messy file system even messier. If the files matter, recovery first is still the smarter move. Disk Drill is solid for Mac external hard drive recovery when the drive shows up but won’t mount, especially if you want to scan before doing anything destructive.
One more angle: permissions and encryption. If it’s an APFS or HFS+ drive that was encrypted, macOS may see the container but not properly unlock it. Same if the drive was last used on a different macOS version and got left in a weird state.
If the drive appears, disappears, freezes Finder, or causes beachballs, stop plugging it in over and over. That’s the point where “just test one more thing” turns into “cool, now it’s worse.”
Also, if you want extra reading, this covers more fixes for an external hard drive not mounting on Mac pretty well.
One angle missing from @waldgeist, @nachtdromer, and @mikeappsreviewer is power negotiation. A drive can light up yet still not get enough stable current to initialize data properly, especially 2.5-inch HDDs on bus power. If it has an optional power adapter, use it. If it uses a Y-cable, that matters too.
I’d also check this in Terminal:
log stream --predicate 'process == 'kernel'' --info
Then plug the drive in. You may catch timeout, eject, or USB reset messages that Disk Utility hides.
Another thing: if the enclosure supports USB only, but the bare disk is healthy, SMART often will not pass through correctly. So “no SMART shown” is not proof either way.
I slightly disagree with jumping to repair logic too early. If the drive is making new noises or mounting intermittently, image it first. Disk Drill is useful there.
Disk Drill pros: good at seeing unmounted volumes, byte-to-byte backup, Mac-friendly UI.
Disk Drill cons: deeper scans can be slow, preview/recovery success depends on filesystem damage, not a miracle fix for bad hardware.
If the disk mounts read-only anywhere, that’s actually good news. Copy first, diagnose later.