Honestly… this seems familiar. But I never could reproduce it, and it never happened again. The snapshots before and after were completely intact, but one snapshot in particular had just a handful of CRC mismatches.
Mine was backing up an external SSD to the cloud… but I had also used rhash to embed CRC codes in the filename for occasional “scrubbing” purposes. That’s how I caught it.
Question. Have you done another snapshot after this? Do those files appear OK? What about the snapshot before the corrupted one, if there is one?
Just curious if we’ve ran into the same bug, or if this is unrelated… I could never prove or disprove whether it was my hardware or Restic, but I have yet to ever have this issue again, and I’m still using the same drive which has zero issues according to the SMART data. The original files on the drive check out, as do the snapshots immediately before, and after. It’s just that one snapshot with randomly corrupt data. I should add I don’t get any ciphertext errors, however. So maybe it’s unrelated. But this will forever be my white whale until I figure out what in the world happened haha