Re: Using SMARTd to monitor drives

Thane Sherrington wrote:
>       I've read through the manpage on SMARTD, but clearly I'm too dense
> to grasp it.
>
>       I understand that I can do a devicescan in the smartd.conf file to
> scan for all devices, so I have the following in the smartd.conf
>
> DEVICESCAN -l error -l xerror -s L/../.././(00|06|12|18)
>
> Now as I understand it, this should log errors and extended errors, and
> run a long test at 12AM, 6AM, 12PM and 6PM.

Yes, but this does not actually 'log errors'. It issues LOG_CRIT 
messages if the maximum of both error counts has increased. Pending and 
offline uncorrectable sectors (attribute 197 and 198) are also checked 
by default unless -C 0 -U 0 is specified.

Note that you could print the test schedules with 'smartd -q showtests' 
(see smartd man page).


> Am I doing this correctly?

Yes and no. It is probably a bad idea to run 4 long(!) tests a day.

Here is the default setting I use on one machine ('console' and ',ns' 
are Windows specific). One long test on Saturday, short tests each other 
day.

DEFAULT \
   -n standby \
   -a -l xerror -l selfteststs,ns -l offlinests,ns \
   -R 5! -r 5! \
   -R 177! -r 177! \
   -W 3,40,45 -I 190 -I 194 \
   -s (S/../../[1-57]/17|L/../../6/17) \
   -m console -M daily -M test

Thanks,
Christian


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