My external hard drive suddenly stopped mounting on my Mac, but Disk Utility says First Aid completed without errors. I’ve tried unplugging it, restarting, and using a different cable, but it still won’t show up normally. I need help figuring out why a Mac hard drive won’t mount even though First Aid passed and what I should try next to access my files.
I’ve run into this on my Mac enough times that I stopped treating an unmounted external drive like an obituary. Early on, I saw the drive fail to show up and figured the disk was dead and the files were gone. Most of the time, I was wrong. What I found instead was a messed up file system, some hung macOS process, or a volume that sat there visible to the system but refused to mount.
Before you do anything bigger, check the boring stuff first.
Plug the drive straight into the Mac. Skip the hub or dock for now. Try a different cable. Move it to another USB or Thunderbolt port. If you’ve got another computer nearby, test the drive there too. Then open Finder Settings and make sure external disks are set to show on both the desktop and in the sidebar. I’ve missed that once, felt dumb after.
If the disk shows up in Disk Utility and the size looks close to what you expect, I’d take that as a decent sign.
This only applies to drives with no clear hardware failure. If Disk Utility doesn’t see the drive at all, if the reported size is nonsense, if it keeps dropping out, if it clicks, or if it won’t power up, you’re outside normal mount-fix territory. At that point I’d suspect the hardware first. Software steps usually don’t fix those cases. I mean, I never got lucky with them.
What I’d try first
1. Run First Aid on the whole device
This is the low-friction move.
1. Open Disk Utility.
2. Click View > Show All Devices.
3. Pick the physical disk, the top item in the list, not only the volume under it.
4. Click First Aid.
5. Approve it and wait.
6. Try mounting the drive again.
When the issue is small file system damage, First Aid sometimes cleans it up enough for the volume to come back.
2. Kill a stuck fsck process
I’ve seen macOS get hung up after a bad disconnect. It starts a file system check in the background, then never seems to finish. While it’s stuck, the drive stays unavailable.
1. Open Terminal.
2. Run: sudo pkill -f fsck
3. Press Return.
4. Type your admin password if asked.
5. Wait a bit.
6. Check the drive again.
This does not repair corruption. It only clears out a process that might be blocking the mount.
3. Mount it yourself in Terminal
Sometimes the volume is there, the disk is fine, and macOS still won’t mount it on its own. Manual mount worked for me more than once.
1. Open Terminal.
2. Run: diskutil list
3. Find your volume identifier, something like disk4s1.
4. Run: diskutil mount /dev/disk4s1
5. Swap disk4s1 with your own identifier.
6. Press Return.
7. Read the Terminal output.
If it works, the volume usually appears right away.
4. Reformat the drive
This is the last stop, not the first.
1. Open Disk Utility.
2. Click View > Show All Devices.
3. Select the physical drive.
4. Click Erase.
5. Give it a name.
6. Choose APFS if the drive stays with Mac only, or exFAT if you need Windows too.
7. Click Erase.
8. Wait for it to finish.
If the files matter, don’t rush into repairs. I learned this the annoying way. These steps are aimed at making the drive usable again, not protecting your data. Some repair actions change the file system layout. Reformatting wipes it outright, sure, but even repair tools can make later recovery harder by changing structures while they try to fix them.
If you care about the files, pull data first
My usual move is to recover the files before trying repairs. For drives that show up in Disk Utility but won’t mount in Finder, I’ve had decent results with Disk Drill. macOS tends to give up once the file system gets messy. This tool still talks to the device directly and scans for recoverable data.
The part I keep coming back to is the Byte-to-byte Backup feature. If the drive feels unstable, drops connection, or behaves different every time you plug it in, making an image first is safer. You copy readable sectors into an image file, then work from the copy instead of beating up the original drive over and over. I did this once with a flaky portable SSD and it saved me some pain.
The workflow is simple enough:
1. Download and open Disk Drill.
2. Select the unmounted drive from the list.
3. Create a Byte-to-byte Backup first if the drive acts unstable.
4. Scan the original drive or the image.
5. Look through the found files.
6. Preview important items so you know they still open.
7. Recover them to a different storage device.
After your files are safe and open fine from another disk, go back to the repair steps. At that point you’re not gambling with the only copy. wich is a much better place to be.
1 Like
First Aid passing only means Disk Utility did not find a repairable file system error. It does not mean the volume is mountable.
A few things still block mounting:
-
Wrong file system support.
If the drive is Linux ext4, BitLocker, or some NAS format, macOS sees the device but will not mount it natively. Check Disk Utility, select the volume, then look at Format. If it says something macOS does not support for write or mount, taht’s your answer. -
Bad partition map.
I’ve seen drives where the volume checks out, but the GUID partition table is damaged. First Aid often reports clean on the volume while the map is still off. In Terminal, run:
diskutil list
Look for odd partition sizes, missing names, or “Free Space” where your volume should be. -
Mount point conflict.
macOS mounts volumes under /Volumes. If a stale folder is stuck there, the drive fails to appear right. Open Terminal and run:
ls /Volumes
If you see your drive name already there while the drive is not mounted, remove the stale folder with:
sudo rmdir /Volumes/YourDriveName
Then try mounting again from Disk Utility. -
Permission or security blocks.
If the disk is encrypted with FileVault, APFS encrypted, or third party software, Finder might hide the normal prompt. Try mounting from Disk Utility and watch for an unlock option. -
Failing bridge board.
This is common on external HDDs and some SSD enclosures. The disk inside works, the USB bridge does not behave right. Disk Utility still sees something, First Aid passes, mount fails. If the drive is a standard SATA disk inside an enclosure, test it in another enclosure or with a SATA to USB adapter. I disagree a bit with @mikeappsreviewer on one point, a “good size” in Disk Utility is helpful, but it does not rule out enclosure failure. -
Power draw issues.
Some portable drives spin up, then brown out. They show in Disk Utility, then hang on mount. More common on older USB-A ports and bus-powered HDDs.
If the files matter, stop poking it too much. At this stage I’d image or recover first. Disk Drill is one of the top data recovery tools for Mac if the drive is visible but won’t mount. Also worth checking this best data recovery software for Mac and Windows list if you want compare options.
One more quick check. Open Console, plug the drive in, and search for “diskarbitrationd” or “I/O error”. Those logs often tell you more than First Aid did.
First Aid passing just means the file system check didn’t find anything it knows how to fix. It does not mean macOS can actually complete the mount. That part trips people up all the time.
A couple things I’d check that @mikeappsreviewer and @shizuka didn’t really lean on:
- Try mounting in Safe Mode. Weird login items, antivirus junk, NTFS helpers, old kernel extensions, all that can interfere with Disk Arbitration. Boot Safe Mode, plug the drive in, see if it mounts there. If it does, the drive may be fine and macOS is the problem.
- Create a new user account and test there. Sounds dumb, but corrupted Finder prefs / user-level settings can make externals act invisible or fail to appear properly.
- Check System Information, not just Disk Utility. Apple menu > System Information > USB or Thunderbolt. If the enclosure shows there with sane vendor/product info, that tells you more about the connection layer.
- Look for a corrupted volume label. I’ve had drives fail to mount because the name had weird characters after being used on another system. Finder gets cranky in bizzare ways sometimes.
Also, small disagreement with the usual “if First Aid passed, it’s probably software” thinking. Not always. I’ve seen plenty of half-dead enclosures and portable HDDs that still report enough clean metadata to satisfy First Aid, then choke the second macOS tries a real mount.
If the data matters, stop testing it 40 times in a row. Repeated mount attempts can make a weak drive worse. At that point I’d recover or image it first. Disk Drill is solid for a Mac external hard drive that shows up but won’t mount, especially if you need to pull files off before erasing anything.
Also useful if you want a visual walkthrough: step by step Mac external drive mount fix video
If Disk Utility sees it, but Finder doesn’t, I’d suspect:
- bad enclosure/bridge
- background software conflict
- corrupted partition metadata
- encryption/unlock issue
- dying drive that hasn’t fully died yet
That annoying in-between state is super common, actualy.
First Aid can pass and the disk still fail at the mount handshake. That’s the part I think @shizuka, @boswandelaar, and @mikeappsreviewer are circling, but I’d look at one extra angle: macOS may be refusing the volume because of dirty metadata outside the file system itself.
A few checks they did not really spell out:
-
Terminal mount reason
Run:log show --last 10m --predicate 'process == 'diskarbitrationd''
This often shows the actual refusal reason, not just “could not mount”. -
Read-only test
Try:diskutil mount readOnly /dev/diskXsY
If read-only works but normal mount does not, that points to journal / permission / write negotiation weirdness. -
Check for APFS container weirdness
diskutil apfs list
I’ve seen APFS containers look fine in First Aid but the volume role or preboot linkage is off. -
Spotlight / Finder hang
Sometimes the disk mounts, then Finder chokes indexing it. Check Terminal:mount
If it’s listed there, the issue is visibility, not mounting.
Small disagreement with the usual stale-folder theory: it happens, sure, but less often than plain old enclosure firmware weirdness or a half-broken partition header.
If the data matters, stop repeated retries and image it first. Disk Drill is decent here because it can scan drives that appear but won’t mount.
Pros: simple UI, byte-to-byte backup, good for Mac users.
Cons: not the cheapest, deep scans can be slow, recovery quality still depends on hardware health.
If it were my drive, I’d check whether it mounts read-only before doing anything more invasive. That one test tells you a lot.