How can I fix an external drive not mounting on Mac without reformatting?

Data Recovery
1

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 need to access the data without erasing or reformatting the drive. I’m looking for safe ways to troubleshoot an external drive not mounting on Mac and recover access if possible.

2

I know this one too well. You plug in an external drive and macOS acts like nothing happened. No desktop icon. Nothing in Finder. No folder tree, no warning, no clue. It feels bad fast. Still, I wouldn’t assume the disk is finished yet. I’ve had this happen on my own Macs, and more than once the disk itself was fine. The connection, Finder settings, or a stalled system process was the thing breaking it.

Start with the easy stuff first. I’ve wasted time going straight to repair tools and missed a bad cable.

Method 1: Rule Out the Connection

This is the boring check, but it saves time.

  1. Unplug the external drive from your Mac.
  2. If it’s going through a hub, adapter, or dock, remove all of that and plug it straight into the Mac.
  3. Switch to another USB or Thunderbolt port.
  4. Swap in a cable you already know works.
  5. Try the drive on another Mac, or even a Windows PC if that’s what you have nearby.
  6. Watch for signs of life, spinning, vibration, indicator LEDs, any startup noise. If it powers on, you at least know it’s getting electricity.

I’ve had one case where the only problem was a cheap cable from a drawer. Looked fine. Wasn’t.

Method 2: Check Finder

Sometimes the drive is mounted and Finder is the one hiding it.

  1. Open Finder.
  2. Go to Finder > Settings. On older macOS versions, it’s Finder > Preferences.
  3. Open the General tab.
  4. Make sure External disks is turned on.
  5. Then open the Sidebar tab.
  6. Make sure External disks is enabled there too.
  7. Go back to Finder and see if the drive shows up.

Yeah, it feels dumb when this fixes it, but it does happen.

Recover the Files First with Disk Drill

If the disk shows up in Disk Utility but won’t mount, I’d pull files off before trying repairs. I’ve seen people run First Aid, then erase, then realize the only copy of their photos was on that disk. Bad order.

Disk Drill reads the device more directly, so it doesn’t depend on macOS mounting the disk in the usual way.

  1. Install and open Disk Drill.
  2. Find the unmounted drive in the list.
  3. If the disk seems unstable, use Byte-to-byte Backup first and make a full image.
  4. Wait until the image is finished.
  5. Scan either the original drive or the image file.
  6. Look through the recovered results.
  7. Preview important files to check if they open right.
  8. Select what you want back.
  9. Save recovered files to another drive. Don’t write them back to the troubled disk.

Once your data is somewhere safe, you’ve got room to test fixes without making things worse.

Stop a Hung fsck Process

One odd macOS issue I keep seeing is a stuck file system check. If the system thinks the disk was removed the wrong way, it might start fsck in the background and then sit there forever.

  1. Open Terminal.
  2. Run: sudo pkill -f fsck
  3. Press Return.
  4. Enter your admin password if macOS asks for it.
  5. Wait a few seconds and see whether the drive mounts.

I’ve seen drives pop up almost right after killing that process. Feels random, but it works often enough to try.

Reset NVRAM on Intel, or Restart Apple Silicon

Sometimes the problem sits higher up in the system. Storage settings and hardware state get weird once in a while.

For Intel Macs:

  1. Shut the Mac down.
  2. Press the power button.
  3. Right away, hold Option + Command + P + R.
  4. Keep holding for around 20 seconds.
  5. Let go and allow the Mac to start normally.
  6. Plug the drive back in and test it.

For Apple Silicon Macs:

  1. Unplug the drive.
  2. Restart the Mac normally.
  3. Wait until macOS fully loads.
  4. Reconnect the drive and check again.

I’ve had restarts fix storage weirdness I couldn’t explain. Annoying, but there it is.

Last Step, Reformat the Disk

If none of the earlier steps help, and your files are already recovered, formatting is the cleanup option.

  1. Open Disk Utility.
  2. Click View > Show All Devices.
  3. Select the physical disk, not one of its volumes.
  4. Click Erase.
  5. Name the drive. Pick APFS if you use it only with Macs. Pick exFAT if you need it to work with both macOS and Windows.
  6. Click Erase and wait.

After the format finishes, unplug it, reconnect it, and see if it mounts normally. If it still fails after a clean format, I’d start suspecting the hardware itself. At that stage, replacing the drive usually makes more sense than chasing it for another afternoon.

The pattern I keep coming back to is simple. Get the files first. Fix the disk after. Drives are replaceable. Your data isn’t.

1 Like
3

If the drive shows in Disk Utility, I would not jump to erase yet. Mount failures on Mac often come from a damaged file system, a bad partition map, low bus power, or macOS refusing the volume after an unsafe eject. Different issue than a dead drive.

A few things I’d try that @mikeappsreviewer did not cover:

  1. In Disk Utility, click View, Show All Devices. Select the volume first, then click Mount. If it fails, select the container or parent disk and check what format it reports. If the format looks wrong or blank, the partition table might be hurt.

  2. Run this in Terminal:
    diskutil list
    Find your external disk identifier, like disk4s2, then run:
    diskutil mountDisk /dev/disk4
    or
    diskutil mount /dev/disk4s2
    Sometimes Disk Utility fails, Terminal works. Kinda dumb, but yup.

  3. Check the log while plugging it in:
    log stream --predicate ‘process == ‘kernel’’ --info
    If you see I/O errors, repeated disconnects, or media not present, that points more to hardware, enclosure, or power.

  4. If it is an old spinning HDD in a USB enclosure, remove it from the enclosure and connect it with a known-good SATA to USB adapter. I disagree a bit with the idea of focusing on the disk first every time. I’ve seen the enclosure board fail way more often than the bare drive.

  5. Try safe mode on the Mac, then reconnect the drive. Third-party NTFS or security tools sometimes block mounts.

  6. If the volume is NTFS, install the proper driver or test on Windows. macOS reads NTFS, but damaged NTFS volumes often mount poorly.

Before repairs, recover files if you can. Disk Drill is a solid pick for an external hard drive not mounting on Mac, since it often sees volumes Finder will not. If the drive is clicking, slow, or drops off, clone first.

Also, this thread covers a related Mac mount error well:
fixing external drive error 49153 on Mac

If First Aid reports catalog or node errors but won’t repair them, I’d stop messing with the disk and pull data off first. One bad write is all it takes to make it worse.

4

If Disk Utility sees the drive, I’d check whether macOS is refusing to auto-mount it because of a stale mount point or a weird ownership flag. That gets missed a lot.

Open Terminal and run:

diskutil list

Find the external volume, then check if macOS thinks it is already mounted somewhere broken:

mount

If you see the disk listed with a strange path, unmount and remount it manually:

diskutil unmountDisk force /dev/diskX
sudo mkdir -p /Volumes/TestMount
sudo mount -t hfs /dev/diskXs1 /Volumes/TestMount

If it is APFS or exFAT, use diskutil mount instead of forcing the filesystem type. Sometimes Finder just never catches up.

Another thing I’d try, which neither @mikeappsreviewer nor @andarilhonoturno really dug into, is checking sharing/permissions corruption. In Disk Utility, select the volume and look at the info pane. If “Owners Enabled” is weird, try:

sudo diskutil disableOwnership /Volumes/YourDriveName

That has fixed a couple of “shows up but won’t open” drives for me.

Also, if Spotlight is choking on the disk, it can stall access. Disable indexing for that volume:

sudo mdutil -i off /Volumes/YourDriveName

If the drive is visible but flaky, I would personally clone or recover before doing much else. I agree with the others there. Disk Drill is useful specifically because it can scan an external hard drive that won’t mount on Mac and pull files to another disk first. If you want a decent breakdown, this full Disk Drill review for Mac data recovery explains the recovery side pretty clearly.

One small disagreement though: I would not start killing random fsck processes unless logs actually suggest that’s the hangup. Sometimes that makes a messy disk even more weird tbh.

If Terminal mount fails, post the exact error text from diskutil mount and the filesystem format shown in Disk Utility. That usually tells the real story fast.

5

I’d add one check none of the others really leaned on: see if the volume is only failing in Finder, not at the block device level. In Terminal, run:

diskutil info /dev/diskXsY

Look for File System Personality, Read-Only Media, and Volume Read-Only. If macOS flipped it read-only because of corruption, that explains a lot. I slightly disagree with trying too many repair attempts early. Repeated writes on a shaky drive are how recoverable turns unrecoverable.

Also try System Information > USB / Thunderbolt and confirm the bridge chipset is negotiating properly. If the drive appears/disappears there, that points more to enclosure firmware than filesystem damage.

If SMART is available, check it:

diskutil info /dev/diskX | grep SMART

If it says failing or not supported through the enclosure, test with a different enclosure/adapter before trusting any repair result.

For data-first recovery, Disk Drill is reasonable here.
Pros: can see unmounted disks, image unstable drives, simple preview.
Cons: scan time can be long, deep scans lose original folder structure sometimes, full recovery features are paid.

So my order would be: verify hardware visibility, check read-only state, inspect SMART/enclosure behavior, then recover to another disk with Disk Drill before any serious repair. @andarilhonoturno, @mike34, and @mikeappsreviewer already covered the common mount commands well, so I’d focus on narrowing whether this is filesystem damage or flaky hardware first.