smart(8) Call for Testing

[Miroslav Lachman]

Chuck Tuffli wrote on 2018/03/27 16:32:
> On Mon, Mar 26, 2018 at 1:59 PM, Mark Saad <nonesuch at longcount.org> wrote:
> ...
>> I was thinking more along the lines of when smartctl reports the overall-health
>> which is always a good time to read; and very Monty Python-eske
>>
>> SMART overall-health self-assessment test result: FAILED!
>> Drive failure expected in less than 24 hours. SAVE ALL DATA.
>>
>> https://serverfault.com/questions/114196/smart-warns-me-but-i-dont-trust-it
> 
> This app is different from others in that it only reports the values;
> it is up to the user / script / etc. to provide analysis. In the
> serverfault example, spin-up time is attribute ID 3. One of my drives
> shows:
> 
> $ smart -t da0 | grep "208 3"
> 208 3 39 0 100 100 1029
> 
> smartctl shows it as follows
> 
> $ smartctl -A /dev/da0
> ...
>    3 Spin_Up_Time            0x0027   100   100   001    Pre-fail
> Always       -       1029
> 
> It would be up to the user or script to decide at what point this
> might indicate an imminent failure.

What is the purpose of this utility and why it should be in base if 
almost everyone will need to write something to do the "real job" or 
"pkg install smartmontools".

Maybe I just don't see something...

Miroslav Lachman