My encrypted external drive suddenly stopped mounting on my Mac and now I keep getting the com.apple.diskmanagement.disenter error. I need help figuring out whether this is a macOS issue, a FileVault or encryption problem, or a sign the disk is failing, because I have important files on it and can’t access anything.
I hit this with an external SSD a while back. Disk Utility saw it, but the mount button did nothing and the log threw the usual com.apple.DiskManagement.disenter mess. In plain terms, macOS notices the hardware, but it fails at the file system step.
What I kept seeing came down to three common causes:
1. The drive got unplugged without ejecting first.
2. The file system took damage, or macOS stopped handling it cleanly.
3. A background repair process got stuck and held the disk hostage.
This is the order I’d use.
Kill the frozen file system check first
After a rough disconnect, macOS often starts fsck. Sometimes it finishes. Sometimes it sits there forever and the drive never mounts.
Open Terminal and run:
sudo pkill -f fsck
Hit Enter, type your Mac password, then wait a few seconds. You won’t see the password as you type. Apple still does it this way, annoyng but normal.
If the drive pops up right after this, stop troubleshooting and copy your files off now. If it mounts read-only, even more reason to move fast.
Run First Aid from the top down
Disk Utility hides part of the layout by default, which wastes time. Open Disk Utility, click View, then pick Show All Devices.
Then do First Aid in this order:
1. Physical disk
2. Container, if one exists
3. Volume
I’ve had cases where the visible volume looked like the problem, but the mess was one layer higher. Running First Aid once is not always enough either. If you get directory errors, B-tree complaints, or header issues, a second pass sometimes clears it. Not elegant, still worth trying.
Try a clean user session
I know this sounds off topic, but I’ve seen the disk be fine while the user session was the broken part. Log out, then log back in. If you have another account on the Mac, test from there too.
If the drive mounts under a different account, your main profile is where I’d look next. Permissions, stuck preferences, odd session junk, any of those can trip mount behavior.
Turn off Time Machine for a minute
This one got me once and I lost an hour chasing the wrong thing.
If the disk used to be a Time Machine target, macOS sometimes keeps poking at it in the background. Go into System Settings, disable automatic Time Machine backups for the moment, then try mounting the disk again.
Not common every time, but common enough.
When it still won’t mount, switch from repair to recovery
At some point, more repair attempts stop helping. If the drive keeps failing, I would stop trying to force a mount and start pulling data off it instead.
Disk Drill is one option for this. It scans below the normal mount process, so it may still read the drive when Finder and Disk Utility refuse to cooperate. I’ve seen tools like this rebuild a usable file list even when the volume itself looked dead.
Save recovered files to a different healthy drive. Don’t write them back to the problem disk. Sounds obvious, people still do it.
Erase the disk only after your data is safe
Once your files are somewhere else, wipe the bad disk and set it up again in Disk Utility. Pick the physical drive, click Erase, then choose the format based on how you use it.
For Mac-only use, APFS is usually the right pick. Mac OS Extended Journaled still has its place on older setups. If the disk needs to move between macOS and Windows, exFAT is the practical option.
If the drive spends most of its life on a Mac, I’d format it there instead of bouncing between systems and hoping for the best.
The part I’d avoid
I would not keep hammering First Aid over and over once the disk starts throwing the same mount errors. That’s where people burn time and sometimes make recovery harder. Get your files first. Clean up the disk later.
And yeah, eject the drive before unplugging it. Boring advice. Still cheaper than data recovery.
1 Like
If the disk is encrypted, I’d look at the unlock layer first, not the mount layer. The disenter error often shows up after decryption fails, and Disk Utility reports it like a generic mount issue. So I partly disagree with @mikeappsreviewer on starting with file system repair. On an encrypted external, I’d confirm the crypto state before pushing First Aid.
Open Terminal and run:
diskutil list
Find the external disk identifier, then run:
diskutil apfs list
If you see an APFS encrypted volume, try:
diskutil apfs unlockVolume diskXsY
If it asks for a password and rejects the correct one, the issue is often the volume metadata or keybag, not Finder. If it unlocks but still will not mount, then try:
diskutil mount diskXsY
If the drive was encrypted as HFS+ instead of APFS, use:
diskutil cs list
Older encrypted HFS+ and CoreStorage volumes break in different ways after macOS updates. I’ve seen Sonoma and Ventura get picky with older external setups.
Also check system logs. This helps more than Disk Utility’s vague errors:
log show --last 10m | grep -i diskmanagement
log show --last 10m | grep -i apfs
Look for lines mentioning wrong passphrase, crypto user, object map, checkpoint, or container superblock. Those point in differnt directions fast.
One more thing. FileVault is for your internal startup disk. External disk encryption is usually APFS encrypted or old CoreStorage, so don’t chase FileVault settings too hard.
If the volume still refuses to unlock or mount, stop writing to it. At that point a recovery tool like Disk Drill makes sense, since it reads the disk without depending on a normal mount. Also, if you want a quick read on user feedback, check real Disk Drill user reviews and ratings.
I’d split this into unlock problem, file system problem, and hardware problem, because com.apple.DiskManagement.disenter is just macOS saying “nope” without telling you which layer actually failed.
I agree with @ombrasilente that FileVault is probly a red herring here. On an external disk, it’s usually APFS encryption or older CoreStorage, not FileVault in the normal startup-disk sense. I also kinda disagree with @mikeappsreviewer on jumping into repeated repair first if the drive is encrypted. If the encryption header or APFS metadata is shaky, too much poking around can waste time.
What I’d do that hasn’t been covered yet:
- Try the drive on another Mac, ideally one on a different macOS version
- Try a different cable, port, and if possible a powered hub
- Check if the disk shows the correct size in System Information
Apple menu > About This Mac > System Report > USB / Thunderbolt
If it appears with the wrong capacity, disconnects randomly, clicks, or vanishes/reappears, that leans more toward a physical external drive hardware issue causing the Mac mount error, not just a macOS encryption glitch.
Also, boot into Safe Mode once and test mounting there. That helps rule out third-party disk utilities, AV tools, old NTFS drivers, etc. Those can absolutely break mount behavior.
If the disk unlocks nowhere and multiple Macs fail the same way, stop trying to “fix” it in place. That’s when I’d move to Disk Drill for encrypted external drive recovery on Mac, assuming the hardware is still readable at all. Recover to another disk only.
If you want a decent example of troubleshooting a failing external drive before total death, this is worth skimming: external hard drive troubleshooting steps that actually make sense.
Short version: if it’s seen but won’t unlock, think encryption/APFS metadata. If it’s seen wrong or unstable, think hardware first. That distinction matters a lot.
I’d add one check none of the others really leaned on: power and bridge chipset weirdness. @ombrasilente is right to focus on the unlock layer, and @viajeroceleste is right that hardware symptoms matter, but I would not assume encryption metadata is the first culprit if this is a bus-powered external SSD or HDD in a cheap enclosure. A flaky USB-SATA bridge can trigger com.apple.diskmanagement.disenter even when the actual disk is fine.
Try this:
- Connect it directly, no dock if possible
- Use a different cable even if the current one “looks fine”
- Run in Terminal:
diskutil info diskX
system_profiler SPUSBDataType
or for Thunderbolt
system_profiler SPThunderboltDataType
What you’re looking for is whether the Mac sees a stable device model, serial, and negotiated speed. If those fields keep changing after reconnects, I’d suspect enclosure electronics before APFS.
Another angle: if this started right after a macOS update, check whether kernel extensions or security software are intercepting storage events. EtreCheck can help spot junk at login or old low-level drivers. Safe Mode helps, sure, but EtreCheck gives you a faster clue about what is loaded.
If the disk is visible but painfully slow to respond, stop mounting attempts and clone or recover first. Disk Drill is reasonable there.
Pros: easy scan workflow, can read disks that Finder refuses, good for previewing recoverable files.
Cons: not magic on failing hardware, deep scans take a while, and recovery quality depends heavily on how damaged the encryption or file system layer is.
So my split would be: stable hardware ID = likely logical issue. Unstable detection = enclosure, cable, power, or drive electronics first.