Disk images gone corrupt cause of power failure

Voltago

Registered
I'll give it another try:

After a power failure (which shut down my iMac) two very important encrypted disk images (about 20 GB each), which were mounted at that incident, failed to mount again. I got this message instead:

The following disk images have failed to mount: Reason "corrupt image".

After that I tried to do a fsck-check in the Terminal (I don't know very much about the command line but I were able to check this out). Outcome:

BAD SUPER BLOCK: MAGIC NUMBER WRONG ioctl (GCINFO): Inappropriate ioctl for device fsck: /Users/ral/Desktop/IT Kopie.sparseimage: can't read disk label.

I've done further investigations in the Terminal (with help of the manual on the Apple Dev site) with the following results:

rainer-****-imac-g5:~ ral$ fsck_hfs -d -y /Users/ral/Desktop/ITkopie.sparseimage
/Users/ral/Desktop/ITkopie.sparseimage is not a character device
CONTINUE? yes

** /Users/ral/Desktop/ITkopie.sparseimage
ioctl(DKIOCGETBLOCKCOUNT) for fd 3: Inappropriate ioctl for device
invalid device information for volume - total sectors = 0 sector size = 0
CheckForClean - unknown volume type
invalid device information for volume - total sectors = 0 sector size = 0
** Volume check failed.
volume check failed with error 7
unknown volume type
primary MDB is at block 0 0x00
alternate MDB is at block 0 0x00
primary VHB is at block 0 0x00
alternate VHB is at block 0 0x00
sector size = 0 0x00
VolumeObject flags = 0x01
total sectors for volume = 0 0x00
total sectors for embedded volume = 0 0x00

and:

rainer-****-imac-g5:~ ral$ fsck -b 32 /Users/ral/Desktop/ITkopie.sparseimage
Alternate super block location: 32
/Users/ral/Desktop/ITkopie.sparseimage is not a character device
CONTINUE? [yn] y

** /Users/ral/Desktop/ITkopie.sparseimage
BAD SUPER BLOCK: MAGIC NUMBER WRONG

I'm really desperate! Because I don't have a backup of the data (I was actually on the way to do backups when the power failure occurred!). What can I do? Is there a way to save my data? There has to be one! Perhaps with a disk repair app or something like that (I have already tried some, but failed (the volumes have to be mounted...)?

BTW shouldn't the "journaled" feature of the file system on the DMG prevent this from happening? I really need your help!

Thanks!!!
 
Back
Top