I replaced my two 6TB parity disks with two 12TB disks in preparation for growing my array. One of the 6TB former parity disks replaced a disk with errors, and the other expanded the array as a new disk. Then, I ran a parity sync with 0 errors. A few weeks later, I ran another parity sync with 370 errors. Parity sync finished today with 2608 errors. For all 3 syncs, Write Corrections was checked. I started a sync with Write Corrections unchecked, and it began with 10 errors.

 

This is my first time dealing with parity sync errors. Can I get some advice on how best to proceed with troubleshooting? Thank you!

pterodactyl-diagnostics-20240729-1641.zip

Edited July 30, 20241 yr by marionza
One symptom disappeared

Start by running memtest, since bad RAM is the number one reason for sync errors.

After this suggestion, I realized I recently added 16GB of RAM to my system, but I ran a few parity 0 error syncs since.

 

My main array is connected via an HBA with 8 SAS cables and 6 SATA cables to ports on the mobo. I tried to ensure these were all connected properly, as I read that this could be the culprit. I then started a parity sync without corrections, beginning with 0 errors.

 

Then, I ran a memtest, which passed.

 

When I booted back up and ran another parity sync without corrections, it started with 1 error. Also, the estimated speed is very slow, around 800K/sec.

 

What do you think I should try next? Should I consider swapping out all of my SAS and SATA cables? Any advice is greatly appreciated!

 

 

Edited July 31, 20241 yr by marionza
Adding info

Post new diags while it's running slow.

Should I stop the sync or download diags while the sync is running slow?

While it's running

I noticed that while the diags were downloading, it held for a beat on the parity logs.

pterodactyl-diagnostics-20240731-1200.zip

ATA errors for parity, check/replace cables (power and SATA) and try again.

I will replace the power and SATA on only the two parity drives, correct? Also, in what log file did you see the ATA errors? Thank you!

Only parity1 needs replacing, the errors are in the syslog

I replaced the cables. Parity sync speed is back to normal, around 90MB/s! I started the sync (without correction) and showed 11 errors at the outset. Should I let it run or restart it with write correction and let it complete? Thank you!

 

Update: After 7m of elapsed sync, the speed has increased to 190 MB/s, and the error count has increased to 18.

pterodactyl-diagnostics-20240731-1343.zip

Edited July 31, 20241 yr by marionza
Update

Run a correcting check, then a non correcting one, all without rebooting and post new diags.

It's done with what I think is good news. The correcting sync found around 2,700 errors, while the non-correcting sync found 0.

pterodactyl-diagnostics-20240802-1402.zip

That's good, if the next scheduled check also doesn't find errors it should be resolved.

Amazing! Thank you so much! This is such a relief.

 

For my knowledge moving forward, I was curious how you knew parity 1 was the drive experiencing ATA errors. I found ATA errors in syslog, but I wasn't sure how to associate them to a specific drive.

You can find which disk ATA# corresponds to by looking at lsscsi.txt in the diags.

Got it.

I ran another sync this weekend. 0 errors!

Thank you again!