The File Appears to be Unsupported or Damaged - Ideas

[carolyn plant nerd in PDX]

I know this topic has been posted before but the only answers i see is 1, move the file to another place and  back or 2,  restart Lightroom CLassic and see if that works. Both of these have worked sometime; however, the first is time consuming and the second is a hassle ofter the first or second time.

The biggest issue is it appears to happen after I have touched the folder, doing a edit or simpy staring for later review. The catch, sometimes they are avaialble and sometimes they are not.

Process: 1, import to drive (NAS Raid 5 over 10Gbe network), cull and name using Photo Mechanic, import to LrC. Review files and issues happen. This NAS is copied to another nas in Raid 5. Not everythign mind you and very inconsistent. The interesteing thin is I can go to the files on the drive and open in Preview with no issues.

Anyone else seeing this kind of problem

[GoldingD]

Please clarify.

• Your working catalog is located where? Hopefully not on the NAS.
• Your photos imported into your catalog, are located on a NAS?
• What LrC version, v12.1? A actual number please, not words like latest.
• I see you are on a MAC, what MACOS?

[carolyn plant nerd in PDX]

Working Catalog on Mac hard drive, Image files on NAS, Catalog references files on NAS, Lightroom Classic 12.1, Ventura 13.0.1

[dj_paige]

The File Appears to be Unsupported or Damaged

This file cannot be used. Restore a copy of the file from your backups or from the camera card.

I don't know where you read to move it and then move it back, but moving a damaged file does not cause the damage to be removed.

[carolyn plant nerd in PDX]

dj_paige, i have done this step as well. My concern is that ths is a moving problem. I have a folder wiht 4 images in it, none are edited. One was coming up unsupported or damaged. I closed that work and did somethign else in lightroom for a few minutes and came back to that same folder. Now, a different image was giving me the upsupported message and the original was fully avaialble.

Since last night, I have pulled the NAS off the network and I have moved the NAS/RAID 5 to a DAS connection with Thunderbolt. I wanted to see if there was some issue happenign over the network. Will updat eif this cleans up. I use a QNAP TS-453BT3

[TheDigitalDog]

I've very rarely seen this error, but indeed, when I checked, it was a damaged document. So first off, you need to do as suggested, find a backup, and replace it. If this continues, you've got some drive issue that needs fixing ASAP and you need to make sure you're no longer backing up damaged documents in such a case. Your last attempt (pulling NAS and moving) is a really good idea! You can try using Apple's Disk Utility to examine and maybe fix the drives but it's not the best tool for this (but free and better than nothing). 

[dj_paige]

Damaged file, almost certainly because of a hardware malfunction. You need to perform diagnostics on the disk (whichever on the photos are on) and test the computer's memory as well. If sometimes a file is damaged and later its not apparently damaged, the primary suspect would be the computer's memory.

[carolyn plant nerd in PDX]

Thank you both. I felt like I was going crazy becasue I wasn't seeing others wiht this issue.. I will do some work on my end and see where things land.  Cheers.