External Drive Not Mounting on Mac? Fix the Real Causes

Drive not showing up on Mac? Usually it's a mount issue, not dead hardware. Here are the fixes that actually work, in order.

You plug in the drive. The LED lights up. But nothing appears on the Desktop or in Finder. Before you panic and start shopping for a new drive, know this: what's actually happening here is almost never dead hardware. It's the mount process failing, or the drive format being something macOS won't touch by default.

I've fixed this exact issue more times than I can count, on Macs from a 2015 MacBook Pro running High Sierra to an M1 Mac mini on Sonoma. The same root causes keep coming back. Here's how to hunt them down, from the most common to the weird edge cases.

1. The Drive Is Mounted But Hidden

This is the sneakiest one. Your Mac actually sees the drive and mounts it, but Finder hides it because of a setting you probably never touched.

Open FinderSettings (or Preferences on older macOS) → General. Look for the section labeled "Show these items on the desktop." If "External disks" isn't checked, that's your whole problem. The drive is sitting there mounted, just invisible on the desktop.

But wait—it might also be missing from the Finder sidebar. Go to FinderSettingsSidebar, and under "Locations," make sure "External disks" is checked. This happens to me after every macOS update, by the way. The update resets the sidebar preferences for no good reason.

If you'd rather not touch settings, you can always check the drive in Disk Utility. Press Cmd + Space, type "Disk Utility," and hit Enter. Look at the left sidebar under "External." If your drive's name shows up there, it's mounted and healthy—you're just not seeing it in Finder.

2. The Drive Isn't Mounted at All (But It's Detected)

Okay, so Disk Utility shows the physical drive but the volume name is grayed out, or there's no volume listed under it. That means macOS sees the hardware but didn't mount the filesystem. This is your classic "drive won't mount" scenario.

Fix: Force Mount from Disk Utility

In Disk Utility, click the volume (the sub-item under the physical drive name), then click the Mount button in the toolbar. If that fails, click the physical drive itself and try First Aid. This checks the filesystem structure—not your files, just the structure—and can often repair the mount issue.

If First Aid finds errors, let it finish. It's safe. I've never seen it delete user data, and I've run it on drives with failing SMART status.

Fix: Force Mount from the Terminal

When Disk Utility fails, the Terminal is your friend. Open Terminal (again, Cmd + Space, type "Terminal"). First, find the disk identifier:

diskutil list external

Look for your drive. It'll be something like /dev/disk4 with a volume like MyDrive. Then force the mount:

diskutil mountDisk /dev/disk4

If that gives you an error about the filesystem being unsupported, skip to section 3. But if it succeeds, your drive appears on the desktop instantly.

The reason this works when clicking Mount fails? The GUI sometimes tries to mount only the currently selected volume, and if the volume's mount point is in a weird state, it silently fails. diskutil mountDisk tells the kernel to remount the entire disk, which resets the mount state.

3. The Drive Uses a Format macOS Won't Mount Automatically

This is the second most common cause, and it's a real trap. If your drive was formatted on a Windows machine as NTFS, macOS will read it but often won't mount it by default, or it mounts it read-only. Similarly, if it's formatted as exFAT but has an MBR partition map, macOS might see the partition table but refuse to mount a partition with a dirty file system flag.

How do you check? Open Disk Utility and select the physical drive. If the format reads "Windows NT Filesystem" or "exFAT," that's your issue.

Fix for NTFS: Use a Driver or Reformat

Your options: install a free NTFS driver like macFUSE plus the NTFS-3G plugin, or use the paid Paragon NTFS for Mac. I've used both. macFUSE is fine if you're technical and don't mind occasional kernel extension warnings on newer macOS versions. Paragon is dead simple but costs money. For a one-time file extraction, neither is worth it—boot into Windows, copy the files to an exFAT drive, and move on.

If you're reformatting the drive anyway, choose exFAT if you need cross-platform compatibility, or APFS if it's Mac-only. Formatting erases everything, so back up first.

Fix for exFAT with Dirty Flag

If you see an error in Disk Utility like "The volume … could not be mounted because it is not clean," the exFAT journal has a dirty bit set from an unclean shutdown (like yanking the cord on Windows). Mount it on a Windows PC, run chkdsk /f on that drive, then safely eject. That clears the flag. No Windows PC? Try the Terminal:

sudo fsck_exfat -d /dev/disk4s1

Replace the identifier with what diskutil list shows. This clears the dirty flag directly. It might take a minute on a large drive.

Quick-Reference Summary

CauseSymptomFix
Hidden by Finder settingsDrive appears in Disk Utility, not on desktop/sidebarCheck Finder → Settings → General & Sidebar
Not mounted (detected but no volume)Disk Utility shows grayed-out volume or no volumeClick Mount, run First Aid, or use diskutil mountDisk
NTFS or dirty exFATFormat shows NTFS, or mount error about unclean volumeInstall NTFS driver, or run fsck_exfat / chkdsk
Hardware issue (rare)Drive doesn't show in Disk Utility at all, no LEDTry a different cable, port, or another computer

One last thing: if the drive doesn't show in Disk Utility's external list at all, don't bother with the above. Test the cable—USB-C cables are notoriously flaky for data even when they charge fine. Try a different port too. If it's still invisible, plug it into a Windows PC or Linux box. If that machine sees it, your Mac's USB controller might be the problem. If nothing sees it, then, yeah, it's probably dead. But that's the minority case.

Related Errors in Hardware – Hard Drives
Disk Hot-Swap Detection Failed Disk Hot-Swap Detection Failed on Dell PowerEdge R740 – Fixed Storage Drive Fails Chkdsk Stage 4: Fix Without Replacing Fixing LVM metadata corruption on Linux servers 0XC00D10DD Fix 0XC00D10DD: Missing device drivers in Windows Media Player

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.