My external drive is showing up grayed out on my Mac, and I keep getting the com.apple.diskmanagement.disenter error when I try to mount it. It has important files on it, and I’m worried about losing data. I need help figuring out what caused this and the safest way to get the drive working again.
Disk Utility showing an external drive, then refusing to mount it with “com.apple.DiskManagement.disenter” is one of those Mac problems that wastes an entire evening. I ran into it on an exFAT SSD after pulling it too fast from a hub. The Mac saw the hardware. The file system never came online.
From what I saw, the usual causes are plain stuff. Bad eject. File system damage. A format macOS does not like. Or macOS starts a repair job in the background and never finishes it.
I’d work through it like this.
1. Stop the stuck disk check first
macOS often launches fsck after a drive was removed badly. While it is running, the disk might stay unavailable. On bigger external drives, and on exFAT in particlar, I’ve seen fsck hang for ages.
Open Terminal and run:
sudo pkill -f fsck
Enter your password. You will not see the characters while typing. That part is normal.
If the drive mounts right after this, don’t trust it. I would copy off the important files first and mess with repairs later.
2. Check the full disk tree in Disk Utility
Disk Utility hides too much by default. Open it, hit View, then choose Show All Devices.
You want to inspect the whole stack, not only the volume name. Usually you’ll see:
physical disk
container, sometimes
volume
Run First Aid in order, top to bottom. Start with the physical disk, then the container if there is one, then the volume.
One failed pass does not always mean the drive is done. I had First Aid fail once, then finish on the second run after the parent device got checked first. Not pretty, but it happens.
3. Reset your user session
Sometimes the issue looks less like drive damage and more like macOS getting confused. I’ve had logout and login fix it once. A full reboot helped another time.
If you want a cleaner test, sign into a different user account on the same Mac and try mounting the disk there. If it works under another account, your main profile might have some broken cache, permission weirdness, or stale settings tied to DiskManagement.
4. Turn off Time Machine for a minute
If the drive used to be part of Time Machine, macOS might still try to talk to it like a backup target. I’d go into System Settings, disable automatic backups for now, then try the mount again.
This one feels random until it works. I ignored it the first time. Then I tried it, and the disk mounted right after. So yeah, worth the 30 seconds.
5. Stop forcing repairs if they keep failing
If First Aid keeps throwing errors and the disk still won’t mount, I would stop there. Repeated repair attempts on a damaged file system are how people turn a bad day into a worse one.
At this point, I’d switch to recovery and pull data off before doing anything destructive.
Disk Drill is one option. It scans the raw disk even when Finder refuses to mount it. On a damaged external drive, tools like this sometimes recover the files directly, and sometimes rebuild enough of the folder layout to make the data usable again.
Important part, save recovered files to a different healthy drive. Do not write them back onto the broken one. I know this sounds obvious, but when you’re tired and annoyed it’s easy to click the wrong target. Ask me how I know. heh
6. Reformat only after your files are safe
Once your data is off, wipe the drive and start fresh. In Disk Utility, select the physical disk itself, then choose Erase.
Format picks are simple:
APFS for modern Mac-only use
Mac OS Extended Journaled for older Mac workflows
exFAT if you need Mac and Windows on the same drive
I’d also format exFAT on the Mac you plan to use with it, instead of leaving whatever layout came from another machine. I’ve had fewer mount problems doing it this way.
The order matters. Recovery first. Erase second.
And yeah, always eject external drives before unplugging them. People roll their eyes at this until a volume goes read-only, or disappears, or shows up in Disk Utility like a ghost you can’t touch. Then it stops feeling optional prety fast.
3 Likes
I’d avoid doing more repair passes if the files matter. That’s where I differ a bit from @mikeappsreviewer. First Aid is fine once. After that, switch to diagnosis and recovery.
Do this in Terminal first:
diskutil list
Find the external disk identifier, like disk4s1. Then try:
diskutil mountDisk /dev/disk4
diskutil mount readOnly /dev/disk4s1
Read-only is the safer test. If it mounts, copy your files off fast.
Next, check if macOS sees file system damage without trying to “fix” it:
diskutil verifyDisk /dev/disk4
diskutil verifyVolume /dev/disk4s1
If you get I/O errors, weird size output, or the disk drops in and out, suspect the cable, adapter, or enclosure before blaming the drive. I’ve seen cheap USB-C hubs cause disenter errors. Plug it straight into the Mac. Try another cable. Try another port. Boring step, but it saves time.
If the drive is exFAT, test it on a Windows PC too. macOS is pickier with damaged exFAT volumes. Windows sometimes mounts them read-only or offers a clearer repair message.
If it still stays gray, use Disk Drill to scan the drive before formatting. It’s one of the better Mac data recovery options for an external drive not mounting with com.apple.diskmanagement.disenter. Save recovered files to a different disk.
After recovery, erase the physical device, not the gray volume. If you want a clear guide, here’s a solid video for how to format a problem drive in Terminal on Mac:
watch how to format a failing external drive in Terminal on Mac
Short version. Test read-only mount. Verify, don’t keep repairing. Rule out cable and enclosure. Recover with Disk Drill. Format after your data is safe. Two typo-prone hours now beats losing the whole drive later, trust mee.
I’d add one thing neither @mikeappsreviewer nor @cazadordeestrellas really leaned on enough: check the drive’s health before you let macOS keep poking at it.
If the disk is visible in Disk Utility but grayed out, open Terminal and run:
diskutil info /dev/diskX
and look for:
- Read-Only Media: yes/no
- File System Personality
- SMART status, if available
If SMART says failing, or the capacity shows wrong, stop trying to mount it. That points more to hardware than just a messy file system. Also check Console.app for live errors when you plug it in. Repeated I/O or bridge errors usually means enclosure, adapter board, or power issue. People blame the file system too fast tbh.
Another thing: if it’s a desktop external HDD, use its original power supply if it has one. I’ve seen underpowered drives throw disenter errors and act “corrupted” when they were just not getting enough juice. Annoying, but real.
If the files matter, my order would be:
- Try a different cable and direct connection
- Check SMART / disk info
- Clone or recover first
- Repair later
That’s where Disk Drill makes sense. If the drive won’t mount but is still detected, it can scan the raw device and let you pull files off to another disk. I would do that before getting too brave with First Aid.
Also, for a cleaner walkthrough on fixing Mac DiskManagement disenter errors and getting an external drive to mount again, that guide covers the common error variations pretty well.
One small disagreement with the usual advice: rebooting is fine, but I would not keep replugging a clicking or disappearing drive over and over. That can make a dying disk worse real fast. If it starts making noises, stop. Seriously.
One angle I’d add beyond what @cazadordeestrellas, @sognonotturno, and @mikeappsreviewer covered: check whether macOS is refusing the volume because of ownership/encryption metadata, not just corruption.
In Terminal, inspect it with:
diskutil apfs list
diskutil cs list
sudo gpt -r show /dev/diskX
Why? A gray volume with disenter can happen when the partition map is ugly, the APFS container is present but the volume role metadata is broken, or FileVault/APFS encryption is waiting on an unlock state that Disk Utility does not show clearly.
Also try mounting in Safe Mode. I know people roll their eyes at that, but third party NTFS/exFAT helpers and old kernel extensions still interfere with external disks. If it mounts there, the drive may be fine and the Mac software stack is the problem.
One small disagreement with the repeated “just run First Aid in order” advice: on flaky USB bridges, that can waste time because the bridge lies before the filesystem even gets a fair read. If possible, remove the bare drive from the enclosure and connect it with a known good SATA-to-USB adapter or dock.
If recovery is the priority, Disk Drill is reasonable before any erase:
- Pros: good raw scan support, easy preview, handles drives that won’t mount
- Cons: scans can take ages, folder structure is not always perfect, recovery quality depends heavily on how damaged the filesystem is
If Disk Drill sees the drive but reports tons of read errors, stop stressing the disk and consider cloning it first with ddrescue from another environment. That’s the point where recovery strategy matters more than Mac mount tricks.