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 5, 2007 3:46 AM in response to The Shad Guy

You should get about 2 Pages of text output from this command.

Also, I dont want you to mount the image.
The command will only attach the image, so that you then can eventually try to repair it using disk utility or Disk-warrior, or try to salvage files using Disk-warrior.

Please, if you dont want to post the whole ouput of the command
try again with
hdid /Path/to/image.dmg -nomount

Nov 5, 2007 6:06 AM in response to nobody loopback

Okay heres the output, I had to use -nomount and -verbose to get anything worthwhile, and if you need to I can also post the -debug as well, let me know what ever is needed

hdid /Users/jasonbrennan/Desktop/MACPROBACKUP.dmg -nomount -verbose
DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: interface 3, score 100, 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 100, CBSDBackingStore
DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: interface 3, score 100, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: interface 4, score -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: interface 5, score -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: interface 6, score -1000, CVectoredBackingStore
DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
DIFileEncodingInstantiatorProbe: interface 0, score -1000, CMacBinaryEncoding
DIFileEncodingInstantiatorProbe: interface 1, score -1000, CAppleSingleEncoding
DIFileEncodingInstantiatorProbe: interface 2, score -1000, CEncryptedEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIFileEncodingInstantiatorProbe: interface 0, score 900, CUDIFEncoding
DIFileEncodingInstantiatorProbe: selecting CUDIFEncoding
DIFileEncodingNewWithBackingStore: CUDIFEncoding
DIFileEncodingNewWithBackingStore: instantiator returned 0
DIFileEncodingInstantiatorProbe: interface 0, score -1000, CSegmentedNDIFEncoding
DIFileEncodingInstantiatorProbe: interface 1, score -1000, CSegmentedUDIFEncoding
DIFileEncodingInstantiatorProbe: interface 2, score -1000, CSegmentedUDIFRawEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIDiskImageInstantiatorProbe: interface 0, score 0, CDARTDiskImage
DIDiskImageInstantiatorProbe: interface 1, score 0, CDiskCopy42DiskImage
DIDiskImageInstantiatorProbe: interface 2, score -1000, CNDIFDiskImage
DIDiskImageInstantiatorProbe: interface 3, score 1000, CUDIFDiskImage
CRawDiskImage: data fork length 0x0000001DC012CBF0 (127776508912) not a multiple of 512.
DIDiskImageInstantiatorProbe: interface 5, score -100, CRawDiskImage
DIDiskImageInstantiatorProbe: interface 6, score -100, CShadowedDiskImage
DIDiskImageInstantiatorProbe: interface 7, score 0, CSparseDiskImage
DIDiskImageInstantiatorProbe: interface 8, score 0, CSparseBundleDiskImage
DIDiskImageInstantiatorProbe: interface 9, score -1000, CCFPlugInDiskImage
DIDiskImageInstantiatorProbe: interface 10, score -100, CWrappedDiskImage
DIDiskImageInstantiatorProbe: selecting CUDIFDiskImage
DIDiskImageNewWithBackingStore: CUDIFDiskImage
CUDIFDiskImage::setBackingStore unable to open resource fork (-4960)
DIDiskImageNewWithBackingStore: instantiator returned -4960
DIHLDiskImageAttach() returned -4960
hdid: attach failed - error -4960

Nov 5, 2007 10:22 AM in response to The Shad Guy

The output shows, that no matching disk-image type can be found.

If this is a "Raw" image, then according to the output, its length must be a multiple of 512 bytes, which is not the case.

Question:
Is this a compressed image or an uncompressed image ?
meaning: The disk or partition you imaged, had this also a size of approximately 120MB ?

if the image is uncompressed, you can write it back to a disk or a partition (using the dd command in the terminal), regardless if its complete or not.
if its compressed, we should check, if there is something missing at the end or at the beginning and then try again to attach it.

Nov 5, 2007 11:36 AM in response to The Shad Guy

Maybe, also check if its not something else:
"CUDIFDiskImage::setBackingStore unable to open resource fork (-4960)"


Assuming, this is not a Raw disk image,
but a compressed image:

- on what kind of filesystem is the image saved ( HFS+, HFS+ Case sensitive ... )?
- have you checked you have rights to read and write the folder containg the image and if you have read and write rights to the file ?

- dmgs do not need a resource-fork:
does this image has a resource fork ?
do a:
ls -l /Users/jasonbrennan/Desktop/MACPROBACKUP.dmg/rsrc
what is the output ?

maybe try to delete the resource fork and then retry mounting the image:
First, make a copy of the image to a safe location
then do a:
rm /Users/jasonbrennan/Desktop/MACPROBACKUP.dmg/rsrc
a question comes up like "override ....", press y
then again try to mount the image.

-------
When you did the imaging process, do you remember, what kind of image disk utility chose ?
During the imaging, have you observed that the process was finished sucessful ?

Nov 5, 2007 12:29 PM in response to nobody loopback

Okay, it sounds like we might be getting somewhere. This is just the restore image from everything on my harddrive (ei the entire volume), and I believe I just used the default setting of "compressed". The disk itself was a "250GB" harddrive, although I had a ~50GB bootcamp partition on it too (which I did not include when I made the restore image) and I also had about 120GB of data, so this size seems reasonable.

The filesystem of my disk was HFS+ not case sensitive. I've done a chmod 777 to ensure I have rights to the file as well.

This is the output to the ls command:
ls -l ~/Desktop/MACPROBACKUP.dmg/rsrc
-rwxrwxrwx 1 jasonbrennan staff 0 29 Oct 11:55 /Users/jasonbrennan/Desktop/MACPROBACKUP.dmg/rsrc

So yes, when I made the image with the Tiger Install DVD Disk Utility, I made a restore image from my internal drive using the default settings of a compressed image. It looks like the size of the "rsrc" file is 0 bytes though..I will try removing it....Yeah it can't be removed because it's not there, says "no such file or directory". It's strange though, that ls would still show it, even though its zero bytes.

Okay so that's what I've got from here. I was previously thinking of just dd'ing it back to the disc but I'm not sure how this whole "compression" thinger works.

I forgot to mention, when I created the image, it suceeded without error, as far as I know. Because it was so large, it obviously took a few hours so I didn't watch it the whole time, but when I returned to my machine hours later, it was complete with no error messages to be seen.

Message was edited by: The Shad Guy

Nov 5, 2007 12:42 PM in response to The Shad Guy

I tried a compressed disk diskimage, removed the resource-fork, and the image still mounted ok.

This is, how it should look:
<pre>
user% hdid tuxracer-0.61f\ copy.dmg -verbose -nomount
DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: interface 3, score 100, 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 100, CBSDBackingStore
DIBackingStoreInstantiatorProbe: interface 1, score -1000, CBundleBackingStore
DIBackingStoreInstantiatorProbe: interface 2, score -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: interface 3, score 100, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: interface 4, score -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: interface 5, score -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: interface 6, score -1000, CVectoredBackingStore
DIBackingStoreInstantiatorProbe: selecting CBSDBackingStore
DIFileEncodingInstantiatorProbe: interface 0, score -1000, CMacBinaryEncoding
DIFileEncodingInstantiatorProbe: interface 1, score -1000, CAppleSingleEncoding
DIFileEncodingInstantiatorProbe: interface 2, score -1000, CEncryptedEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIFileEncodingInstantiatorProbe: interface 0, score 900, CUDIFEncoding
DIFileEncodingInstantiatorProbe: selecting CUDIFEncoding
DIFileEncodingNewWithBackingStore: CUDIFEncoding
DIFileEncodingNewWithBackingStore: instantiator returned 0
DIFileEncodingInstantiatorProbe: interface 0, score -1000, CSegmentedNDIFEncoding
DIFileEncodingInstantiatorProbe: interface 1, score -1000, CSegmentedUDIFEncoding
DIFileEncodingInstantiatorProbe: interface 2, score -1000, CSegmentedUDIFRawEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
DIDiskImageInstantiatorProbe: interface 0, score 0, CDARTDiskImage
DIDiskImageInstantiatorProbe: interface 1, score 0, CDiskCopy42DiskImage
DIDiskImageInstantiatorProbe: interface 2, score -1000, CNDIFDiskImage
DIDiskImageInstantiatorProbe: interface 3, score 1000, CUDIFDiskImage
CRawDiskImage: data fork length 0x000000000011DA57 (1170007) not a multiple of 512.
DIDiskImageInstantiatorProbe: interface 5, score -100, CRawDiskImage
DIDiskImageInstantiatorProbe: interface 6, score -100, CShadowedDiskImage
DIDiskImageInstantiatorProbe: interface 7, score 0, CSparseDiskImage
DIDiskImageInstantiatorProbe: interface 8, score 0, CSparseBundleDiskImage
DIDiskImageInstantiatorProbe: interface 9, score -1000, CCFPlugInDiskImage
DIDiskImageInstantiatorProbe: interface 10, score -100, CWrappedDiskImage
DIDiskImageInstantiatorProbe: selecting CUDIFDiskImage
DIDiskImageNewWithBackingStore: CUDIFDiskImage
DIDiskImageNewWithBackingStore: instantiator returned 0
DI_kextWaitQuiet: about to call IOServiceWaitQuiet...
DI_kextWaitQuiet: IOServiceWaitQuiet took 0.000025 seconds
2007-11-05 21:38:45.475 diskimages-helper[2701:2417] -serveImage: attaching drive
{
autodiskmount = 0;
"hdiagent-drive-identifier" = "E37156E8-1353-4C37-BBF6-08AF2753DA20";
"unmount-timeout" = 0;
}
2007-11-05 21:38:45.489 diskimages-helper[2701:2417] -serveImage: connecting to myDrive 0x00003707
2007-11-05 21:38:45.490 diskimages-helper[2701:2417] -serveImage: register _readBuffer 0x0x477000 with myDrive 0x0x0
2007-11-05 21:38:45.491 diskimages-helper[2701:2417] -serveImage: activating drive port 0x0x3807
2007-11-05 21:38:45.497 diskimages-helper[2701:2417] _serveImage: set cache enabled=TRUE returned SUCCESS.
2007-11-05 21:38:45.497 diskimages-helper[2701:2417] _serveImage: set on IO thread=TRUE returned SUCCESS.
2007-11-05 21:38:45.503 diskimages-helper[2701:2417] -serveImage: starting server loop - myPort is 0x0x3807
/dev/disk2 Apple partitionscheme
/dev/disk2s1 Apple partitionmap
/dev/disk2s2 Apple_HFS
</pre>

Strange.
Have you tried disk-utilities "verify" function for the image ?

Nov 5, 2007 1:16 PM in response to nobody loopback

The only difference I could think of is that your image is just of a folder, where mine is a restore image, although I'm not sure how they are different. Also, what is contained in the resource fork? You said you removed yours and it still worked. Would I be able to possibly add one in to mine (cp from another image)? I'm trying to think what purpose it serves.

Nov 5, 2007 1:27 PM in response to The Shad Guy

Okay, I've been poking around in disk utility on the Instal Disk again and now I'm not so sure what I did when I made my image.

I'm thinking now that instead of using the restore function to make the image, *I instead did File->New Image From-> disk02* or whatever the appropriate selection was. Then when prompted what to call it, I named it MACPROBACKUP.dmg, and I left it the default type, which was Compressed.

Does this mean I can dd it back to my drive? Obviously I'd lose my current Leopard install but that's really not an issue at all.

I should also probably note that since I've used Leopard, I have erased my bootcamp partition and used the BC Tool to give that blank space back the main partition.

Nov 5, 2007 1:46 PM in response to The Shad Guy

The resource fork of a disk image seems only to be exist for compatibility reasons with pre 10.1 systems. It normally is not used any more.

I dont think, that you can just use dd to copy back the file, because it then must have at least the size of the partition. AFAIK the term "compression" means here that unused parts of the filesystem are not stored in the image. Real compression would mean an image compressed with bzip2.

Maybe, the error message about the resrouce forks is, because the dmg is corrupt/incomplete and the diskimage-Framwork is unable to locate the resourcefork inside the image.
-----
There is another command:
hdiutil info xyz.dmg

That should give you information about a disk image.
If this works, you would at least know, what kind of image this is.

Nov 5, 2007 2:01 PM in response to nobody loopback

using the hdiutil info disk.dmg, didn't work, and omitting the disk.dmg argument just told me info about the disk driver in OS X. I tried the imageinfo argument and that gave me the same information as hdid had already.

Now, concerning dd, is it really an issue if I were to do that then? If I dd the whole thing over, will it not just occupy 120GB of my disk. The other, unused space would not appear in a partition but that's really not a problem to me at all, so long as I would get my files back. Do you think something like that is worth a try? I'm not very familiar with dd however, so I could be mistaken and I'd also need some exact guidance on the usage.

Maybe if we should try this I could talk to you over iChat (AIM/.Mac whatever) or some other IM, or we can just continue here. Again, I'm really glad for your help!

Nov 5, 2007 2:27 PM in response to The Shad Guy

sorry for that typo:
hdiutil imageinfo xyz.dmg

Of course you could try dd to write back the disk - better then nothing.
But better get a new disk, dont overwrite your running system.

I dont have an iChat account, but its certainly not difficult to register one.
But I think explaining dd here will do.

but try the imageinfo again.

My plan:
you can convert an image with hdiutil to an image with 2 forks, one data, one resourcefork. If it is possible to do this, you then probably could try to zap the resourcefork and then mount the data.
That way you would loose nearly nothing (only fonts, applications, no movies, music, photos, documents)


edit:
i recovered my unused aim account: nobodyloopback

Message was edited by: nobody loopback

Nov 5, 2007 2:28 PM in response to nobody loopback

Well, I have a second system to work with (my Macbook Pro), so dd wouldn't be a problem for that, all I really care about is getting my stuff so it doesnt matter if I basically have a bummed computer for a little while... there are replacements!

imageinfo gives me identical output to our earlier probing with hdid, errors out when it finds the lack of resource fork.

Now how do I go about converting the image to have 2 forks? Im reading through the man pages but they are hard to decipher.

Nov 6, 2007 8:42 AM in response to The Shad Guy

Okay, so last night I attempted to dd the entire image onto a partition on my external drive... after hours and hours of dd running, it finally finished sucessfully.. However, the partition will not mount! So at this point, as nobody loopback suggested, I can likely use DataRescue and see what I can pull out of this newly dd'd partition.

I also tried using Disk Utility and Disk Warrior on the drive but neither could fix it. I'm not giving up yet though, I know the files are in there somewhere and there MUST be a way to get at them... Im hoping to hear from Apple soon about the DMG format, then I can get started.

Nov 6, 2007 4:50 PM in response to MJWeb

Thanks!! I really appreciate the support, it really does help on some levels.

I managed to find a technical document on the HFS+ File system so this may be of help to me/anyone else

http://developer.apple.com/technotes/tn/tn1150.html

Again, don't really know how much it will help people, but it's worth a shot. Like has been said before, journaling is likely part of the problem here!! I wish Apple could be a little more supportive though. I'm a smart Computer Science student, but I'm no Apple Engineer (yet!)

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.