Howboys Posted September 4, 2022 Share Posted September 4, 2022 On the Main page, I see that my parity drive has 3 errors. So I can a parity check with write corrections. It did it and fixed the 3 errors. Then I ran the party check again, and this time it shows 0 errors. But the drive still shows the 3 errors on the Main page. Are these actual errors or just leftover state? How do I get rid of it? Quote Link to comment
itimpi Posted September 4, 2022 Share Posted September 4, 2022 You can use the option to clear the Statistics. Quote Link to comment
Howboys Posted September 4, 2022 Author Share Posted September 4, 2022 Nothing happens when I click the "Clear Stats" button. Quote Link to comment
trurl Posted September 5, 2022 Share Posted September 5, 2022 Post a screenshot of Main - Array Devices Quote Link to comment
Howboys Posted September 5, 2022 Author Share Posted September 5, 2022 2 hours ago, trurl said: Post a screenshot of Main - Array Devices Quote Link to comment
Solution JorgeB Posted September 5, 2022 Solution Share Posted September 5, 2022 I believe stopping and re-starting the array will clear that, if not reboot, note that those are disk errors, not sync errors, that's why they remain, if you want us to take a look at why caused them post the diagnostics before rebooting. Quote Link to comment
Howboys Posted September 5, 2022 Author Share Posted September 5, 2022 That's odd because the disk looks fine from smart. Here's the diagnostics. I won't reboot for a few more hours in case someone wants me to grab other logs. tower-diagnostics-20220905-0810.zip Quote Link to comment
JorgeB Posted September 5, 2022 Share Posted September 5, 2022 It's not logged as a disk problem, looks more like a power/connection issue, check/replace/swap cables. Quote Link to comment
Howboys Posted September 5, 2022 Author Share Posted September 5, 2022 Alright rebooting the server has worked (though it started a parity check). Quote Link to comment
trurl Posted September 6, 2022 Share Posted September 6, 2022 If you had a clean shutdown you shouldn't get a parity check. post new diagnostics Quote Link to comment
Howboys Posted September 6, 2022 Author Share Posted September 6, 2022 Oh weird because I rebooted from the GUI. Should've been clean. tower-diagnostics-20220905-1754.zip Quote Link to comment
trurl Posted September 6, 2022 Share Posted September 6, 2022 Sep 5 13:55:38 Tower emhttpd: unclean shutdown detected 8 minutes ago, Howboys said: rebooted from the GUI. Should've been clean Quote Link to comment
Howboys Posted September 6, 2022 Author Share Posted September 6, 2022 1 hour ago, trurl said: Sep 5 13:55:38 Tower emhttpd: unclean shutdown detected Wow didn't know about this. Alright time to tweak shutdown settings (most likely it's just a ssh session that was open from one of my remote cron jobs). 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.