I believe LR 5 has corrupted all Raw/Jpeg images tied to the catalogue

  • 1
  • Problem
  • Updated 5 years ago
Was working on photo editing one day, and the next day I can't open any JPEG or CR2 (RAW files) on any of my drives, when they start with my cameras default naming prefix(s)...

Pretty sure it's not a drive issue - it's happened on my C: (SSD), my P: (SATA2) and even on my NAS.
I was worried that it was a Virus or something, but I did a complete scan, and it would be strange that it would affect JPEG and RAW, and only files of a certain name rather than extension...

For example, I have a file for photos of my daughter.
All of the images with the camera's default numbering have corrupted, and all of the one's I've bothered to rename are fine.
EG:
5P0H0096.jpg - not working
7 October 2013.jpg - completely fine.

This SAME issue has happened to the exact same folder that I backed up on my NAS.
Oh, and it's happened to ALL my photos - about 1.5tb worth...

I have used every version of Lightroom since Version 1, and at this stage (on closer inspection since I OP'd) it seems as though only the files that have interacted with Lightroom 5 are affected. All of my much older files (same camera) that I used Lightroom 1-4 with exclusively are able to be opened.
This includes very old images that I recently opened up with Version 5 to reprint for a client.

To make matters even more strange, I have a number of plugins within Lightroom which open files in 3rd Party editing (Photoshop being an example). When it does this, it creates a virtual clone of the image which it renames *-edit.jpg upon export.
For example: 5P0H0096-edit.jpg
These files are fine and able to be opened as per normal.

I WAS THINKING;
What I'm thinking now is that the Catalogue file has in someway been corrupted, and maybe stripped the header info from all the files that it 'knew' of? (this would be where metadata is stored yeah?)
My limited understanding is that this is what tells windows that a picture is in fact a picture? So if that were the case then the file would remain relatively intact, but be unable to be opened by any program?
Photo of Steve Tanti

Steve Tanti

  • 2 Posts
  • 0 Reply Likes

Posted 5 years ago

  • 1
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4533 Posts
  • 1719 Reply Likes
So what's telling you that these files are corrupted? Is it just in Lightroom (in Library or Develop or both?) or in other programs too?
Photo of Steve Tanti

Steve Tanti

  • 2 Posts
  • 0 Reply Likes
Hi Victoria,
Lightroom has an error message saying the file cannot be opened, and I can't open it in any other programs - including Windows Picture Viewer, etc.
The message in those programs is 'can't open because file is invalid, too big or corrupted.'

In Lightroom, I can only see the rendered previews. Can't edit or export.

I've even looked at recovery software specifically made to repair corrupt jpeg/raw files - it won't detect the files as being images at all.
This is another thing that made me think the header info within the file has been affected.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4533 Posts
  • 1719 Reply Likes
Do you write settings to xmp, either manually or via 'automatically write to xmp' in preferences? And even then, proprietary raw files wouldn't be affected as they're written to sidecar files. Everything else Lightroom does only reads the files, not writes to them.

I'd still be suspecting hardware - have you tested your RAM using something like MemTest?

Can you upload a working and not-working file somewhere so we can take a look please? We should just double check that they're definitely corrupted, and not just an issue reading on your machine.