Why won’t my hard drive mount on my Mac if the light is still on?

Data Recovery
1

My external hard drive suddenly stopped mounting on my Mac, but the power light still turns on like it’s connected. It was working fine before, and now I can’t access important files I need right away. I’m looking for help figuring out whether this is a Mac issue, a cable problem, or if the drive might be failing.

2

I’ve run into this enough times on Macs to stop assuming the drive is dead right away. Sometimes you plug it in and get nothing. No desktop icon. No Finder entry. No noise except your own blood pressure climbing. A lot of the time, the disk still works. macOS is the part failing to deal with it.

Start with the boring stuff first. I know, nobody wants to hear it, but I’ve wasted hours on drives which turned out to be fine.

Method 1: Check the connection

  1. Unplug the drive.
  2. If it’s going through a hub or dock, skip it. Plug the drive straight into your Mac.
  3. Try another USB or Thunderbolt port.
  4. Swap the cable for one you know works.
  5. If you have another Mac or even a Windows PC nearby, test the drive there.
  6. Look for signs of life. Spin, vibration, LED, any little hint. If it powers on, you at least know it’s getting juice.

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

Method 2: Finder might be hiding it

This one catches people off guard. The drive mounts, Finder refuses to show it.

  1. Open Finder.
  2. Go to Finder > Settings. On older macOS versions, it says Preferences.
  3. Open the General tab.
  4. Make sure External disks is checked.
  5. Then open the Sidebar tab.
  6. Check External disks there too.
  7. Go back to Finder and look again.

If Disk Utility sees the drive but Finder does not, this setting is one of the first things I check.

Recover the files before repairs

If the disk shows up in Disk Utility but won’t mount, I’d pull the data off first before trying repair tools. I’ve seen people run First Aid, then erase the disk, then realize the only copy of their files was sitting there the whole time.

Disk Drill reads the device more directly, so it sometimes sees files even when macOS refuses to mount the volume.

  1. Install and open Disk Drill.
  2. Find the unmounted drive in the list.
  3. If the disk seems shaky, use Byte-to-byte Backup first and make an image.
  4. Wait for the image process to finish.
  5. Scan the original drive or the image.
  6. Look through what it finds.
  7. Preview important files to make sure they open.
  8. Pick what you want back.
  9. Save recovered files to another drive. Don’t write them back to the same problem disk.

Once your files are somewhere safe, the stress level drops a lot. Then you can poke at the drive without making things worse.

Stop a stuck fsck process

I’ve seen macOS get hung up doing a file system check in the background after a bad eject. The Mac sits there acting like the drive doesn’t exist, while fsck spins its wheels 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.
  6. Check if the drive mounts on its own.

I’ve had drives pop up right after this. Felt dumb the first time, since I had been trying everything else first.

Reset NVRAM on Intel, restart if it’s Apple Silicon

This is one of those system-level fixes I don’t love, but I’ve seen it help with weird external device behavior.

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 about 20 seconds.
  5. Let go and let the Mac 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 finishes loading.
  4. Reconnect the drive.

Not fancy. Still worth trying.

Reformat the drive

If none of the earlier steps fix it, and your files are already recovered, formatting is the last stop before giving up on the hardware.

  1. Open Disk Utility.
  2. Click View > Show All Devices.
  3. Select the physical disk, not only the volume under it.
  4. Click Erase.
  5. Name the drive.
  6. Pick APFS if it’s staying in the Mac world. Pick exFAT if you need it to work with both Mac and Windows.
  7. Click Erase and let it finish.

Afterward, unplug and reconnect it. If it still won’t mount even after a clean format, I’d stop blaming the file system. At that point the hardware is the suspect.

The pattern I keep coming back to is simple. Save the files first. Repair later. Drives are replaceable. Your data isn’t.

3 Likes
3

Power light on only means the enclosure gets power. It does not prove the disk is healthy, or even talking to macOS. I slightly disagree with @mikeappsreviewer on one part, I would not jump to fsck killing or NVRAM stuff early. First I’d check whether the drive is failing at the hardware bridge level.

Do this.

  1. Open System Information, then USB or Thunderbolt.
  2. See if the enclosure shows there.
  3. Open Disk Utility, click View, Show All Devices.
  4. If you see the physical disk in gray, note the size. If size shows wrong, like 0 bytes or some nonsense, that points to enclosure or drive failure.
  5. If the volume is missing but the disk is present, the partition map might be damaged.
  6. Run this in Terminal:
    diskutil list

If diskutil sees the device but no mountable volume, try:
diskutil mountDisk /dev/diskX

Replace X with the right number.

If you get I/O errors, stop writing to it. That usually means failing hardware. If this is a desktop-style external with its own power brick, check the brick too. LEDs lie all the time, seen it a bunch.

One more thing people miss. Some external cases fail while the bare drive inside is fine. If it’s a standard SATA drive in a USB enclosure, remove it and connect it with another enclosure or SATA dock. I’ve recovered drives this way more than once.

If your files matter now, use Disk Drill to scan the disk or make a backup image first. That’s safer than poking at repairs for too long.

For a decent thread on Mac mount errors, see Mac external drive 49153 mount error fixes.

Short version for searchers. External hard drive not mounting on Mac often comes from a bad enclosure, damaged partition map, file system corruption, power issues, or a failing disk, even when the light is on.

4

Light on just means the enclosure is getting power. It does not mean the actual disk is healthy or that macOS can read the partition table. That part I agree on with @mikeappsreviewer and @nachtdromer. Where I slightly disagree is the urge to keep trying random mount/repair commands early, because repeated attempts on a dying drive can make things worse.

A couple things I’d check that haven’t been hit enough:

  • Disk Arbitration may be hung. In Activity Monitor, search diskarbitrationd. If it’s not responding, force quit it. macOS restarts it automatically, and sometimes the drive suddenly appears.
  • Safe Mode test. Boot into Safe Mode and connect the drive there. If it mounts in Safe Mode, some third-party extension, security tool, or NTFS helper is probly interfering.
  • Check Console logs. Open Console and filter for diskmanagementd, kernel, or I/O. If you see repeated I/O errors, that’s a red flag for hardware trouble.
  • Watch for clicking or spin-up spin-down loops. If you hear that, stop messing with it.

If the files matter right now, skip “fixing” and focus on recovery first. Disk Drill is useful here because it can often detect an external hard drive that won’t mount on Mac and let you scan or image it before you do anything risky. This full Disk Drill review for Mac data recovery gives a decent breakdown of what it can do.

Also, if this is an older external HDD and the enclosure has a sleep/power quirk, try leaving it connected for 10 to 15 mins. Sounds dumb, but I’ve seen drives mount way late after macOS finally stops choking on them. Macs can be weird like that.

5

Light on is the most misleading “everything’s fine” signal ever. I’m with @nachtdromer and @jeff on checking whether macOS even sees the device at a low level, and with @mikeappsreviewer on prioritizing recovery. Where I’d push back a bit is this: if the drive has become painfully slow, freezes Finder, or causes beachballs the second you plug it in, stop doing repeated remount attempts. That pattern often screams hardware trouble.

A couple of checks that complement what they already covered:

  • Try mounting it from Recovery Mode. If it mounts there, some login item, third-party driver, antivirus, or filesystem helper in your normal boot is interfering.
  • In Terminal, run log stream --predicate 'process == 'kernel'' --info right after plugging it in. If you see repeated read/write failures, that’s a bad sign.
  • If it’s a 3.5-inch external, listen for weak spin-up. A dying power adapter can light the LED but still not supply stable current under load.
  • If the drive is encrypted, check whether the problem is actually the unlock prompt failing to appear.

Also, if the drive vanishes only on your Mac, create a new macOS user account and test there. Weird Finder or permissions-level issues do happen.

For recovery, Disk Drill is reasonable if the disk still appears at all.
Pros: simple UI, can image the drive first, good for unmountable volumes.
Cons: deep scans can take forever, license cost, and it won’t magically fix failing hardware.

If Disk Drill can preview your files, recover them to another disk first. If the drive clicks, disconnects itself, or keeps reconnecting, stop and consider professional recovery. That’s the point where DIY gets expensive.