I walked away from my PC for a day with Adobe Premiere and Illustrator open accessing files on my server. When I returned, an error notification stated that my first parity disk had read errors. I ran an extended self-test on the drive, which came back clean. I then noticed that I couldn't load the docker tab and my apps were not working. Also, the server would not respond to shutdown or reboot. Eventually, I initiated a hard reboot from the console. When I powered on the machine and started the array, all seemed normal, but there was a notice that the array had detected an improper shutdown. The machine initiated a parity sync. I noticed that the sync had uncovered a few errors. Most disconcerting was that the speed of the sync was under 1 MB/s. Usually, the sync runs around 40 MB/s. I shut down the server and reseated the SATA cables to the parity drive that experienced read errors. I brought the machine back online and initiated a non-error-correcting sync. It immediately found errors (normal), but the sync was still sub 1 MB/s. I have ordered new SATA cables, but would appreciate any insights gleaned from my attached diags.

pterodactyl-diagnostics-20241203-0836.zip

Replace cables for parity ad try again.

I swapped in a brand new SATA data cable, but not power. This resolved the read error, but the parity sync speed still runs at ~1–3 MB/s.

pterodactyl-diagnostics-20241205-0828.zip

Still ata errors with parity if you don't have a new power cable, try swapping with a different disk.

I should try swapping the power cable first though, right?

I think I figured it out. I have been overloading the power cable's power rating. Once I swapped it out with a new one and distributed other drives across other power cables. the issue was resolved. Thanks for your help, @JorgeB! You're the best.

Ugh. I spoke too soon.

 

I completed a parity check at a good average speed, resulting in 37,961 corrected errors. Eeep.

 

Then, I started a non-correcting sync, which immediately resulted in errors.

 

When I encountered this issue before, it was resolved by @JorgeB's suggestion to remove half of the RAM. I never put that RAM back in my machine.

 

What do you suggest? Should I try purchasing new RAM?

pterodactyl-diagnostics-20241209-0939.zip

You have both modules installed on the same channel, for better performance and stability, install them on different channels, if sync errors continue, try just one stick of RAM, if the same try the other one, that will basically rule out bad RAM.

 

Keep in mind that you need to run two checks for each test, since the first one can still find error even if the issue is resolved.

Once again, your suggestion fixed the problem. When a SATA cable goes bad, I wonder if it creates errors in the RAM that hang around and show up during parity checks. Once I reseat the RAM, the errors go away.

SATA cables should not create RAM errors, not even sync errors, though the latter is not impossible, if there's some bad firmware on the drives or controller.