Consume Product

From the command line manual on my computer:

                                                                                                                                                                                                                                                SMART Monitoring Tools SMARTD(8)

NAME
       smartd - SMART Disk Monitoring Daemon

SYNOPSIS
       smartd [options]

DESCRIPTION
       [This man page is generated for the Linux version of smartmontools. It does not contain info specific to other platforms.]

       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/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] 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/smartd.conf, the smartd daemon first scans for all devices that support SMART. The scanning is done as follows:

       LINUX: Examine all entries "/dev/hd[a-t]" for IDE/ATA devices, and "/dev/sd[a-z]", "/dev/sd[a-z][a-z]" for ATA/SATA or SCSI/SAS devices. Disks behind RAID controllers are not included.

                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).