"No mountable file systems" error upon attempt to mount backup dmg

I see it's been a while since you posted. I have the same problem and would love to know of a solution if you found one.

Exactly the same thing happening here....surely there's SOMEONE in the world (or even Apple) who knows what to do here?

Message was edited by: MickWolf

I too have this problem and I find it hard to believe that NO ONE has been able to provide any sort of answer on this. Disk Utility created the image without a problem but was somehow corrupted during a restore of all things!

Maybe we're all just fracked? 😟 I guess the lesson here is: Having only one backup is not enough. Backup, and then backup your backup.

Thanks in advance to anyone who can shed some light, or even better a solution to this dilemma.

I have this problem as well. I bought new external hard drive and saved backup of internal HD there. Then I formatted the internal drive but now I cannot mount DMG with the backup.
I hope there is some solution for this because I need the backup.

Although it can bring a few new levels of intricacy into the situation, I have found that the best way to do backups of this sort is to NOT use the 'Image...' button, but use the 'Restore' button instead to copy it to another drive. This means of course that if the target drive is larger than your source that you will be better off creating a partition that is slightly larger than the source so that you won't have to commit the entire disk to this one backup.

Doing it this way give the extra benefit of allowing you to test your backup before erasing the contents of the source drive by booting from the newly restored target volume.

You can never have too many backups! Good luck.

Message was edited by: SCI Drew

Message was edited by: SCI Drew

Gah! This happened to me too!
It ***** knowing the information is there are not accessable.
Is there any way to sector edit in the partition/file system information?
I want my photos back..

Please help. Any guidance?

Here is some information:
Finnian:~ Corey$ hdiutil attach "/Volumes/MACINTOSH\ EXT/FUJITSU\ MHW2120BH\ Media.dmg" -verbose
Initializing…
DIBackingStoreInstantiatorProbe: interface 0, score 1, CBSDBackingStore
DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: interface 3, score -1000, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: interface 4, score -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: interface 5, score -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: interface 6, score -1000, CVectoredBackingStore
DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
DIBackingStoreInstantiatorProbe: interface 0, score 1, CBSDBackingStore
DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: interface 3, score -1000, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: interface 4, score -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: interface 5, score -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: interface 6, score -1000, CVectoredBackingStore
DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
Attaching…
Error 2 (No such file or directory).
Finishing…
DIHLDiskImageAttach() returned 2
hdiutil: attach failed - No such file or directory



Anyone? >.<

well, I had the same problem. I'm happy to say I have solved it. Please take a look at http://discussions.apple.com/thread.jspa?threadID=1218394&tstart=0. In the last post I described my case. It turned out that my dmg was truncated: the xml part at the end of dmg and "resource part" was missing. Thankfully blkx part of the xml seems to be ok. I have managed to create the end of dmg in hex editor.
It is really shame for Apple that they didn't published any description of dmg. That's not fair. Apple PLEASE make it more 'open'!!!!!

Some people have reverse engineered it. Look at code of libdmg at: http://github.com/planetbeing/libdmg-hfsplus/tree/master.
Of course there are some problems with the code (it seems it works best for compressed UDIF, for read-only uncompressed UDIF the buffer is not allocated). But I hope this code may give you some idea how it works. So I created in 'similar' way another dmg and used it to make missing ending.

You have to modify these sections of resources part:
uint64_t fUDIFRsrcForkLength;
uint64_t fUDIFDataForkLength;
uint64_t fUDIFRsrcForkOffset;
uint64_t fUDIFXMLOffset;
uint64_t fUDIFXMLLength;

I hope this was helpfull.

I had the same error on a smaller dmg file. Although Disk Utility "Verified" the image, it would not mount it.

Disk Utility did let me Burn it to a cd. The burn went fine, and the info is now available to me on the cd.

90 GB is pretty large, maybe burning to several dvds?

romarcin,

Could you 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. My 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!

I have started a thread for my problem here.
http://discussions.apple.com/thread.jspa?threadID=1699574

I got this after a "multi-language screen of death". Extra scary because the backup is for a computer that's been wiped, so it's my only copy (though I have offsite backup for the irreplaceable stuff).

Thankfully seems to work after a reboot, though.

Hello, I realize I'm very late to this party, but here's my experience:

I had a similar issue with a very large .dmg ~70GB, it was created OK, and seemed to verify fine till it was time to be mounted, then it popped up a "No mountable file system" error.

The solution I found required Disk utility, DiskWarrior, and a lot of hard drive space.

1. Copy the image to a different computer (this may have no impact, but it's what I did)
2. Convert the image to a read/write .dmg using disk utility
3. double click the new image, it should throw up the same error as befor.
4. Launch DiskWarrior, and select "Unknown Disk"
you may also notice disk utility has a unmounted volume under the newly converted disk image
5. click "repair" in DiskWarrior
6. if diskwarrior can replace the directory structure do it, that should fix the problem, otherwise click "preview."
7. if the preview image mounts, great! you should have access to your files. if not, find the unmounted disk image in DiskUtility (there should be 2 now, one is the diskwarrior preview drive and the other is your converted disk image), hi-light the unmounted preview drive and click "mount" in Disk utility.
8. The drive should mount. Copy the files off the PreviewDrive to somewhere safe.

you may need to reboot your mac to get the disk images to unmount/go away.

This is the method that worked for me, Good Luck!!!!

details:
image was ~70GB and created on a MacPro Mac OS X Server 10.5.3.
all the work was done on a similar MacPro with Mac OS X 10.5.6.
DiskWarrior 4.1.1 on the local hard drive

Okay, I'm going to try this out.
I have had the same problem as everyone else has described,
I was on the phone to apple for hours and none of them
understood the problem.

I will try the last solution and see what I can do,
otherwise I may try to find an apple technician to help.

This works perfectly..

If your like me and don't really understand all this console commands etc
then this is perfect.

although one thing i found which you didn't mention.

When you try to open the new .dmg (this must be attempted via finder)
the error will appear LEAVE THE ERROR OPEN then Disk Warrior will find the
new drive... (Which should be the name of the original drive you made a copy of)

Then simply use the rebuild option, once finished this will then bring up a window with the PREVIEW option, click it... then take what you need!

Thanks - Caius Eugene