If you run a server with more than a couple of hard drives, you’re probably already familiar with S.M.A.R.T and the smartd daemon. If not, it’s an incredible open source project described as the following:
smartd is a daemon that monitors the Self-Monitoring, Analysis and Reporting Technology (SMART) system built into many ATA, IDE and SCSI-3 hard drives. The purpose of SMART is to monitor the reliability of the hard drive and predict drive failures, and to carry out different types of drive self-tests.
These S.M.A.R.T hard drive self-tests can help you detect and replace failing hard drives before they cause permanent data loss. However, there’s a couple issues with smartd:
There are more than a hundred S.M.A.R.T attributes, however smartd does not differentiate between critical and informational metrics
smartd does not record S.M.A.R.T attribute history, so it can be hard to determine if an attribute is degrading slowly over time.
S.M.A.R.T attribute thresholds are set by the manufacturer. In some cases these thresholds are unset, or are so high that they can only be used to confirm a failed drive, rather than detecting a drive about to fail.
smartd is a command line only tool. For head-less servers a web UI would be more valuable.
Scrutiny is a Hard Drive Health Dashboard & Monitoring solution, merging manufacturer provided S.M.A.R.T metrics with real-world failure rates.
I installed Scrutiny, but it seems like it’s not displaying real-time SMART data, especially the temperature, which is the information I was most interested in. The data it shows corresponds exactly to the time of installation and the first time the app was opened, but after that, it stops updating.
I was able to solve it, I searched the application documentation and found that if you add a variable.
Key: COLLECTOR_CRON_SCHEDULE
Value: */10 * * * *
Determines the time in which the application will check and update the information.
In my case, I set it to 10 minutes, just increase this value if you want to decrease or increase the time.
