Re: Using SMARTd to monitor drives

Ray Andrews wrote:
> ...
> It really would be nice if one could control the timing of reports
> Christian.

The current possible settings -M once (default if state persistence is 
disabled) and -M daily  (default if state persistence is enabled) are 
IMO sufficient. The warning emails (or scripts) are only intended to 
alert the admin about serious problems immediately after detection - 
with optional daily reminders if the problem persists.

Feel free to request an enhancement here:
https://www.smartmontools.org/newticket


> As above, I've found that it doesn't matter how often I
> test, the running of smartd-notifier remains random.

No, if smartd is running 24x7 a reminder email is sent each ~24 hours 
for each device and each type of disk problem detected. If smartd is not 
running 24x7, it depends on state persistence setting (enabled by 
default on Debian/Ubuntu).

It is logged to syslog as: "Sending warning via MAILER to ADDRESS ..." 
immediately after the actual warning message.


> Here's my little log:
>
> 2017-01-26_Thu_19:56:28:IDENTICAL
> 2017-01-26_Thu_19:56:28:Device: /dev/sdb [SAT], Self-Test Log error
> count increased from 15 to 16

This means that another SMART self test has failed. Did you check the 
self-test log(s) in output of 'smartctl -x /dev/sdb' ? A failed 
self-test typically reports the LBA of the first bad sector.


> 2017-01-28_Sat_08:33:09:Device: /dev/sdb [SAT], 77 Currently unreadable
> (pending) sectors
> ...
>
> BTW, I can't clear that error no matter what I do :-/

In a previous mail from 2017-01-19, I already explained how to disable 
the pending sectors alert with the -C directive.

Regards,
Christian


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot