An external disk refuses to mount, com.apple.DiskManagement.disenter error -119930868.

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 ?

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.

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.

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.

Yeah, this thread is 12 pages long. You'd think that someone from Apple would've responded by now. I feel your pain Getaway Driver. I do video and have video files on separate hard drives. So it's a lot of in/out every day. I had to buy a piece of unreliable Microsoft software to fix my issue and shouldn't have had to. This is really unacceptable. Plug n' play Apple. Shouldn't be that hard to do!

You do so how ridiculous that is though, right? If I'm on a project and I need access to files at that exact moment from a hard drive, with your solution, I'd have to wait overnight before I can access the files? That's just NOT ACCEPTABLE. EVER. Not in any work environment I know of.

I'm going to try leaving it in overnight, but at this point I think my next computer is going to be a Dell. I can't believe that Apple is just ignoring this problem.

Unfortunately the fsck process does not seem to work for me as I cannot locate this function in the Activity Monitor.

So here is my rendition of the "My drive won't mount on Catalina and..." posts that have stacked up nicely in this thread.

So I'm running a 12 tb 4 bay media sonic raid 5 to back up video and photo work. I backed up my back up to a JBOD earlier in the week and all was well. Then I decided to shuffle some media around, end goal being to move a few things back onto 12tb array. Decent amount of files, I'd say like around 1.5 tb. So I set it forget it and let it do it's thing overnight. When I check in the morning my system is frozen. The transfer errored out and I panic, instinctively tapping the caps lock button hoping to see the green light blink on then off. The only vital sign I can check before doing the much dreaded hard shut down. I do the hard shutdown, fire it back up and the array will not mount. I tried the whole Kill the "FSCK" in activity monitor, this did not work. I've also heard rumors on here of people hooking the "unmountable drive" up to a system running a different OSX. I am running a dual boot with Catalina on one volume and Mojave 10.14.6 on another. I am currently typing this post from Safari on the Mojave volume as I stare blankly at disk manager and the greyed out drive (array) which is yet to mount.. I supposed I will "give it time" which was also mentioned in this monumental thread which has yet to be addressed by anyone from apple. I'll check back here in a few days with an update but if you're any where near as optimistic as I am for a fix on this, you won't hold your breath.

Nothing wrong with holding your breath & waiting. That’s all you can do for now.

Has happened to me a number of times when on boot up, the HDs were not seen on the desktop. Tried all sorts of remedies. Nothing worked. Resigned to fate !

Mysteriously, after some time, up to an hour or two, or even the next day, the HDs reappear.

Happened both in High Sierra & Catalina.

I have no idea what happened.

Have faith. Good luck !

Update on my previous post. I left the drive in for 72 hours and it still did not mount. I have also never seen the fsck process appear in the Activity Monitor. The most recent Catalina update has also not fixed the issue.

This is beyond ridiculous.

Apple, why will you not at least tell us you are working on a fix?

I am on an early 2015 Macbook Pro.

So here I am again, a couple months after my original reply in this thread. Raid still won't mount. I found and tried all this stuff. Can confirm this does not work either. It's a bunch of terminal commands to mount and unmount drives. Terminal said the process timed out. I did it a bunch of times.

https://osxdaily.com/2013/05/13/mount-unmount-drives-from-the-command-line-in-mac-os-x/#comments