com.apple.DiskManagement.disenter error 49153

I have the same problem with the error com.apple.DiskManagement.disenter error 49153

i ran first aid to an external drive that has been working flawlessly for the past 3 years just to see if There are any errors or if there are issues I need to fix. I regretted this right away as after running first aid (and the machine saying there’s nothing wrong with the external drive) that drive wouldn’t mount no matter what I do. Similar issues as others, greyed out, repair and other first aid options work but won’t mount on my desktop or laptop computers. Of course Apple techs says it’s the machine’s fault that it decided to clonk out at that very exact moment I ran first aid. This is an 8Tb drive and many years’ worth of work. The only reason I’m not freaking out is I have a cloud service (not apple’s!) provider that sent me a copy of that drive. Best investment in my life. But c’mon Apple, don’t undermine my intelligence by saying it is the fault of the drive.

Thats' great that it worked for your situation, but that preference was already set on my system, and it doesn't address the error when mounting HFS Standard formatted CDs on my system. So, when you say "I finally got Apple to fix *this* issue..." it sounds like this fix is only for a very specific scenario.

Thanks for letting us know, though!

STILL waiting on Apple to either:

1) Acknowledge the problem, even if there is no currently planned fix

2) Tell us this is the new way of things, so we'd better find our own workarounds.

I had a very nice chat with Apple support. It’s not the drive — it’s the cd. Catalina does not recognize ANY of the audiobooks that I have on cd. The solution that was offered was to revert to a previous back up. No mention of an official fix. Very disappointing.

Hi,

I had the exact same issue with an old CD which was not mountable / readable in macOS Catalina, due to the error 49153. Figured out it was because it used the old HFS standard disc format, for which support in new macOS versions was dropped.

Found 2 ways to retrieve the data by using hfsfuse and hfsutils tools in Catalina. As it takes some steps and preparations, I detailed everything in a blog post here: https://swissmacuser.ch/hfs-volume-data-recovery-diskutility-could-not-mount-error-49153/

Hope it helps,

Oliver

Oliver said: "...it was because it used the old HFS standard disc format, for which support in new macOS versions was dropped." [emphasis added]

Although your findings coincide with many of our personal experiences, the question at hand is, did Apple deliberately drop support of the "old HFS standard disc format" or was it an unintentional side-effect (i.e., a bug).

Do you (or anyone) have some official Apple Tech Note that states that they have dropped support of HFS Standard-formatted media, or are you inferring it from all of our collective experiences with Catalina?

I'd love to hear from Apple one way or the other on this. (Actually, I'd love for them to "fix" this decision to make HFS Standard obsolete)

@EddieOP it says on Wikipedia on the HFS Standard page:

«With the introduction of Mac OS X 10.6, Apple dropped support for formatting or writing HFS disks and images, which remain supported as read-onlyvolumes.[1] Starting with macOS 10.15, HFS disks can no longer be read.»

I was able to at least get the data off of my drive by un-journaling it. It wouldn't quite mount, but i could back everything up. You might try that. There are a couple of ways to do that out there on the web.

CATALINA IS A HOT MESS, and Apple seems to be refusing to acknowledge this issue, and many others including the fact that you can't even copy songs from the Music app to an iPhone without creating a playlist first. Audio books is effed up, dual display problems, and this "com.apple.DiskManagement.disenter error 49153" is absolute bullsh*t.

This would have never happened if Steve Jobs was still alive. Apple is in that weird spot Disney was in after Walt died and they'd better pull out of it and start supporting their loyal customers.

I really regret upgrading to Catalina for so many reasons.

I had the same error with my Seagate HDD. Initially, I was only able to access it in Read Only via NTFS. What I did (by accident, coz I cannot find anything in the web) is, click Verify in NTFS menu and after that it will run and once done I was able to have a write access as well. Let me know if this works for you guys.

I've run into a similar issue - seems to be related to Time Machine in my case. I followed the post that talked about going into Activity Monitor and force quitting FSCK. That worked for me. Fortunately the HDD in question had already been backed up, so I was able to reformat and continue as usual. So far so good.

I had the same problem. In my case it was a somewhat obvious solution. I opened NTFS for Mac and I said that the extention was blocked. I had to go to system preferences > security and privacy > at the bottom it said the extension was blocked and I had to allow it. After that I was able to mount the hard drive.

Hope this helps.

2 possible solutions:

1) Using VirtualBox, I ran Windows 10 on my Mac, installed HFSExplorer on it, then I could read my HFS CD. I could also copy all the material onto a thumb drive. However, the "identity" of the files got lost. For instance, a text file would show up as an "executable" file of 0 bytes. Adding ".txt" (without the quotes, of course) to the end of the file name fixed it. Adding the correct extension to the end of each file will fix it, but will take a long time. This is where a batch name changing utility would be handy. I recall one for Windows, but not for Mac. HFSExplorer, by the way, is supposed to be usable on a Mac or Linux machine, but I couldn't figure out how to do that.

2) I am downloading Mojave and will install that on an external drive, then boot my Mac from that drive. I expect I will then be able to read the CD. (I have a 2015 MBA with 2 USB ports.)

Yeah, I went the Mojave on an external drive route and was able to read HFS CDs/DVDs.

It's incredibly lame of Apple to just disable this without even mentioning it. Why disable it at all??

Just one other reason Catalina is a huge unstable letdown.

As a follow-up to my last post, I did download Mojave, install it on an external drive (had to put the installer on a thumb drive first, using the program "Install Disk Creator" from macdaddy.io, thank you very much, then booted from the thumb drive and then installed Mojave to an external drive.) And it worked. Just as it did for wage1968 (below).

Most of the files are properly identified as applications, text files, etc., but some aren't, such as files that may be connected to specific (old) programs, such as MathBlaster, Lotus 1-2-3, etc.

I've downgraded my entire computer to Mojave, not just because of the instability of Catalina and problems with drives, but because of the removal of support for 32 bit apps. As far as I'm concerned, Apple have removed the upgrade path for macOS. My entire system is now noticeably smoother and more reliable.

Sadly, this adds the Mac to the growing list of products I will no longer update.