No Mountable File System Dmg Problem

Posted on  by
No Mountable File System Dmg Problem Rating: 8,1/10 9821 reviews

According to your description, you got the error “no mountable file system” when you try to open the teamsosx.dmg file on your Mac. In this case, as you have tried to download the dmg file many times, if possible, please check and turn off any download assistant plug-ins you may have and try to download the dmg file again. DMG which stand for Disk Mounted Graphics is one of the most common file in Mac OS X as well as UNIX based OS and are used for storage of all data. DMG files have “.dmg” extension and are created by disk utility of Mac OS. The benefit of this DMG file is that data can get easily mounted and as a result accessing data become much easier. Are you facing Mac OS X DMG no mountable file system error? Do you get any errors while trying to mount an image? Well, here are the solutions to try out!

  1. Ubuntu No Mountable File Systems
  2. Dmg No Mountable File System
  3. No Mountable File System Dmg Problem Key
  • If you are facing Mac error no mountable file systems problem, follow these steps: In most cases, the downloaded dmg file is actually corrupt or had an error downloading. Reboot your Mac if you haven't already tried that. Try mounting the DMG on the command line in Terminal.
  • Apr 13, 2019 Method 1: Repairing Corrupt DMG File. In most cases, the issue can be the corrupt or dmg file which is not downloaded correctly. So what you can do is to download the same dmg file again to make sure there is no problem with the download. Also, try downloading the file again with the download assistant plug-ins being off.
  • QT.dmg 'No mountable file systems' on El Capitan. Backwards compatibility issue? No Mountable file system' Any simple QT program should be fine to test (or any program at all?). It would be very helpful if someone else could try to reproduce the problem and report what happens. Reply Quote 0. 1 Reply Last reply. StevenFS last edited.

I'm trying to do a complete backup of my wife's MB from my MBP. I booted the MB into Firewire Target Disk Mode, then used Disk Utility on my MBP to make a DMG of it onto another external FW drive. Here's the log from Disk Util:


2008-03-22 15:07:40 -0700: Disk Utility started.
2008-03-22 15:08:32 -0700: Creating Image “TiffanyBook032208.dmg”
2008-03-22 15:08:40 -0700: Preparing imaging engineÂ…
2008-03-22 15:08:44 -0700: Reading Driver Descriptor Map (DDM : 0)Â…
2008-03-22 15:08:44 -0700: (CRC32 $51B6B901: Driver Descriptor Map (DDM : 0))
2008-03-22 15:08:44 -0700: Reading Apple (Apple_partition_map : 1)Â…
2008-03-22 15:08:44 -0700: (CRC32 $A3D7DA6A: Apple (Apple_partition_map : 1))
2008-03-22 15:08:44 -0700: Reading (Apple_Free : 2)Â…
2008-03-22 15:08:45 -0700: (CRC32 $00000000: (Apple_Free : 2))
2008-03-22 15:08:45 -0700: Reading Apple_HFS_Untitled_1 (Apple_HFS : 3)Â…
2008-03-22 15:57:57 -0700: (CRC32 $CE3D7CF0: Apple_HFS_Untitled_1 (Apple_HFS : 3))
2008-03-22 15:57:57 -0700: Reading (Apple_Free : 4)Â…
2008-03-22 15:57:58 -0700: (CRC32 $00000000: (Apple_Free : 4))
2008-03-22 15:57:58 -0700: Adding resourcesÂ…
2008-03-22 15:57:59 -0700: Elapsed Time: 49m 13.314s
2008-03-22 15:57:59 -0700: File size: 28521921586 bytes, Checksum: CRC32 $C61693A6
2008-03-22 15:57:59 -0700: Sectors processed: 312581808, 79974513 compressed
2008-03-22 15:57:59 -0700: Speed: 13.2Mbytes/sec
2008-03-22 15:57:59 -0700: Savings: 82.2%
2008-03-22 15:58:01 -0700: Image “TiffanyBook032208.dmg” created successfully.
2008-03-22 16:08:24 -0700: Name : TiffanyBook032208.dmg
Type : Unattached Disk Image
Disk Name : /Cow-e-fornia/Backup/TiffanyBook032208.dmg
Disk Image Path : /Volumes/Cow-e-fornia/Backup/TiffanyBook032208.dmg
Disk Image Size : 26.6 GB (28,521,921,586 Bytes)
Location : External
2008-03-22 16:08:24 -0700:
2008-03-22 16:10:51 -0700: Attach Image “TiffanyBook032208.dmg”
2008-03-22 16:10:51 -0700: InitializingÂ…
2008-03-22 16:10:57 -0700: VerifyingÂ…
2008-03-22 16:10:58 -0700: Driver Descriptor Map (DDM : 0): verified CRC32 $51B6B901
2008-03-22 16:10:59 -0700: Apple (Apple_partition_map : 1): verified CRC32 $A3D7DA6A
2008-03-22 16:11:00 -0700: (Apple_Free : 2): verified CRC32 $00000000
2008-03-22 16:32:14 -0700: Apple_HFS_Untitled_1 (Apple_HFS : 3): verified CRC32 $CE3D7CF0
2008-03-22 16:32:15 -0700: (Apple_Free : 4): verified CRC32 $00000000
2008-03-22 16:32:15 -0700: Verification completedÂ…
2008-03-22 16:32:15 -0700: verified CRC32 $C61693A6
2008-03-22 16:32:15 -0700: AttachingÂ…
2008-03-22 16:32:16 -0700: Checking volumesÂ…
2008-03-22 16:33:14 -0700: Volume check completedÂ…
2008-03-22 16:33:14 -0700: AttachingÂ…
2008-03-22 16:33:14 -0700: FinishingÂ…
2008-03-22 16:34:06 -0700: Unable to attach “TiffanyBook032208.dmg”. (no mountable file systems)


When I tried to mount the image, it went through a 20 minute verification procedure, then failed with the 'no mountable file systems' error.

Ubuntu No Mountable File Systems


I tried mounting it from Finder by double-clicking the DMG and got the same error. So I deleted the DMG and re-created it from scratch (including rebooting the MB into TDM):

2008-03-22 16:37:22 -0700: Disk Utility started.
2008-03-22 16:37:54 -0700: Creating Image “TiffanyBook032208.dmg”
2008-03-22 16:37:58 -0700: Preparing imaging engineÂ…
2008-03-22 16:38:02 -0700: Reading whole disk (Apple_HFS : 0)Â…
2008-03-22 17:29:22 -0700: (CRC32 $DB22F44F: whole disk (Apple_HFS : 0))
2008-03-22 17:29:23 -0700: Adding resourcesÂ…
2008-03-22 17:29:25 -0700: Elapsed Time: 51m 20.825s
2008-03-22 17:29:25 -0700: File size: 28525037851 bytes, Checksum: CRC32 $7D6B0BB2
2008-03-22 17:29:25 -0700: Sectors processed: 312319584, 79999257 compressed
2008-03-22 17:29:25 -0700: Speed: 12.7Mbytes/sec
2008-03-22 17:29:25 -0700: Savings: 82.2%
2008-03-22 17:29:27 -0700: Image “TiffanyBook032208.dmg” created successfully.


I get the same failure, whether mounting from Finder or from Disk Utility.
WTF? Does anyone know what might be going on? I came > < this close to repartitioning her HDD, then I got the willies and decided to verify the image first. Good thing I'm paranoid, otherwise my wife would have had a factory-fresh MB right about now. -- View image here: https://cdn.arstechnica.net/forum/smilies/scared_classic.gif -- Rated (3.9 of 5.0) by 7 reviewers.
Kelly Heffner Wilkerson
November 8, 2019 at 6:30 AM
Categories: macOS View Comments


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.

Dmg No Mountable File System

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:

No Mountable File System Dmg Problem Key

  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:

    • 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:

  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. Giga does 0 dmg at training dummy.

      Or the Mac user can drag the program icon to the 'Applications' folder icon to move it to the 'Applications' directory in macOS.After the software stored in the DMG file is installed, the DMG file is no longer needed. DMG files are especially common since their contents can be verified upon installation to ensure they have not been tampered with and they can also be compressed to reduce the size of the installer.When a Mac user downloads a DMG file, he can simply double-click it to open it with the DiskImageMounter utility that comes with macOS. Opening dmg files on windows online. Today, software developers typically build and distribute applications for Mac users as DMG, or files. When the DMG file is opened, it a virtual disk on the desktop and in an Apple Finder window as if it was a or a that was just inserted into the computer.In the Finder window, the Mac user can double-click the program icon, which is an APP file, to run the app.

    • Restart your Mac.