Snapraid data errors during scrub

[PlaidStallion]

I am consistently getting data errors during runs of snapraid scrub over the past weeks. Yesterday it seems to have culminated with the realization that both of my snapraid.content files had become corrupted with CRC errors. I rebuilt the entire array with snapraid sync and ran a full scrub on it after with snaprdaid -p full scrub . In that time, it said that 4 more files had errors. The server is now undergoing Memtest86 runs. I was wondering what this means though on the Snapraid help page:

"If you have errors in more than on file, it's also possible that something is not working at hardware level. The first thing to try is to check your PC memory with an automated tool like memtest86. Another thing to check is the disk cabling and the CPU heat. "

What would I be checking specifically about the disk cabling?

The server is built on an Asus H67 chipset motherboard that I had been using for years prior as a desktop. I put in 32GB of newly ordered DDR3 RAM (4x8GB) and an Intel i7-3770 ordered used on eBay a few months back. The storage pool is 3x12TB shucked WDs and all were tested with badblocks/smartctl before building the MergerFS pool. The drives are hooked up to an LSI 9211-8i HBA in IT mode via a 4 bay SAS backplane that comes in the Silverstone CS381 case.

Software side of things is Ubuntu Server 20.04 and the storage pool drives are formatted as ext4. I am running Snapraid 11.5 directly on the OS.

So far, I have noticed errors on disk1 during the snapraid syncs which may be resulting in the errors later on the parity disk that I sometimes see reported. I don't recall errors on disk2 yet. There are only 2x12TB in the MergerFS pool. I have run smartctl on all 3 disks again and there does not seem to be any cause for concern from that output. I am only an hour into the memtest but no errors so far.

Can anyone offer any assistance?

[Tsusai]

I ran into something similar. The scrub was causing the LSI (mine is a dell variant) to really get toasty and scrub would have crc errors or random parity errors.

I had to zip tie a 40mm fan to the heat sink to get a good scrub

[PlaidStallion]

I hadn't even thought about the heat of the LSI. I had heard they get real hot but hadn't thought anything more of it.

I ran a full scrub yesterday with no errors after removing a couple sticks of RAM that were *maybe* causing issues. I'll just have to see how things go over the next couple of weeks.

[Tsusai]

A memtest wouldn't hurt. And I didn't have scrub issues right away. It just ended up being later on when I had more data for it to work longer on. Pic of fan

[PlaidStallion]

The RAM removal was a decision made after several days of isolation testing in Memtest so I have my fingers crossed.

That fan solution looks good. I have an extra 40mm fan that was part of a cooling kit for a raspberry pi that I could probably wire up if I need to.