My external SSD suddenly stopped mounting on my Mac and now I keep getting the com.apple.diskmanagement.disenter error 49218 message. I’ve tried unplugging it, restarting, and checking Disk Utility, but I still can’t access my files. I need help figuring out what caused this and how to fix the drive without losing data.
I hit this with an external SSD a while back. Finder showed nothing useful, Disk Utility saw the device, and the volume sat there gray with a mount failure. The usual meaning of “com.apple.DiskManagement.disenter” is pretty plain, macOS sees the hardware, but it is refusing to attach the file system.
What I kept seeing came down to three common messes. Someone yanked the drive without ejecting it. The file system took damage, or macOS stopped handling it cleanly. Or a background repair process got stuck and held the disk hostage.
This is the order I would go in.
Kill the hung file system check first
After a rough unplug, macOS often starts fsck. That is the file system checker. Nice idea, bad result when it freezes, because the disk sits in limbo and never mounts.
Open Terminal and run:
sudo pkill -f fsck
Hit Enter. Type your Mac password. You will not see characters while typing. macOS does that on purpose.
If the drive shows up right after, stop poking at it and copy your files off now. No heroics. If it mounts read-only, even more reason to move fast.
Run First Aid in the right order
This part trips people up. Disk Utility often hides part of the structure, so first go to View, then choose Show All Devices.
I would run First Aid top to bottom like this:
1. Physical drive
2. Container, if one appears
3. Volume
I learned the hard way that running it only on the visible volume misses problems higher up. Repeating First Aid once or twice sometimes helped for directory issues, B-tree damage, or messed up headers. Feels dumb, but I have seen the second pass catch what the first one didn't.
Try a clean user session
One time the disk was fine and my login session was the broken part. Logging out fixed it. No clue why.
So, sign out of your account and sign back in. If you have another user on the Mac, test there too. If the drive mounts under the other account, your main profile is where the mess lives, permissions, session junk, old prefs, something along those lines.
Look at Time Machine before you keep digging
This one feels random until it happens to you. If the drive used to be a Time Machine target, macOS sometimes keeps a grip on it in the background.
Turn off automatic Time Machine backups for a minute in System Settings. Then try mounting the disk again.
When mounting keeps failing, switch from repair to recovery
There is a point where more repair attempts stop being useful. I crossed it once by rerunning tools over and over, and the drive got worse, not better. If the same errors keep coming back, I would stop trying to fix the file system in place.
At that stage, pull data first.
Disk Drill is one of the tools people use for this. It scans below the normal mount layer, so even when macOS refuses to mount the volume, you still have a shot at finding files or rebuilding something close to the old folder layout. Save recovered files to a different healthy drive. Not the same one. Don't write back onto the problem disk, typo or not, you dont want to do that.
Erase it only after the files are safe
Once your important stuff is somewhere else, then wipe the drive and start over.
In Disk Utility, select the physical disk, not only the volume, then click Erase.
If the drive stays with Macs, use APFS or Mac OS Extended Journaled. If you need it on both Mac and Windows, pick exFAT. If the drive spends most of its life on your Mac, formatting it there has worked better for me.
The main mistake is panic. The second mistake is hammering the disk with endless repair passes. Get your files off first. Reformat after. And yeah, eject the thing before unplugging it next time. Boring advice, but it saves hours.
1 Like
Error 49218 usually means macOS sees the SSD, but it rejects the volume layer. I’d look at a different angle than @mikeappsreviewer.
Check the file system format first. A lot of these cases are exFAT drives with a dirty bit set, bad allocation table, or damage from unsafe removal. APFS and HFS+ often show cleaner errors. In Terminal, run:
diskutil list
Then run:
diskutil info /dev/diskX
Replace diskX with your SSD. Look for File System Personality and Read-Only Media. If it shows exFAT, test the drive on a Windows PC too. Windows sometimes mounts exFAT disks Mac refuses to touch. Weird, but it happnes.
Also check SMART or USB bridge health. Cheap enclosures fail before the SSD does. Swap the cable. Swap the port. If it is in an enclosure, remove the SSD and test with another enclosure or adapter. I’ve seen 49218 caused by the USB-SATA bridge, not the data on disk.
One point I slightly disagree on, killing fsck is not where I’d start unless Activity Monitor shows it stuck for a long time. First I’d rule out hardware path issues.
If Disk Utility won’t mount it, try a manual read-only mount attempt from Terminal. Safer for a shaky disk.
If your files matter, move to recovery fast. Disk Drill is a solid option for Mac external SSD recovery because it scans drives even when Finder will not mount them. Before deciding, read Disk Drill user reviews and ratings.
If recovery works, erase the SSD, then retest it. If it fails again after a clean format, the enclosure or SSD is dying.
49218 usually means macOS can see a disk, but something in the chain above raw hardware is failing. I agree with parts of what @mikeappsreviewer and @hoshikuzu said, but I would not jump straight into repeated repair attempts if the SSD is making weird disconnect sounds, vanishing from diskutil list, or taking forever to populate info. That pattern screams connection path or failing controller more than simple file system damage.
What I’d check next is the system log, because Disk Utility errors are often too vague to be useful. In Terminal:
log show --last 10m | grep -i diskmanagement
and also:
log show --last 10m | grep -i 'I/O error'
If you see I/O errors, disconnects, or bridge resets, the problem may be the external SSD hardware, enclosure, cable, or adapter, not just macOS mount logic. That matters because running repairs on unstable hardware can make recovery harder.
Another thing people miss: if the drive is encrypted, corrupted encryption metadata can throw mount errors that look generic. In Terminal, run:
diskutil apfs list
If the volume shows as encrypted or locked, try unlocking it manually instead of normal mount attempts.
If the data matters, stop testing too much and recover first. Disk Drill is a solid Mac data recovery option for external SSDs that show the com.apple.diskmanagement.disenter error 49218 because it can scan the device even when the volume won’t mount in Finder.
Also, this kind of mount failure can sometimes point to a physical issue with the external drive itself, not just a software glitch. This external hard drive troubleshooting guide for drive detection and hardware faults covers that side pretty well.
If the SSD works in another enclosure or with a direct adapter, you found the real culprit. If it fails everywhere, yeah, the drive may be on its way out. Sad but prety common.
