macOS Error Opening .dmg Disk Image - No Mountable File Systems

   Rated (5.0 of 5.0) by 2 reviewers.
Kelly Heffner Wilkerson

Categories: macOS | View Comments

macOS error message no mountable file systems while trying to open a dmg.

I ran into an interesting macOS error while working with a customer a couple of weeks ago. I didn't find a lot of good search results addressing the issue, so I decided to write up a post about it myself.

The error was as the screenshot above shows; trying to open a dmg (disk image), macOS showed the error "no mountable file systems". If you see the "no mountable file systems error" while opening a dmg, here's what you should try:

  1. In most cases, the downloaded dmg file is actually corrupt or had an error downloading. If possible, try downloading the dmg again, turning off any download assistant plug-ins you may have. You can try downloading the file in a different browser as well. Or if you don't need to be logged in to the site to download the file and you want to be fancy, you can try curl -O url in Terminal to download the file. (There's an example of that in my screenshot below.)

  2. Reboot your Mac if you haven't already tried that. Apparently there is an issue sometimes after opening too many dmg files, that is fixed with a reboot.

  3. Try mounting the DMG on the command line in Terminal. We will at least get some sort of useful error message to go on if it still fails:

    Downloading a dmg with curl and mounting with hdiutil on the terminal.

    • Open Terminal: In Spotlight, the search magnifying glass at the upper right corner of your screen, search for Terminal, and press enter to open the Terminal app.

    • Type hdiutil attach -verbose into the terminal. Add a space at the end, but don't press enter yet.

    • Drag the dmg file from your Finder window onto the Terminal window and let go. This will fill in the location of the dmg file into your Terminal window.

    • Press enter.
  4. macOS Sierra (10.12) and earlier is not able to mount the new Apple File System (APFS). So if you're on macOS Sierra (10.12) or earlier and you ran hdiutil and see references to Apple_APFS or error 112, the issue is likely legitimate incompatibility, and this disk image won't open on this Mac without an update to the operating system.

    Here's an example of the end of hdiutil attach -verbose output that shows an APFS error due to an older version of macOS:

    Mounting… 
    2019-06-03 21:10:17.499 diskimages-helper[2092:23120] -remountReturningDictionary: detaching because no mountable filesystems. 
    Attaching… 
    Error 112 (no mountable file systems). 
    Finishing… 
    DIHLDiskImageAttach() returned 112 
    hdiutil: attach failed - no mountable file systems
    
  5. Think about if you have any kind of security policies on this machine to prevent writing to external drives (thumb drives, optical drives, etc). I haven't seen this one in action, but I read about this being a possibility while researching the issue.

  6. Another suggestion added by a reader (thank you, Markus!) is that filesystem errors on your main Mac drive could be the cause of the disk image mounting errors. Here are instructions from Apple for scanning and repairing errors using Disk Utility. Note that in order to scan and repair errors on your main Macintosh HD drive, you'll need to reboot your Mac into recovery mode. You'll want to choose Disk Utility in the utilities listed in the recovery mode menu.

  7. A new discovery from a reader (thank you, Colby!) is that APFS DMGs won't mount if you're booted in macOS booted in Safe Mode. (Who knew!?!) If you're not sure if you're in safe mode, select the Apple menu  > About This Mac > System Report button, then select the "Software" heading from the left column. To exit safe mode, restart your Mac, without holding Shift during startup. Or, if you previously set your Mac to always boot into safe mode using nvram, turn off safe mode and have your Mac boot normally on the terminal:

    • Open Terminal: In Spotlight, the search magnifying glass at the upper right corner of your screen, search for Terminal, and press enter to open the Terminal app.

    • Type/paste sudo nvram boot-args="" and press enter.

    • Restart your Mac.


Buy Me a Coffee

58 Comments



  • J Crowley June 6, 2019

    Have had the same problem. MacOS 10.14.5. All are sparsebundles created by Time Machine, either on a Time Capsule or an external USB drive connected to the Time Capsule.

    Some appear to be transient upon reboot of the Mac or power-cycle Time Capsule and the attached USB drives.

    What really seems strange, is that after hdiutil fails, can go into Finder, connect to the Time Capsule, see the sparsebundle that failed, and mount using DiskImageMounter.app - with absolutely no problem. So what is different between hdiutil and DiskImageMounter????

    • Kelly HW

      Kelly HW June 6, 2019

      Interesting. The transient nature... I've definitely seen timeout issues for connections to external drives on macOS since Yosemite, that could be related to this.

      If you connect to the Time Capsule in Finder, and then try hdiutil again, does it then work?

  • SuniDar June 6, 2019

    da

  • SuniDar June 6, 2019

    Hello, when I did it, It shows Me this: hdiutil: attach failed - no mountable file systems
    How Can I Fix It?

    • Kelly HW

      Kelly HW June 6, 2019

      Hi SuniDar,

      Can you do a “hdiutil attach -verbose” to get more information about the error?

      • SuniDar June 6, 2019

        Shows me this hdiutil: attach: missing <image>
        Usage: hdiutil attach [options] <image>
        hdiutil attach -help

        • Kelly HW

          Kelly HW June 6, 2019

          Ah, my apologies, I meant to use hdiutil verbose as the article describes:

          Type hdiutil attach -verbose into the terminal. Add a space at the end, but don't press enter yet.

          Drag the dmg file from your Finder window onto the Terminal window and let go. This will fill in the location of the dmg file into your Terminal window.

          Press enter.

          • SuniDar June 6, 2019

            Shows me this:
            Initializing…
            DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
            DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore
            DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore
            DIBackingStoreInstantiatorProbe: interface 3, score 100, CCarbonBackingStore
            DIBackingStoreInstantiatorProbe: interface 4, score -1000, CDevBackingStore
            DIBackingStoreInstantiatorProbe: interface 5, score -1000, CCURLBackingStore
            DIBackingStoreInstantiatorProbe: interface 6, score -1000, CVectoredBackingStore
            DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
            DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore
            DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore
            DIBackingStoreInstantiatorProbe: interface 3, score 100, CCarbonBackingStore
            DIBackingStoreInstantiatorProbe: interface 4, score -1000, CDevBackingStore
            DIBackingStoreInstantiatorProbe: interface 5, score -1000, CCURLBackingStore
            DIBackingStoreInstantiatorProbe: interface 6, score -1000, CVectoredBackingStore
            DIFileEncodingInstantiatorProbe: interface 0, score -1000, CMacBinaryEncoding
            DIFileEncodingInstantiatorProbe: interface 1, score -1000, CAppleSingleEncoding
            DIFileEncodingInstantiatorProbe: interface 2, score -1000, CEncryptedEncoding
            DIFileEncodingInstantiatorProbe: interface 0, score 900, CUDIFEncoding
            DIFileEncodingNewWithBackingStore: CUDIFEncoding
            DIFileEncodingNewWithBackingStore: instantiator returned 0
            DIFileEncodingInstantiatorProbe: interface 0, score -1000, CSegmentedNDIFEncoding
            DIFileEncodingInstantiatorProbe: interface 1, score -1000, CSegmentedUDIFEncoding
            DIFileEncodingInstantiatorProbe: interface 2, score -1000, CSegmentedUDIFRawEncoding
            DIDiskImageInstantiatorProbe: interface 0, score 1000, CUDIFDiskImage
            DIDiskImageInstantiatorProbe: interface 1, score 0, CSparseBundleDiskImage
            DIDiskImageInstantiatorProbe: interface 2, score 0, CSparseDiskImage
            CRawDiskImage: data fork length 0x00000000050562B2 (84239026) not a multiple of 512.
            DIDiskImageInstantiatorProbe: interface 3, score -100, CRawDiskImage
            DIDiskImageInstantiatorProbe: interface 4, score 0, CDARTDiskImage
            DIDiskImageInstantiatorProbe: interface 5, score 0, CDiskCopy42DiskImage
            DIDiskImageInstantiatorProbe: interface 6, score -1000, CNDIFDiskImage
            DIDiskImageInstantiatorProbe: interface 8, score -100, CShadowedDiskImage
            DIDiskImageInstantiatorProbe: interface 9, score -1000, CCFPlugInDiskImage
            DIDiskImageInstantiatorProbe: interface 10, score -100, CWrappedDiskImage
            DIDiskImageNewWithBackingStore: CUDIFDiskImage
            DIDiskImageNewWithBackingStore: instantiator returned 0
            Verifying…
            Verification completed…
            Error 0 (Undefined error: 0).
            expected CRC32 $EF2F2432
            Attaching…
            DI_kextWaitQuiet: about to call IOServiceWaitQuiet...
            DI_kextWaitQuiet: IOServiceWaitQuiet took 0.000004 seconds
            2019-06-08 20:41:34.782 diskimages-helper[59215:1121855] DIHelperHDID serveImage: attaching drive
            {
            autodiskmount = 1;
            "hdiagent-drive-identifier" = "D40CC9DD-3F20-4005-A92F-20E88B98C320";
            "unmount-timeout" = 0;
            }
            2019-06-08 20:41:34.785 diskimages-helper[59215:1121855] DIHelperHDID serveImage: connecting to myDrive 0x4913
            2019-06-08 20:41:34.785 diskimages-helper[59215:1121855] DIHelperHDID serveImage: register _readBuffer 0x10ce07000
            2019-06-08 20:41:34.786 diskimages-helper[59215:1121855] DIHelperHDID serveImage: activating drive port 18187
            2019-06-08 20:41:34.786 diskimages-helper[59215:1121855] DIHelperHDID serveImage: set cache enabled=TRUE returned SUCCESS.
            2019-06-08 20:41:34.787 diskimages-helper[59215:1121855] DIHelperHDID serveImage: set on IO thread=TRUE returned SUCCESS.
            2019-06-08 20:41:34.787 diskimages-helper[59215:1121855] -processKernelRequest: will sleep received
            Volume check completed…
            Mounting…
            2019-06-08 20:41:34.814 diskimages-helper[59215:1121852] -remountReturningDictionary: detaching because no mountable filesystems.
            Attaching…
            Error 112 (no mountable file systems).
            Finishing…
            DIHLDiskImageAttach() returned 112
            hdiutil: attach failed - no mountable file systems

            • Kelly HW

              Kelly HW June 6, 2019

              Hi again SuniDar,

              This means the DMG uses APFS, and I assume you’re running macOS Sierra or earlier, which does not support APFS.

  • daveee

    daveee May 5, 2019

    I also had this problem with a disk image that I had created. The image got corrupted when a power glitch rebooted my system while the image was mounted. I was able to attach it via "hdiutil attach -noverify -nomount ....", then used a quick scan with Data Rescue. It copied everything out of the image to a different drive. I used an old version of Data Rescue (version 3), have no idea if a newer one would work, but no reason to think it wouldn't.

    Lesson learned - disk images may make things easy to organize, but one small glitch and you can lose a lot of data.

  • Markus S

    Markus S February 2, 2019

    Had the same problems mounting .dmg files. I was helped by a repair of the filesystem with the "Disk Utility" in "Recovery Mode". Maybe you also have a corrupt filesystem - just check it with "Disk Utility".

    • Kelly HW

      Kelly HW February 2, 2019

      Hi Markus,

      Thanks for the great additional tip! I want to make sure I clarify and got it right before I update the post with the additional thing to try. You rebooted in to recovery mode (probably Command + R at startup) and then checked your main Mac hard drive with Disk Utility?

      • Markus S

        Markus S March 3, 2019

        sorry for the late reply - yes, this is correct!

  • Ruben Ramos

    Ruben Ramos February 2, 2019

    I tried what you said and nothing happened but can you try installing fortnite on yours and tell me how to do it.

    • Kelly HW

      Kelly HW February 2, 2019

      Hi Ruben,

      What version of macOS are you running?

      Also, just to make sure, did you try restarting your Mac, and are you using any "download manager" software? (versus just downloading through your browser)

      • Ruben Ramos

        Ruben Ramos February 2, 2019

        2012 macbook air also i tried downloading it on browser because i didnt know how to download it on a software?

        • Kelly HW

          Kelly HW February 2, 2019

          Browser should be fine. If you click the Apple menu in the upper left corner, then About this Mac, it will tell you what version of macOS/Mac OS X is on the mac. Can you tell me what version number that says?

          • Ruben Ramos

            Ruben Ramos February 2, 2019

            MacBook Air (11-inch, Early 2015)

            • Kelly HW

              Kelly HW February 2, 2019

              Hi again Ruben,
              https://uploads.disquscdn.c...

              That is the computer model, but we're interested in the version of the software operating system, to make sure it's compatible with the DMG. What does it say next to "Version"? I included a picture to help you find where it should be.

              • Ruben Ramos

                Ruben Ramos February 2, 2019

                Sorry about that it is a macOs Sierra

                • Kelly HW

                  Kelly HW February 2, 2019

                  Perfect :) that shouldn't be the problem then either!

                  I just downloaded the same DMG and have the same checksums, etc as you, so the download should be ok too.

                  Can you try:
                  1. Checking to make sure you have a good amount of free disk space? https://www.macworld.com/ar... (All sorts of weird things happen when your hard drive is almost full.)

                  2. Reboot the Mac (Apple menu > Restart) and try to open the DMG again?

  • Moses Gbonda November 11, 2018

    I get "hdiutil: attach failed - no mountable file systems" when trying to install ubuntu operating system on my mac OS (mojave) partiioned with windows OS. Is there any way to fix this problem ?

    • Kelly HW

      Kelly HW November 11, 2018

      Hi Moses,

      Are you able to paste the output from hdiutil attach -verbose? Also, is it a publicly available DMG that can be downloaded to test on my end (if so do you have the link)?

      For sure, I would try downloading the DMG again with curl and rebooting your Mac, before we dig in to deeper measures.

  • William Speir November 11, 2018

    Hi, I'm getting a "no mountable file systems" every time I try to install steam on my computer. I have tryed everything. Please help me.

    • Kelly HW

      Kelly HW November 11, 2018

      Hi William,

      I checked the latest steam dmg and it mounts ok on my High Sierra machine. The partitions are HFS, so it should be ok even on older macOS versions.

      A few "silly" things to try, just in case it's a simple corrupt dmg or system reboot kind of problem: Try downloading it on the terminal with curl as described in the post, as well as rebooting your mac.

  • Waffles And Pepto-Bismol November 11, 2018

    I did the whole terminal thing, and it failed, I am using a MacOS 10.13.6

    • Kelly HW

      Kelly HW November 11, 2018

      Are you willing to post the output from hdiutil attach -verbose? Also, is it a publicly available DMG that can be downloaded to test on my end, or one of your own?

      • Waffles And Pepto-Bismol November 11, 2018

        Yes, it is a public DMG

        Last login: Tue Nov 6 20:41:12 on ttys000

        lbaylo5374s-MacBook-Air:~ lbaylo5374$ hdiutil attach -verbose /Users/lbaylo5374/Downloads/SURVEY_PROGRAM_MACOSX_ENGLISH.dmg

        Initializing…

        DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore

        DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore

        DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore

        DIBackingStoreInstantiatorProbe: interface 3, score 100, CCarbonBackingStore

        DIBackingStoreInstantiatorProbe: interface 4, score -1000, CDevBackingStore

        DIBackingStoreInstantiatorProbe: interface 5, score -1000, CCURLBackingStore

        DIBackingStoreInstantiatorProbe: interface 6, score -1000, CVectoredBackingStore

        DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore

        DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore

        DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore

        DIBackingStoreInstantiatorProbe: interface 3, score 100, CCarbonBackingStore

        DIBackingStoreInstantiatorProbe: interface 4, score -1000, CDevBackingStore

        DIBackingStoreInstantiatorProbe: interface 5, score -1000, CCURLBackingStore

        DIBackingStoreInstantiatorProbe: interface 6, score -1000, CVectoredBackingStore

        DIFileEncodingInstantiatorProbe: interface 0, score -1000, CMacBinaryEncoding

        DIFileEncodingInstantiatorProbe: interface 1, score -1000, CAppleSingleEncoding

        DIFileEncodingInstantiatorProbe: interface 2, score -1000, CEncryptedEncoding

        DIFileEncodingInstantiatorProbe: interface 0, score 900, CUDIFEncoding

        DIFileEncodingNewWithBackingStore: CUDIFEncoding

        DIFileEncodingNewWithBackingStore: instantiator returned 0

        DIFileEncodingInstantiatorProbe: interface 0, score -1000, CSegmentedNDIFEncoding

        DIFileEncodingInstantiatorProbe: interface 1, score -1000, CSegmentedUDIFEncoding

        DIFileEncodingInstantiatorProbe: interface 2, score -1000, CSegmentedUDIFRawEncoding

        DIDiskImageInstantiatorProbe: interface 0, score 1000, CUDIFDiskImage

        DIDiskImageInstantiatorProbe: interface 1, score 0, CSparseBundleDiskImage

        DIDiskImageInstantiatorProbe: interface 2, score 0, CSparseDiskImage

        CRawDiskImage: data fork length 0x0000000004392041 (70852673) not a multiple of 512.

        DIDiskImageInstantiatorProbe: interface 3, score -100, CRawDiskImage

        DIDiskImageInstantiatorProbe: interface 4, score 0, CDARTDiskImage

        DIDiskImageInstantiatorProbe: interface 5, score 0, CDiskCopy42DiskImage

        DIDiskImageInstantiatorProbe: interface 6, score -1000, CNDIFDiskImage

        DIDiskImageInstantiatorProbe: interface 8, score -100, CShadowedDiskImage

        DIDiskImageInstantiatorProbe: interface 9, score -1000, CCFPlugInDiskImage

        DIDiskImageInstantiatorProbe: interface 10, score -100, CWrappedDiskImage

        DIDiskImageNewWithBackingStore: CUDIFDiskImage

        DIDiskImageNewWithBackingStore: instantiator returned 0

        Verifying…

        Verification completed…

        Error 0 (Undefined error: 0).

        expected CRC32 $7C40D8EF

        Attaching…

        DI_kextWaitQuiet: about to call IOServiceWaitQuiet...

        DI_kextWaitQuiet: IOServiceWaitQuiet took 0.000006 seconds

        2018-11-06 20:43:48.888 diskimages-helper[13087:44281] DIHelperHDID serveImage: attaching drive

        {

        autodiskmount = 1;

        "hdiagent-drive-identifier" = "337AE1C7-5895-4D25-92C4-652C59FD805F";

        "unmount-timeout" = 0;

        }

        2018-11-06 20:43:48.889 diskimages-helper[13087:44281] DIHelperHDID serveImage: connecting to myDrive 0x460B

        2018-11-06 20:43:48.889 diskimages-helper[13087:44281] DIHelperHDID serveImage: register _readBuffer 0x105145000

        2018-11-06 20:43:48.889 diskimages-helper[13087:44281] DIHelperHDID serveImage: activating drive port 18187

        2018-11-06 20:43:48.890 diskimages-helper[13087:44281] DIHelperHDID serveImage: set cache enabled=TRUE returned SUCCESS.

        2018-11-06 20:43:48.890 diskimages-helper[13087:44281] DIHelperHDID serveImage: set on IO thread=TRUE returned SUCCESS.

        2018-11-06 20:43:48.890 diskimages-helper[13087:44281] -processKernelRequest: will sleep received

        Mounting…

        2018-11-06 20:43:48.984 diskimages-helper[13087:44278] -remountReturningDictionary: detaching because no mountable filesystems.

        Attaching…

        Error 112 (no mountable file systems).

        Finishing…

        DIHLDiskImageAttach() returned 112

        hdiutil: attach failed - no mountable file systems

        lbaylo5374s-MacBook-Air:~ lbaylo5374$

        • Kelly HW

          Kelly HW November 11, 2018

          Sadly, all I've been able to find in my research about this specific form of failure is to try rebooting and try redownloading the DMG. The places where I've seen the error, the person reports that it was transient and the DMG worked fine later.

  • Tamim A. AlThunayan

    Tamim A. AlThunayan November 11, 2018

    I tried the 3rd option and I received this:

    hdiutil: attach/Volumes/My Files' Backup Book/APPLE HDD ST2000DM001 Media.dmg: verb not recognized
    Usage: hdiutil <verb> <options>
    <verb> is one of the following:
    help flatten
    attach imageinfo
    detach internet-enable
    eject isencrypted
    verify makehybrid
    create mount
    compact mountvol
    convert unmount
    burn plugins
    info resize
    checksum segment
    chpass pmap
    erasekeys udifderez
    unflatten udifrez

    What can I do? it has my entire backup.

    • Kelly HW

      Kelly HW November 11, 2018

      Hi Tamim,

      Try the hdiutil command again, making sure to do two things:
      1) Add a space after attach before the dmg file name.
      2) Instead of typing the DMG filename, try dragging the DMG file to the terminal window. That will fill in the DMG filename, making sure the spaces are done correctly, just in case.

      Also, let me know what version of macOS you're running :)

      • Tamim A. AlThunayan

        Tamim A. AlThunayan November 11, 2018

        I did both things and I got this:

        expected CRC32 $152A6E47
        hdiutil: attach failed - no mountable file systems

        • Kelly HW

          Kelly HW November 11, 2018

          Hi again Tamim,

          Can you paste the entire output from hdiutil, as well as let me know what version macOS you're running? Those two lines aren't enough to know.

          Or alternatively if you see "disk image (Apple_APFS : a number)" and you're on macOS 10.12 or earlier, the issue is that APFS is only usable in High Sierra and later versions of macOS.

          • Tamim A. AlThunayan

            Tamim A. AlThunayan November 11, 2018

            that's all I got.

            my mac is running on mojave

            • Kelly HW

              Kelly HW November 11, 2018

              Ah, hmm interesting! Ok, so it's not an APFS issue ;) Can you add -verbose into the hdiutil line, so it would be

              hdiutil attach -verbose dmgname

              Also, if you prefer, you can send us an email through here https://deciphertools.com/s... and we can take this discussion to email.

              • Tamim A. AlThunayan

                Tamim A. AlThunayan November 11, 2018

                I did send an email after trying: hdiutil attach -verbose and I receive this:

                Initializing…
                DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
                DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore
                DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore
                DIBackingStoreInstantiatorProbe: interface 3, score 100, CCarbonBackingStore
                DIBackingStoreInstantiatorProbe: interface 4, score -1000, CDevBackingStore
                DIBackingStoreInstantiatorProbe: interface 5, score -1000, CCURLBackingStore
                DIBackingStoreInstantiatorProbe: interface 6, score -1000, CVectoredBackingStore
                DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
                DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore
                DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore
                DIBackingStoreInstantiatorProbe: interface 3, score 100, CCarbonBackingStore
                DIBackingStoreInstantiatorProbe: interface 4, score -1000, CDevBackingStore
                DIBackingStoreInstantiatorProbe: interface 5, score -1000, CCURLBackingStore
                DIBackingStoreInstantiatorProbe: interface 6, score -1000, CVectoredBackingStore
                DIFileEncodingInstantiatorProbe: interface 0, score -1000, CMacBinaryEncoding
                DIFileEncodingInstantiatorProbe: interface 1, score -1000, CAppleSingleEncoding
                DIFileEncodingInstantiatorProbe: interface 2, score -1000, CEncryptedEncoding
                DIFileEncodingInstantiatorProbe: interface 0, score 900, CUDIFEncoding
                DIFileEncodingNewWithBackingStore: CUDIFEncoding
                DIFileEncodingNewWithBackingStore: instantiator returned 0
                DIFileEncodingInstantiatorProbe: interface 0, score -1000, CSegmentedNDIFEncoding
                DIFileEncodingInstantiatorProbe: interface 1, score -1000, CSegmentedUDIFEncoding
                DIFileEncodingInstantiatorProbe: interface 2, score -1000, CSegmentedUDIFRawEncoding
                DIDiskImageInstantiatorProbe: interface 0, score 1000, CUDIFDiskImage
                DIDiskImageInstantiatorProbe: interface 1, score 0, CSparseBundleDiskImage
                DIDiskImageInstantiatorProbe: interface 2, score 0, CSparseDiskImage
                CRawDiskImage: data fork length 0x0000009313F0881E (631694723102) not a multiple of 512.
                DIDiskImageInstantiatorProbe: interface 3, score -100, CRawDiskImage
                DIDiskImageInstantiatorProbe: interface 4, score 0, CDARTDiskImage
                DIDiskImageInstantiatorProbe: interface 5, score 0, CDiskCopy42DiskImage
                DIDiskImageInstantiatorProbe: interface 6, score -1000, CNDIFDiskImage
                DIDiskImageInstantiatorProbe: interface 8, score -100, CShadowedDiskImage
                DIDiskImageInstantiatorProbe: interface 9, score -1000, CCFPlugInDiskImage
                DIDiskImageInstantiatorProbe: interface 10, score -100, CWrappedDiskImage
                DIDiskImageNewWithBackingStore: CUDIFDiskImage
                DIDiskImageNewWithBackingStore: instantiator returned 0
                Verifying…
                Verification completed…
                Error 0 (Undefined error: 0).
                expected CRC32 $152A6E47
                Attaching…
                Mounting…
                2018-11-06 07:56:02.815 diskimages-helper[34556:967961] DIHelperHDID serveImage: attaching drive
                {
                autodiskmount = 1;
                "hdiagent-drive-identifier" = "1138DD79-26E7-4132-BD18-83CE4478F7B4";
                "unmount-timeout" = 0;
                }
                2018-11-06 07:56:02.816 diskimages-helper[34556:967961] DIHelperHDID serveImage: connecting to myDrive 0x3F0B
                2018-11-06 07:56:02.816 diskimages-helper[34556:967961] DIHelperHDID serveImage: register _readBuffer 0x12af18000
                2018-11-06 07:56:02.816 diskimages-helper[34556:967961] DIHelperHDID serveImage: activating drive port 14603
                2018-11-06 07:56:02.816 diskimages-helper[34556:967961] DIHelperHDID serveImage: set cache enabled=TRUE returned SUCCESS.
                2018-11-06 07:56:02.816 diskimages-helper[34556:967961] DIHelperHDID serveImage: set on IO thread=TRUE returned SUCCESS.
                2018-11-06 07:56:02.816 diskimages-helper[34556:967961] -processKernelRequest: will sleep received
                2018-11-06 07:56:03.906 diskimages-helper[34556:967749] _postflightMountPointsAfterDAMount: disk4 aborting because no mount point found.
                2018-11-06 07:56:03.907 diskimages-helper[34556:967749] _postflightMountPointsAfterDAMount: disk4s1 aborting because no mount point found.
                2018-11-06 07:56:03.907 diskimages-helper[34556:967749] _postflightMountPointsAfterDAMount: disk4s2 aborting because no mount point found.
                2018-11-06 07:56:03.907 diskimages-helper[34556:967749] _postflightMountPointsAfterDAMount: disk4s3 aborting because no mount point found.
                2018-11-06 07:56:03.908 diskimages-helper[34556:967749] allowMountReturningDictionary: detaching because no mountable filesystems.
                Attaching…
                Error 112 (no mountable file systems).
                Finishing…
                DIHLDiskImageAttach() returned 112
                hdiutil: attach failed - no mountable file systems

                • Kelly HW

                  Kelly HW November 11, 2018

                  Hi Tamim,

                  I see the email, and I'll be taking a look at this verbose log shortly! Will followup via email as soon as I can. (And hopefully we can post the end result answer here as soon as we figure it out!)

                  • Hien

                    Hien November 11, 2018

                    Hi Kelly could you please send me the answer for this particular case? Cuz I'm having problem exactly the same as his, all steps and messages. MacOS Mojave too and Early 2016 Macbook.

                    • Kelly HW

                      Kelly HW November 11, 2018

                      Hi Hien,

                      I'm not sure if Tamim has gotten his DMG mounted properly yet, or if the DMG is actually damaged. But we did make some progress using advice from this thread:

                      https://superuser.com/quest... (let us know if this separate attach and mount worked, and I'll update the blog post!)

                      and then this other page may be helpful if the above doesn't help, and you want to try making a copy of the DMG and trying the diskutil verifyvolume and repairvolume commands https://www.applegazette.co... (But, definitely do this on a COPY, and I would try the first post with instructions to attach and mount separately first.)

  • Jérôme Jaglale

    Jérôme Jaglale October 10, 2018

    This is what hditutil says for me (for the latest version of VirtualBox, but I encountered the same problem for other images). It doesn't look like an APFS problem? Any idea what it could be? Thank you.

    $ hdiutil attach -verbose /Users/jlj7/Downloads/VirtualBox-5.2.20-125813-OSX.dmg
    Initializing…
    DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
    DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore
    DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore
    DIBackingStoreInstantiatorProbe: interface 3, score 100, CCarbonBackingStore
    DIBackingStoreInstantiatorProbe: interface 4, score -1000, CDevBackingStore
    DIBackingStoreInstantiatorProbe: interface 5, score -1000, CCURLBackingStore
    DIBackingStoreInstantiatorProbe: interface 6, score -1000, CVectoredBackingStore
    DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
    DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore
    DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore
    DIBackingStoreInstantiatorProbe: interface 3, score 100, CCarbonBackingStore
    DIBackingStoreInstantiatorProbe: interface 4, score -1000, CDevBackingStore
    DIBackingStoreInstantiatorProbe: interface 5, score -1000, CCURLBackingStore
    DIBackingStoreInstantiatorProbe: interface 6, score -1000, CVectoredBackingStore
    DIFileEncodingInstantiatorProbe: interface 0, score -1000, CMacBinaryEncoding
    DIFileEncodingInstantiatorProbe: interface 1, score -1000, CAppleSingleEncoding
    DIFileEncodingInstantiatorProbe: interface 2, score -1000, CEncryptedEncoding
    DIFileEncodingInstantiatorProbe: interface 0, score 900, CUDIFEncoding
    DIFileEncodingNewWithBackingStore: CUDIFEncoding
    DIFileEncodingNewWithBackingStore: instantiator returned 0
    DIFileEncodingInstantiatorProbe: interface 0, score -1000, CSegmentedNDIFEncoding
    DIFileEncodingInstantiatorProbe: interface 1, score -1000, CSegmentedUDIFEncoding
    DIFileEncodingInstantiatorProbe: interface 2, score -1000, CSegmentedUDIFRawEncoding
    DIDiskImageInstantiatorProbe: interface 0, score 1000, CUDIFDiskImage
    DIDiskImageInstantiatorProbe: interface 1, score 0, CSparseBundleDiskImage
    DIDiskImageInstantiatorProbe: interface 2, score 0, CSparseDiskImage
    CRawDiskImage: data fork length 0x0000000005B34543 (95634755) not a multiple of 512.
    DIDiskImageInstantiatorProbe: interface 3, score -100, CRawDiskImage
    DIDiskImageInstantiatorProbe: interface 4, score 0, CDARTDiskImage
    DIDiskImageInstantiatorProbe: interface 5, score 0, CDiskCopy42DiskImage
    DIDiskImageInstantiatorProbe: interface 6, score -1000, CNDIFDiskImage
    DIDiskImageInstantiatorProbe: interface 8, score -100, CShadowedDiskImage
    DIDiskImageInstantiatorProbe: interface 9, score -1000, CCFPlugInDiskImage
    DIDiskImageInstantiatorProbe: interface 10, score -100, CWrappedDiskImage
    DIDiskImageNewWithBackingStore: CUDIFDiskImage
    DIDiskImageNewWithBackingStore: instantiator returned 0
    Verifying…
    Verification completed…
    Error 0 (Undefined error: 0).
    expected CRC32 $C3C6B9D6
    Attaching…
    DI_kextWaitQuiet: about to call IOServiceWaitQuiet...
    DI_kextWaitQuiet: IOServiceWaitQuiet took 0.000006 seconds
    2018-10-24 12:28:30.416 diskimages-helper[92430:2447233] DIHelperHDID serveImage: attaching drive
    {
    autodiskmount = 1;
    "hdiagent-drive-identifier" = "564F3A76-9EDA-4671-8902-F6B8E50CC955";
    "unmount-timeout" = 0;
    }
    2018-10-24 12:28:30.419 diskimages-helper[92430:2447233] DIHelperHDID serveImage: connecting to myDrive 0x490B
    2018-10-24 12:28:30.419 diskimages-helper[92430:2447233] DIHelperHDID serveImage: register _readBuffer 0x107161000
    2018-10-24 12:28:30.419 diskimages-helper[92430:2447233] DIHelperHDID serveImage: activating drive port 18187
    2018-10-24 12:28:30.419 diskimages-helper[92430:2447233] DIHelperHDID serveImage: set cache enabled=TRUE returned SUCCESS.
    2018-10-24 12:28:30.420 diskimages-helper[92430:2447233] DIHelperHDID serveImage: set on IO thread=TRUE returned SUCCESS.
    2018-10-24 12:28:30.420 diskimages-helper[92430:2447233] -processKernelRequest: will sleep received
    Mounting…
    2018-10-24 12:28:30.766 diskimages-helper[92430:2447229] -remountReturningDictionary: detaching because no mountable filesystems.
    Attaching…
    Error 112 (no mountable file systems).
    Finishing…
    DIHLDiskImageAttach() returned 112
    hdiutil: attach failed - no mountable file systems

    • Kelly HW

      Kelly HW October 10, 2018

      Hi Jérôme,

      What version of macOS are you running? I can try it on my end assuming I have a similar machine to do it on. My High Sierra machine mounts it ok. It doesn't look like an APFS problem (and it's not an APFS dmg). Also if you didn't try rebooting yet, I'd try that now.

      • Jérôme Jaglale

        Jérôme Jaglale October 10, 2018

        Hi Kelly, macOS 10.10.5. Yes, I tried rebooting. What's frustrating is that it used to work just fine.. Anyway, don't worry about it, I was just wondering if it was something obvious. Thank you for taking the time to have a look and to answer me.

  • Tim Russell

    Tim Russell October 10, 2018

    I'm getting a "no mountable file systems" message for the wxHexEditor install image. It's an open source utility, downloadable from sourceforge @ https://sourceforge.net/pro.... The hdiutil output, showing the included disk image to be apple_apfs, is below. i've tried on both os x 10.8.5 and El capitan > get the same error to mount. How should I proceed?

    Checksumming Protective Master Boot Record (MBR : 0)…
    Protective Master Boot Record (MBR :: verified CRC32 $B70CB786
    Checksumming GPT Header (Primary GPT Header : 1)…
    GPT Header (Primary GPT Header : 1): verified CRC32 $F3C75B6F
    Checksumming GPT Partition Data (Primary GPT Table : 2)…
    GPT Partition Data (Primary GPT Tabl: verified CRC32 $2470C31E
    Checksumming (Apple_Free : 3)…
    (Apple_Free : 3): verified CRC32 $00000000
    Checksumming disk image (Apple_APFS : 4)…
    disk image (Apple_APFS : 4): verified CRC32 $299274BE
    Checksumming (Apple_Free : 5)…
    (Apple_Free : 5): verified CRC32 $00000000
    Checksumming GPT Partition Data (Backup GPT Table : 6)…
    GPT Partition Data (Backup GPT Table: verified CRC32 $2470C31E
    Checksumming GPT Header (Backup GPT Header : 7)…
    GPT Header (Backup GPT Header : 7): verified CRC32 $AC67B7D1
    verified CRC32 $A539A4C8

    hdiutil: attach failed - no mountable file systems

    • Kelly HW

      Kelly HW October 10, 2018

      Hi Tim,

      Thanks for the reference to the DMG. Unfortunately, since this DMG uses APFS, it's only compatible with macOS 10.13 (High Sierra) or later. The error message is the same as if the DMG was broken, but in this case means hdiutil can see the partitions and everything looks ok, but macOS 10.12 and earlier isn't actually able to mount/use APFS partitions.

      So sadly, the only way to proceed is to open the DMG on High Sierra or higher.

  • prodromosBB

    prodromosBB October 10, 2018

    This could be because you're running an older version of MacOS. I got this when trying to install MachOExplorer [1] on my main computer which still runs El Capitan.

    Then I tried on my side computer which is updated to High Sierra. The disk image opened fine. Looking the output of the mount command, it turned out that the disk image contained an APFS partition which is not supported by El Capitan.

    [1] https://github.com/everettj...

  • Adun Wang October 10, 2018

    none of them work.
    I got error form suggestion 3.
    hdiutil: attach failed - no mountable file systems

    • Kelly HW

      Kelly HW October 10, 2018

      Hi Adun,

      If it's a DMG that is publicly available, can you send us an email via our support form and let us know where we can download it to see if it's a damaged DMG? Also, what version of macOS are you running?

  • Tuan Van October 10, 2018

    none of them work helppp

    • Kelly HW

      Kelly HW October 10, 2018

      Hi Tuan,

      What version of macOS are you running? If you want, you can run the terminal command from suggestion 3 and send us the error it prints out via our support page so we can take a look. https://deciphertools.com/s...

  • Oscar Pacheco

    Oscar Pacheco September 9, 2018

    I got a "attach failed - no mountable file systems"message
    , what can I do for solve it?

    Thanks

    • Kelly HW

      Kelly HW September 9, 2018

      Hi Oscar,

      If suggestion #1 and #2 from the article didn't help fix the error, can you comment or email us https://deciphertools.com/s... with what you see in the terminal when you try suggestion #3?

      • Tuan Van October 10, 2018

        i have the same thing

  • Madeline DeCotes

    Madeline DeCotes August 8, 2018

    I was able to resolve this problem by opening up my macOS Security & Privacy settings, navigating to General, and then clicking Allow on the app developer that was being blocked. Hope this helps!

    • Kelly HW

      Kelly HW August 8, 2018

      Hi Madeline,

      That's interesting - I haven't seen this specific error from the disk image signing before, so that is a good new tip to check! Thank you for letting us know!

    • Kaoru Nelson October 10, 2018

      Thank you! This method worked for me!