rikdegraaff Posted February 7, 2019 Share Posted February 7, 2019 Hello Everyone, After a time of 0 erros the last 2 months, my unRAID array gives my at the parity check 5 errors. I cannot find where it came from. It suddenly appeared. The only thing is that my parity disk broke down, but I replaced it safely and by the manual, so it showing up as an error. Hereby the syslog. If you need more info about my system i.e., I would like to hear that. tower-diagnostics-20190207-1328.zip Quote Link to comment
JorgeB Posted February 7, 2019 Share Posted February 7, 2019 Reboot and run another check, if you get the same 5 errors it's the SAS2LP, it's one of the known problems with them. Quote Link to comment
rikdegraaff Posted February 7, 2019 Author Share Posted February 7, 2019 Okay, thanks for the help. I've rebooted my server, and I'm now running a parity-check. I'll keep you'll updated, parity-checks costs around 9 hrs, so that will be tomorrow morning (CET). Greetz. Quote Link to comment
JorgeB Posted February 7, 2019 Share Posted February 7, 2019 After it's done, if it finds 5 errors again, and most likely it will, check if they are the same: Feb 6 20:35:27 Tower kernel: md: recovery thread: P corrected, sector=1565565768 Feb 6 20:35:27 Tower kernel: md: recovery thread: P corrected, sector=1565565776 Feb 6 20:35:27 Tower kernel: md: recovery thread: P corrected, sector=1565565784 Feb 6 20:35:27 Tower kernel: md: recovery thread: P corrected, sector=1565565792 Feb 6 20:35:27 Tower kernel: md: recovery thread: P corrected, sector=1565565800 If yes it's the HBA, replace it with an LSI. Quote Link to comment
rikdegraaff Posted February 10, 2019 Author Share Posted February 10, 2019 Well @johnnie.black, the parity check gave 0 errors as return... I hope that it will stay so. But what is the HBA, and what is a LSI?? Quote Link to comment
JorgeB Posted February 10, 2019 Share Posted February 10, 2019 the parity check gave 0 errors as return... That's good, as long as you rebooted first, if it's the SAS2LP problem it only happens after rebooting. HBA is an host bus adapter, or non RAID controller, HBAs from LSI are the ones recommended for Unraid. Quote Link to comment
rikdegraaff Posted February 10, 2019 Author Share Posted February 10, 2019 I rebooted first, as you said. I've scheduled my parity-check every first day of the month, so what should give the next parity-check number of errors? Because my unRAID server is on-line 24/7... (and the SAS2LP isn't being removed...) Quote Link to comment
JorgeB Posted February 10, 2019 Share Posted February 10, 2019 2 hours ago, rikdegraaff said: so what should give the next parity-check number of errors? Only acceptable number of sync errors is 0. Quote Link to comment
rikdegraaff Posted February 11, 2019 Author Share Posted February 11, 2019 17 hours ago, johnnie.black said: Only acceptable number of sync errors is 0. Okay, I will see hopefully that number on the next parity-sync, scheduled at the first of march 2019... Quote Link to comment
JonathanM Posted February 11, 2019 Share Posted February 11, 2019 Hopefully all your disks stay healthy. Remember that sync errors mean that a failed disk will be rebuilt with those errors, so the chance of data loss is much higher. Personally I wouldn't wait to see, I'd run checks until I consistently got 0 errors. Until that happens, you are running at risk. Quote Link to comment
rikdegraaff Posted February 12, 2019 Author Share Posted February 12, 2019 Okay, I'll start a parity sync right away. And I will do some more after this one. So I hope it stays on 0, if not, I shall post my diagnostics here. Thanks for the advice! Quote Link to comment
rikdegraaff Posted February 13, 2019 Author Share Posted February 13, 2019 Sorry for the bump/doublepost but is it needed to check the box Write corrections to parity? It is by default turned on, but my logic says uncheck it, if a HDD-data is corrupt, it writes the corrupted data to use as parity numbers. Please let me be wrong...😫 Quote Link to comment
JorgeB Posted February 13, 2019 Share Posted February 13, 2019 Unless sync errors are expect, like after an unclean shutdown, always do a non correcting check. Quote Link to comment
rikdegraaff Posted February 13, 2019 Author Share Posted February 13, 2019 2 hours ago, johnnie.black said: Unless sync errors are expect, like after an unclean shutdown, always do a non correcting check. Thanks for the information, because I am really a beginner with unRAID and other Linux based os'ses. The speed and accuracy of the support forums is since I am been a member, is perfect! 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.