BrandonG777 Posted January 14, 2019 Share Posted January 14, 2019 I'm receiving parity errors on a regular basis now. I don't recall ever seeing them in the past. I was seeing a lot of call traces due to having a custom docker net, I believe I have resolved those issues but the parity errors continue to show up during parity-checks. Any help/advice is appreciated, server seems to be running fine otherwise. veyron-diagnostics-20190114-1257.zip Quote Link to comment
JorgeB Posted January 14, 2019 Share Posted January 14, 2019 If there were no unclean shutdowns start by running memtest, bad RAM is the number one reason for unexpected sync errors. Quote Link to comment
itimpi Posted January 14, 2019 Share Posted January 14, 2019 (edited) 3 minutes ago, BrandonG777 said: I'm receiving parity errors on a regular basis now. I don't recall ever seeing them in the past. I was seeing a lot of call traces due to having a custom docker net, I believe I have resolved those issues but the parity errors continue to show up during parity-checks. Any help/advice is appreciated, server seems to be running fine otherwise. veyron-diagnostics-20190114-1257.zip Are you running your parity checks as correcting or non-correcting? If you are using non-correcting then the errors will persist until you run a correcting check. If you keep getting new errors then that is more concerning. Edited January 14, 2019 by itimpi Quote Link to comment
BrandonG777 Posted January 14, 2019 Author Share Posted January 14, 2019 Yeah, they keep showing up despite being corrected each week. I never recall seeing them before running into the call traces though, like something got corrupted somewhere. Also, just noticed this... I'm thinking that's indicative of a failing drive <sigh> ... Quote Link to comment
JorgeB Posted January 14, 2019 Share Posted January 14, 2019 2 minutes ago, BrandonG777 said: I'm thinking that's indicative of a failing drive <sigh> ... No, usually a bad SATA cable, though a single error is no case for concern, if it keeps increasing replace the cable. Quote Link to comment
BrandonG777 Posted January 14, 2019 Author Share Posted January 14, 2019 1 minute ago, johnnie.black said: No, usually a bad SATA cable, though a single error is no case for concern, if it keeps increasing replace the cable. What should I do about the continuous parity errors though? Like I said I don't recall seeing these on a regular basis prior to my docker call trace problems. Quote Link to comment
JorgeB Posted January 14, 2019 Share Posted January 14, 2019 1 minute ago, BrandonG777 said: What should I do about the continuous parity errors though? 16 minutes ago, johnnie.black said: If there were no unclean shutdowns start by running memtest, bad RAM is the number one reason for unexpected sync errors. Quote Link to comment
WizADSL Posted January 14, 2019 Share Posted January 14, 2019 Be careful about running a correcting parity check on a schedule. If a drive starts to fail/has read errors during a parity check (which is very possible since the hardware is under higher stress when checking parity) you could end up with a failed disk and invalid parity. Quote Link to comment
WizADSL Posted January 14, 2019 Share Posted January 14, 2019 How many parity errors are you seeing? Quote Link to comment
BrandonG777 Posted January 14, 2019 Author Share Posted January 14, 2019 (edited) 6 minutes ago, WizADSL said: How many parity errors are you seeing? Between 4 and 22 but they've consistently come up since my docker call traces a couple months back. Doing an extended smart test now, and plan on doing a full memtest once I'm at home. EDIT: @WizADSL I will take your advice on the parity correction scheduling. Edited January 14, 2019 by BrandonG777 Quote Link to comment
trurl Posted January 14, 2019 Share Posted January 14, 2019 42 minutes ago, BrandonG777 said: I will take your advice on the parity correction scheduling. In addition to not correcting on a schedule, weekly would be considered excessive by most. Any reason for that frequency? Quote Link to comment
BrandonG777 Posted January 14, 2019 Author Share Posted January 14, 2019 Just now, trurl said: In addition to not correcting on a schedule, weekly would be considered excessive by most. Any reason for that frequency? Honestly, I don't remember my reasoning for that schedule. What would you recommend, monthly? Quote Link to comment
trurl Posted January 14, 2019 Share Posted January 14, 2019 5 minutes ago, BrandonG777 said: What would you recommend, monthly? That is the usual. Quote Link to comment
BrandonG777 Posted March 6, 2019 Author Share Posted March 6, 2019 Okay I've had a couple months with no parity errors. Not sure what I did to resolve this but memtest came up clean. I did blow the dust out and ensured all the SATA connectors were secure. I also changed the schedule to start earlier in the night. Sent from my Pixel 2 XL using Tapatalk 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.