Smart: fetch the values 177, 231 and 233 as normalized instead of raw #472
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dear LibreNMS developers,
After investigating how SMART can be monitored efficiently, I discovered that the values
177 Wear Range Delta
,231 Life Left (SSDs)
and233 Media Wearout Indicator
are typically read as normalized numbers rather than interpreting their raw numbers.While the raw value 177 defines the delta between most-worn and least-worn Flash blocks, describing how good/bad the wear levelling of the SSD works, its normalized value is a number between 100 and 0, where 100 is the best state and 0 the worst. Having this 100-0 range is way easier to set up alert rules, compared to a value where the threshold may be manufacturer dependant.
Regarding values 231 and 233, Wikipedia describes them as normalized values, except in very old disks, in which they are also referenced in other numbers. Normalizing these values will also help set up alert rules, instead of internal manufacturer numbers.
Cheers!
Sources: