Corrupt Files? (OS X)

[galexkeene]

This isn't strictly a Lightroom issue but was hoping someone could help me. I had my photos (all .CR2s) being backed up by Time Machine and then had my computer fail on an OS X Java update and I had to restore from my backups.

Ever since, Lightroom has worked great, but Time Machine hasn't been able to backup my Pictures folder. It works fine on everything else, but not the Pictures. I tried doing some manual backups of the pictures, and that failed. Even trying to back up day by day (folder by folder), it seems some photos are corrupt in some way that they can't be copied and it usually crashes/hangs Finder to even try. Even just trying to browse to that photo in Finder with the Preview option turned on seems to hang Finder.

The weirdest thing here, is the files are still browsable just fine with no errors at all in Lightroom. Is this because I'm really just seeing the preview stored in Lightroom's DB? Any way to restore these files?

Thanks for any help I can get here!

 

[sizzlingbadger]

You could check the file permissions and also run the disk utility and check the disk.

 

[galexkeene]

I used the disk utility and had no luck. I can't imagine random files having permission errors, but I will check. I mean, I can't even get the preview thumbnail, somethings clearly more fundamentally wrong

 

[sizzlingbadger]

Use finder to copy a single image from the pictures folder to the desktop and let me know what happens. See if you can open the image in preview. You should still have a TM backup of the Pictures folder from before the Java update. If that is the case then we should be able to rename the picture folder to pic_temp for example and then use TM to restore the folder from a backup that was taken earlier than the Java update date.

It is highly unlikely that the failed Java install or the TM restore has corrupted the images. Just a note for the future there was possibly a better way to re-install the failed Java update rather than returning to a backup. It could be possible that there is something corrupted in the files system already which could have also caused the Java update to fail in the first place.