An external disk refuses to mount, com.apple.DiskManagement.disenter error -119930868.
What causes this particular error and what can I do to mount this drive or retrieve the data from it?
iMac Line (2012 and Later)
You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
What causes this particular error and what can I do to mount this drive or retrieve the data from it?
iMac Line (2012 and Later)
I ran into this issue with a Western Digital 2TB drive... I had seen some irreperable disk errors and was ironically, attempting to back the drive up so I could reformat it... so, I was panicking because I've got some important data on the drive and was starting to research data recovery tools. After messing around and doing some research, I discovered the system was trying to run a filesystem check on it and was getting hung up.
I opened a terminal window and entered the following commands
$ ps -ef | grep fsck
$ sudo kill [pid from above]
BAM! Disk mounted just like that.
At this point, I opened Disk Utility and ran First Aid... which ironically unmounted the drive and then got hung up again... DUH! So had to repeat the process. At this point, with the drive mounted, I backed up the drive and reformatted it.
Hope this helps.
I've several HDD's of different brands and sizes. Until I had the 17" MBP, non things happened to me fo years. After buying the new 16" with Catalina, it happens about once a month that one of my HDD's can no longer mounted, as if it were broken. But they are not broken...; all broken ?
HDD's are formatted with Mac OS Journaled (no code). After that error (49244) I have to recover the files with DiskDrill, reset the disk and go on....
But it is impossible that happens every times, to different HDD's !!
I tried to changed the usb-hub with a new direct dedicated cable...but it's the same.
It's a Catalina bug (10.15.5). Now I tried to initialize with APFS...Let see what happens.
Does anyone have any suggestions ?
for some of you downloading Tuxera (and paying for it), I would look into getting Paragon Software, on the Seagate website. I would assume It works with only Seagate drives, but it fixes the issue for free. I was also able to mount one of my drives that was greyed out in Disk Utility. Hope this helps!
For anyone who gets this issue in future, open 'Activity Monitor' ---> search "fsck" ---> check all tabs (CPU, Memory, etc.) i got it in "Disk" tab ---> 'Force quit' the process --------> Your disk will show up. :-)
I wasted few hours on this after i "not safely" removed my hard drive. Just end the fsck process and it should work. It worked for me.
Thanks! I've never worked with codes, never even launched Terminal. Your instructions, though, make it seem like something I could handle. I'll try it out next time I get that 'disenter' error message. Much appreciated.
I'm having the same problem as Bill Canada.
The thing is that I have spent the last 2 weeks formatting and reformatting drives. I actually bought a new computer to transfer more quickly! (My mid 2010 MBP with Yosemite didn't have the muscle to reformat in a reasonable amt of time.)
The drives are 5TB WD Easystore drives I'm working with, and I'm formatting in ExFAT to be compatible with Playstation gamesystems.
I switched from SiliconPower to WD because of the great ratings. I haven't revisited that SP drive because it's smaller than the WD drives. It's commonly known that ExFAT is less stable and slower than Apple's preferred language. Bigger drives also mean more things can go wrong. Seriously though: every time a drive has been accidentally unplugged I have had to completely reformat the drive, and that seems a bit excessive. I didn't have this problem with my 32bit mid2010MBP using Yosemite, and I hate to admit how many times that 2TB SiliconPower drive had been accidentally unplugged from it not having any problems for YEARS. I'm wondering if the bit size leaves more room for things to go wrong? (Kind of like 3G vs 4G vs 5G: more compressed wavelengths or something?)
I'm chasing a deadline here, and when you pay thousands of dollars for new tech, you hope it would work. I haven't called AppleCare yet, but if it's an external drive problem, that's not their problem. I hope people are troubleshooting Catalina and can find a way to bootstrap the processes, so that these frequent wipe/reformats aren't necessary. I have been an apple user for over 10 years now and freaking love the intuitive design of most of their products. Microsoft is worse, no way I'm going back. I don't want to learn Linux and open source culture, so much work--so much time.
- - - -
Oh wait... now after 1 hour of drafting this searching for trouble shooting options, etc. (with the drive still plugged in) it decided to suddenly recognize it, mount, and populate the icon on the desktop.
I did nothing to it to cause this--it just took time (an engineer's nightmare: no process, no evidence).
I'm going to create a backup now. This is nerve-racking. Please find a way to bootstrap this process!
I'm glad your drive mounted...after an hour of waiting. C'mon guys. We have to push back on Apple here. This is ridiculous!!! Would you have to wait an hour for a drive to mount on a PC? It should just be plug 'n play! I work in video and my workflow involves projects on different drives. I frequently need to swap drives during the day. I can't wait an hour for a drive to mount.
Alsoft DiskWarrior. Expensive, but it worked for me. Used the mount button. Then rebuilt the drive's directory with no data loss. I can't guarantee anyone else's results. I don't work for Alsoft. Just saying, it worked for me.
After trying many of these possible solutions to the following error:
Could not mount (com.apple.DiskManagement.disenter error 49153)
This https://forums.macrumors.com/threads/invalid-content-in-journal.1941721/ worked for me! I finally gained access to a 2 TB San Disk thumb drive with an HFS file system.
My 2012 Macbook Pro Retina with Mac OS Catalina was not running the FCSK process either, so that possible resolution was N/A for me.
I am having the same issue. Very frustrating. I am getting the error: (com.apple.DiskManagement.disenter error-119930868) on my WD 1 TB drive.
The fsck process everyone has been talking about is not showing up in my Activity Monitor so I am just going to wait a few hours and see what happens.
I upgraded the 128GB SSD in my 2012 MBP with a 480GB and used the old SSD with a OWC enclosure as external drive. It worked for a while but when I plugged it in after a month or two I got the same error message and unable to mount the drive. I really need to access the files on there.
I have "disenter 0"
Upgraded to Catalina few days ago.
Initially was able to see my external Hard Disks.
Today, Catalina suddenly hanged.
When I restarted the iMac again, the Hard Disks have disappeared.
Can see them in Disk Utility but cannot repair nor mount them.
What this means, I think, is that the HDs are working but are unable to be mounted.
Previously, had similar problem when using High Sierra.
The HDs reappeared mysteriously after a few days !
Not sure what will happen this time.
Any help is much appreciated.
I'm having the same issue. I am upgrading to MacOS Bigsur as soon as possible. It seems like it is only happening to users using Catalina. Someone even said that their iMac Pro running Catalina has this issue but not their MacBook running Mojave. I also didn't have this issue at all until I upgraded from High Sierra to Catalina. Either I wait a billion years for Bigsur to release, or I get support and downgrade to Mojave.
That is because Catalina uses fsck to read drives, no other MacOS versions use it. I am either going to downgrade from Catalina to Mojave or upgrade to Bigsur as soon as it releases. I recommend you do the same.
This is the exact answer that works... I keep having this problem using a 5TB external HD (it came as Exfat - so I have kept it like that so I can plug it in to my PCs also). But quite regularly it has this "mount" problem which is really getting irritating.
This answer took me to the exact problem in Activity Monitor - I just searched for fsck in the top right search bar. Eventually it showed the fsck process. The very second I killed the process the external drive way instantly visible.
Thanks Dahn for your persistent answer to this problem. It is the only one that works. Appreciate it!
An update to my previous post: I think the external drive did not show up because it was not properly ejected before being disconnected. When the drive is reconnected OS X starts an automatic disk check (fsck) and the drive will not show up until this process is done. This can take a long time for large disk with multiple TBs of data.
The com.apple.DiskManagement.disenter error is caused by the running fsck process.
Force quitting fsck will only give you read-only access to the drive. After force quitting it I manually started a "first aid" fsck from the OS X disk utility. This took a long time. After it was done I could eject and reconnect the drive and this time everything was OK.
Suggest people just leave the fsck_ext process running and wait for it complete. I think the problem will fix itself if you just give it time to do its job (can take many hours for a large drive).
An external disk refuses to mount, com.apple.DiskManagement.disenter error -119930868.