My Backup.dmg is not mounting: No mountable file systems

I had Mac OS X Leopard running with Boot Camp (Windows Vista). I needed extra space for my Mac OS so I deleted the Windows partition using the Boot Camp Assistant. Then, I shut down the computer, but after I turned it on, there was the flashing question mark, which meant that the computer couldn't recognize the Macintosh operating system that was installed. Therefore, I put in the Mac OS Install Disk, and tried to repair the disk but it said invalid BS_jmpBoot in block 000000. Seeing this, I decided to reinstall Mac OS X, but backing up with Disk Utility: Create New Compressed .DMG Image before doing so. After a successful installation, I tried to mount the image, but it says No Mountable File System. I feel hopeless, because all of my precious data was backed up in that disk image. When I try to verify or repair that disk using Disk Utility, it says Unrecognized File System. Are all the files on that image corrupt and impossible to recover, or is it possible to recover those files (but of course, losing some files, since the image appears to be corrupt).

Again, if you cannot mount the image then there's no way to recover the files. If the image would mount then you could try repairing it with Disk Utility or try using recovery software to recover files from it. But if it doesn't mount then there's nothing you can do with it.
If you want to try you can see if recovery software can find files on it. See the following:
Basics of File Recovery
Files in Trash
If you simply put files in the Trash you can restore them by opening the Trash (left-click on the Trash icon) and drag the files from the Trash to your Desktop or other desired location. OS X also provides a short-cut to undo the last item moved to the Trash -press COMMAND-Z.
If you empty the Trash the files are gone. If a program does an immediate delete rather than moving files to the Trash, then the files are gone. Recovery is possible but you must not allow any additional writes to the hard drive - shut it down. When files are deleted only the directory entries, not the files themselves, is modified. The space occupied by the files has been returned to the system as available for storage, but the files are still on the drive. Writing to the drive will then eventually overwrite the space once occupied by the deleted files in which case the files are lost permanently. Also if you save a file over an existing file of the same name, then the old file is overwritten and cannot be recovered.
General File Recovery
If you stop using the drive it's possible to recover deleted files that have not been overwritten with recovery software such as Data Rescue II, File Salvage or TechTool Pro. Each of the preceding come on bootable CDs to enable usage without risk of writing more data to the hard drive.
The longer the hard drive remains in use and data are written to it, the greater the risk your deleted files will be overwritten.
Also visit The XLab FAQs and read the FAQ on Data Recovery.
You can download trial versions of the software. The trials can be used to see if the software can recover anything, but then you must purchase the software to actually do any file recovery.

Similar Messages

Years of data gone, backup DMG won't mount "No mountable file systems"

Could someone help me here, I have this problem.
The reason for this was that I ran into some complications with my boot camp windows install and wanted to start over. After returning the boot camp FAT partition space to Mac OS X it froze while attempting to create a new boot camp partition. "Boot Camp Assistant" suggested I backup my "Macintosh HD" and re-partition my HD because "some files could not be moved." Ok so, I backed-up my "Macintosh HD" volume to a DMG using Disk Utility selecting the volume and clicking new image icon, it is compressed, it is Leopard. I then booted with Leopard install DVD and began the restore process. Everything was working smoothly until the progress bar stopped animating, waited awhile and forced restart. When I restarted my internal HD had only an "Applications" folder which ended its contents with a half copied iDVD.app preceded by 73 other apps successfully restored. Now worst of all my Backup DMG produces the "No mountable file systems" error. Help, oh please help!
hdiutil imageinfo produces this:
Format: UDRW
Backing Store Information:
Name: Macintosh HD.dmg
URL: file://localhost/Volumes/Macintosh%20HD/Macintosh%20HD.dmg
Class Name: CBSDBackingStore
Format Description: raw read/write
Checksum Type: none
partitions:
appendable: false
partition-scheme: none
block-size: 512
burnable: false
partitions:
0:
partition-length: 92073985
partition-synthesized: true
partition-hint: unknown partition
partition-name: whole disk
partition-start: 0
Properties:
Partitioned: false
Software License Agreement: false
Compressed: no
Kernel Compatible: true
Encrypted: false
Checksummed: false
Checksum Value:
Size Information:
Total Bytes: 47141880320
Compressed Bytes: 47141880320
Total Non-Empty Bytes: 47141880320
Sector Count: 92073985
Total Empty Bytes: 0
Compressed Ratio: 1
Class Name: CRawDiskImage
Segments:
0: /Volumes/Macintosh HD/Macintosh HD.dmg
Resize limits (per hdiutil resize -limits):
92073985 92073985 92073985
Message was edited by: Marcus S

Ok, here is the output. It shows there is a problem with the resource fork XML, just like yours Shad Guy. If only their were some specs available I could try to fix it myself. An Apple engineer could most likely fix this in 20 min.
Also, thanks for your help man, having people tell me to give up is the worst.
hdiutil udifxmldet
"Macintosh HD.dmg" has 1365301792551680312 bytes of embedded XML data.
hdiutil: udifxmldet: unable to read XML data at offset 2841561349885781055 from "Macintosh HD.dmg": 29 (Illegal seek).
hdiutil: udifxmldet failed - Illegal seek
hdiutil udifderez
hdiutil: udifderez: could not get resource fork of "Macintosh HD.dmg": Function not implemented (78)
hdiutil: udifderez failed - Function not implemented
------------------------

Ocfs2 can not mount the ocfs2 file system on RedHat AS v4 Update 1

Hi there,
I installed ocfs2-2.6.9-11.0.0.10.3.EL-1.0.4-1.i686.rpm onto RedHat linux AS v4 update 1. Installation looks OK. And configure ocfs2 (At this stage i only added 1 node in the cluster), load and start accordingly. Then paritition the disk and mkfs.ocfs2 the partition. Everything seems OK.
[root@node1 init.d]# ./o2cb status
Module "configfs": Loaded
Filesystem "configfs": Mounted
Module "ocfs2_nodemanager": Loaded
Module "ocfs2_dlm": Loaded
Module "ocfs2_dlmfs": Loaded
Filesystem "ocfs2_dlmfs": Mounted
Checking cluster ocfs2: Online
Checking heartbeat: Not active
But here you can check if the partition is there:
[root@node1 init.d]# fsck.ocfs2 /dev/hda12
Checking OCFS2 filesystem in /dev/hda12:
label: oracle
uuid: 27 74 a6 70 32 ad 4f 77 bf 55 8e 3a 87 78 ea cb
number of blocks: 612464
bytes per block: 4096
number of clusters: 76558
bytes per cluster: 32768
max slots: 2
/dev/hda12 is clean. It will be checked after 20 additional mounts.
However, mount -t ocfs2 /dev/hda12 just does not work.
[root@node1 oracle]# mount -t ocfs2 /dev/hda12 /oradata/m10g
mount.ocfs2: No such device while mounting /dev/hda12 on /oradata/m10g
[root@node1 oracle]# mount -L oracle
mount: no such partition found
Looks like mount just can not see the ocfs2 partition somehow.
I cannot find much info in metalink and anywhere else, does anyone here come across this issue before?
Regards,
Eric

I have been having a similar problem.
However, when I applied your fix I ended up with another problem:
(20765,0):ocfs2_initialize_osb:1179 max_slots for this device: 4
(20765,0):ocfs2_fill_local_node_info:851 I am node 0
(20765,0):dlm_request_join:756 ERROR: status = -107
(20765,0):dlm_try_to_join_domain:906 ERROR: status = -107
(20765,0):dlm_join_domain:1151 ERROR: status = -107
(20765,0):dlm_register_domain:1330 ERROR: status = -107
(20765,0):ocfs2_dlm_init:1771 ERROR: status = -12
(20765,0):ocfs2_mount_volume:912 ERROR: status = -12
ocfs2: Unmounting device (253,7) on (node 0)
Now the odd thing about this bit of log output (/var/log/messages)
is the fact that this is only a 2 node cluster and only one node has
currently mounted the file system in question. Now, I am running
the multipath drivers with my qla2xxx drivers under SLES9-R2.
However, at worst that should only double everything
(2 nodes x 2 paths through the SAN).
How can I get more low level information on what is consuming
the node slots in ocfs2? How can I force it to "disconnect" nodes
and recover/cleanup node slots?

No mountable file system error when open dowloaded dmg

I was provided a link to dowload Fireworks CS3 for Mac. The link allowed me to connect to the adobe ftp server and downloaded a 1.1MB dmg for Fireworks for Mac. However, when I attempt to open the file I get the following error: "The following disk images failed to mount, no mountable file systems". Note the file size seems too small for the full program, but I have downloaded it twice with no error messages on downloading and same file size.
Previously posted under Fireworks but no responses....any ideas?

You have an incomplete file. there is no way that a 1.1MB file could contain the app Fireworks. redownload the complete file and it will mount.

Time Machine backup volume will not mount

Once I goy Time Machine up and running over almost two years ago, I have had little cause for concern. A few lengthy backups here and there but I have been able to restore without any problems whatsoever. It has been extremely useful many times.
A couple of days ago, I noticed that the backup volume was not mounted (I backup to one of my four internal drives) and launched Time Machine. I got the error:
The storage location for Time Machine backups can't be found.
When I run Disk Utility the generic disk icon is in the left hand pane but not the volume. None of the tasks are available except Erase and Partition - there is no option to Verify Disk, Repair Disk, Verify Disk Permissions or Repair Disk Permissions.
According to my logs, the last backup at 18:12 on 20th November was successful. I didn't notice that the volume had not mounted the until the next day.
I'm very concerned that I have lost almost two years of data security. Is there any way I can repair the disk or recover the backups?
Thanks.

If Disk Utility can't see any partitions, it's not good.
First, turn TM off.
Then try ejecting, disconnecting and powering the drive off for a few minutes, then reattaching it. Then try again with Disk Utility. If still no help, the drive is likely dead.
There's a very small chance that +Disk Warrior+ (version 4.1.1 or 4.2 only), or another heavy-duty disk repair app can fix it, if you already have one. But I wouldn't suggest spending the $$ for one unless you think you'll need it in the future -- DW is about $100.
Most likely, your disk is dead. There's a small chance that a +Data Recovery+ app such as +Data Rescue+ can recover some of the data. Check via Google, VersionTracker.com, or MacUpdate.com for +Data Recovery.+ There are services and apps, none cheap. Some of the apps have a free demo or test mode that will tell you if there's anything that can be recovered, and perhaps actually recover a single file; then you pay for it and recover whatever else can be recovered. You'll need another external disk to receive the recovered items.
You won't get the normal Time Machine folder structure, though, just "raw" files. Even if you do recover files, you'll most likely have to figure out what goes where and copy them to the right places manually.
So I'd suggest immediately getting a new drive and doing a new TM backup to it, so you have something. Put a second partition on it that you can use for the recovered files if and when you do that.
If those are your only backups, I'd recommend getting a second external, perhaps a portable one, and using CarbonCopyCloner or SuperDuper to make a full "bootable clone" to it, then take it to your safe deposit box, workplace, relative's house, or other secure location. And/or, you might want to look at Mozy, Carbonite, or other online backup services.

Problems mounting dmg images "no mountable file systems"

I have noticed with many DMG images I cannot open them. I constantly get an error "no mountable file systems".I sent the same DMG image to my friend on his Mac and he can open it, so it is on my side. I also have noticed my pen drive is not showing up on the desktop, but shows in disk utility. I have noticed these problems since I cloned and replaced my HD. I have also added a 50 GB partition to Boot Camp, if this should matter. Any idea??

repaired permissions and rebooted.
all ok now

Corrupt DMG file - "No Mountable File Systems"

Hello, I have an important backup DMG file that I can't mount. When I try, I get this error..."No Mountable File Systems".
I have tried the following with no success...
- repairing the DMG in Disk Utility.
- converting the DMG in Disk Utility to a R/W image.
- Repair in Data Rescue 3
- Repair in Disk Warrior
- Repair in File Salvage (this actually recovered a single mp3 file, so this makes me think the data is still there)
- Repair in Stellar Phoenix
- Repair in Disk Drill
I have read on one of these forums (I can't seem to find it anymore) that someone had a similar issue and someone helped them through a lot of digging around in the broken file (something to do with headers?)...and in the end they managed to repair the broken DMG file. I would really like to repair this file, so just in case someone who knows how to fix this sort of thing, I've shared the file here...
files.me.com/jeffvandyck/x4qv9c
I have a few other files like this and would really like to recover those as well. I'm relatively technical, and once I understand what I'm looking for I can try to fix the others.
Thanks in advance for any help!
Cheers,
Jeff

Output of hdid -nomount -verbose -debug
Jeffs-MacBook-Pro:~ Jeff$ hdid /Users/Jeff/Jeff\ Projects.dmg -nomount -verbose -debug
calling DIHLDiskImageAttach with
agent: hdid
mount-required: false
debug: true
quiet: false
image-options:
drive-options:
main-url: /Users/Jeff/Jeff Projects.dmg
verbose: true
mount-attempted: false
2011-10-10 13:30:57.030 hdiutil[438:60f] DIHLDiskImageAttach: creating DIHelperProxy
2011-10-10 13:30:57.032 hdiutil[438:60f] [DIHelperProxy alloc]
2011-10-10 13:30:57.032 hdiutil[438:60f] [DIHelperProxy alloc] returning self 0x100500a20, retainCount 1
2011-10-10 13:30:57.033 hdiutil[438:60f] DIHLDiskImageAttach: running DIHelperProxy
2011-10-10 13:30:57.033 hdiutil[438:60f] [DIHelperProxy performOperationReturning] entry
2011-10-10 13:30:57.034 hdiutil[438:60f] [DIHelperProxy performOperationReturning] detaching thread
2011-10-10 13:30:57.034 hdiutil[438:2603] [DIHelperProxy workerThread] entry
2011-10-10 13:30:57.034 hdiutil[438:2603] [DIHelperProxy workerThread] setting up server
2011-10-10 13:30:57.035 hdiutil[438:2603] [DIHelperProxy threadSetupServer] entry
2011-10-10 13:30:57.035 hdiutil[438:2603] [DIHelperProxy threadSetupServer] setting up _headerConnection
2011-10-10 13:30:57.035 hdiutil[438:2603] [DIHelperProxy threadSetupServer] setting up _headerConnection rootObject
2011-10-10 13:30:57.036 hdiutil[438:2603] [DIHelperProxy threadSetupServer] adding NSConnectionDidInitializeNotification notification
2011-10-10 13:30:57.036 hdiutil[438:2603] [DIHelperProxy threadSetupServer] exiting
2011-10-10 13:30:57.036 hdiutil[438:2603] [DIHelperProxy workerThread] launching
2011-10-10 13:30:57.037 hdiutil[438:2603] [DIHelperProxy threadLaunchToolAuthenticated] entry
2011-10-10 13:30:57.038 hdiutil[438:2603] launching helper tool at "/System/Library/PrivateFrameworks/DiskImages.framework/Resources/diskimages-he lper".
2011-10-10 13:30:57.038 hdiutil[438:2603] [DIHelperProxy threadLaunchToolAuthenticated] adding NSTaskDidTerminateNotification notification
2011-10-10 13:30:57.038 hdiutil[438:2603] [DIHelperProxy thread LaunchToolAuthenticated] launching
2011-10-10 13:30:57.039 hdiutil[438:2603] [DIHelperProxy threadLaunchToolAuthenticated] exiting
2011-10-10 13:30:57.040 hdiutil[438:2603] [DIHelperProxy workerThread] running runloop
2011-10-10 13:30:57.040 hdiutil[438:2603] DIHelperProxy threadRunRunLoop] entry, retainCount 3
2011-10-10 13:30:57.049 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] entry
2011-10-10 13:30:57.049 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] adding new NSConnectionDidDieNotification notification
2011-10-10 13:30:57.049 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] removing old NSConnectionDidDieNotification notification
2011-10-10 13:30:57.050 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] removing old connection rootObject
2011-10-10 13:30:57.050 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] invalidating old connection
2011-10-10 13:30:57.050 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] releasing old connection
2011-10-10 13:30:57.051 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] and replacing with new connection
2011-10-10 13:30:57.051 hdiutil[438:2603] [DIHelperProxy helperConnectionInitialized] exit
2011-10-10 13:30:57.052 hdiutil[438:2603] [DIHelperProxy connectToFramework] entry, helper 0x10011d350
2011-10-10 13:30:57.052 hdiutil[438:2603] [DIHelperProxy connectToFramework] exit
2011-10-10 13:30:57.152 hdiutil[438:2603] [DIHelperProxy sendOperationToHelper] entry
2011-10-10 13:30:57.153 hdiutil[438:2603] [DIHelperProxy sendOperationToHelper] starting operation with helper
2011-10-10 13:30:57.155 hdiutil[438:2603] [DIHelperProxy sendOperationToHelper] exit
2011-10-10 13:30:57.159 hdiutil[438:2603] [DIHelperProxy frameworkCallbackWithDictionary] entry
status proc called: initialize
myStatusProc: returning 0
2011-10-10 13:30:57.159 hdiutil[438:2603] [DIHelperProxy frameworkCallbackWithDictionary] exit
2011-10-10 13:30:57.160 diskimages-helper[440:2003] _imageOptions: {
    "enable-keychain" = 1;
2011-10-10 13:30:57.162 diskimages-helper[440:2003] _driveOptions: {
    autodiskmount = 0;
    "unmount-timeout" = 0;
2011-10-10 13:30:57.162 diskimages-helper[440:2003] DIHelperAttach: performOperation: initializing framework
2011-10-10 13:30:57.163 diskimages-helper[440:2003] {
    agent = hdid;
    "auto-fsck-failure-override-type" = callback;
    "auto-open-ro-root" = 0;
    "auto-open-rw-root" = 0;
    "auto-stretch" = 0;
    "bundlebs-checkpointing" = 0;
    "bundlebs-localcloseonflush" = 0;
    "bundlebs-localcloseonidle" = 0;
    "bundlebs-localcloseonsleep" = 0;
    "bundlebs-localfdcount" = 6;
    "bundlebs-remotecloseonflush" = 0;
    "bundlebs-remotecloseonidle" = 0;
    "bundlebs-remotecloseonsleep" = 0;
    "bundlebs-remotefdcount" = 3;
    "burn-apple-supported-devices-only" = 0;
    "burn-no-underrun-protection" = 0;
    "burn-synthesize-content" = 1;
    "bzip2-level" = 0;
    "callback-with-sla" = 1;
    debug = 1;
    "disable-encrypted-images" = 0;
    "disable-kernel-mounting" = 1;
    "disable-owners" = 0;
    "drive-options" = <62706c69 73743030 d0080000 00000000 01010000 00000000 00010000 00000000 00000000 00000000 0009>;
    "enable-owners" = 0;
    "filevault-default-case-sensitive-file-system" = "Case-sensitive Journaled HFS+";
    "filevault-default-encryption-type" = "AES-128";
    "filevault-default-file-system" = "Journaled HFS+";
    "filevault-default-image-type" = SPARSEBUNDLE;
    "filevault-default-partition-type" = SPUD;
    "filevault-default-volume-name" = FileVault;
    "force-idme" = 0;
    "hfsplus-stretch-parameters" =     {
        "hfsplus-stretch-allocation-block-size" = 4096;
        "hfsplus-stretch-allocation-file-size" = 8388608;
        "hfsplus-stretch-threshold" = 524288;
    "idle-timeout" = 15;
    "ifd-format" = UDZO;
    "ifd-ignore-io-errors" = 1;
    "ifd-segment-size" = 0;
    "iff-format" = UDZO;
    "iff-fs" = "HFS+";
    "iff-layout" = SPUD;
    "iff-source-owners" = auto;
    "iff-spotlight-indexing" = 0;
    "iff-temp-sparse-band-size" = 20480;
    "iff-temp-use-rw-if-possible" = 1;
    "iff-usehelper" = 1;
    "ignore-bad-checksums" = 0;
    "image-options" = <62706c69 73743030 d0080000 00000000 01010000 00000000 00010000 00000000 00000000 00000000 0009>;
    "main-url" = "file://localhost/Users/Jeff/Jeff%20Projects.dmg";
    "mount-attempted" = 0;
    "mount-point" = "/Volumes/";
    "mount-private" = 0;
    "mount-required" = 0;
    "mount-type" = in;
    "nbi-spotlight-indexing" = 0;
    operation = DIHelperAttach;
    "progress-delay" = 5;
    "pthread-reader-cap" = 4;
    quiet = 0;
    "reauthenticate-upon-wake" = 1;
    "skip-auto-fsck-for-system-images" = 1;
    "skip-idme" = 1;
    "skip-idme-reveal" = 0;
    "skip-idme-trash" = 0;
    "skip-previously-verified" = 1;
    "skip-sla" = 0;
    "skip-verify" = 1;
    "skip-verify-locked" = 0;
    "skip-verify-remote" = 1;
    "sparsebundle-compactonidle" = 0;
    "suppress-uiagent" = 1;
    "unmount-timeout" = 0;
    "use-compressed-xml" = 0;
    "use-keychain" = 1;
    verbose = 1;
    "zlib-level" = 1;
DILoadDriver: checking for disk image driver
DILoadDriver: DI_kextExists() returned 0x00000000 (0)
DIIsInitialized: returning NO
2011-10-10 13:30:57.169 diskimages-helper[440:2003] -checkForPreviouslyAttachedImage: entry
2011-10-10 13:30:57.169 diskimages-helper[440:2003]
file://localhost/Users/Jeff/Jeff%20Projects.dmg - (null) ((null), (null)). perm=0
DIIsInitialized: returning YES
DIBackingStoreNewWithCFURL: entry with
file://localhost/Users/Jeff/Jeff%20Projects.dmg
skip-permissions-check: true
DIBackingStoreInstantiatorProbe: entry
file://localhost/Users/Jeff/Jeff%20Projects.dmg
skip-permissions-check: true
DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
CBSDBackingStore::newProbe score 100 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 0, score      100, CBSDBackingStore
DIBackingStoreInstantiatorProbe: probing interface 1 CBundleBackingStore
CBundleBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 1, score    -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: probing interface 2 CRAMBackingStore
CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
CRAMBackingStore::probe: score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 2, score    -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: probing interface 3 CCarbonBackingStore
CCarbonBackingStore::newProbe: setting initial rval to +100
CCarbonBackingStore::newProbe score 100 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 3, score      100, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: probing interface 4 CDevBackingStore
CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Users/Jeff/Jeff Projects.dmg).CDevBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 4, score    -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: probing interface 5 CCURLBackingStore
CCURLBackingStore::probe: scheme is: file
CCURLBackingStore::probe: not recognized URL scheme.
CCURLBackingStore::probe: score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 5, score    -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: probing interface 6 CVectoredBackingStore
CVectoredBackingStore::newProbe not "vectored" scheme.
CVectoredBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 6, score    -1000, CVectoredBackingStore
DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
DIBackingStoreNewWithCFURL: CBSDBackingStore
CBSDBackingStore::setNoFollow: setting _noFollow to 0
DIBackingStoreNewWithCFURL: instantiator returned 0
DIBackingStoreNewWithCFURL: returning 0x00000000
2011-10-10 13:30:57.170 diskimages-helper[440:2003] -checkForPreviouslyAttachedImage: resolving file://localhost/Users/Jeff/Jeff%20Projects.dmg returned 0
2011-10-10 13:30:57.170 diskimages-helper[440:2003] -checkForPreviouslyAttachedImage: imageUID (
    "d234881026:i2592177"
) shadowUID (null)
***** testing:
0: d234881026:i939052
(null)
(null)
***** testing:
0: d234881026:i939052
(null)
(null)
***** testing:
0: d234881026:i939052
(null)
(null)
2011-10-10 13:30:57.173 diskimages-helper[440:2003] DIHelperAttach: performOperation: resolving disk image
DIIsInitialized: returning YES
DIIsInitialized: returning YES
DIBackingStoreNewWithCFURL: entry with
file://localhost/Users/Jeff/Jeff%20Projects.dmg
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIBackingStoreInstantiatorProbe: entry
file://localhost/Users/Jeff/Jeff%20Projects.dmg
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
CBSDBackingStore::newProbe score 100 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 0, score      100, CBSDBackingStore
DIBackingStoreInstantiatorProbe: probing interface 1 CBundleBackingStore
CBundleBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 1, score    -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: probing interface 2 CRAMBackingStore
CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
CRAMBackingStore::probe: score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 2, score    -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: probing interface 3 CCarbonBackingStore
CCarbonBackingStore::newProbe: setting initial rval to +100
CCarbonBackingStore::newProbe score 100 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 3, score      100, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: probing interface 4 CDevBackingStore
CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Users/Jeff/Jeff Projects.dmg).CDevBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 4, score    -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: probing interface 5 CCURLBackingStore
CCURLBackingStore::probe: scheme is: file
CCURLBackingStore::probe: not recognized URL scheme.
CCURLBackingStore::probe: score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 5, score    -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: probing interface 6 CVectoredBackingStore
CVectoredBackingStore::newProbe not "vectored" scheme.
CVectoredBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.dmg
DIBackingStoreInstantiatorProbe: interface 6, score    -1000, CVectoredBackingStore
DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
DIBackingStoreNewWithCFURL: CBSDBackingStore
CBSDBackingStore::setPermission: opening /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::setPermission: kDI_PERM_READWRITE granted.
CBSDBackingStore::setNoFollow: setting _noFollow to 0
DIBackingStoreNewWithCFURL: instantiator returned 0
DIBackingStoreNewWithCFURL: returning 0x00000000
DIResolveURLToBackingStore: processing level 1 encodings.
DIFileEncodingNewWithBackingStore: entry for encoding level 1
DIFileEncodingInstantiatorProbe: entry for level 1
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIFileEncodingInstantiatorProbe: probing level 1 interface 0 CMacBinaryEncoding
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::openDataFork: returning 0
CBSDBackingStore::closeDataFork fSIZE = 868220928
00000000: 7801 edd0 3101 0000 00c2 a0f5 4fed 6d07   | x...1.......O.m. |
00000010: 8840 61c0 8001 0306 0c18 3060 c080 0103   | [email protected]`.... |
00000020: 060c 1830 60c0 8001 0306 0c18 3060 c080   | ...0`.......0`.. |
00000030: 0103 060c 1830 60c0 8001 0306 0c18 3060   | .....0`.......0` |
00000040: c080 0103 060c 1830 60c0 8001 0306 0c18   | .......0`....... |
00000050: 3060 c080 0103 060c 1830 60c0 8001 0306   | 0`.......0`..... |
00000060: 0c18 3060 c080 0103 060c 1830 60c0 8001   | ..0`.......0`... |
00000070: 0306 0c18 3060 c080 0103 060c 1830 60c0   | ....0`.......0`. |
diskimages-helper: fileNameLength          $00000001
diskimages-helper: resourceForkLength      $0C183060
diskimages-helper: dataForkLength          $80010306
diskimages-helper: commentLength           $000060C0
diskimages-helper: MacBinary III signature   \001\003\006\f (0x0103060C)
diskimages-helper: header CRC              $00001830
diskimages-helper: minimum decoder version $0000000C
diskimages-helper: encoder version         $00000006
no MacBinary III signature - checking for MacBinary I or IIDIFileEncodingInstantiatorProbe: interface 0, score    -1000, CMacBinaryEncoding
DIFileEncodingInstantiatorProbe: probing level 1 interface 1 CAppleSingleEncoding
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::openDataFork: returning 0
00000000: d0ed 0178 0000 0131 00c2 a0f5 4fed 6d07   | ...x...1....O.m. |
00000010: 8840 61c0 8001 0306 180c 3060 c080 0103   | [email protected]`.... |
00000020: 060c 1830 60c0 .... .... .... .... ....   | ...0`........... |
CBSDBackingStore::closeDataFork fSIZE = 868220928
CAppleSingleEncoding::isAppleSingleFile loadAppleSingleHeader failed with error 22
DIFileEncodingInstantiatorProbe: interface 1, score    -1000, CAppleSingleEncoding
DIFileEncodingInstantiatorProbe: probing level 1 interface 2 CEncryptedEncoding
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::openDataFork: returning 0
CEncryptedEncoding::copyHeaderInformation: inBackingStore->openDataFork returned 0
CEncryptedEncoding::copyHeaderInformation: inBackingStore->getDataForkLength (stub header) returned 0
CEncryptedEncoding::copyHeaderInformation: backingStore data fork length is 868220928
CEncryptedEncoding::copyHeaderInformation: reading V1 header from offset 868219652
CEncryptedEncoding::copyHeaderInformation: inBackingStore->readDataFork (stub header) returned 0
CEncryptedEncoding::copyHeaderInformation: not recognized as v1 header
CEncryptedEncoding::copyHeaderInformation: reading V2 header from offset 0
CEncryptedEncoding::copyHeaderInformation: inBackingStore->readDataFork (stub header) returned 0
CEncryptedEncoding::copyHeaderInformation: not recognized as v2 header
CBSDBackingStore::closeDataFork fSIZE = 868220928
(null)
DIFileEncodingInstantiatorProbe: interface 2, score    -1000, CEncryptedEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
DIFileEncodingNewWithBackingStore: returning 0x0000006B
DIResolveURLToBackingStore: level 1 encoding match failed. 107.
(continuing)
DIResolveURLToBackingStore: processing level 2 encodings.
DIFileEncodingNewWithBackingStore: entry for encoding level 2
DIFileEncodingInstantiatorProbe: entry for level 2
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIFileEncodingInstantiatorProbe: probing level 2 interface 0 CUDIFEncoding
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::openDataFork: returning 0
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: returning 0
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: returning 0
CBSDBackingStore::closeDataFork fSIZE = 868220928
CUDIFEncoding::newProbe: failing because backing store is not UDIF file
DIFileEncodingInstantiatorProbe: interface 0, score    -1000, CUDIFEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
DIFileEncodingNewWithBackingStore: returning 0x0000006B
DIResolveURLToBackingStore: level 2 encoding match failed. 107.
(continuing)
DIResolveURLToBackingStore: processing level 3 encodings.
DIFileEncodingNewWithBackingStore: entry for encoding level 3
DIFileEncodingInstantiatorProbe: entry for level 3
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIFileEncodingInstantiatorProbe: probing level 3 interface 0 CSegmentedNDIFEncoding
checkTypeCreator:     /
checkTypeCreator: returning     , score 0
CSegmentedNDIFEncoding::isSegmentedNDIFFile checkTypeCreator failed
DIFileEncodingInstantiatorProbe: interface 0, score    -1000, CSegmentedNDIFEncoding
DIFileEncodingInstantiatorProbe: probing level 3 interface 1 CSegmentedUDIFEncoding
CSegmentedUDIFEncoding::isSegmentedUDIFFile backing store is not of type CUDIFEncoding
DIFileEncodingInstantiatorProbe: interface 1, score    -1000, CSegmentedUDIFEncoding
DIFileEncodingInstantiatorProbe: probing level 3 interface 2 CSegmentedUDIFRawEncoding
CSegmentedUDIFRawEncoding::isSegmentedUDIFRawFile looking for segment 2 "file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart"
DIIsInitialized: returning YES
DIBackingStoreNewWithCFURL: entry with
file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIBackingStoreInstantiatorProbe: entry
file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
CBSDBackingStore::newProbe stat() failed. No such file or directory.
CBSDBackingStore::newProbe score 1 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 0, score        1, CBSDBackingStore
DIBackingStoreInstantiatorProbe: probing interface 1 CBundleBackingStore
CBundleBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 1, score    -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: probing interface 2 CRAMBackingStore
CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
CRAMBackingStore::probe: score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 2, score    -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: probing interface 3 CCarbonBackingStore
CCarbonBackingStore::newProbe stat() failed. No such file or directory.
CCarbonBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 3, score    -1000, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: probing interface 4 CDevBackingStore
CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Users/Jeff/Jeff Projects.002.dmgpart).CDevBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 4, score    -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: probing interface 5 CCURLBackingStore
CCURLBackingStore::probe: scheme is: file
CCURLBackingStore::probe: not recognized URL scheme.
CCURLBackingStore::probe: score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 5, score    -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: probing interface 6 CVectoredBackingStore
CVectoredBackingStore::newProbe not "vectored" scheme.
CVectoredBackingStore::newProbe score -1000 for file://localhost/Users/Jeff/Jeff%20Projects.002.dmgpart
DIBackingStoreInstantiatorProbe: interface 6, score    -1000, CVectoredBackingStore
DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
DIBackingStoreNewWithCFURL: CBSDBackingStore
DIBackingStoreNewWithCFURL: instantiator returned 2
DIBackingStoreNewWithCFURL: returning 0x00000002
DIResolveURLToBackingStore: unable to resolve to any backing store class. 2.
CSegmentedUDIFRawEncoding::isSegmentedUDIFRawFile failed because could not find second segment.
DIFileEncodingInstantiatorProbe: interface 2, score    -1000, CSegmentedUDIFRawEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIFileEncodingNewWithBackingStore: probe fails to find appropriate CFileEncoding class.
DIFileEncodingNewWithBackingStore: returning 0x0000006B
DIResolveURLToBackingStore: level 3 encoding match failed. 107.
(continuing)
DIIsInitialized: returning YES
DIDiskImageNewWithBackingStore: entry with
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIDiskImageInstantiatorProbe: entry
image-path: /Users/Jeff/Jeff Projects.dmg
enable-keychain: true
DIDiskImageInstantiatorProbe: probing interface 0 CDARTDiskImage
DIDiskImageInstantiatorProbe: interface 0, score        0, CDARTDiskImage
DIDiskImageInstantiatorProbe: probing interface 1 CDiskCopy42DiskImage
DIDiskImageInstantiatorProbe: interface 1, score        0, CDiskCopy42DiskImage
DIDiskImageInstantiatorProbe: probing interface 2 CNDIFDiskImage
checkTypeCreator:     /
checkTypeCreator: returning     , score 0
CNDIFDiskImage::checkExtension: dmg
CNDIFDiskImage::newProbe: checkExtension gives score -1000.
DIDiskImageInstantiatorProbe: interface 2, score    -1000, CNDIFDiskImage
DIDiskImageInstantiatorProbe: probing interface 3 CUDIFDiskImage
CUDIFDiskImage::checkBackingStoreType: backing store is wrong type
DIDiskImageInstantiatorProbe: interface 3, score    -1000, CUDIFDiskImage
DIDiskImageInstantiatorProbe: probing interface 5 CRawDiskImage
checkBackingStoreType returned score 0 type
checkTypeCreator returned score 0 type
CRawDiskImage::checkExtension: dmg
checkExtension returned score 100 type WRDU
CBSDBackingStore::setPermission: opening /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000000 -> 0x00000014 (locks are MANDATORY)
(RO lock acquired)
CBSDBackingStore::setPermission: kDI_PERM_READONLY granted
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000000 -> 0x00000014 (locks are MANDATORY)
(RO lock acquired)
CBSDBackingStore::openDataFork: returning 0
===== iso scan =====
(null)
(null)
===============================
none
0:
          partition-name: whole disk
          partition-start: 0
          partition-synthesized: true
          partition-length: 1695744
          partition-hint: unknown partition
block-size: 512
burnable: false
appendable: false
CBSDBackingStore::closeDataFork fSIZE = 868220928
CRawDiskImage::checkExtension: dmg
CRawDiskImage: checkExtension returns score 100
DIDiskImageInstantiatorProbe: interface 5, score      100, CRawDiskImage
DIDiskImageInstantiatorProbe: probing interface 6 CShadowedDiskImage
DIDiskImageInstantiatorProbe: interface 6, score     -100, CShadowedDiskImage
DIDiskImageInstantiatorProbe: probing interface 7 CSparseDiskImage
CSparseDiskImage::checkExtension: dmg
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000000 -> 0x00000014 (locks are MANDATORY)
(RO lock acquired)
CBSDBackingStore::openDataFork: returning 0
CBSDBackingStore::closeDataFork fSIZE = 868220928
DIDiskImageInstantiatorProbe: interface 7, score        0, CSparseDiskImage
DIDiskImageInstantiatorProbe: probing interface 8 CSparseBundleDiskImage
CSparseBundleDiskImage::checkExtension: dmg
CSparseBundleDiskImage::newProbe: returning 0
DIDiskImageInstantiatorProbe: interface 8, score        0, CSparseBundleDiskImage
DIDiskImageInstantiatorProbe: probing interface 9 CCFPlugInDiskImage
DIDiskImageInstantiatorProbe: interface 9, score    -1000, CCFPlugInDiskImage
DIDiskImageInstantiatorProbe: probing interface 10 CWrappedDiskImage
DIDiskImageInstantiatorProbe: interface 10, score     -100, CWrappedDiskImage
DIDiskImageInstantiatorProbe: selecting CRawDiskImage
DIDiskImageNewWithBackingStore: CRawDiskImage
checkBackingStoreType returned score 0 type
checkTypeCreator returned score 0 type
CRawDiskImage::checkExtension: dmg
checkExtension returned score 100 type WRDU
CBSDBackingStore::setPermission: opening /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::setPermission: kDI_PERM_READWRITE granted.
CBSDBackingStore::openDataFork: /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::openDataFork: about to open /Users/Jeff/Jeff Projects.dmg
CBSDBackingStore::getNoFollow: returning 0
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CBSDBackingStore::openDataFork: returning 0
DIDiskImageNewWithBackingStore: instantiator returned 0
DIDiskImageNewWithBackingStore: returning 0x00000000
2011-10-10 13:30:57.258 diskimages-helper[440:2003] DIHelperAttach: performOperation: resolving shadow/section options
2011-10-10 13:30:57.258 diskimages-helper[440:2003] resolveShadowAndSectionOptions: returned 0
2011-10-10 13:30:57.258 diskimages-helper[440:2003] DIHelperAttach: performOperation: checking in-use (1)
DIBackingStore::inUse: this->_fUniqueID
0: d234881026:i2592177
DI_kextCreateDiskImageIdentifierArray: exiting
0:
          writeable-components:

Problem with DMGs and error: "No Mountable File Systems"

Problem with DMGs and error: "No Mountable File Systems"
The files are not corrupt. The problem is occurring with all DMGs that are apparently formatted in MS-DOS FAT16. No the file will not mount with Disk utility or any other disk mounter programs I have found.
This is now the second time this occurred and now effects my MBP and my iMac. First time i spent days with Apple support and the only solution was ultimately back up the data, reformat the HD, start over from scratch and reload everything. That lasted about a month before the problem resurfaced and is now an issue on both iMac and MBP.
I tried to identify all the programs I installed immediately before the error, as I am convinced it is the result of a software conflict.
Recent programs includes:
1) upgrading from Parallels 5.5 to 6.0 on both machines.
2) using an HP secure II usb drive and setting up a secure disk.
3) installing new itunes 10
4) new update to Flip For Mac.
The files affected are downloaded dmgs, including personal brain and google earth, both which are formatted in FAT16.
Any help or thoughts? Apple has now spent hours trying and they say i now have to reformat and wipe and start over. That is unacceptable and based on pasted experience the problem is likely to repeat itself. having to wipe and rebuild a HD ever month is not an solution. i need to fid the root problem.
In the meantime, anyone got a real solution on how to extract the data for a DMG using a different method?
Message was edited by: remaia

Where you able to find the solution, i am having the same problem, all was fine till i install some programs only same one i saw did we both did was flip4mac i uninstalled it but the problem is still there, i also restored and erased the hardrive but im not up to doing that all over again. If you found anything out let me know i would greatly appreciate it

Dmg - no mountable file systems

I am running 10.3.9 - all my dmg files now come back with this warning: The following disk images failed to mount
Image: <dmg>
Reason: no mountable file systems
I've got no multiple users (just me) no file sharing no file protection that I can think of and this just strated out of the blue
Thanks

Hi,
Welcome to Apple Discussions!
It really depends how you're acquiring these .dmg files. If you're saying that you've got some .dmg files on your Mac that you've had for some time and that you used to access and now cannot, then I'd be concerned that you've a disk problem. In this case I'd run First Aid from Disk Utility or run your Apple Hardware Test CD and see what responses you get. It never hurts to Repair Permissions as well... Oh, and verify your disk's SMART status - you'll find this by highlighting your HDD in the left-column in Disk Utility, and the SMART status is reported in the pane at the bottom. It should read Verified. Otherwise, I'd make a backup ASAP.
If you're saying that every .dmg file that you are downloading recently has reported this error, then it may be that these are simply corrupt, especially if they're all coming from the same source (e.g. P2P, the same website, etc.).
You may want to check out this thread at another discussions board. The reply from Silversleeves should help.
Good Luck.
SiR G.

DMG "no mountable file system" created when booting Leopard DVD

I was in the process of rebuilding my managers MacBook but I decided to make a full disc image before messing with any of her data. I plugged in a firewire hard drive and booted off my Leopard DVD. I selected the internal hard drive and clicked the new image button. Saved the image to the external. No errors were reported. Everything ran fine. Made a 50.3GB image file.
I them selected the internal HD and selected Restore and used our corp image file for and restored the internal drive with our image. I rebooted ran some updates joined it to the domain. Now it was ready for her user data. I went to mount the image of her data and it gives me "No mountable files system".
I have tried LOTS of things to get back at her data. I have used Data Rescue II, Disc Warrior, trying terminal commands listed in the following threads:
http://discussions.apple.com/thread.jspa?messageID=8036718
http://discussions.apple.com/thread.jspa?threadID=1218394&tstart=0
When I do the command "hdiutil udifxmldet <yourbrokenimage>" it tells me no XML data is present. Data Rescue II shows me all the files in the image but when I try to restore them all the data is 0 bytes. When I scavenge the data files it gives me files with random names and some data but a 2 page PDF file is 100MB and there is no file large enough to be her entourage database. So somehow things are kind of smushed together.
Is there any way to recover this data properly? He last backup, which she is responsible for doing on her own, was 6 weeks ago. But i know I will never hear the end of it if I lose 6 weeks of her data.
Please help if possible. Her MacBook is still under AppleCare and the Leopard DVD is a licensed retail copy though the computer is actually runnning 10.4.11 I used the Leopard dvd to make the image. And yes I tried opening the image with a leopard machine.

If you failed to mount the image after initially creating the image (a bootable backup/clone would have been a better option); then, I surmise that her stuff is gone. Sorry, but I have nothing else to offer.

I am trying to install End Note for Mac I am getting the message 'no mountable file systems'?

I am trying to install End Note for Mac I am getting the message 'no mountable file systems'?

Hi
This is the link it is endnote for mac from my university library site it is a referencing tool. http://moodle.uws.ac.uk/mod/page/view.php?id=132753

What "mountable file system" is xcode3.2.6 looking for on install?

I just updated my Mac Mini to OS X 10.6.8 after dowloading the xcode3.2.6+iOS DMG file. But now I am a little puzzled by the error message I get when I double-click to install: it fails with the message, "no mountable file systems".
I can find no special instructions in the readme file (downloaded separately), and I thought that it was only in the distant past that Apple required installs to be done from a separate filesystem. Hence the question: what "mountable file system" is it looking for? It is already ON a mounted file system.
Now speaking of that readme: when it starts talking about install from download (p4-5), it assumes the download yielded a .mpkg file. But I did not get this: I got a .dmg. Are they simply assuming the user knows the trick to get from DMG to MPKG?

You can check the disk image using the 'hdiutil' tool at the command line (Terminal.app):
hdiutil verify /Users/JD/Downloads/xcode_4.2_and_ios_5_sdk_for_snow_leopard.dmg
... (specify the path of your disk image that you downloaded). There should be several lines of output, and if the image is good, the last line should look something like this:
hdiutil: verify: checksum of "/Users/JD/Downloads/xcode_4.2_and_ios_5_sdk_for_snow_leopard.dmg" is VALID
... if it's not good, you'll see a variety of complaints and issues spit out.
The files are served and downloaded via the HTTP protocol which doesn't provide any particular validation on data transfer outside of what little negotiation happens at the TCP protocol layer. There's no Firefox plugin that can fix that, nor option to wget.
If it took 11 hours to download, that's < 44kbps. You might want to choose something other than a dial-up connection to download such large files. It wouldn't be at all surprising for there to be a minor error over such a connection.

Mounting the Root File System into RAM

Hi,
I had been wondering, recently, how can one copy the entire root hierarchy, or wanted parts of it, into RAM, mount it at startup, and use it as the root itself. At shutdown, the modified files and directories would be synchronized back to the non-volatile storage. This synchronization could also be performed manually, before shutting down.
I have now succeeded, at least it seems, in performing such a task. There are still some issues.
For anyone interested, I will be describing how I have done it, and I will provide the files that I have worked with.
A custom kernel hook is used to (overall):
Mount the non-volatile root in a mountpoint in the initramfs. I used /root_source
Mount the volatile ramdisk in a mountpoint in the initramfs. I used /root_ram
Copy the non-volatile content into the ramdisk.
Remount by binding each of these two mountpoints in the new root, so that we can have access to both volumes in the new ramdisk root itself once the root is changed, to synchronize back any modified RAM content to the non-volatile storage medium: /rootfs/rootfs_{source,ram}
A mount handler is set (mount_handler) to a custom function, which mounts, by binding, the new ramdisk root into a root that will be switched to by the kernel.
To integrate this hook into a initramfs, a preset is needed.
I added this hook (named "ram") as the last one in mkinitcpio.conf. -- Adding it before some other hooks did not seem to work; and even now, it sometimes does not detect the physical disk.
The kernel needs to be passed some custom arguments; at a minimum, these are required: ram=1
When shutting down, the ramdisk contents is synchronized back with the source root, by the means of a bash script. This script can be run manually to save one's work before/without shutting down. For this (shutdown) event, I made a custom systemd service file.
I chose to use unison to synchronize between the volatile and the non-volatile mediums. When synchronizing, nothing in the directory structure should be modified, because unison will not synchronize those changes in the end; it will complain, and exit with an error, although it will still synchronize the rest. Thus, I recommend that if you synch manually (by running /root/Documents/rootfs/unmount-root-fs.sh, for example), do not execute any other command before synchronization has completed, because ~/.bash_history, for example, would be updated, and unison would not update this file.
Some prerequisites exist (by default):
Packages: unison(, cp), find, cpio, rsync and, of course, any any other packages which you can mount your root file system (type) with. I have included these: mount.{,cifs,fuse,ntfs,ntfs-3g,lowntfs-3g,nfs,nfs4}, so you may need to install ntfs-3g the nfs-related packages (nfs-utils?), or remove the unwanted "mount.+" entires from /etc/initcpio/install/ram.
Referencing paths:
The variables:
source=
temporary=
...should have the same value in all of these files:
"/etc/initcpio/hooks/ram"
"/root/Documents/rootfs/unmount-root-fs.sh"
"/root/.rsync/exclude.txt" -- Should correspond.
This is needed to sync the RAM disk back to the hard disk.
I think that it is required to have the old root and the new root mountpoints directly residing at the root / of the initramfs, from what I have noticed. For example, "/new_root" and "/old_root".
Here are all the accepted and used parameters:
Parameter Allowed Values Default Value Considered Values Description
root Default (UUID=+,/dev/disk/by-*/*) None Any string The source root
rootfstype Default of "-t <types>" of "mount" "auto" Any string The FS type of the source root.
rootflags Default of "-o <options>" of "mount" None Any string Options when mounting the source root.
ram Any string None "1" If this hook sould be run.
ramfstype Default of "-t <types>" of "mount" "auto" Any string The FS type of the RAM disk.
ramflags Default of "-o <options>" of "mount" "size=50%" Any string Options when mounting the RAM disk.
ramcleanup Any string None "0" If any left-overs should be cleaned.
ramcleanup_source Any string None "1" If the source root should be unmounted.
ram_transfer_tool cp,find,cpio,rsync,unison unison cp,find,cpio,rsync What tool to use to transfer the root into RAM.
ram_unison_fastcheck true,false,default,yes,no,auto "default" true,false,default,yes,no,auto Argument to unison's "fastcheck" parameter. Relevant if ram_transfer_tool=unison.
ramdisk_cache_use 0,1 None 0 If unison should use any available cache. Relevant if ram_transfer_tool=unison.
ramdisk_cache_update 0,1 None 0 If unison should copy the cache to the RAM disk. Relevant if ram_transfer_tool=unison.
This is the basic setup.
Optionally:
I disabled /tmp as a tmpfs mountpoint: "systemctl mask tmp.mount" which executes "ln -s '/dev/null' '/etc/systemd/system/tmp.mount' ". I have included "/etc/systemd/system/tmp.mount" amongst the files.
I unmount /dev/shm at each startup, using ExecStart from "/etc/systemd/system/ram.service".
Here are the updated (version 3) files, archived: Root_RAM_FS.tar (I did not find a way to attach files -- does Arch forums allow attachments?)
I decided to separate the functionalities "mounting from various sources", and "mounting the root into RAM". Currently, I am working only on mounting the root into RAM. This is why the names of some files changed.
Of course, use what you need from the provided files.
Here are the values for the time spend copying during startup for each transfer tool. The size of the entire root FS was 1.2 GB:
find+cpio: 2:10s (2:12s on slower hardware)
unison: 3:10s - 4:00s
cp: 4 minutes (31 minutes on slower hardware)
rsync: 4:40s (55 minutes on slower hardware)
Beware that the find/cpio option is currently broken; it is available to be selected, but it will not work when being used.
These are the remaining issues:
find+cpio option does not create any destination files.
(On some older hardware) When booting up, the source disk is not always detected.
When booting up, the custom initramfs is not detected, after it has been updated from the RAM disk. I think this represents an issue with synchronizing back to the source root.
Inconveniences:
Unison needs to perform an update detection at each startup.
initramfs' ash does not parse wild characters to use "cp".
That's about what I can think of for now.
I will gladly try to answer any questions.
I don't consider myself a UNIX expert, so I would like to know your suggestions for improvement, especially from who consider themselves so.
Last edited by AGT (2014-05-20 23:21:45)

How did you use/test unison? In my case, unison, of course, is used in the cpio image, where there are no cache files, because unison has not been run yet in the initcpio image, before it had a chance to be used during boot time, to generate them; and during start up is when it is used; when it creates the archives. ...a circular dependency. Yet, files changed by the user would still need to be traversed to detect changes. So, I think that even providing pre-made cache files would not guarantee that they would be valid at start up, for all configurations of installation. -- I think, though, that these cache files could be copied/saved from the initcpio image to the root (disk and RAM), after they have been created, and used next time by copying them in the initcpio image during each start up. I think $HOME would need to be set.
Unison was not using any cache previously anyway. I was aware of that, but I wanted to prove it by deleting any cache files remaining.
Unison, actually, was slower (4 minutes) the first time it ran in the VM, compared to the physical hardware (3:10s). I have not measured the time for its subsequent runs, but It seemed that it was faster after the first run. The VM was hosted on a newer machine than what I have used so far: the VM host has an i3-3227U at 1.9 GHz CPU with 2 cores/4 threads and 8 GB of RAM (4 GB ware dedicated to the VM); my hardware has a Pentium B940 at 2 GHz CPU with 2 cores/2 threads and 4 GB of RAM.
I could see that, in the VM, rsync and cp were copying faster than on my hardware; they were scrolling quicker.
Grub, initially complains that there is no image, and shows a "Press any key to continue" message; if you continue, the kernel panics.
I'll try using "poll_device()". What arguments does it need? More than just the device; also the number of seconds to wait?
Last edited by AGT (2014-05-20 16:49:35)

I am trying to download EndnoteX4 but keep getting the message 'no mountable file systems'. What does this mean and how do I fix it?

I am trying to download EndNoteX4 but keep getting the message 'no mountable file systems'. What does this mean and how do fix it?

jenitsallgood wrote:
I am really unsure as to what I am doing wrong.
Maybe you are doing nothing wrong and the problem is with the disk.
Use SuperDuper or CarbonCopy Cloner
to clone your system to an external drive.
Then boot from your DVD go to Disk Utility and choose your entire drive > top icon in DIsk Utility.
Go to Erase tab. Choose format: Mac OS Extended (Journaled). Click on erase. Now, install Lion and when you get to setup assistant choose to migrate from your external drive.
This is slightly different than baltwo described and slighly longer but if there is any corruption on your disk a more through way to go, IMO.
What baltwo is saying is to clone your volume over to an external hard drive with CCC reformat and clone it back. This will defragment the files and make them all contiguous but will not address any directory problems.
Your choice. You can do it one way, then the other if it doesn't work out for you.

HT1199 I need your help, PLEASE. How can to fix "NO MOUNTABLE FILE SYSTEM" error of my back up hard drive on Mountain Lion OS?

I need your help, PLEASE. How can to fix "NO MOUNTABLE FILE SYSTEM" error of my back up hard drive on Mountain Lion OS?

Did you format the drive for Mac use before you tried to use it as a backup drive?
Are you using Time Machine on the drive? You can't view the contents of its backup database and the only way to access the info is directly from the Time Machine app.

My Backup.dmg is not mounting: No mountable file systems

Similar Messages

Maybe you are looking for