Non-destructive editing? Yeah, totally.

Editing a photo in Lightroom, and all of a sudden, THIS happened to it.

HTTP response: NOT FOUND | MIME changed to 'image/png'

who cares! Just leave it and call it your "new style!"

Andrushka wrote in post #7872309
who cares! Just leave it and call it your "new style!"

In the split-seconds before I realized what it was (or what I thought it was) the first thought in my head was "looks kinda like a Warhol..."

Clear the cache, check the file in DPP. If it's corrupt there's something seriously wrong with your hardware IMHO.

You weren't editing off the flash card were you? That would eliminate that piece.

You said it happened while you were editing the image?

Might be a corrupt Raw file, with okay embedded jpg. In that case the image would look okay, until LR reads the Raw data and displays the image based on that...

As Tim said, check the file in different software.
If it's corrupt there as well, check the original (copy again from the CF card) or backup of the image. If all are corrupt, try a different card / card reader.

If that doesn't help, it might be your HDD or something else...

René Damkot wrote in post #7875143
Might be a corrupt Raw file, with okay embedded jpg. In that case the image would look okay, until LR reads the Raw data and displays the image based on that...

As Tim said, check the file in different software.
If it's corrupt there as well, check the original (copy again from the CF card) or backup of the image. If all are corrupt, try a different card / card reader.

If that doesn't help, it might be your HDD or something else...

Yes it could be many things but usually related to something like memory/bad hd (main or swap)/cf card. You have to see if it is a one off thing or always happens in some pattern like when a file gets to be a certain size or first goes to swap.

I had small corruptions (which are worse as they sometimes slip your notice) happen but only when I saved the file after it got to be a certain size. It was bad memory in an iRAM drive that was a swap drive. It was strange as even though the swap file was what was bad it did not merge to the main file until a save. This was easy to figure out as it happened in some pattern that I noticed but it could easily be a tricky thing to figure out. Hopefuly it is just a bad cf card since that will be easy to trace.

Thanks for all of the suggestions.

Sadly, I have absolutely no way to check that it is a CF card, as the image was from three months ago (not really a high priority).

Opening a copy of the image in CS2 yields ACR to open the corrupted or otherwise "pinkified" image, and then revert to the original image in a couple seconds.

Is it possible that only the preview is corrupted and not the RAW data itself?

So you're seeing the corrupted version *first* and a good version later? Does it export okay? In that case I'd say the embedded preview is corrupt. Lucky you

I would find some way to test your CF cards.

René Damkot wrote in post #7877163
So you're seeing the corrupted version *first* and a good version later? Does it export okay? In that case I'd say the embedded preview is corrupt. Lucky you

Amen to that!

I backup images on a RAID1 system, and I'm still saving for that external backup drive! I booted each drive individually, and pulled the image off of the second drive. Image turned out to be still intact, so I simply rebuilt the array using the second drive.

Doesn't inspire much confidence about the RAID system though

I doubt it was the memory cards, since this appeared in the middle of an editing session and not directly after an import.

I really wish I could get that backup drive ASAP...

You can afford a raid setup but not an external backup?

If a drive has corrupted i'd replace it. It's not worth the risk.

tim wrote in post #7878424
You can afford a raid setup but not an external backup?

If a drive has corrupted i'd replace it. It's not worth the risk.

Well it's software RAID on the motherboard, and I won the hard drives in a contest, so excuse me for not shelling out extra cash for an external drive immediately.

If I buy another drive in the near future it would be to replace the one that apparently (allegedly) had the issue, and move that drive to an external backup capacity.

But of course, cash is tight

You'd put your backups on a drive that's strongly suspected to be faulty? I think you need to think a little more about this. Having faulty backups is probably worse than having no backups, as they'll give you a false sense of security.

If a drive's new and faulty the manufacturer will usually replace it. Testing it will be the hard part.

tim wrote in post #7878684
You'd put your backups on a drive that's strongly suspected to be faulty? I think you need to think a little more about this. Having faulty backups is probably worse than having no backups, as they'll give you a false sense of security.

If a drive's new and faulty the manufacturer will usually replace it. Testing it will be the hard part.

Old, sadly.

The "strongly suspected to be faulty" phrase comes from one photo which was corrupt, which may or may not be the cause of the hard drive. I would suspect the motherboard more than anything, considering some of the previous issues I've had with it...

If I were to get one (and only one) replacement hard drive, then yes, I would use the so-called "faulty" one as an external backup. On the two drives that mirror each-other, I would prefer to have absolutely no issues. The external one, which may or may not be a drive that has "issues," would be a secondary backup solution, and so it's not quite as high of a priority.

Besides, I would much rather have a backup of 99.9% of my images than no backup at all. False security be damned. It's not a thought issue, it's a cash issue. The latter of which I have very little at the moment.

Running tests now, regardless...