levster Posted August 1, 2021 Share Posted August 1, 2021 I just noticed that my Parity 2 disk is reporting errors. I am not sure when those popped up as the parity was just checked and passed. What do I make of these and how to correct them? Thanks. tower-diagnostics-20210801-1505.zip Quote Link to comment
trurl Posted August 1, 2021 Share Posted August 1, 2021 I assume you mean nonzero in the Errors column on Main? Since it hasn't been disabled nothing to correct but I notice no SMART tests have been run on that disk. Haven't found these errors in your syslog yet because it is spammed with these: Aug 1 15:04:04 Tower rpcbind[18066]: connect from 192.168.1.167 to getport/addr(mountd) Aug 1 15:04:04 Tower rpc.mountd[8077]: Bad path in mount request from 192.168.1.167: "Amcrest" Any idea what that is about? Quote Link to comment
trurl Posted August 1, 2021 Share Posted August 1, 2021 OK, I found them back on Jul 18. Run an extended SMART test on that disk. Quote Link to comment
levster Posted August 1, 2021 Author Share Posted August 1, 2021 I am running extended test under Fix Common Problems right now. It has been for the last 45 minutes. I'll post the results as soon as it finishes, although I have no idea how long it may take. I'm also running the extended SMART test on that disk. And, yes, the errors were in the Main page, and I got alerted to them because Fix Common Problems also reported them. Thanks, Lev Quote Link to comment
ChatNoir Posted August 1, 2021 Share Posted August 1, 2021 He meant a SMART for the disk. From Main, click the disk name and scroll down to find the button to run the extended SMART test on that drive. Might take a few hours depending on the drive size. Quote Link to comment
levster Posted August 3, 2021 Author Share Posted August 3, 2021 (edited) So, the extended Smart test reported - completed without errors. However, I see errors in the log. What do I do next about the reported errors? Do I just ignore them? Do I need to re-run parity check? Thanks, Lev tower-smart-20210802-2330.zip Edited August 3, 2021 by levster Quote Link to comment
JorgeB Posted August 3, 2021 Share Posted August 3, 2021 Disk is OK for now, keep monitoring. Quote Link to comment
trurl Posted August 3, 2021 Share Posted August 3, 2021 8 hours ago, levster said: What do I do next about the reported errors? You can reset the error counts on Main using the Clear Stats button in Array Operations. Or reboot. Quote Link to comment
trurl Posted August 3, 2021 Share Posted August 3, 2021 On 8/1/2021 at 3:09 PM, levster said: I am not sure when those popped up On 8/1/2021 at 3:34 PM, trurl said: I found them back on Jul 18. Be sure to setup Notifications to alert you immediately by email or other agent as soon as a problem is detected. Probably for these errors that didn't really disable anything you would get alerted by the daily status report or Fix Common Problems. Quote Link to comment
levster Posted August 3, 2021 Author Share Posted August 3, 2021 6 hours ago, trurl said: Be sure to setup Notifications to alert you immediately by email or other agent as soon as a problem is detected. Probably for these errors that didn't really disable anything you would get alerted by the daily status report or Fix Common Problems. OK. Sounds good. I'll keep an eye on this drive. Appreciate your help! Lev 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.