Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Can't Open my Backup DMG years of data gone

Okay I'm going to try to describe this in as much detail as I can and hopefully someone out there can help. I'm using a Mac Pro that has one harddrive in it, 250gb. I also have a Macbook Pro. I also have an external USB drive that's 250gb, and it's partitioned in 2 parts, on is about 200 and the other is 50. I can NOT boot from this drive.

A couple of days ago I decided I would back up my Mac Pro in anticipation of Leopard. So I booted into the Tiger Install disc that came with my computer, and used the disc utility to create a restore image of my entire Harddrive, using the default settings. The image is saved to my external drive.

I got Leopard on Friday and installed it using a clean instal, erasing everything on my computer and installing it fresh. The install went fine and Leopard works magically on this machine. I decided it was time to start bringing my files over from my image I had created, so I attached my drive and opened the DMG, but it wouldn't open, giving me error -4960. PANIC ENSUED. I also tried to mount it on my MacBook Pro which is still running Tiger and I got the same error!

The next day (yesterday) I called Apple, and the man I spoke with told me the reason why it won't mount is because its a raw restore image and what I'll have to do is restore it using the disk utility again. That made sense to me. This morning I tried restoring the image with both the Leopard utility and the Tiger one as well (booting off the install DVDs, that is), but no matter what I do, I get the same error -4960!!

So at this point I'm basically shattered. I live on my computer, it's my whole life (I know that may sound sad haha but it's the truth). This is like having my house burn down, and on top of that, the IRONY of the situation is just too much. The whole reason for upgrading is to get Time Machine.. Ugh. Anyway, Im starting to run out of ideas here. I think maybe it could be because my external drive is a piece of crap or something, so I'm currently copying the thing over to my internal drive and I'll try that. Other than that, I'm thinking the image must be corrupt or something, does anybody know any hardcore tools that could be used in such a situation? Any terminal-fu that could possibly fix this whole problem? I did use data recovery software on the drive yesterday and managed to get a few things, I think,, but I havent really looked through them and it's really not the same as having the files themselves, you know? But I guess it's something.

So yeah, if ANYONE has any ideas on what to do, you have no idea how thankful I would be to hear it.

Jason

touch fuzzy, get dizzy

Posted on Nov 4, 2007 9:20 AM

Reply
Question marked as Best reply

Posted on Nov 4, 2007 10:06 AM

I'm very sympathetic to your situation and have been investigation error -4960 for you. These aren't specific answers but they might point you in the right direction, on your own, or communicating with Apple. Both of these, though unrelated, suggest the problem and solution is related to the User account. Just a hunch, but I'd try opening the DMG from your Guest Account. Keep bugging Apple, too!

http://docs.info.apple.com/article.html?artnum=93311

http://www.tech-archive.net/Archive/Mac/microsoft.public.mac.office.entourage/20 05-02/0052.html
85 replies

Nov 15, 2007 3:16 PM in response to The Shad Guy

Greetings.

Surgery is presently underway. The disk containing your image has been attached to a computer at Apple Canada's offices and I am remotely logged in doing "tele-recovery".

My prosthetic XML patch has been installed and the disk image is mounting which is absolutely fantastic news. This means that the patient will regain quite a bit of functionality after surgery.

Please note, however, that there was some data-loss and when you receive the disk back, you will want to carefully go through your files. I would recommend re-installing applications and other software from original installers.

There is about 110MB of data loss (out of 119GB) *that I detected and repaired*. There may be other hidden data corruption issues.

I am in the process of copying the files off of the disk image onto the drive that you sent. This will take awhile.

Okay, back to monitoring the patient.

Cheers!

Nov 15, 2007 8:28 PM in response to nahnoryb

Has the original drive been scanned to see if it has any bad blocks that have not been remapped to spare blocks?

The Surface Scan in TechTool Deluxe can find such blocks. It is part of AppleCare. It would be worth investigating whether the corruption is internal to the data of the disk image only, or is a consequence of media defects in the drive.

Nov 20, 2007 4:18 PM in response to The Shad Guy

Hi all, I'm very happy to announce an end to this tremendous adventure of mine. It's been a stressful few weeks and there have been some bleak moments, but I am very very happy to say that I got my data back!!

Yep, Byron managed to patch the corruption out of my DMG and copied all my data back for me! I have no idea how he did it (I'm thinking he uses magic.) but by golly I've got it all back. Out of 119GB, I guess there is about 110mb or so missing but I don't know where from, pretty much everything is there. Truly remarkable. Everything works as expected, I really can't believe it.

So I'd like to wish a thanks to everyone here on the boards who have offered help and support to me through these times, it's been really something special. Thanks to Apple, Byron and Tajai too. And of course Steve. This is why I love Apple so much, and why it's my dream job (hopefully only a matter of time!).

Again, thank you so much. And as a final word, VERIFY YOUR BACKUPS. Haha.

^_^
Jason

Feb 9, 2008 8:34 AM in response to texasfred

I have precisely the same problem. But my dmg file could not have been damaged, because I made it just before I've tried to mount it.

So, first I made an image with Disk Utility from my diskpartition (disk0s2), choosing "New/Disk Image from disk0s2 (PivMac HD)", then select the standard settings (compressed, Encryption=none). Then I've tried to open/mount the resulting .dmg file with DIsk Utility, its command line version, hdiutil or even from Toast as well. But I have been getting the famous -4960 error.

The "hdiutil verify" gives similar output which was discussed in this thread earlier:

many InstantiationProbes .... then
DIDiskImageInstantiatorProbe: interface 8, score -1000, CCFPlugInDiskImage
DIDiskImageInstantiatorProbe: interface 9, score -100, CWrappedDiskImage
DIDiskImageInstantiatorProbe: selecting CUDIFDiskImage
DIDiskImageNewWithBackingStore: CUDIFDiskImage
CUDIFDiskImage::setBackingStore unable to open resource fork (-4960)
DIDiskImageNewWithBackingStore: instantiator returned -4960
hdiutil: verify: unable to recognize "/Volumes/Backup HD/Backups/disk0s2.dmg" as a disk image. (error -4960)
hdiutil: verify: result: -4960
hdiutil: verify failed - error -4960

So my feeling is that Disk Utility realy makes a dmg (from a disk partition) which then could not be mounted.

The only thing I should mention that the .dmg file was/is stored on an external HD's NTFS partion, which is mounted with Paragon NTFS sotware. But if the good old unix axiom would work this should be transparent for any programs reading from this NTFS drive.

So. what is Apple's opinion about this "reproduced case".

Thanks for any help,

piv

May 4, 2008 12:08 PM in response to pivpiv

Hey,

I have the same problem. Here is what I did:

I wanted to repartition my hd, because I couldn't have shrink it with diskutil resizeVolume. So I booted up my mbp with Leopard DVD and connected another hd in external usb enclosure. I run DiskUtility and verified both drives. Then I opened terminal and created backup image:

hdiutil create -srcdevice /dev/disk0s2 -format UDRO /externalvolume/Macintosh.dmg

// about 52GB, journaled case-sensitive hfs+

I have mounted the image, to see if everything works ok.
Then I scanned this image for restore using DiskUtility and repartitioned my MacBook hd.

After that, I've chosen restore without checking "erase destination". It started to copy files. After 3 hours it slowed down and dvd started working intensely. It was no longer coping data from external hd. So I waited an hour and restarted the computer with ctrl commandpower. It was really silly. It turned out, that the dmg no longer mounts.

It seems, that xml at the end of dmg is truncated. It shouldn't occur, because DiskUtility shouldn't modify image while restoring, since it's read-only. I suppose, that the image could have been improperly closed or the date not flushed to dmg while creating image or "scanning for restore".

I can normally read the data using hexedit. I also tried to dd the image to another partition with no success.

Here is some output:
hdiutil udifxmldet /Macintosh.dmg

hdiutil: udifxmldet: "/Macintosh.dmg"; has no embedded XML data.

hdiutil udifderez /Macintosh.dmg

hdiutil: udifderez: could not get resource fork of "/Macintosh.dmg";: Function not implemented (78)
hdiutil: udifderez failed - Function not implemented

I made tail -c 1024 /Macintosh.dmg > tail and dd if=/Macintosh.dmg count=2^20 > head.
Here are these files:
http://alan.umcs.lublin.pl/~mroman/head
http://alan.umcs.lublin.pl/~mroman/tail

hdiutil attach -verbose -debug /Macintosh.dmg >& attach.out
http://alan.umcs.lublin.pl/~mroman/attach.out

mbp:/ mroman$ hdiutil attach -verbose -debug -imagekey diskimage-class=CRawDiskImage /Macintosh.dmg >& attachRaw.out
http://alan.umcs.lublin.pl/~mroman/attachRaw.out
mbp:/ mroman$ hdiutil attach -verbose -debug -imagekey diskimage-class=CUDIFDiskImage /Macintosh.dmg >& attachUDIF.out
http://alan.umcs.lublin.pl/~mroman/attachUDIF.out

There is 0 length rsrc.

Is there any hope to fix the dmg? Please, help!!! There is all my work.

Can't Open my Backup DMG years of data gone

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.