Inconsistent --test outputs across multiple runs

[Funtimes909]

I have been dealing with some music library corruption the past few days, and noticed that while replacing corrupted songs, the flac --test command produces wildly different results across executions in a short period of time.

I've spent a lot of time verifying that this isn't drive or filesystem failure, even going so far as to reformat the drive and reinstall a few days ago, same outcome.
These inconsistencies are making it very difficult to find actually corrupted files and replace them, any help would be appreciated.

[ktmf01]

This is certainly very peculiar, but with just this I can't really help you. The output doesn't point in any particular direction. I need some material to be able to reproduce this.

[Funtimes909]

Apologies, I looked for some sort of verbose option but there isn't any, I'm more than willing to share some example files if you let me know the best way to send them over to you :)

[Funtimes909]

Some new information, after replacing an album that reported as corrupted, running "sync" to write cached data to storage immediately, and rerunning the above command, songs at random in the album report decoding errors. but upon each rerun, less and less files report issues until eventually it consistently reports all files are normal.
Some context as well, I am running this command over an sshfs mount, although I have noticed the same thing happening (less frequently) on the machine itself.

[madah81pnz1]

Likely bad RAM?

If you try this:
shasum -a 512 -b *.flac >_checksums

and then verify with:
shasum -c _checksums

Run this in a loop for some time (hours?), for example:
while true ; do shasum -c _checksums || break ; done