My external hard drive suddenly won’t mount on my Mac, even though it was working fine before. I’m wondering if the USB cable could be causing the problem or if it’s something with macOS or the drive itself. I need help figuring out what to check first so I don’t risk losing access to my files.
I’ve run into this on Macs enough times that I don’t assume the drive is dead anymore. Early on, I saw an external disk refuse to mount and figured the files were gone. Most of the time, the drive itself was fine. What broke was the file system, or macOS got hung up on a background check, or the volume sat there and refused to mount for no obvious reason.
Before you start poking at fixes, do the boring checks first. I skipped these once and wasted an hour.
Plug the drive straight into your Mac. Skip the hub or dock for now. Swap the cable if you have another one. Try a different USB or Thunderbolt port. If you have access to another computer, plug it in there and see if it shows up. Then check Finder settings and make sure external disks are set to appear on the desktop and in the sidebar.
If Disk Utility sees the drive and the size looks about right, I usually take that as a decent sign.
This only applies to drives with no obvious hardware failure. If the disk does not appear in Disk Utility at all, shows a nonsense capacity, keeps dropping off, makes clicking sounds, or won’t power up, you’re in hardware trouble. Software fixes won’t do much there, if anyhting.
Start with First Aid on the whole drive
This is the first thing I try because it’s built in and quick.
1. Open Disk Utility.
2. Click View > Show All Devices.
3. Pick the physical drive at the top, not only the volume under it.
4. Click First Aid.
5. Confirm it.
6. Wait for the scan to finish.
7. Try mounting the drive again.
When the problem is minor file system damage, this sometimes clears it up with no extra drama.
Kill a stuck fsck process
I’ve seen macOS start a file system check after a bad disconnect, then get stuck there and block the mount. Annoying one, because the disk looks half alive.
1. Open Terminal.
2. Enter: 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 stops a hung process that is getting in the way.
Try mounting it by hand in Terminal
Sometimes the volume is there, healthy enough, and macOS still refuses to mount it on its own.
1. Open Terminal.
2. Run: diskutil list
3. Find your drive identifier, something like disk4s1.
4. Run: diskutil mount /dev/disk4s1
5. Replace disk4s1 with your real identifier.
6. Press Return.
7. Read the result in Terminal.
If it works, the drive usually mounts right away.
Reformat only if you’ve already accepted the data loss risk
If nothing else works, erase and reformat is the last stop.
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 you use it only with Macs, or exFAT if you need Windows support too.
7. Click Erase.
8. Wait for it to finish.
I would not start with repairs if the files matter. This stuff is aimed at getting the drive mountable again. Good for the hardware side. Bad if your main goal is saving data first. Even tools meant to repair a file system can rewrite structures and make recovery harder later. Reformatting is the obvious case, but it’s not the only one.
If the files matter, recover them first
My usual move is to pull data off before I try to fix the mount issue. For drives that appear in Disk Utility but won’t show up in Finder, I’ve had decent results with Disk Drill. macOS tends to give up fast when the file system is messy. Disk Drill reads the storage device more directly and scans for recoverable files.
The part I keep coming back to is the Byte-to-byte Backup feature. If the drive is acting weird, disconnecting at random, or feels unstable, I make an image first. That copies every readable sector into an image file, so you work from the copy instead of hammering the original disk over and over.
The recovery flow 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 seems unstable.
4. Scan the drive or scan the backup image.
5. Review the found files.
6. Preview important files and make sure they still open.
7. Recover them to a different storage device.
After your files are safe somewhere else and you’ve checked they open fine, then go back and try repairs. At that point, if First Aid or a reformat changes the file system, you’re not making a bad situation worse.
Yes, the cable is high on the suspect list. I’d put it near the top, especialy if the drive spins up off and on, disconnects, or only fails on one port. A bad USB cable causes a lot of fake “dead drive” scares on Macs.
A few things I’d check that @mikeappsreviewer did not cover.
Reset Finder and USB detection first. Finder sometimes stops refreshing mounted volumes.
- Relaunch Finder from the Apple menu, Force Quit, Finder, Relaunch.
- Open System Information, then check USB or Thunderbolt. See if the drive appears there.
- If it shows in System Information but not in Disk Utility, reboot the Mac fully, not sleep-wake.
Check power draw. This gets missed a lot.
2.5-inch portable drives often fail to mount when the port or adapter does not give stable power.
- Use a direct port on the Mac.
- Avoid front ports on displays.
- If it has its own power brick, swap that too.
- For desktop externals, listen for spin-up, spin-down loops.
I disagree a bit with killing fsck early. If the disk is large, macOS file checks sometimes take a long time. I’ve seen exFAT drives sit there for 20 to 60 minutes after a dirty unplug. If the drive light is active, I’d wait first before stopping processes.
Also check disk format compatibility. If the drive was used on Windows, old macOS versions can be picky with BitLocker, NTFS tools, or damaged exFAT headers. If you installed any NTFS helper app, update or remove it and test again. Those tools do break mounting somtimes.
If your goal is files first, skip erase. Use Disk Drill and recover to another disk. It’s one of the more trusted Mac data recovery apps for external drives that show up but refuse to mount. If you want a broader list, this guide to top data recovery software is easy to scan.
Fast triage:
- New cable.
- New port.
- No hub.
- Check System Information.
- Wait if disk activity continues.
- Test on another Mac or PC.
- Recover data with Disk Drill before repair if the files matter.
If the drive clicks, grinds, or vanishes during transfer, stop there. That points more to hardware than macOS.
Cable absolutely can be the culprit, but one thing I’d add to what @mikeappsreviewer and @espritlibre said is to check whether macOS is refusing the drive because of security or disk ownership weirdness, not just corruption.
A few less-mentioned checks:
-
Open Terminal and run
diskutil list external
If the physical disk appears there but the volume does not mount, macOS still sees the hardware path. -
Then run
log stream --predicate 'eventMessage contains 'disk'' --info
Plug the drive in while watching logs. You can sometimes catch the real reason, like I/O errors, power issues, or a mount denial. Kinda nerdy, but super useful. -
If it is an older external enclosure, the enclosure board itself may be failing, not the actual hard drive. I’ve had this happen twice. Pulled the drive out, put it in a new SATA-to-USB enclosure, boom, files back. People blame the disk too fast somtimes.
-
If the drive is greyed out in Disk Utility, try mounting the parent container/volume group structure, especially with APFS drives. Sometimes the container is fine and the actual volume is what’s stuck.
-
Safe Mode can help. Booting the Mac in Safe Mode sometimes loads fewer third-party extensions, especially junky NTFS tools or old disk utilities that interfere with mounting. Then test the drive there.
I slightly disagree with going too hard on First Aid if the drive is unstable. If it disconnects mid-check, you can make a messy situation worse. If the data matters, I’d lean toward recovery first with Disk Drill, especially if the disk is visible but not mounting. That’s usually the line for me.
Also, if you want a clear walkthrough, here’s a step-by-step video on fixing an external hard drive that won’t mount on Mac.
If the drive shows nowhere, not Disk Utility, not System Information, not Terminal, then yeah, cable/port/enclosure/power jumps way up the suspect list. If it shows up but won’t mount, that smells more like filesystem or enclosure issues.
Cable is definitely a prime suspect, but I’d also test something people skip: the enclosure bridge chip. If the bare disk is fine but the USB-SATA bridge is flaky, macOS will act like the whole drive is cursed. I’ve seen externals fail on Mac, then work instantly once moved into a different enclosure.
A couple checks that complement what @espritlibre, @cazadordeestrellas, and @mikeappsreviewer already covered:
- Check Console.app right when you plug it in. Search for
diskarbitrationdorI/O. You’ll often see whether macOS is rejecting the mount, timing out, or hitting read errors. - In Disk Utility, check the S.M.A.R.T. status if it appears. If it says Failing or not supported through the enclosure, that tells you a lot.
- Try the drive on a powered USB-C dock only as a test. I know people say avoid hubs, and usually that’s right, but sometimes a powered dock is more stable than a weak Mac port for bus-powered drives.
- If it mounts read-only somewhere, copy data immediately. Don’t chase the perfect fix first.
Small disagreement with the usual advice: I would not keep retrying mounts over and over if the drive is making new noises or disappearing. Repeated retries can stress a dying drive.
If the files matter, use Disk Drill before repair attempts.
Pros of Disk Drill
- easy Mac interface
- good for drives visible but not mounting
- byte-to-byte backup is useful on unstable disks
Cons
- not magic for real hardware failure
- deep scans can take forever
- recovery quality depends on how damaged the filesystem is
If the drive shows in hardware info but not Finder, that’s more recoverable than people think. If it shows nowhere at all, I’d blame cable, power, enclosure, then the drive itself.

