Hdiutil: verify failed - corrupt image

problem: sparseimage is not mountable and verify ends with a "hdiutil: verify failed - corrupt image".
cause: tiger crashed and the image was mounted. the only way to boot was power down the machine. after the reboot the image was not mountable anymore.
thats the verbose output:
hdiutil verify -verbose conti.sparseimage
hdiutil: verify: processing "conti.sparseimage"
DIBackingStoreInstantiatorProbe: interface 0, score 100, CBSDBackingStore
DIBackingStoreInstantiatorProbe: interface 1, score -1000, CRAMBackingStore
DIBackingStoreInstantiatorProbe: interface 2, score 100, CCarbonBackingStore
DIBackingStoreInstantiatorProbe: interface 3, score -1000, CDevBackingStore
DIBackingStoreInstantiatorProbe: interface 4, score -1000, CCURLBackingStore
DIBackingStoreInstantiatorProbe: interface 5, 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 -1000, CUDIFEncoding
DIFileEncodingInstantiatorProbe: nothing to select.
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
DIDiskImageInstantiatorProbe: interface 5, score -100, CRawDiskImage
DIDiskImageInstantiatorProbe: interface 6, score -100, CShadowedDiskImage
DIDiskImageInstantiatorProbe: interface 7, score 1000, CSparseDiskImage
DIDiskImageInstantiatorProbe: interface 8, score -1000, CCFPlugInDiskImage
DIDiskImageInstantiatorProbe: interface 9, score -100, CWrappedDiskImage
DIDiskImageInstantiatorProbe: selecting CSparseDiskImage
DIDiskImageNewWithBackingStore: CSparseDiskImage
DIDiskImageNewWithBackingStore: instantiator returned 103
hdiutil: verify: unable to recognize "conti.sparseimage" as a disk image. (corrupt image)
hdiutil: verify: result: 103
hdiutil: verify failed - corrupt image
the problem is not that i dont have a backup of tha date within this 7GIG imagefile. the problem is now that i dont trust this format anymore. i do have a couple of AES-secured sparesimages FOR backup-reason (including one on my iPod) and if something happens to them i might be in serious trouble.
so now my question: is it possible to rescue this AES-secured spareseimage or is this kind of methos unsafe for important data?
thanks
klaus

Regular tools like Disk Utility and DiskWarrior
didn't solve anything. I was wondering if it is
possible to rescue some files by manually decrypting
the image with some low-level tool.
Did you have any succes? Given all reports on the
web, it seems a bit hopeless, but I like to give it a
chance.
no success at all, sorry.
i dumped the images now and also went back to some backups.
but i definitly don't use filevault anymore
cu

Similar Messages

  • Cannot load 3.6 - disk image failed to mount - reason: corrupt image

    Tried to load 3.6 and get the msg: disk image failed to mount. Reason: corrupt image.
    == This happened ==
    Every time Firefox opened

    *Firefox 4 versions and later do not run on a PowerPC Mac.
    *Firefox 4 and later require at least OS X 10.5 and an Intel Mac.
    * http://www.mozilla.com/firefox/6.0/system-requirements/
    For an unofficial Firefox 4 compatible version (TenFourFox) that runs on PowerPC Macs with OS X 10.4.11 or OS X 10.5.8 you can look at:
    * http://www.floodgap.com/software/tenfourfox/
    * http://tenfourfox.blogspot.com/2011/08/601-now-available.html
    Firefox 3.6.x (Mac OS X 10.4 and later) can be found here:
    * http://www.mozilla.com/en-US/firefox/all-older.html

  • I am trying to download Firefox 3.6 to use on my Mac OS X version 10.3.9. Three attempts and I continue to get "mounting failed" and "corrupt image". Help please?

    I am trying to download Firefox 3.6 to use on my Mac OS X version 10.3.9. Three attempts and I continue to get "mounting failed" and "corrupt image". Help please?

    Firefox 3.6 requires at least OS X 10.4, the last version of Firefox that worked on OS X 10.3.9 was Firefox 2.0.0.20 which is available from ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.20/mac/

  • When I attempt to download Firefox 3.5.10 I get a warning stating "disk image failed to mount - corrupt image", what can I do?

    I am attempting to download "Firefox 3.5.10", each attempt the results state "The disk image failed to mount due to corrupt image". I really need this browser for my on-line learning. Please help! By the way 2.0 downloaded fine, but is not compatible with the University web site.
    == This happened ==
    Every time Firefox opened
    == Every time I attempted to download Firefox 3.5.10

    Ran into this problem this afternoon. Had to download after the latest version failed to start after progressively becoming a bit tweeky. Got the failed to mount message also broken pipe, even though I am running 10.4.
    I went into Mac OS Updates and downloaded the latest version of Java Script. After restart I was able to mount the new Firefox and it seems to be working now.

  • Checking for corrupt image or element

    Hi
    Hoping someone may be able to help, I have a 256 page book which I created in InDesign CS3, the book is made up of several documents.
    I need to export to a PDF, each time I try it fails as there is a corrupt image. Is there anyway I check the documents for corrupt elements before I create the PDF?
    Any help appreciated.

    You need to "Divide and Conquer." It's not unusual to have a failure exporting to PDF with low disk space, but that might not be your problem. In either case the first step is the same. Divide the document in half during the export process and see if each half will export separately.
    If you can export both halves, you may need to live with that and simply recombine them in Acrobat. I don't recall any definitive answers for what to do fix this. Deleting temporary files may help.
    If you still get a failure, divide that section in half and try again (see below). If both sections fail, it could be either a bad font or more than one bad image.
    Make a copy of the document and change all the fonts to something simple and reliable, like Times New Roman, and see if that works. If it does, make a new copy of the original and eliminate fonts one by one, starting with cheap or freebie fonts from the web, and test after each replacement.
    If only one section failed it's more likely an image, and you should be able to isolate the page by continuing to divide the section that fails. Once you know which page, make a copy, and remove images one by one, starting with .eps if there are any.
    If you find a bad image, try resaving it and replacing with a native .ai or .psd.
    Peter

  • QuarkXpress 8 won't start up and the filesystem verify failed

    HELP Quark won't start - Exception Type: EXCBADACCESS (SIGBUS)
    Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000004
    Then the filesystem verify failed -
    Verifying volume “Macintosh HD”
    Performing live verification.
    Checking Journaled HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking volume bitmap.
    Checking volume information.
    Invalid volume file count_
    (It should be 464046 instead of 464060)
    Invalid volume directory count_
    (It should be 118092 instead of 118078)
    The volume Macintosh HD needs to be repaired.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking volume bitmap.
    Checking volume information.
    Invalid volume file count_
    (It should be 464046 instead of 464060)
    Invalid volume directory count_
    (It should be 118092 instead of 118078)
    Error: Filesystem verify or repair failed.

    Safe boot runs fsck as part of the process, which is one of the reasons it takes a little longer. The Unix fsck routine is essentially the disk repair routine that Disk Utility runs and if it fixed the disc directory errors, then good.
    Is Quark crashing on open or are you getting a kernel panic? It looks like you have some excerpts from the crash log in your original post, so I am guessing crash on open. There may be a damaged file in the Quark world or more likely a corrupt cache file somewhere.
    You might look in /Users/yourshort_username/Library/Caches to see if there is a Quark cache folder and just trash it and try again for a start.
    If that doesn't work, then you might try Applejack at http://sourceforge.net/projects/applejack/ and let it clean out things a little more thoroughly.

  • %CRYPTO-4-RECVD_PKT_MAC_ERR: decrypt mac verify failed

    Hello,
    I know this question has been asked many times on the forum, I am constantly getting the below error message on my 2811 Router:
    *Aug  9 07:07:01.507: %CRYPTO-4-RECVD_PKT_MAC_ERR: decrypt: mac verify failed for connection id=3004 local=3.3.3.1 remote=3.3.3.2 spi=CDE6EACF seqno=00005214
    N.R-HQ#        
    *Aug  9 07:08:33.231: %CRYPTO-4-RECVD_PKT_MAC_ERR: decrypt: mac verify failed for connection id=3004 local=3.3.3.1 remote=3.3.3.2 spi=CDE6EACF seqno=000056E4
    I did some research and found the IOS is in the KAV list of bug#CSCsv43145. I upgraded the IOS to 12.4(25e) which doesn't appear in the list but still same error occurs.
    -is the error just cosmetic
    -is there anyway to go around it?
    I have attached the config.
    10x,
    E.B:.

    Hi,
    12.4(25e) should not be affected by CSCsv43145, which is cosmetic. The issue you are seeing is likely not cosmetic, and is actually resulting in dropped packets due to mac authentication failures. To troubleshoot this type of issue, you really need to get sniffer traces on the WAN (encrypted) side from both tunnel end points and compare the packet in question (based on the spi/seq number reported in the log) and see if the packet is corrupted somehow. There is no easy way to get around this other than turning off authentication check in your ipsec transform, in which case no mac authentication will be performed on the packet, and you do need to consider the security implications when doing that.
    Hope this helps,
    Thanks,
    Wen

  • Hdiutil: create failed - error -5341

    Hi,
        I have this error on 2 Macosx Mavericks machines:
       hdiutil: create failed - error -5341
    This happens when I create an image larger than 100MB. Here the srcfolder is 120MB:
    $ hdiutil create  -srcfolder myapp.app myapp.dmg
    hdiutil: create failed - error -5341
    The solution is to specify the size on the command line
    valodm:~ jedi$ hdiutil create -size 130m  -srcfolder myapp.app myapp.dmg
    created: myapp.dmg
       This is disturbing because this bug breaks the munkiimport tool. When trying to import the folder in Munki, I can't specify the size of the sourcefolder, so the tool fails with the error above. The workaround is to create the dmg with the command line, and then import the dmg.
        I didn't have this problem on Mountain Lion.

    Maybe size does matter?
    I once had a similar (maybe the same) error a while ago when I was creating disk images as backups of folders using Disk Utility. I eventually split the source folder into two folders and Disk Image was able to create the dmg file properly.
    Fast forward. I use hdiutil to do the same task now in a more automated way from a bash script. I just ran the script on 25 folders. 23 of them were archived into dmg files as expected. Two failed with the -5341 error.
    I edited one of the files in one of the folders slightly, reducing the file size by about 3%, ran the script again and it worked properly.
    I modified a file in the other folder that hdiutil failed on the first time and, again, it worked.
    There is no .Trash in either folder.
    Neither folder was anywhere near 520 mb. They were different sizes (~130 mb and ~260 mb).
    Conclusion: either there was something in those files, or on the area of the SSD that those files were sitting on, that was giving hdiutil a problem, or there is something with various sizes of dmg files that brings out a bug in hdituil.

  • Attempting to upgrade to Firefox 3.6 (using an ancient Mac OS 10.3), but received an error message (corrupt image file) when downloading - any way to correct this with my current OS?

    I'm currently trying to update a few programs on my good old (VERY old) Mac Powerbook, but I ran into an error when downloading Firefox version 3.6...I'm currently running Mac OS X 10.3.9, which isn't compatible with the most recent versions of Firefox (or anything, for that matter), but it should still allow an upgrade of version 3.6; however, once the file finished downloading, an error message popped up indicating there's a corrupt image file. Is there any way to work around/correct this problem, or am I stuck with my old version of Firefox until I bite the bullet and upgrade my OS??? Any help is greatly appreciated!!

    Firefox 3.6 requires at least OS X 10.4, the last version of Firefox that runs on OS X 10.3.9 is Firefox 2.0.0.20 available from https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.20/mac/en-US/

  • Error message: CONNECTION FAILURE. DOWNLOADING FAILED. IMAGE CANNOT BE LOADED. PLEASE TRY AGA

    I recently purchased Photoshop Touch for use on my Samsung Galaxy Note 10.1. I have uploaded files to Creative Cloud from CS5 version of Photoshop. I can view the file thumbnails on my tablet, but when I go to open them, I get the following error every time:
    CONNECTION FAILURE. DOWNLOADING FAILED. IMAGE CANNOT BE LOADED. PLEASE TRY AGAIN.
    Any ideas on what I can do to resolve this issue would be greatly appreciated. I am ready to pull my hair out!! Thanks

    What kind of file type are you trying to open? - Guido

  • Corrupted Images in Pages, now unable to open file

    Pages 2.0.1 has lost the ability to open any pages documents with images on my computer. Some image files are corrupted, but other documents with no corrupted images still will not open and crash Pages if I try. Also, the Dock changed unexpectedly after the first crash, removing my Final Cut Pro icon and restoring the iLife icons. Any suggestions?

    Hello Sahu,
    I too had a very similiar experience with one of my clients. There is nothing to do with missing authorizations.
    Ask him/her to set the resolution of their display to 1024 by 768 pixels. This is because some high display resolutions are not supported by SAP Front end. Believe me, I was amazed to discover that something like this exits.
    Have a nice weekend...............
    Shashi kanth

  • Corrupted images captured by new 5D Mark III

    Hi,
    I got two corrupted images while shooting with my new 5D Mark III..I was using 45mbps sandisk extreme SD card and the mode was only JPEG(fine). After getting two corrupted images I shoot 1k images but no problem there after..Later I copied those images in my HDD except two corrupted images all are looked nice.. My y question is what was the actual problem?Thank you in advance..
    Solved!
    Go to Solution.

    I'd advise at least doing a quick in-camera format each time you insert a memory card (or right after downloading, if you use the USB cable to transfer your images).
    The in-camera format preps the memory card for use, configuring it with some needed file structures and writing over old files.
    If you ever format in computer, always re-format it in your camera before shooting. It's possible that the computer won't configure the card in a way that will work properly in the camera.
    Usually corrupt images are due to card issue or connectivity when downloading. If you are seeing the corruption in the camera, then I'd first suspect the card (either it's faulty, or it's configured incorrectly, or something on there is causing a conflict).
    I once corrupted a number of images on a Compact Flash by opening the memory card door and pulling the card out too quickly, while the last image or two were still being written. It corrupted about 1/3 of the images on the card, not just the last one taken. Initially all the images on the card were unreadable, until I ran a recovery program. That was able to repair about 2/3 of the images... roughly 200 out of 300 images, if I recall correctly.  
    The worst corruption issue I've had (in ten years shooting digital almost exclusively, nearly 20 years shooting some digital), was due to connectivity issues. I had a card reader connected to a USB hub. Took it off the hub and connected it directly to the computer's USB port and the problem was solved.
    It's possible, but pretty rare that the camera itself causes occasional corrupt files. Usually if the camera starts throwing off corrupted files, it's most or all images... not just an occasional one. I'd keep an eye on it and if it continues happening, try a different memory card first. If it continues to happen with a different card, have the camera looked at.
    Alan Myers
    San Jose, Calif., USA
    "Walk softly and carry a big lens."
    GEAR: 5DII, 7D(x2), 50D(x3), some other cameras, various lenses & accessories
    FLICKR & PRINTROOM 

  • Any new fixes for corrupt images in Lightroom 4.4?

    I have seen many threads on this and tried a lot of the tings people say to try. But I do get corrupt images in Lightroom. I currently have an AMD FX-8150, 32GB ram, 2 SSD Raid0 + USB3.0 drives as backup.
    Drive and Memory:
    Note, I only keep up to the last 3 shoots on my SSD, the rest are stored on my USB3 drives. Any time I import files to the USB drive I get no corruption. Now that would imply that I have bad drives, I have run diskcheck and contacted Muskin and they had me run some disk checks, speed tests, +other things and identified that the drives are running fine with no issues and this has to be a software issue.
    I have run memtest86+ with no errors, also ran memtest86+ with my memory in another machine with no errors.
    To rule out the card reader:
    When I just copy files from my CF Card to a folder using explorer all images import fine and you can even open every image in photoshop with no issues. As soon as you add those files already copied to the HD to lightroom, they start to corrupt. I just recently used the windows explorer method and added ~400 images to lightroom, all images imported fine, when I later accessed lightroom(Today), about 10% of those images are not corrupt.
    Does anyone have any suggestions? Could it be because I use Raid0? Or even SSD drives?
    This is quite annoying and I would like to get things fixed.

    jproductions111 wrote:
    Usually when Lr renames the photos as you saw kianjillwedding-19, Lr changed the name from IMG_1968. Thats may have something to do with the corruption.
    I don't see how. Renaming shouldn't change anything on disk except, well, the name - and of course update a bunch of things in the catalog.
    jproductions111 wrote:
    I will get back to you if the problem continues but everything still seems to be fine in Lr5, even after letting Lr rename all the photos with my current(today's) import of 700 images.
    OK - thanks.
    jproductions111 wrote:
    I know you don't believe its software
    ~impossible it's Lr4 software. Theoretically possible, but highly unlikely. As I said, Lr4 should never be rewriting those files, and therefore essentially can not corrupt them. I mean, its possible that it got it's brains scrambled, and went ahead and rewrote them, for god-knows why or just for the he|| of it - because some bits seemed to be set wrong..., thus invalidating the assumption that it's not rewriting them. It's just that this scenario is the least likely. I mean, Jeff Schewe has given me spankings more than once before, for even bringing it up, since it's so unlikely...
    jproductions111 wrote:
    maybe Lr 4 was causing some sort of bug to make the hardware malfunction
    Although theoretically possible, I'd still venture to guess that's not what happened.
    jproductions111 wrote:
    this is not happening to my in Lr5.
    Didn't you also change your disk drive situation around just before you started using Lr5?
    jproductions111 wrote:
    But I am keeping my fingers crossed.
    Me too - please keep us posted...
    R

  • I downloaded Montain Lion several times. I could not install. It said `could not be verified or corrupted'. How to solve this? Can I get a refund?

    I downloaded Montain Lion several times. I could not install. It said `could not be verified or corrupted'. How to solve this? Can I get a refund?

    On your profile, you say that you are using Mountain Lion. Is that correct? If you are using Mountain Lion, you don't have to download the Mountain Lion installer again.
    Also, that error is usually caused by problems with your Internet connection or your hard disk, so first, open Disk Utility, select Macintosh HD in the sidebar and verify the disk. If it's OK, you have problems with your Internet connection, so contact with your ISP

  • The message: corrupt image showed so that I can't upgrade the new version. how can I fix it?

    when I try to upgrade Firegfox in my iBook G4 with Mac OS X . The message always came out: corrupt image.

    Which version of OS X? <br />
    Firefox 2.0.0.20 is the last ever release for Mac OS X 10.3.9 and earlier versions. Get it here:
    https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/2.0.0.20/mac/en-US/

Maybe you are looking for