How do I get a disk to mount on my Mac after a force eject?

Data Recovery
1

I force ejected an external drive from my Mac, and now it won’t mount in Finder or Disk Utility like it should. I need help figuring out if the drive is damaged, how to safely recover my files, and what steps I can take to get the disk mounting again on macOS.

2

I ran into this on my Mac more than once. You plug in an external drive and get nothing. No desktop icon. No Finder entry. No files. It feels bad fast, but I wouldn’t assume the data is gone yet. A lot of the time the disk still works and macOS is the part acting weird.

I’d start with the boring checks first. Those saved me more time than the fancy fixes.

Method 1: Check the connection first

This one got me before. I spent way too long blaming a drive when the cable was the mess.

  1. Unplug the drive from your Mac.
  2. If it’s connected through a hub or dock, skip the middleman and plug it straight into the Mac.
  3. Try another USB or Thunderbolt port.
  4. Swap in a cable you already know works.
  5. If you have another Mac or even a Windows PC around, test the drive there too.
  6. Look for signs of life, spin, vibration, LED activity, any noise at all. If it powers up, I’d take it as a decent sign because the device is at least getting power.

Method 2: Make sure Finder isn’t hiding it

I’ve seen drives mount fine, but Finder was set up in a way where you’d never know.

  1. Open Finder.
  2. Go to Finder > Settings. On older macOS releases, it might say Finder > Preferences.
  3. Open the General tab.
  4. Check External disks.
  5. Then open the Sidebar tab.
  6. Check External disks there too.
  7. Go back to Finder and see if the drive shows up.

Recover the files before you repair anything

If the disk shows up in Disk Utility but refuses to mount, I’d stop there and pull the data off first. I learned this the hard way. People rush into First Aid or erase the disk, then figure out later they needed the files.

Disk Drill reads the device more directly, so it does not depend on Finder behaving or the disk mounting the usual way.

  1. Install and open Disk Drill.
  2. Find the unmounted drive in the device list.
  3. If the disk seems unstable, use Byte-to-byte Backup first and make a full image.
  4. Wait until the image finishes.
  5. Scan either the original disk or the image file.
  6. Look through what it finds.
  7. Preview the important files and make sure they open.
  8. Pick what you want to recover.
  9. Save everything to another drive. Don’t write recovered files back to the problem disk.

Once the files are safe somewhere else, you’ve got room to test fixes without sweating every click.

Kill a stuck fsck process

This one is weird, but I saw it work. If macOS thinks the disk was removed wrong, it sometimes starts a background file system check. Once in a while, that process hangs and the disk never mounts.

  1. Open Terminal.
  2. Run: sudo pkill -f fsck
  3. Type your admin password if macOS asks for it.
  4. Wait a few seconds.
  5. Check if the drive appears on its own.

I had one disk show up almost imediately after doing this.

Reset NVRAM on Intel, restart normally on Apple Silicon

Sometimes the problem sits higher up in the system settings, not in the disk itself.

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 up.
  6. Reconnect the drive and test again.

For Apple Silicon Macs:

  1. Unplug the drive.
  2. Restart the Mac normally.
  3. Wait until macOS fully loads.
  4. Plug the drive back in and check it again.

Reformat the disk if you already saved the files

If none of the earlier stuff helped, and your data is already recovered, I’d move to a format. At this point you’re trying to get the disk usable again, not protect files still sitting on it.

  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, then pick APFS if it stays Mac-only. Pick exFAT if you need it to work with both macOS and Windows.
  6. Click Erase and wait.

When the format finishes, unplug the drive and connect it again. If it still refuses to mount after a clean format, I’d start leaning toward a hardware fault. At that stage, replacing the drive usually makes more sense than dragging the problem out.

The main thing I took from all this was simple. Recover first. Repair second. Drives are replaceable. Your files arent.

5 Likes
3

Force ejects often leave an external hard drive unable to mount on Mac because the file system journal, partition map, or volume header got left in a bad state. That does not mean the disk is dead.

I agree with some of what @mikeappsreviewer said, but I would not start by killing random fsck processes unless you already confirmed the disk is visible at the system level. First figure out if macOS sees the hardware.

Do this in Terminal.

diskutil list

If the drive appears there, note the disk ID, like disk4. Then run:

diskutil info /dev/disk4

Look for three things. Protocol. Partition Map. File System Personality. If those fields look blank or weird, the enclosure or partition table might be damaged.

Next, check system detection:

system_profiler SPUSBDataType
system_profiler SPThunderboltDataType

If it shows in System Information but not in Disk Utility, I start suspecting a bridge board issue or corrupted metadata.

If the volume is listed but unmounted, try a manual mount:

diskutil mountDisk /dev/disk4

If it fails, try a read-only attach path with Disk Drill first. That part matters. Disk Drill is useful here because it often sees drives Finder ignores, and you want file recovery before repair if the disk has important stuff. Save recovered files to a different disk. Not the same one. People mes this up.

One more thing I would try before erase is Safe Mode. Boot into Safe Mode, plug the drive in, then test mount again. Safe Mode blocks a lot of third-party junk, including flaky NTFS drivers and old kernel extensions. I have seen Paragon and older security tools interfere with mounts.

Also check Console.app for mount errors. Search for ‘diskarbitrationd’ and ‘I/O error’. If you see repeated I/O errors, slow reads, or disconnects, think hardware.

If the drive does not appear in diskutil list at all on multiple Macs, I’d stop DIY repair. That points more to enclosure, power, or disk failure.

This thread also matches what you’re dealing with, Mac external drive error 49153, cannot be mounted.

4

I’d add one thing neither @mikeappsreviewer nor @codecrafter really leaned on enough: check the disk’s S.M.A.R.T. or health status before you start poking it too much.

In Disk Utility, hit View > Show All Devices, select the physical drive, and see if S.M.A.R.T. says Failing or Verified. If it’s an SSD in a decent enclosure, you can also try:

diskutil verifyDisk /dev/diskX

That checks the partition map, not just the volume. Different problem, different fix.

If the volume is greyed out in Disk Utility, try mounting from Terminal with a specific slice, not just the whole disk:

diskutil mount readOnly /dev/diskXs1

Read-only is the key bit. Less risk if the file system is shaky. If that works, copy stuff off imediately.

Also, if this is an external HDD and it’s clicking, beeping, or spinning down, stop. Don’t keep retrying mounts. That can make recovery worse fast. Same if Console shows lots of I/O errors.

If the data matters, image first, then recover from the image. Disk Drill is solid for that workflow, especially when a Mac external drive won’t mount after force eject. If you want a decent overview of what it does, this is worth a look: see how Disk Drill helps recover unmountable drives on Mac.

One small disagreement with @mikeappsreviewer: I would not jump to NVRAM resets early. Usually this is disk metadata, enclosure, cable, or power. Not Mac firmware being dramatic for no reason.

5

I’d add one angle the others only touched lightly: sometimes the drive is fine, but macOS cached a bad mount state after the force eject.

Try this sequence:

  1. Unplug the drive.
  2. In Terminal, run
    diskutil activity
    and see if Disk Arbitration is stuck looping on old mount attempts.
  3. Then run
    log show --last 10m --predicate 'process == 'kernel' OR process == 'diskarbitrationd''
    You’re looking for things like invalid b-tree node, wrong fs type, media not present, or repeated resets.

Why this matters:

  • wrong fs type often means the filesystem driver is the issue, not total disk death.
  • repeated resets usually means enclosure, cable, or power instability.
  • invalid b-tree points more toward directory corruption.

Small disagreement with @mikeappsreviewer: I would not put much weight on Finder settings if Disk Utility also does not mount it. At that point it is below Finder.

If the drive is visible as a raw device but the volume won’t mount, I’d avoid repeated repair attempts and make an image first. That is where Disk Drill is useful.

Disk Drill pros

  • Good at seeing unmountable external drives
  • Byte-to-byte backup is the right move on unstable media
  • Easier preview and recovery workflow than pure Terminal tools

Disk Drill cons

  • Not magic if the enclosure or disk keeps disconnecting
  • Deep scans can take forever
  • Paid recovery features may not be worth it for minor issues

Also worth noting from @codecrafter and @sonhadordobosque: if this thing behaves differently in a new enclosure or with a SATA-to-USB adapter, the actual disk may be okay and the USB bridge board may be the real failure. That gets missed a lot.