Here is my smart.conf file:
# This is the configuration file for smartd. It is automatically generated by
# the script /usr/TKLC/plat/sbin/smartCreateConfig, which gets called any time
# 'syscheck --reconfig' is called.
# Here's a brief description of what the command line means:
# -d: Specifies the type of devices (ata, scsi, 3ware, etc). This is only
# required when a 3ware controller is present.
# -S on: Enable Attribute auto save
# -o off: Disable automatic offline testing
# -H: Check the SMART health status of the drive. If health fails, it's very BAD!
# -l error: Monitor the smart error log and report any new failures
# -l selftest: Monitor the smart selftest log and report any new failures
# Note: -f is intentionally not used. This is due to concern over
# false positive failures as the disks age.
# '-m <nomailer> -M test -M exec /usr/TKLC/plat/sbin/smartd_logger' -
# call smartd_logger if there are failures and once on initial startup.
# See the man page for smartd.conf for more details concerning the flags set here.
/dev/sda -S on -o off -H -l error -l selftest -m <nomailer> -M test -M exec /usr/TKLC/plat/sbin/smartd_logger
/dev/sdb -S on -o off -H -l error -l selftest -m <nomailer> -M test -M exec /usr/TKLC/plat/sbin/smartd_logger
Smartd man pages has a lower case “s”.
-s PREFIX, --savestates=PREFIX
[ATA only] Reads/writes smartd state information from/to files ´PREFIX´´MODEL-SERIAL.ata.state´. This preserves SMART
attributes, drive min and max temperatures (-W directive), info about last sent warning email (-m directive), and the time of
next check of the self-test REGEXP (-s directive) across boot cycles.
MODEL and SERIAL are build from drive identify information, invalid characters are replaced by underline.
If the PREFIX has the form ´/path/dir/´ (e.g. ´/var/lib/smartd/´), then files ´MODEL-SERIAL.ata.state´ are created in directory
´/path/dir´. If the PREFIX has the form ´/path/name´ (e.g. ´/var/lib/misc/smartd-´), then files 'nameMODEL-SERIAL.ata.state'
are created in directory '/path/'. The path must be absolute, except if debug mode is enabled.
The state information files are read on smartd startup. The files are always (re)written after reading the configuration file,
before rereading the configuration file (SIGHUP), before smartd shutdown, and after a check forced by SIGUSR1. After a normal
check cycle, a file is only rewritten if an important change (which usually results in a SYSLOG output) occurred.
Q1. Is “s” same as “S” in this case? I am trying to find out is we save attributes in the smartd logfiles via our “-S on” option.
Q2. In our smartd Test.pm code, we look in the logfiles for the field “SMARTD_FAILTYPE” for smartd “Errors”. Are these the same as attributes. Will we see changes in ATTRBIUTES given the “-S on” option used in smartd.conf? I am just not sure if smartd “errors” means the same thing as smartd “attributes”?