com.apple.DiskManagement.disenter error 49153

I finally got Apple to fix this issue on my Mac Pro (Late 2013) after I upgrade to Catalina. Under Finder, Preferences, General tab, make sure "CDs, DVDs, and iPods," is checked. Guess it defaulted unchecked when I upgraded.

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

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 was having the same problem. I could see the drive in Disk Utility, but the drive wouldn't mount the drive. I noticed that when I physically disconnected the drive, the drive continued to appear in the drive list in the Disk Utility. I rebooted my machine and the disk was able to mount.

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.)

I actually found a workaround but not sure it will work on your guys. In my case, I have to log off the account and re-log in. ( note, even restart isn’t working for me, it must log off. I knew it is wired so I’m not sure it will work with others)

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.

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.

@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.»

There seems to be different things causing the 49153 error. In my case, it's very specific:

Catalina has not been able to mount any of my HFS-formatted CD-ROMs (HFS+ CD-ROMs mount just fine). The CD drive spins, then gives up without mounting the CD-ROM. If you then open Disk Utility, you can see the CD Title grayed out. If you right-click on the CD Title and select Mount, it generates the 49153 error.

I'm sure there are other causes of the 49153 error in Catalina, but this is the specific problem that is plaguing me, as our business has many, many such legacy CD-ROMs in our customers' hands, and they are destined to fail under Catalina, it seems.

Again, Apple Support??

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 was same problem. In my case helped open disk in another laptop (Macbook Air with Catalina). On first laptop error again but on second laptop opening correctly. I was insert disk again to mine macbook after this operation and it worked correctly.

Where is Apple Support when we need them? So many people having this error message. I upgraded my OS to Catalina only last week and my Mac Superdrive which has always worked no longer appears in finder, and when I try to mount using disk utility I also get the error message: com.apple.DiskManagement.disenter error 49153.

Not good enough Apple! Where are you?

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)

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.