rikdegraaff Posted July 25, 2019 Share Posted July 25, 2019 (edited) I have let my scheduled parity check ran last Saturday night, and again 5 parity errors. I do not let the scheduled check overwrite the parity. This is what I've got of errors from the last parity check. One said here on the forums, the only good number at a parity check errors is zero, so that's why I am opening this topic. Here the five errors from the log: Jul 24 03:17:43 RIK-TOWER kernel: md: recovery thread: P incorrect, sector=3519069768 Jul 24 03:17:43 RIK-TOWER kernel: md: recovery thread: P incorrect, sector=3519069776 Jul 24 03:17:43 RIK-TOWER kernel: md: recovery thread: P incorrect, sector=3519069784 Jul 24 03:17:43 RIK-TOWER kernel: md: recovery thread: P incorrect, sector=3519069792 Jul 24 03:17:43 RIK-TOWER kernel: md: recovery thread: P incorrect, sector=3519069800 I don't think they are harmful, but I'm not sure... Also will attach full system diag. Thanks in advance, Rik rik-tower-diagnostics-20190725-1720.zip Edited July 25, 2019 by rikdegraaff Quote Link to comment
JorgeB Posted July 25, 2019 Share Posted July 25, 2019 SAS2LP is in some cases known to cause the same 5 sync errors after every reboot, if that's your case you should replace it a data is being corrupted on those sectors. Quote Link to comment
rikdegraaff Posted July 25, 2019 Author Share Posted July 25, 2019 Okay thanks @johnnie.black. Going to do that, en set this topic to solved. Greetz! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.