January 2, 20197 yr Please can someone help me analyse the attached diagnostics? Thanks, Luke tower-diagnostics-20190101-2220.zip
January 2, 20197 yr Community Expert Diags are after rebooting, but SMART looks fine and there are some CRC errors, so likely a cable problem, replace SATA cable and re-sync parity.
January 5, 20197 yr Author Thanks for this, I have replaced the SATA cables. How do I re-sync parity?
January 5, 20197 yr Author I found Parity Check in settings, which I scheduled and it's now running. Is this the correct process?
January 5, 20197 yr Community Expert 43 minutes ago, gooner_47 said: I found Parity Check in settings, which I scheduled and it's now running. Is this the correct process? Not really. I'm not sure what it would do if you did parity check on a disabled parity disk. Did you check the box telling it to correct parity errors? Post new diagnostics and a screenshot of Main - Array Operations just for my curiosity.
January 5, 20197 yr Author What should I have done then? Yes I checked that box. Should I cancel the parity check? tower-diagnostics-20190105-1217.zip
January 5, 20197 yr Community Expert It says Read-Check in progress and no corrections so far in syslog. So I'm pretty sure it won't fix your "red cross". Resync parity is just another way of saying rebuild parity. The procedure to rebuild a disk to the same drive, whether parity or data, is the same. Stop array Unassign disk Start array with disk unassigned Stop array Reassign disk Start array to begin rebuild
January 5, 20197 yr Author Rebuild started. It's still warning me about the CRC errors, despite replacing the SATA cables:
January 5, 20197 yr Community Expert If CRC errors continue to increase there's still a problem, try another SATA cable, then another SATA port and/or enclosure if you have one.
January 5, 20197 yr Community Expert Click on the SMART warning indicator for that disk on the Dashboard and acknowledge it. 19 is the number of CRC errors in your original diagnostic so it doesn't look like they are increasing. After acknowledging that warning, it shouldn't give it again unless they increase.
Archived
This topic is now archived and is closed to further replies.