September 4, 20223 yr 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?
September 5, 20223 yr Community Expert Solution 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.
September 5, 20223 yr Author 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
September 5, 20223 yr Community Expert It's not logged as a disk problem, looks more like a power/connection issue, check/replace/swap cables.
September 5, 20223 yr Author Alright rebooting the server has worked (though it started a parity check).
September 6, 20223 yr Community Expert If you had a clean shutdown you shouldn't get a parity check. post new diagnostics
September 6, 20223 yr Author Oh weird because I rebooted from the GUI. Should've been clean. tower-diagnostics-20220905-1754.zip
September 6, 20223 yr Community Expert Sep 5 13:55:38 Tower emhttpd: unclean shutdown detected 8 minutes ago, Howboys said: rebooted from the GUI. Should've been clean
September 6, 20223 yr Author 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).
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.