Add debug output to understand calculation of failure probability (FP) #16
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.
Please don't actually merge this. I just wanted to publish it here for others facing the same confusion, that I faced.
When running
snapraid smart
on my machine I was surprised to see a failure probability of 84% even though all 5 SMART values mentioned in the SnapRAID FAQ suggested a perfectly healthy drive.To understand where this high value came from I added some debug ouput along the code path for the calculation and saw that it was based on
Load_Cycle_Count (193)
which was not mentioned in the FAQ, nor in the Backblaze blogposts.With this patch the output looks like this: