I upgraded my Mac to macOS Tahoe, and now my external hard drive shows up in Disk Utility but will not mount on my Mac. It was working fine before the update, and I need help figuring out whether this is a macOS Tahoe compatibility issue, a file system problem, or something I can safely repair without losing data.
I’ve run into this on Macs more times than I want to admit. The drive looks dead, Finder shows nothing, and it always seems to happen when you need the files right now. Most of the time, the data is still on the disk. macOS is refusing to mount it because something in the file system looks off.
First, I’d rule out the boring stuff before touching anything else.
Try another cable. Skip the USB hub and plug the drive straight into the Mac. Test a different port. Then open Finder settings and check whether external drives are set to appear in General and Sidebar. If the drive light is on, or you hear it spin up, I wouldn’t assume the disk is gone yet.
The blunt fix is formatting the drive. That wipes it clean, so I only do it when I do not need the files. If the data matters, stop chasing random repair tricks for a minute and recover the files first.
What I’ve seen is simple. macOS gets picky fast. A small bit of corruption is enough for it to refuse the mount. In those cases, recovery software tends to work better than fighting Finder or Disk Utility for an hour. I’ve had decent results with Disk Drill, mainly because it still detects drives when Disk Utility shows them grayed out, unmounted, or uninitialized.
If you use it, make a byte-to-byte backup first. I learned this the hard way once with an old external SSD that got worse during repeated scans. Cloning the drive first takes pressure off the original hardware. After that, scan the clone, preview the files, then recover them somewhere else. Once the files are safe, you’ve got room to mess with the original disk.
What I usually try before formatting
I go from least annoying to most technical.
Method 1: Show the full device list in Disk Utility
Sometimes the problem is the volume, not the whole drive. Disk Utility hides this more than it should.
1. Open Disk Utility.
2. Click View, then choose Show All Devices.
3. In the sidebar, pick the top-level physical disk, not only the indented volume. It often shows the maker name, like WD or Seagate.
4. Run First Aid on that top-level entry.
I’ve had drives mount right after First Aid repaired the partition map. Not every time, but enough times that I always check here first.
Method 2: Kill a stuck fsck process
If the drive got unplugged without ejecting, macOS sometimes starts a file system check in the background and then hangs there. The disk stays unavailable while fsck sits and chews on nothing.
1. Open Terminal.
2. Run sudo pkill -f fsck
3. Type your Mac password. You will not see the characters as you type.
4. Wait a few seconds and see if the drive appears.
I’ve seen this fix the issue almost instantly. Feels dumb, but yeah, it happens.
Method 3: Reset NVRAM and SMC on Intel Macs
I only bother with this if the USB behavior feels flaky across multiple devices, not only one drive. On Apple silicon Macs, a normal restart usually covers this.
For NVRAM:
1. Shut down the Mac.
2. Power it on and hold Option + Command + P + R for about 20 seconds.
For SMC on Intel:
1. Shut down.
2. Unplug power for 15 seconds.
3. Plug it back in.
4. Wait 5 seconds.
5. Turn it on.
On some MacBooks, the shortcut is Shift + Control + Option + Power for 10 seconds. Apple changed this stuff enough times to make it annoyng.
Method 4: Mount it manually in Terminal
Disk Utility sometimes gives up before the command line does.
1. Open Terminal.
2. Run diskutil list
3. Find your disk identifier, something like disk4s1
4. Run diskutil mount /dev/disk4s1 with your own identifier
If it mounts, Terminal will tell you. If it fails, the error message is often more useful than what Disk Utility shows. I’ve used those errors to figure out whether the problem was APFS damage, a bad partition map, or a disk the system no longer trusted.
When I stop troubleshooting
If none of the steps above work, I stop trying to rescue the mount and move to formatting, but only after recovery is done.
In Disk Utility, select the drive, click Erase, and choose the file system based on how you use it:
APFS for Mac-only use.
exFAT if you move files between Mac and Windows.
That clears logical file system damage in most cases. The key part is the order. Recover first. Wipe later. If you reverse those steps, you make your own life harder.
If Disk Utility sees the drive, macOS Tahoe is talking to the hardware. That points more to a file system, permission, or driver issue than a dead disk.
A few things I’d check that @mikeappsreviewer did not cover.
1. Check System Information.
Open Apple menu, About This Mac, System Report, then USB or Thunderbolt. If the drive shows there with full capacity, the port and bridge board are alive. If it disappears here but shows in Disk Utility off and on, I’d suspect the enclosure first. I’ve seen older SATA to USB bridge chips fail after a macOS update becuase the new OS gets stricter.
2. Look for readout in Terminal.
Run:
diskutil info /dev/diskX
Replace X with your disk number.
Look for:
File System Personality
Read-Only Media
Device Block Size
Protocol
If it says the media is read-only when it was not before, Tahoe might be forcing safe mode on a damaged file system.
3. Try mount read-only.
This matters if you need files more than repairs.
sudo mkdir /Volumes/testdrive
sudo mount -o rdonly -t exfat /dev/diskXs1 /Volumes/testdrive
If it is APFS or HFS+, use the matching type. If read-only works, copy data off first. Do not run erase yet.
4. Check Privacy and Security.
Some external disks get blocked by security tools after upgrades. Look in System Settings, Privacy & Security for disk access, removable volumes, or third-party endpoint software. Antivirus and drive utility apps are common culprits. CleanMyMac, NTFS tools, old WD or Seagate helpers, stuff like tht.
5. If it is NTFS, Tahoe might be exposing an old problem.
macOS reads NTFS but does not natively write well through hacks or old drivers. If you used an NTFS driver before the upgrade, update or remove it. I’ve seen Paragon and older Tuxera builds break mounts after major macOS changes.
6. Test on another Mac or a Windows PC.
This is the fastest split test. If the drive mounts elsewhere, Tahoe is the issue. If it fails everywhere, the file system is damaged.
I disagree a bit with jumping to fsck-killing early. On newer macOS builds, interrupting checks on a shaky drive is not my first move. I’d rather image it first if the data matters. Disk Drill is solid for this since it can create a byte-level backup and scan from the image instead of hammering the original disk.
Also, keep this handy if you want more clear steps for fixing an external hard drive that won’t mount on Mac after a macOS update:
external drive not mounting on Mac, practical fixes and user reports
If Disk Utility shows S.M.A.R.T. failing, odd size, or no partition map, stop trying random repairs. Recover files first. Then replace the enclosure or the drive.
If Disk Utility sees the drive but Finder will not mount it after Tahoe, I’d also check whether Tahoe changed how it handles **ownership and mount permissions** on that volume. This gets missed a lot.
In Terminal, run:
```bash
log show --last 10m --predicate 'process == 'diskarbitrationd''
```
That can show the actual mount refusal reason, not the vague Disk Utility error. I’ve caught “unsupported filesystem features” and permission-related denials this way.
Also try booting once in **Safe Mode** and then reconnect the drive. Not because Safe Mode is magic, but because it disables third-party filesystem extensions and login junk. If the drive mounts there, Tahoe itself may be fine and some old helper app is the real problem. That’s where I slightly disagree with going straight into deeper repair steps first.
Another one: if the disk is **spinning HDD**, leave it connected for 10 to 15 mins before retrying mount. Tahoe seems a bit less patient with slow external drives during startup. Annoyng, but real.
@mikeappsreviewer and @reveurdenuit already covered the usual repair path, so I’d use this order:
1. Safe Mode test
2. Check `diskarbitrationd` logs
3. Try another enclosure if it’s a bare SATA drive in USB housing
4. Recover data before erase
If the files matter, use **Disk Drill** to make a backup image first and recover from that instead of poking the original disk to death. If you want a quick walkthrough, this Disk Drill external drive recovery guide for Mac is pretty easy to follow.
If it mounts in Safe Mode or another enclosure, I’d blame Tahoe exposing an old compatibility issue, not the disk instantly “dying.”
If Disk Utility sees the disk but mount fails, I’d check one thing none of the others really leaned on: **whether the partition scheme itself got flagged weirdly by Tahoe**.
In Terminal:
```bash
diskutil list
sudo gpt -r show /dev/diskX
```
If the GUID map looks broken, overlapping, or missing entries, First Aid on just the volume may never fix it. That is different from plain file system corruption.
I also would not overfocus on Tahoe as the villain yet. Updates often expose a drive that was already marginal. @reveurdenuit, @sognonotturno, and @mikeappsreviewer covered the common mount, cable, Safe Mode, and recovery angles well, but I’d add this split:
- **Volume visible, container healthy, mount fails** = file system issue
- **Whole disk visible, partition map weird** = partition table issue
- **Disk size incorrect or zero-ish** = enclosure or bridge issue
Another useful check:
```bash
sudo dmesg | tail -50
```
Look for I/O errors, disconnects, or media-read failures right when you try mounting. That can tell you fast if macOS is refusing the mount for safety.
If data matters, clone or image before repair attempts. That’s where **Disk Drill** is actually useful.
**Pros of Disk Drill**
- easy imaging for unstable drives
- good at seeing volumes macOS refuses to mount
- simpler than raw Terminal tools
**Cons**
- not free for full recovery
- can feel heavy if you only want quick diagnostics
- not a substitute for hardware repair or pro recovery on failing disks
If the partition map is bad but hardware is stable, I’d recover files first, then repartition and reformat the whole device from the top-level disk, not just the volume.