My external drive suddenly stopped mounting on my Mac, and Disk Utility shows com.apple.diskmanagement.disenter error 49218. I need the files on it and want to fix the disk without erasing or losing data. Has anyone dealt with this Mac disk mount error and found a safe repair method?
I ran into this with an external SSD last month. Disk Utility saw the drive, Finder did nothing, and the error tied back to “com.apple.DiskManagement.disenter”. What it meant in my case was simple enough. macOS knew the hardware was there, but it would not attach the file system.
A few things tend to cause it. Bad ejects. A damaged file system. A format macOS reads poorly. Sometimes a repair job starts in the background and then hangs there like a dead tab.
What I’d do, in order:
1. Stop the stuck file system check
After an unsafe unplug, macOS often kicks off fsck in the background. If it stalls, the disk sits there in limbo. I’ve seen this more with bigger external drives and exFAT.
Open Terminal and run:
sudo pkill -f fsck
Enter your password. You won’t see characters while typing. That part is normal.
If the mount happens right after, don’t trust the drive yet. I’d copy off anything important first. No cleanup, no experimenting, no extra writes if you can avoid them.
2. Check the full disk layout in Disk Utility
Disk Utility hides parts of the device tree unless you tell it not to. Open it, hit View, then pick Show All Devices.
You should see the whole chain, usually the physical disk, then a container if one exists, then the volume.
Run First Aid in that order, top to bottom. Start with the physical disk. Then the container. Then the volume.
I would not quit after one failed pass. I’ve had a second run fix directory junk the first run skipped, and once it took three tries before the volume came back. Feels dumb, worked anyway.
3. Reset the session before you blame the drive
Sometimes DiskManagement gets weird on its own. I’ve had a logout/login clear it. If you’ve got another user account on the same Mac, test there too.
If the disk mounts fine in the other account, your main profile is part of the problem. Cached settings, permissions, old preferences, something along those lines.
4. Turn off Time Machine for a bit
If this drive was ever used with Time Machine, macOS sometimes keeps poking at it like it still owns it. I’d disable automatic backups in System Settings, then try the mount again.
This one sounds random. I know. Still worth trying because it takes about a minute.
5. Stop forcing repairs if First Aid keeps failing
Once Disk Utility starts throwing the same errors over and over, I stop there. Repeated repair attempts on a damaged file system are how you make a bad day worse.
At that point I switch to recovery. Disk Drill is one option. It can scan a disk even when Finder won’t mount it, and it reads the raw data well enough to pull files or rebuild folders in some cases.
Small rule, but don’t break it. Save recovered files to a different drive. Not the broken one. I did this wrong once years ago and, yeah, that was a dumb week.
6. Wipe and reformat only after the data is safe
After you’ve got your files somewhere else, erase the drive in Disk Utility. Pick the physical disk itself, then Erase.
Format choice matters:
APFS if the drive stays with Macs.
Mac OS Extended (Journaled) if you need older Mac support.
exFAT if you move files between macOS and Windows.
I’ve had fewer weird exFAT issues when the format was done on the Mac I planned to use, instead of some random PC or a TV box or whatever formatted it before.
What I’d keep in mind
The order matters more than people think. Get the files off first. Format later. If the disk starts mounting again after any of these steps, treat it like it’s on borrowed time until you’ve copied your stuff.
And yeah, eject the drive before unplugging it. It sounds fussy till you lose a weekend to cleanup. Been there, typo and all, not fun.
1 Like
Yes, sometimes you fix disenter error 49218 without erasing. I would not start with erase.
One thing I’d add beyond what @mikeappsreviewer listed is to try a manual mount from Terminal. Disk Utility often hides the real error.
Run:
diskutil list
Find the external volume identifier, like disk4s1, then run:
diskutil mount readOnly /dev/disk4s1
Read-only matters. It reduces extra writes while you’re trying to save data. If mount fails, run:
log show --last 10m | grep -i diskmanagement
That log often shows if the block is permissions, file system damage, or I/O errors from the enclosure.
Also, swap the cable and port before doing more repair work. Sounds dumb, fixes more cases than people admit. USB hubs are common troublemakers too.
If the drive shows SMART issues, or if Console logs mention I/O errors, stop trying repairs. At taht point focus on recovery first. Disk Drill is solid for this since it scans unmounted drives well on macOS.
If you later need a wipe, this guide for formatting a problem drive in Terminal on Mac is easier to follow than most text posts.
Small disagreement with repeated First Aid runs. One extra pass, sure. Three or more on a failing disk feels risky to me. Copy files off first if the drive mounts even once.
Yes, sometimes you can fix com.apple.DiskManagement.disenter error 49218 without erasing, but I’d be a little more cautious than @mikeappsreviewer on repeated repair attempts. If the file system is already shaky, too much “fixing” can turn recoverable into cooked.
What I’d do that hasn’t already been covered:
- Test on another Mac if you can. Not just another account. A totally different Mac will tell you fast whether this is your system stack or the drive itself.
- If it’s an NTFS drive, macOS can read it but gets weird when third-party NTFS tools are installed or half-broken. Paragon, Tuxera, old helper kexts, stuff like that. I’ve seen those cause disenter errors.
- In System Information > USB or Thunderbolt, check whether the enclosure is negotiating properly. If the bridge board is flaking out, Disk Utility can still “see” the disk while mount keeps failing.
- If the drive ever mounts for even 30 seconds, skip repairs and copy data first. Seriously. Don’t get brave.
I also like checking this in Terminal:
diskutil verifyDisk /dev/diskX
diskutil verifyVolume /dev/diskXsY
That verifies without jumping straight into repair mode. Better first move imo.
If the volume won’t mount but the disk is still readable, Disk Drill is a solid next step on Mac because it can scan an unmounted external drive and recover files to another disk. That’s probly the safer route before erase/reformat.
Also, this guide on fixing Mac DiskManagement disenter errors like 49218 and related codes is a decent quick reference.
Short version: yes, possible without erasing. But if the drive has actual hardware/enclosure issues, you’re not “repairing” your way out of that one.
I’d add one angle the others only touched lightly: look at whether the volume is simply marked “do not auto-mount” or has a stale mount record, because that can throw disenter errors without the file system being completely toast.
Try this in Terminal after diskutil list:
diskutil info /dev/diskXsY
Check these lines:
- File System Personality
- Type (Bundle)
- Read-Only Media
- Volume Total Space
- Mount Point
- Media OS Use Only
- Protocol
If the disk details look normal but it still refuses to mount, try:
sudo mkdir /Volumes/testmount
sudo mount -t exfat /dev/diskXsY /Volumes/testmount
Or if it is HFS+:
sudo mount -t hfs /dev/diskXsY /Volumes/testmount
I know @reveurdenuit suggested a manual mount already, but I’d go one step further and test a direct filesystem mount like this because it sometimes tells you more than diskutil mount does. If that returns “invalid argument” or “unknown special file”, the partition map may be the actual problem, not the volume itself.
Another useful check:
gpt -r show /dev/diskX
If the GPT table is damaged or weirdly offset, macOS may see the device but reject mounting the partition cleanly. That is one of those cases where First Aid is not really solving the right layer.
One small disagreement with @mikeappsreviewer: I would not keep poking fsck processes unless you are sure they are hung. Sometimes killing them interrupts the one thing that might have completed.
If the partition map looks bad but the drive is still readable sector-by-sector, that is where Disk Drill makes sense before erase.
Pros: good with unmounted drives, simple UI, decent preview/recovery flow on Mac.
Cons: deep scans can take forever, recovery names/folders are not always perfect, and the best features are paid.
So yeah, possible without erasing, but I’d stop thinking only in terms of “repair the file system” and also check partition map, enclosure behavior, and manual filesystem mount. That’s the part people skip.