My external SSD suddenly stopped mounting on my Mac, and I keep getting the Com.apple.diskmanagement.disenter error when I try to open it. Disk Utility can see the drive, but I can’t access any of my files, and I’m worried about losing important data. I need help figuring out what causes this error and the safest way to get the SSD mounted again.
Drive shows up in Disk Utility but stays grayed out
I ran into this with an external drive a while back. Disk Utility saw the hardware, but the volume would not mount, and macOS threw the com.apple.DiskManagement.disenter error. What I found was simple enough. The Mac could see the drive itself, but it was choking on the file system layer.
From what I saw, this usually traced back to one of a few things. The drive got pulled without ejecting. The file system ended up in a bad state. Or macOS started checking the disk in the background and never finished.
Before you assume the data is toast, start with the low-risk stuff.
1. Kill a stuck fsck job
This was the first thing I tried, and in my case it mattered.
If a drive gets unplugged the rough way, macOS often launches fsck on its own. That check is supposed to keep things safe, but while it is running, the disk often stays locked. On big external drives, and on exFAT in partcular, I have seen it sit there forever.
Open Terminal from Applications > Utilities and run:
sudo pkill -f fsck
Type your Mac password when asked. You will not see the characters appear. Apple still does it like this.
What this does is stop the file system check process if it is hung. A few times, I saw the drive mount right after. If yours comes back read-only, stop poking at it and copy the important stuff off first.
2. Run First Aid on every layer, not only the volume
This part gets missed a lot.
Open Disk Utility. Click View, then Show All Devices. You want the whole stack visible, not only the top volume. On many drives, there is the physical disk, then a container, then the mounted or unmounted volume.
Run First Aid in this order:
- Physical disk
- Container
- Volume
I would run it more than once if the first pass reports changes. I have had one pass clear one issue and the second pass catch the next one. Feels dumb, but I saw it work.
3. Log out and try again, or switch users
This sounds too easy, but I would still do it.
A couple times the drive was fine and DiskManagement on my account was the weird part. I logged out, signed back in, and the disk mounted like nothing happened. If your Mac has another user account, test from there too.
If it mounts for the other account, the drive itself might not be the problem. Your main profile, its permissions, or some saved preference junk might be involved.
4. Check whether Time Machine is hanging onto it
If the disk was ever used with Time Machine, macOS sometimes gets clingy about it.
Go into System Settings and turn off automatic Time Machine backups for a bit. I have seen backup processes and snapshots keep a disk busy longer than expected. Once disabled, the drive sometimes frees up and mounts normally.
5. If First Aid and Terminal fail, switch to recovery mode for your files
This is where I stop trying random fixes.
If the drive still refuses to mount, repeated repair attempts are a bad habit. I learned this the hard way on an old external where every extra attempt made the file tree uglier. If directory damage is already there, forcing repairs over and over does not help your odds.
At that stage, I would move to recovery first. Disk Drill is one option. It scans the raw drive data even when macOS will not mount the volume in the normal way. Sometimes it rebuilds enough of the folder layout to pull your files onto another disk.
The order matters. Get the data out first. Fix or wipe the drive after.
6. Erase the drive only after the files are safe
Once your data lives somewhere else, then wipe the problem drive.
In Disk Utility, select the physical disk and choose Erase.
What format you pick depends on where the drive will live:
- Mac only, APFS
- Older Mac workflows, Mac OS Extended Journaled
- Mac and Windows, exFAT
If you need exFAT, I would format it from the Mac side if this problem started there. I have had fewer weird mount issues doing it that way.
A couple things I keep in mind now
- Always eject before unplugging
- Big drives take a long time to check
- exFAT gets flaky more often than I like
- RAID does not replace backups
If First Aid looks frozen, give it more time than feels reasonable. I have seen large disks sit for ages and then finish.
2 Likes
If Disk Utility sees the SSD, I’d stop trying to mount it over and over. Each failed mount or repair attempt risks more file system mess, esp if the partition map is damaged.
A few things I’d check that @mikeappsreviewer didn’t cover.
Run this in Terminal:
diskutil list
Look for whether the drive shows a valid partition scheme, GUID Partition Map, and whether the volume type looks normal, APFS, HFS+, exFAT, NTFS. If the partition entry looks missing or weird, the issue is often the map, not the volume.
Then try a non-mounting verify:
diskutil verifyDisk /dev/diskX
diskutil verifyVolume /dev/diskXsY
Use your actual disk IDs. This checks structure without forcing a mount. Safer first step.
Also check system logs:
log show --last 10m --predicate ‘process == ‘diskmanagementd’’
If you see I/O errors, checksum errors, or repeated disconnects, think hardware path first. Bad cable, bad enclosure, weak USB hub, or SSD power issue. I’ve seen more of these be cable/enclosure probelms than macOS bugs.
I’d also try:
- Different cable.
- Different port.
- No hub or adapter.
- Another Mac, if available.
If the drive is encrypted, try unlocking it in Terminal with diskutil apfs unlockVolume or diskutil coreStorage unlockVolume, depending on format.
If your files matter, Disk Drill is a solid next move before erase or heavy repairs. It’s better to scan and recover data first, then wipe the SSD later.
For anyone reading, the safest move is to stop interacting with the disk and focus on file recovery from an unmountable external SSD. Apple thread here if you want another case example: fixing com.apple.diskmanagement.disenter mount errors on Mac
If Disk Utility sees the SSD but Finder won’t mount it, I’d spend less time on First Aid loops and more time figuring out whether this is a file system problem or a flaky USB/NVMe bridge. I agree with parts of what @mikeappsreviewer and @nachtschatten said, but I’m a little less sold on killing fsck right away unless you know it’s actually stuck. Sometimes it’s just slooow and people interrupt the one thing trying to save the volume.
A couple things I’d do that are different:
1. Check the SMART / health info
In Terminal:
diskutil info /dev/diskX
Look for Media Name, Protocol, SMART status if exposed, and whether it says Read-Only Media: Yes. If the SSD flipped read-only, that can be the drive protecting itself, not macOS being weird.
2. Try mounting read-only
This is underrated if your files matter.
diskutil mount readOnly /dev/diskXsY
If it mounts read-only, stop there and copy data off. Don’t “fix” it first.
3. Rule out enclosure nonsense
External SSD problems are weirdly often the enclosure chipset, not the SSD. If it’s a removable NVMe/SATA inside a USB case, test the bare drive in another enclosure if possible. Cheap bridge boards love to fail in dumb ways.
4. Check if the partition type UUID is wrong
I’ve seen volumes that exist but have the wrong partition type flag, so macOS sees “something” but won’t mount it properly. gpt -r show /dev/diskX can reveal that. This is more advanced, so don’t start editing GPT entries unless you know what you’re doing.
5. If it’s exFAT, be extra careful
Honestly, exFAT is convenient until it decides today is the day. A lot of these mount/disenter issues on portable SSDs end up being exFAT corruption after an unsafe unplug or sketchy hub power event.
If the data matters, I’d prioritize recovery before deeper repairs. Disk Drill is actually useful here because it can scan an external SSD that macOS won’t mount and let you recover files to another drive. That’s a better path than poking the disk 27 more times and hoping Apple magic kicks in.
Also worth checking if this applies to your model or symptoms: fixing Disk Utility and disenter errors on Seagate drives for macOS
Short version: try read-only mount, test another enclosure/cable/path, check health info, then recover with Disk Drill before doing anything destructive. That’s the less regret-y route, imo.
