[popo]

Before you start looking for another backup-strategy, I think it's better to examine why only 36 pictures (so far) got that loading error. I would consider a bad SD card first. If you discover it, trash it. Otherwise it's only a question of time before you loose important pics.

As mentioned earlier, the copy on my backup server was fine and I've done a manual restore of them. It was only the files on my live copy that were corrupt in this weird way. So the problem is either on a hard disk, or on file move, or some other filesystem corruption.

Since the files were originally copied to the hard disk, they have been moved to a different hard disk in my new system. I don't think there is any realistic way for me to tell if it got corrupted on the original hard disk, during the transfer to new hard disk, or since that transfer.

As a precautionary measure, I'm in the process of doing a full surface scan of the 6TB disk. Started it last night. Been running 8 hours with an estimated 2 hours to go...

Maybe when Skylake Xeons come out I'll switch to that with ECC ram, and perhaps create a mirrored ZFS local file store connected over 10G ethernet. Why can't I have lower cost interests?

I guess I am pushing things a bit being an early adopter of Skylake. When I built my current system, there was a bios update. Ok, applied no problem. It has been perhaps 6 weeks since then, and the manufacturer has released 4 more bios updates, two of which simply say "improve system stability" in the description. Scary... I put that on last night too. I've had occasional weird non-boots previously but if it boots it remains up fine (usually left on with CPU intensive processes in background).