Corrupted images in Trash that duplicate good images

I have about 12000 images in a managed database (3.5.1). I had not paid attention to the Aperture Trash for quite a while, but now noted a large number of entries (1200). Some are truly images I rejected, but some images display as various dots or streaks of colors. The image information (filename, date, project) in the Trash for the ones I sampled leads me to a perfectly good image in the stated project. These Aperture Trash entries would appear to be due to some hiccup within Aperture. As a test I tried to edit one of the entries using Photoshop Elements. The message stated that the image file could not be found. I did all of the steps in the Aperture first aid menu (permissions, repair and rebuild) without any effect.
My concern is how to verify that no good images somehow are now only in the Aperture Trash. Bouncing back and forth from the Trash to the projects is too time consuming. I am thinking of simply being able to list the trash entries by filename somehow separately and then using the search tools to display the good photos within Aperture for comparison.
My recollection is that emptying Aperture Trash will put the files into my user trash. If so, I could easily sort them in Finder and display using QuickView.
What is the best way of dealing with this?

Fixed it. Did what I described above with a bit of a twist. Updated a vault on an external drive. Then changed the extension from .apvault to .aplibrary. Opened it and deleted Aperture Trash. This way the removed items will appear in my user Trash, but only while the volume is connected. Just a safety measure. Thankfully and surprisingly, the trashed images were all good images. I then listed the images in the Finder and used the necessary search criteria in my library to verify their inclusion. Then emptied the real library's Trash and then emptied my user Trash while the volume was mounted.
Bottom line this was a waste of time since nothing was removed from my good library. But had to verify. I don't recall any issues with Aperture, so this is a really strange quirk. A large number of the items were random ones recently added. I have been scanning old films to a folder and then dragging groups of newly scanned images directly into a project. And not doing anything to the images.
All is well that ends well

Similar Messages

How to trash a "corrupt image" ?

On the desktop there's a sparse disk image that I can't trash.
Double click on it and I and get a message: "Warning The following disk images couldn't be opened Image [name] Reason -- corrupt image"
Thanks . . . fortes

No problem dragging it to Trash, but Finder > Secure Empty Trash won't work. Same with the Option key depressed, clicking on the trash icon in the Dock and choosing Empty Trash.

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/

Frustration - Iphoto corrupting image files during import (?)

To begin with, I'm a recent convert from Windows to the Mac. I'm running a mac mini at home, and a Macbook with Boot Camp at work (in addition to my desktop pc). All of my software is up to date...
I take alot of pictures with my digital camera (canon powershot). Saturday I took about 300 pictures, took the SD card out of the camera, put it into my Sandisk card reader, imported the pictures into iphoto and everything worked great. I chose to not delete the pictures after the import as I wanted to bring the card into work and upload the pictures on my pc.
The next day (Sunday) I took another 70 or so pictures. I was able to view all of the pictures on my camera that I had taken over the past two days.
I go to do an import , taking the exact same procedures that I took on Saturday (and that I always do). The first thing it does is identifies that there are duplicate pictures. I choose the option of "don't import duplicates" and apply this to all of the other duplicate pictures.
At the end of the import, I got an error message saying that some of the files were corrupt. Now, there were pictures from Saturday that were still on there (and readable/viewable). However, every picture that I took on Sunday was "unreadable" and did not show up in iphoto. I put the card back into the camera, and now I can't view the pictures (they show as "corrupted data".
I then pulled the SD card details up in Finder, and the "corrupt" files still show sizes of 2.4mb to 2.8mb, consistant with the good pictures. It shows the file's "Kind" as JPG Image... I double clicked on them and Preview comes up saying something to the extent that the file is corrupt,
I've taken the Sandisk card reader, plugged it into my Macbook (using iphoto in osx) and was able to view one or two of the pictures from Sunday.
Once I got to work this morning, I plugged the sd card into my Windows machine and it too says the files are corrupt. It shows them being on the card, it shows the file sizes, but I can't open the pictures in anything...
If this was a one time deal, I'd be thinking it may be something I've done to cause the problem. However, this is the third instance I've "lost" all of my photos because of them becoming corrupt during an import into iphoto. There definately appears to be a pattern.
I have somewhere around 8,000 pictures inside iphoto that I've taken and had no problems with. I mention this to illustrate that I'm not doing anything differently than I've done before. I have another 14,000 on my old Dell that I need to move over, but I'm questioning if I should do that now.
Does anyone have any ideas on what the problem might be? Is anyone else experiencing (present or past tense) this problem? Where I'm new to the mac, I understand that I might be doing something wrong. However, I've imported photos to the software (what seems like) hundreds of times, the same way each time. This makes me want to rule out user error...
One other question, I'm saving the "corrupt files" with the hope that there's a software program which will "fix" the files. Do you happen to know of such a piece of software? I'm hoping that I can get them fixed at some point.
Where I'm taking pictures of my kids, its extremely frustrating to find out that the pictures (memories) I was hoping to make prints of are now "gone". Its almost like rolling the dice when doing a photo import any more. Most all of the time it takes, but every now and then the pics are lost...
I'm hoping to identify the problem (either user error, procedure or software issue) and fix it as I really like the mac.
Any help/suggestions you might have for me would greatly be appreciated!
Mac Mini Mac OS X (10.4.10) Also running Macbook 10.4.10

The Chainsaw
Welcome to the Apple Discussions.
First: the corrupt files: download Graphic Coverter, a shareware which is often successful where other software isn't. But first, if the Mac will let you, copy the files off the card to the Mac.
I'm in this board a while now, and I can't recall an issue of iPhoto corrupting images on import. After all, it's just a simple file copy, at heart. I would be more inclined to suspect the card. DO you have more than one? Does the problem also occur with the other cards?
Try use Image Capture to download the pics to the Mac first, then import them, see does that help. Image Capture is in your Applications folder.
Regards
TD

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/

Corrupted image files in Lightroom?

I opened up Lightroom this morning and noticed that some of my files from a recent shoot look like this:
Are they corrupted?
If so, how does that happen? I've never seen this before and I have thousands of images in LR.

Thanks. I read through a few of the other threads. I found one comment that might be applicable to my situation:
Good - most often this tell-tale/signature-looking corruption is due to hardware - transfer hardware if corrupt upon first rendering (true raw rendering, not initial preview display), hard disk if corrupt after first rendering. And sometimes ram.
I think this may have had something to do with how I got these files onto my computer. I shot the pictures while visiting family. I had my Macbook Pro with me, which is not my main image editing machine. I imported the files into LR4 on the MPB from the 5D3 using the USB cable.
When I returned home, I moved the files from their location on the MBP to a USB flash drive, and then imported them from the flash drive to LR4 on my Mac Pro (which is my main image editing machine).
The corrupted images are only from this group. So I'm hoping that it was the transfer to and from the flash drive that caused this, especially since I've never experienced it before and don't see it in any of my other images.
Fingers crossed!

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

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

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

Corrupt Images after syncing Photos

Has anyone experienced corrupt images after performing a sync?
After activation and at some point during my first sync my machine blue screened. After a reboot it appears that everything is running smooth, however, I notice that most of the pictures that are synched are corrupted and many didn't synch at all.
I removed all synch images and re-synched but I'm still experiencing the same problem.
I'm hoping its an issue with Vista or iTunes and not my phone. Looks like I'm going to have to go out and get that Mac Book Pro after all

Are you saying that the photos are appearing in the wrong albums, or that the photos are in their correct albums but are displayed in the different order within them ? If they are in the wrong albums then try deleting the photo cache from your computer and re-try the sync - the location of the cache, and how to delete it, is on this page http://support.apple.com/kb/TS1314
If the photos are displayed in the wrong order in the albums, then they will be displayed by capture date order unless you are syncing via iPhoto or Aperture on a Mac. To get them in a different order you will need to manipulate their capture dates : http://support.apple.com/kb/HT4221

Corrupt image

What does corrupt image mean on download

If you downloaded an installer file, then it means that the download file is corrupted. Download it again.
If you need more help, please provide your operating system details.

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

CS3 corrupting images

I am using CS3 in OS X 10.5. All of a sudden my photos are getting corrupted. I can see an image in Bridge, but when I click on it the image becomes completely distorted. It becomes colorful horizontal lines. I tried removing CS3 and re-installing it, and the corrupted images looked ok after this, but again when I clicked on them, they would get distorted again. I have no idea what's causing this, but I'm hoping someone can tell me, so I know how to fix it and avoid it in the future.
Thank you!
Tom

Thanks for the reply Chris! That was one of my guesses. I ran disk repair on the drive and it didn't come up with any errors, is there a test for the RAM? I've called Apple before with photoshop issues and they've said they can't really help with 3rd party apps, but this is a fairly new iMac. I will be sure apple care is extended for it and work with them. In the meantime, I deleted all the files that seemed to be having issues and will watch to see if any others have problems, but it seems to be limited to one folder so far.
Thanks,
Tom

Corrupted images in Trash that duplicate good images

Similar Messages

Maybe you are looking for