I'm trying to download Office for Home & Student 2011 to my new Macbook. The download gets to 940MB of the 1.04GB. Then I get a message which reads The following disk images couldn't be opened. Image: X18-08827.dmg. Reason: no mountable file systems. In layman's terms, what does this mean and what should I do to fix it? When it does, it then adds an extended attribute of type com.apple.diskimages.fsck to the disk image file, and shouldn’t need to repeat it when you next mount that disk image. You can force macOS to bypass the fsck step using a command in Terminal of the form hdiutil attach filename.dmg -noautofsck. Notarize a dmg 'no mountable file systems' Suddenly the notarization service failed with message: 'b'hdiutil: attach failed - no mountable file systems ', but I can mount the dmg in my mac. Until few days ago, notarization by same build process on CI works as expected. DMG files are known as the proprietary disk image file for Apple that is used generally on Mac OS machines. Therefore, most users are in the habit of keeping image backup of their system data in the form of DMG files. Thus, DMG files prove to be greatly helpful from forensics point of view during investigation of an Apple machine.
No Mountable File Systems Mac Dmg
No Mountable File Systems Dmg Mac Fix
| Click here to return to the 'Force-mount unmountable disk images' hint |
Great, Great, Great.
I am creating a lot of disk images at the moment for the distribution of a product and obviously I have to test those images. After mounting about 10 the Finder stops doing it's work as described in the hint. This problem exists even in 10.3.5 and I am very happy now, cause rebooting, the only solution I had figured out so far, really interrupts my work big time.
Thanks for the tip.
---
DubMaster
--
Rehab is for quitters!
It just so happens that we already built an AppleScript solution using this method; I'll paste it below for those who are Terminally challenged. As for the issue with password protected disks, this script will indeed trigger a GUI window asking for any such passwords not already stored in Keychain. I have yet to find an instance where presentation of the password box triggered the failure we're looking to overcome in this hing, but the -stdinpass switch would likely resolve it (see the man page), and could be added to this script.
Now, if you could add an 'on open' handler that handled drag-and-drop, you'd be all set! Just drag your dmg files onto the script and they would mount. No file dialog to get in the way.. :-)
Hi there...
Well, I tried both versions of your script on several disk images (including one that I KNOW mounts fine by itself), and most of them were grayed out in my file dialog. My first thought was that perhaps they were corrupted, but at least one of them mounts fine on its own, and it was not accessible either.
I very much appreciate your scripting skills, but do you have any idea why I might be having such problems? Any suggestions from anyone else out there? I would really appreciate the help!
Thanks in advance,
mlaurenc
I may just be a big newbie, (and I undoubtably am), but when running this script the only items I could select when it asked me which DMG I wanted to mount were file folders and no DMG files. Even with a foler selected, 'Choose' never highlit. Am I doing something wrong?
Also, is there an applescript super newbie thread I should be hitting up before getting to knee deep in this?
by the way, rebooting still didn't allow me to mount the DMGs. I'm running 10.3.7.
Thanks for any/all help guys!
-Seth
I may just be a big newbie, (and I undoubtably am), but when running this script the only items I could select when it asked me which DMG I wanted to mount were file folders and no DMG files. Even with a foler selected, 'Choose' never highlit. Am I doing something wrong?
Also, is there an applescript super newbie thread I should be hitting up before getting to knee deep in this?
by the way, rebooting still didn't allow me to mount the DMGs. I'm running 10.3.7.
Thanks for any/all help guys!
-Seth
While this is a nice workaround - I really wish the problem would be solved instead. Very annoying. On my machine - happens everyday after about my tenth disk mount. The image actually appears to get mounted and appears in /Volumes but it shows up no where else and is impossible to access.
I must say, it doesn't happen much with me. But if it shows up in /Volumes, you should be able to refresh the finder by doing 'disktool -r'. I am writing a script that triggers mounting of dmg and the 'disktool -r' seems to solve some of my problem.
Good luck
I tried this Hint for the first time today, but I didn't appear to have the relevant utility. Typing in hd and tab brought up
hdiutil
which is not the command quoted in the actual command string in the Hint.
Anyway, I tried hdiutil, and it tried to attach the dmg, but failed with the same problem: no mountable file systems. <sigh>
Back to restarting...
from Clytie, still having trouble
---
Clytie Siddall -- Renmark, in the Riverland of South Australia
iBook G3, 10.3.5, all updates current
Mac Os Dmg No Mountable File Systems
Yeah, 'hdituil' is a typo.
Unfortunately, this didn't work for me. :-(
---
Ron
I tried the applescript but nothing is highlight-able
---
Infants are born. Children learn as they grow. Knowledge is power. Information in the wrong minds is deadly!!!
Same here
It won't work
---
Infants are born. Children learn as they grow. Knowledge is power. Information in the wrong minds is deadly!!!
Using QT 5.9.2 & QTCreator I compiled in release mode today (XCode-Clang 64bit) then ran 'macdeployqt' from the command line to produce a *.dmg. It opened and ran fine on another OSX Sierra machine. However two 'El Capitan' computers can not mount the .dmg. During the 'verifying' process an error is thrown: 'No Mountable File Systems'.
I have a wrapper script to run 'macdeployqt' so I know the dmg and zip are being packaged exactly as they have been for months. This worked just fine the week before Christmas. My computer updated to Mac OS High Sierra 10.13.2 last Friday January 5th.
Are there any known new backwards-compatibility issues running 'macdeployqt' on High Sierra possibly causing the files to fail on El Capitan (10.11.6)? Has anyone else experienced this or can someone else please try to recreate it?