smartd is a daemon that monitors the Self-Monitoring, Analysis and Reporting Technology (SMART) system built into most ATA/SATA and SCSI/SAS hard drives and solid-state drives. The purpose of SMART is to monitor the reliability of the hard drive and predict drive failures, and to carry out different types of drive self-tests. This version of smartd is compatible with ACS-3, ACS-2, ATA8-ACS, ATA/ATAPI-7 and earlier standards (see REFERENCES below).
smartd will attempt to enable SMART monitoring on ATA devices (equivalent to smartctl -s on) and polls these and SCSI devices every 30 minutes (configurable), logging SMART errors and changes of SMART Attributes via the SYSLOG interface. The default location for these SYSLOG notifications and warnings is system-dependent (typically /var/log/messages or /var/log/syslog). To change this default location, please see the '-l' command-line option described below.
In addition to logging to a file, smartd can also be configured to send email warnings if problems are detected. Depending upon the type of problem, you may want to run self-tests on the disk, back up the disk, replace the disk, or use a manufacturer's utility to force reallocation of bad or unreadable disk sectors. If disk problems are detected, please see the smartctl manual page and the smartmontools web page/FAQ for further guidance.
If you send a USR1 signal to smartd it will immediately check the status of the disks, and then return to polling the disks every 30 minutes. See the '-i' option below for additional details.
smartd can be configured at start-up using the configuration
file /etc/smartmontools/smartd.conf (Windows: EXEDIR/smartd.conf).
If the configuration file is subsequently modified, smartd
can be told to re-read the configuration file by sending it a
HUP signal, for example with the command:
killall -HUP smartd.
On startup, if smartd finds a syntax error in the configuration file, it will print an error message and then exit. However if smartd is already running, then is told with a HUP signal to re-read the configuration file, and then find a syntax error in this file, it will print an error message and then continue, ignoring the contents of the (faulty) configuration file, as if the HUP signal had never been received.
When smartd is running in debug mode, the INT signal (normally generated from a shell with CONTROL-C) is treated in the same way as a HUP signal: it makes smartd reload its configuration file. To exit smartd use CONTROL-\.
[Linux only] [NEW EXPERMIMENTAL SMARTD FEATURE] If smartd is started as a systemd(1) service and 'Type=Notify' is specified in the service file, the service manager is notified after successful startup. Other state changes are reported via systemd notify STATUS messages. Notification of successful reloads (after HUP signal) is not supported. To detect this process start-up type, smartd checks whether the environment variable 'NOTIFY_SOCKET' is set. Note that it is required to set the '-n' ('--nofork') option in the 'ExecStart=/usr/sbin/smartd' command line if 'Type=Notify' is used.
On startup, in the absence of the configuration file /etc/smartmontools/smartd.conf, the smartd daemon first scans for all devices that support SMART. The scanning is done as follows:
If directive '-d nvme' or no '-d' directive is specified, examine all entries "/dev/nvme[0-99]" for NVMe devices.
smartd then monitors for all possible SMART errors (corresponding to the '-a' Directive in the configuration file; see the smartd.conf(5) man page).
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.csv' are created in directory '/path/dir'. If the PREFIX has the form '/path/name' (e.g. '/var/lib/misc/attrlog-'), then files 'nameMODEL-SERIAL.ata.csv' are created in directory '/path/'. The path must be absolute, except if debug mode is enabled.
By using '-' for FILE, the configuration is read from standard input.
This is useful for commands like:
echo /dev/sdb -m user@home -M test | smartd -c - -q onecheck
to perform quick and simple checks without a configuration file.
Warning: Mail notification does not work when used.
Note that the superuser can make smartd check the status of the
disks at any time by sending it the SIGUSR1 signal, for example
with the command:
kill -SIGUSR1 <pid>
where <pid> is the process id number of smartd. One may
also use:
killall -USR1 smartd
for the same purpose.
If you would like to have smartd messages logged somewhere other than the default location, include (for example) '-l local3' in its start up argument list. Tell the syslog daemon to log all messages from facility local3 to (for example) '/var/log/smartd.log'.
For more detailed information, please refer to the man pages for the local syslog daemon, typically syslogd(8), syslog-ng(8) or rsyslogd(8).
nodev - Exit if there are no devices to monitor, or if any errors are found at startup in the configuration file. This is the default.
errors - Exit if there are no devices to monitor, or if any errors are found in the configuration file /etc/smartmontools/smartd.conf at startup or whenever it is reloaded.
nodevstartup - Exit if there are no devices to monitor at startup. But continue to run if no devices are found whenever the configuration file is reloaded.
never - Only exit if a fatal error occurs (no remaining system memory, invalid command line arguments). In this mode, even if there are no devices to monitor, or if the configuration file /etc/smartmontools/smartd.conf has errors, smartd will continue to run, waiting to load a configuration file listing valid devices.
onecheck - Start smartd in debug mode, then register devices, then check device's SMART status once, and then exit with zero exit status if all of these steps worked correctly.
This last option is intended for 'distribution-writers' who want to create automated scripts to determine whether or not to automatically start up smartd after installing smartmontools. After starting smartd with this command-line option, the distribution's install scripts should wait a reasonable length of time (say ten seconds). If smartd has not exited with zero status by that time, the script should send smartd a SIGTERM or SIGKILL and assume that smartd will not operate correctly on the host. Conversely, if smartd exits with zero status, then it is safe to run smartd in normal daemon mode. If smartd is unable to monitor any devices or encounters other problems then it will return with non-zero exit status.
showtests - Start smartd in debug mode, then register devices, then write a list of future scheduled self tests to stdout, and then exit with zero exit status if all of these steps worked correctly. Device's SMART status is not checked.
This option is intended to test whether the '-s REGEX' directives in smartd.conf will have the desired effect. The output lists the next test schedules, limited to 5 tests per type and device. This is followed by a summary of all tests of each device within the next 90 days.
ioctl - report all ioctl() transactions.
ataioctl - report only ioctl() transactions with ATA devices.
scsiioctl - report only ioctl() transactions with SCSI devices.
nvmeioctl - report only ioctl() transactions with NVMe devices.
Any argument may include a positive integer to specify the level of detail that should be reported. The argument should be followed by a comma then the integer with no spaces. For example, ataioctl,2 The default level is 1, so '-r ataioctl,1' and '-r ataioctl' are equivalent.
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.
smartd -d -i 30
Run in foreground (debug) mode, checking the disk status
every 30 seconds.
smartd -q onecheck
Registers devices, and checks the status of the devices exactly
once.
The exit status (the shell
$?
variable) will be zero if all went well, and nonzero if no devices
were detected or some other problem was encountered.
Please see the smartctl manual page for further explanation of the differences between Normalized and Raw Attribute values.
smartd
will make log entries at loglevel
LOG_CRIT
if a SMART Attribute has failed, for example:
'Device: /dev/sdc, Failed SMART Attribute: 5 Reallocated_Sector_Ct'
This loglevel is used for reporting enabled by the
'-H', -f', '-l selftest',
and
'-l error'
Directives. Entries reporting failure of SMART Prefailure Attributes
should not be ignored: they mean that the disk is failing. Use the
smartctl
utility to investigate.
Many other individuals have made contributions and corrections, see AUTHORS, ChangeLog and repository files.
The first smartmontools code was derived from the smartsuite package, written by Michael Cornwell and Andre Hedrick.
An introductory article about smartmontools is Monitoring Hard Disks with SMART, by Bruce Allen, Linux Journal, January 2004, pages 74-77. See <https://www.linuxjournal.com/article/6983>.
If you would like to understand better how SMART works, and what it does, a good place to start is with Sections 4.8 and 6.54 of the first volume of the 'AT Attachment with Packet Interface-7' (ATA/ATAPI-7) specification Revision 4b. This documents the SMART functionality which the smartmontools utilities provide access to.
The functioning of SMART was originally defined by the SFF-8035i revision 2 and the SFF-8055i revision 1.4 specifications. These are publications of the Small Form Factors (SFF) Committee.
Links to these and other documents may be found on the Links page of the smartmontools Wiki at <https://www.smartmontools.org/wiki/Links>.