My external hard drive suddenly stopped mounting on my Mac, even though it powers on and shows up in Disk Utility. I already tried restarting, switching cables and ports, and running First Aid, but it still won’t open. I need help figuring out what to try next because I have important files on this drive and I’m worried about losing data.
I hit this on my Mac more than once, and yeah, it feels bad. You plug in an external drive and get nothing. No desktop icon. No Finder entry. Silence. I’ve had drives look dead, then turn out fine after one small fix. A lot of the time, macOS is the part acting weird, not the drive itself.
Start with the boring stuff first. I know. Still worth it.
Method 1: Check the connection before doing anything else
I wasted an evening once because the problem was a flaky cable. The drive was fine.
- Unplug the drive from your Mac.
- If it goes through a hub, dock, or adapter, remove all of that and plug it straight into the Mac.
- Try another USB or Thunderbolt port.
- Swap in a cable you already trust.
- Test the drive on another Mac or PC if you have one nearby.
- Watch for signs of life, spinning, vibration, LEDs, startup noise. If it powers on, you at least know it is getting power.
If the drive stays dead on two machines with two cables, I’d start suspecting hardware. If it powers up but won’t show, keep going.
Method 2: Make sure Finder isn’t hiding it
This one is dumb, but I’ve seen it. The drive mounts, Finder still acts like it does not exist.
- Open Finder.
- Go to Finder > Settings. On older macOS versions, this is Finder > Preferences.
- Open the General tab.
- Make sure External disks is checked.
- Open the Sidebar tab.
- Check External disks there too.
- Go back to Finder and look again.
I missed this once after a clean macOS setup. Felt kinda silly, but there it was.
Grab your files first with Disk Drill
If the drive shows up in Disk Utility but refuses to mount, I would pull data off it before trying repair tools. I’ve seen people run First Aid right away, or wipe the disk, then realize their files were the only thing they cared about.
Disk Drill does one useful thing here. It reads the drive more directly, so you are not waiting for macOS to mount it cleanly first.
- Install and open Disk Drill.
- Find the unmounted drive in the device list.
- If the drive seems unstable, use Byte-to-byte Backup first and make a full image.
- Wait for the image to finish. This part can take a while.
- Scan either the original drive or the image file.
- Look through the recovered results.
- Use preview to check your important files.
- Pick what you want back.
- Save recovered files to another drive. Do not write them back to the same problem disk.
Once your files are somewhere safe, you’ve got room to mess with fixes without sweating every click.
Kill a stuck fsck process
I ran into this one after a drive was unplugged without ejecting. macOS started checking the file system in the background and then seemed to get stuck forever. The disk would not mount until I killed the process.
- Open Terminal.
- Run: sudo pkill -f fsck
- Enter your admin password if macOS asks for it.
- Wait a few seconds.
- See if the drive mounts on its own.
I’ve had a drive pop back up almost immediatly after this. Strange fix, but it worked.
Reset NVRAM on Intel, or restart if you use Apple Silicon
Storage issues sometimes tie back to low-level system settings. Not often, but I’ve seen enough weird Mac behavior to keep this on the list.
For Intel Macs:
- Shut the Mac down.
- Press the power button.
- Right away, hold Option + Command + P + R.
- Keep holding for about 20 seconds.
- Let go and let the Mac boot.
- Reconnect the drive and test again.
For Apple Silicon Macs:
- Unplug the drive.
- Restart the Mac normally.
- Wait until macOS fully loads.
- Reconnect the drive.
Nothing fancy there. Still, I had one SSD start behaving after a restart when nothing else changed. Macs are weird sometims.
Reformat the drive if your data is already safe
If all the earlier steps fail, and your files are recovered, wiping the disk is the last clean shot. I only do this after data is off the drive.
- Open Disk Utility.
- Click View > Show All Devices.
- Select the physical disk, not one of the volumes under it.
- Click Erase.
- Give it a name. Pick APFS for Mac-only use. Pick exFAT if you need it to work on both macOS and Windows.
- Run the erase process and wait.
When it finishes, unplug the drive, reconnect it, and see if it mounts normally.
If a fresh format completes and the drive still refuses to mount, I’d stop blaming software. At that point, the hardware is the likely problem. You can keep poking at it, sure, but replacing the drive is often the better move.
The main lesson I learned from this stuff is simple. Save the data first. Repair the disk second. You can replace storage. Your files are a different story.
3 Likes
If the drive shows in Disk Utility, I’d stop poking Finder and look at the mount state and file system first. @mikeappsreviewer covered the common stuff well, but I would not kill fsck right away. If macOS is checking damage, stopping it too fast sometimes makes a messy disk worse.
Try this instead.
Open Disk Utility, click View, Show All Devices. Look at the volume name under the physical disk. If it is gray, select it and click Mount. If Mount fails, note the exact error.
Then open Terminal and run:
diskutil list
Find your external disk identifier, like disk4s2. Then run:
diskutil info /dev/disk4s2
Check three things.
File System Personality
Mount Point
Read-Only Media
If the format says NTFS, macOS often reads it but gets weird after corruption. If it says unrecognized or Windows_LDM, the partition map may be the issue, not the drive hardware.
Next, try a manual mount:
sudo mkdir -p /Volumes/testdrive
sudo mount -t hfs /dev/disk4s2 /Volumes/testdrive
Swap hfs for apfs or exfat if needed. If manual mount fails, the error text matters.
Also check Console.app while plugging the drive in. Filter for diskarbitrationd or fsck. I fixed one drive after seeing repeated I/O errors there. Turned out the enclosure board was dying, not the disk itself.
If your goal is file recovery first, Disk Drill is a fair pick since it often reads disks macOS refuses to mount. That’s the route I’d take before erase attempts.
For SEO terms, this is basically an external hard drive not mounting on Mac because of file system errors, partition map damage, macOS mount issues, or enclosure failure.
This thread might help if you hit error 49153:
Mac external drive error 49153 fixes people tried
If Disk Utility sees the physical disk but size shows wrong, or SMART fails, I’d start planning for drive replacement. That’s usally the point where software fixes stop working.
If it shows in Disk Utility but still won’t actually mount, I’d check one thing neither @mikeappsreviewer nor @kakeru really leaned on much: whether the volume is only failing in your user session.
Try mounting it from a different macOS account, or boot into Safe Mode and plug it in there. If it mounts in Safe Mode, the disk itself may be fine and some background login item, third-party NTFS helper, antivirus, sync app, or old kernel extension is blocking Disk Arbitration. I’ve seen Paragon/Tuxera leftovers and backup tools cause exactly this kinda nonsense.
Also, in Disk Utility, make sure the container/volume structure looks normal. Sometimes the physical disk is visible, but the actual APFS container is borked. If the parent disk appears healthy but the child volume won’t mount, that points more to file system metadata than dead hardware.
Another thing: if the drive is in an external enclosure, remove the disk and test it in a different enclosure or SATA-to-USB adapter if possible. This gets overlooked a lot. The enclosure can fail while the actual drive is still okay. Happens way more than people think.
If the files matter, stop trying random repair stuff and recover first. Disk Drill is solid for an external hard drive not mounting on Mac because it can often scan a drive that Finder refuses to open. If you want a decent breakdown of what it does, this page is useful: see how Disk Drill helps recover files from unreadable drives.
One small disagreement with @mikeappsreviewer: I would not jump to reformat unless you’ve either recovered the data or confirmed the disk is expendable. Once you erase, the convo changes fast lol.