-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SMART data collection broken for one of my drives (SAMSUNG SpinPoint F2) #657
Comments
A forum member KarstenV has also reported SMART info errors:- |
Linked forum report states errors with:- Western Digital Blue WD5000AAKS 500GB However another older Western Digital Blue WD5000AAKS 500GB they have does report / parse correctly. |
We now have in hand a working and Rockstor upsetting output from two identical drives thanks to the forum poster KarstenV linked above. I have also found an old drive of mine that triggers this behaviour, a ST3160021AS |
I will try and have a look at this soon. |
I am looking at this again today, no promises though. |
…kstor#657 This is at least better than a wall of red text and in tests so far produces viable results, but we now need to deal with the return code in an informative manner.
…kstor#657 This is at least better than a wall of red text and in tests so far produces viable results, but we now need to deal with the return code in an informative manner.
A function to email the root user with a message; used to access the email notification system as all root's email is forwarded to whatever external address is defined in email notifications. Should work without email notifications enabled as root always exists.
the command noted returns a code of 64 when producing drive error logs successfully. As this error report is otherwise muted we notify root via email so as not to bury the error.
My system has three drives, for one of them the SMART data collection is broken, the other ones work just fine:
The text was updated successfully, but these errors were encountered: