Difference between revisions of "S.M.A.R.T."

From ArchWiki
Jump to navigation Jump to search
(Reference dma)
 
(138 intermediate revisions by 56 users not shown)
Line 1: Line 1:
[[Category:HOWTOs (English)]]
+
[[Category:Storage]]
=SMART HOWTO=
+
[[ja:S.M.A.R.T.]]
This page will describe how to setup SMART to monitor your harddisks.
+
[[Wikipedia:S.M.A.R.T.|S.M.A.R.T.]] (Self-Monitoring, Analysis, and Reporting Technology) is a supplementary component built into many modern storage devices through which devices monitor, store, and analyze the health of their operation.  Statistics are collected (temperature, number of reallocated sectors, seek errors...) which software can use to measure the health of a device, predict possible device failure, and provide notifications on unsafe values.
  
===Step 1: Install smartmontools===
+
== Smartmontools ==
<pre>
 
pacman -Sy smartmontools
 
</pre>
 
  
===Step 2: Check if your disk(s) support SMART===
+
The smartmontools package contains two utility programs for analyzing and monitoring storage devices: {{ic|smartctl}} and {{ic|smartd}}. [[Install]] the {{Pkg|smartmontools}} package to use these tools.
IDE-disks:
 
<pre>
 
smartctl -i /dev/hda
 
</pre>
 
SATA-disks:
 
<pre>
 
smartctl -i -d ata /dev/sda
 
</pre>
 
Look for:<br>
 
"SMART support is: Available - device has SMART capability."<br>
 
"SMART support is: Enabled"<br>
 
If SMART is NOT enabled you have to do this.
 
IDE-disks:
 
<pre>
 
smartctl -s on /dev/hda
 
</pre>
 
SATA-discs:
 
<pre>
 
smartctl -s on -d ata /dev/sda
 
</pre>
 
  
===Step 3: Check your disk(s)===
+
SMART support must be available and enabled on each storage device to effectively use these tools. You can use [[#smartctl]] to check for and enable SMART support. That done, you can manually [[#Run a test]] and [[#View test results]], or you can use [[#smartd]] to automatically run tests and email notifications.
Check the SMART health status of a device
 
<pre>
 
smartctl -H /dev/sda
 
</pre>
 
I all goes well, it will return PASSED.  
 
              If the device reports <b>failing health status</b>, this means either that
 
              the  device  has  already  failed, or that it is predicting its own
 
              failure within the next 24 hours.  If this happens,  use the  "-a"
 
              option  to get more information, and <b>get your data off the disk and
 
              someplace safe as soon as you can</b>.
 
  
Check the SMART Error Log
+
=== smartctl ===
<pre>
 
smartctl -l error /dev/sda
 
</pre>
 
If we read No Errors Logged it's ok. If there are a few errors (and they are not so recent) you don't have to worry too much. If there are a lot of errors it's better if you backup your data as soon as you can.
 
  
NOTE: This is not all tests but only two of them. See the manual or [http://gentoo-wiki.com/HOWTO_Monitor_your_hard_disk(s)_with_smartmontools this wiki] for more.
+
smartctl is a command-line tool that "controls the Self-Monitoring, Analysis and Reporting Technology (SMART) system built into most ATA/SATA and SCSI/SAS hard drives and solid-state drives."
  
===Step 4: Make smartd automatically monitor your drives===
+
The {{ic|-i}}/{{ic|--info}} option prints a variety of information about a device, including whether SMART is available and enabled:
smartd  can  be  configured  at  start-up  using  the  configuration  file
 
/etc/smartd.conf. If no configuration exists smartd monitors for <b>all</b> possible SMART errors (corresponding  to  the "-a" Directive in the configuration file).
 
  
If  the  first  non-comment  entry  in  the configuration file is the text
+
{{hc|# smartctl --info /dev/sda {{!}} grep 'SMART support is:'|
string DEVICESCAN in capital letters, then smartd will ignore any  remaining 
+
SMART support is: Available - device has SMART capability.
lines in the configuration file, and will scan for devices. For an ATA device, if no Directives appear, then the device will be monitored as if the "-a" Directive (monitor all  SMART properties)  had  been given.
+
SMART support is: Enabled
 +
}}
  
To make configuration for invidual devices you have to comment the line with DEVICESCAN and add a configuration line for every device. Here is an example (more are given inside /etc/smart.conf):
+
If SMART is available but not enabled, you can enable it:
<pre>
 
#DEVICESCAN
 
  
/dev/hda -a -m root@localhost
+
# smartctl --smart=on /dev/<device>
</pre>
 
This will monitor all atributes and send a warning email to root@localhost if a failure or a new error occurs.
 
  
NOTE: To be able to send internal mail, you need a MTA like sendmail or [http://wiki.archlinux.org/index.php/PostFix_HostOnly_Howto postfix]
+
You may need to specify a device type. For example, specifying {{ic|1=--device=ata}} tells smartctl that the device type is ATA, and this prevents smartctl from issuing SCSI commands to that device.
  
Now start the deamon
+
==== Run a test ====
<pre>
 
/etc/rc.d/smartd start
 
</pre>
 
If everything is working as it should, you can add smartd to your DAEMONS array in /etc/rc.conf
 
  
=Resources=
+
There are three types of self-tests that a device can execute (all are safe to user data):
http://smartmontools.sourceforge.net/
 
  
http://gentoo-wiki.com/HOWTO_Monitor_your_hard_disk(s)_with_smartmontools
+
* Short: runs tests that have a high probability of detecting device problems,
 +
* Extended or Long: the test is the same as the short check but with no time limit and with complete disk surface examination,
 +
* Conveyance: identifies if damage incurred during transportation of the device.
 +
 
 +
The {{ic|-c}}/{{ic|--capabilities}} flag prints which tests a device supports and the approximate execution time of each test. For example:
 +
 
 +
{{hc|# smartctl -c /dev/sda|
 +
...
 +
Short self-test routine
 +
recommended polling time:        (  1) minutes.
 +
Extended self-test routine
 +
recommended polling time:        (  74) minutes.
 +
Conveyance self-test routine
 +
recommended polling time:        (  2) minutes.
 +
...
 +
}}
 +
 
 +
Use {{ic|-t}}/{{ic|1=--test=<test_name>}} flag to run a test:
 +
 
 +
# smartctl -t short /dev/<device>
 +
# smartctl -t long /dev/<device>
 +
# smartctl -t conveyance /dev/<device>
 +
 
 +
==== View test results ====
 +
 
 +
You can view a device's overall health with the {{ic|-H}} flag. "If the device reports failing health status, this means either that the device has already failed, or that it is predicting its own failure within the next 24 hours. If this happens […] get your data off the disk and to someplace safe as soon as you can."
 +
 
 +
# smartctl -H /dev/<device>
 +
 
 +
You can also view a list of recent test results and detailed information about a device:
 +
 
 +
# smartctl -l selftest /dev/<device>
 +
# smartctl -a /dev/<device>
 +
 
 +
=== smartd ===
 +
 
 +
The smartd daemon monitors SMART statuses and emits notifications when something goes wrong. It can be managed with systemd and configured using the {{ic|/etc/smartd.conf}} configuration file. The configuration file syntax is esoteric, and this wiki page provides only a quick reference. For more complete information, read the examples and comments within the configuration file, or read {{man|5|smartd.conf}}.
 +
 
 +
==== daemon management ====
 +
 
 +
To start the daemon, check its status, make it auto-start on system boot and read recent log file entries, simply [[start/enable]] the {{ic|smartd.service}} systemd unit.
 +
 
 +
smartd respects all the usual systemctl and journalctl commands. For more information on using systemctl and journalctl, see [[systemd#Using units]] and [[systemd/Journal]].
 +
 
 +
==== Define the devices to monitor ====
 +
 
 +
To monitor for all possible SMART errors on all disks, the following setting must be added in the configuration file.
 +
{{hc|/etc/smartd.conf|DEVICESCAN -a}}
 +
Note this is the default ''smartd'' configuration and the {{ic|-a}} parameter, which is the default parameter, may be omitted.
 +
 
 +
To monitor for all possible SMART errors on {{ic|/dev/sda}} and {{ic|/dev/sdb}}, and ignore all other devices:
 +
 
 +
{{hc|/etc/smartd.conf|
 +
/dev/sda -a
 +
/dev/sdb -a
 +
}}
 +
 
 +
To monitor for all possible SMART errors on externally connected disks (USB-backup disks spring to mind) it is prudent to tell ''smartd'' the UUID of the device since the /dev/sdX of the drive might change during a reboot.
 +
 
 +
First, you will have to get the UUID of the disk to monitor: {{ic|ls -lah /dev/disk/by-uuid/}} now look for the disk you want to Monitor
 +
 
 +
{{hc|ls -lah /dev/disk/by-uuid/|
 +
lrwxrwxrwx 1 root root  9 Nov  5 22:41 820cdd8a-866a-444d-833c-1edb0f4becac -> ../../sde
 +
lrwxrwxrwx 1 root root  10 Nov  5 22:41 b51b87f3-425e-4fe7-883f-f4ff1689189e -> ../../sdf2
 +
lrwxrwxrwx 1 root root  9 Nov  5 22:42 ea2199dd-8f9f-4065-a7ba-71bde11a462c -> ../../sda
 +
lrwxrwxrwx 1 root root  10 Nov  5 22:41 fe9e886a-8031-439f-a909-ad06c494fadb -> ../../sdf1
 +
}}
 +
 
 +
I know that my USB disk attached to /dev/sde during boot. Now to tell ''smartd'' to monitor that disk simply use the {{ic|/dev/disk/by-uuid/}} path.
 +
 
 +
{{hc|/etc/smartd.conf|
 +
/dev/disk/by-uuid/820cdd8a-866a-444d-833c-1edb0f4becac -a
 +
}}
 +
 
 +
Now your USB disk will be monitored even if the /dev/sdX path changes during reboot.
 +
 
 +
==== Notifying potential problems ====
 +
 
 +
To have an email sent when a failure or new error occurs, use the {{ic|-m}} option:
 +
 
 +
{{hc|/etc/smartd.conf|
 +
DEVICESCAN -m address@domain.com
 +
}}
 +
 
 +
To be able to send the email externally (i.e. not to the root mail account) a MTA (Mail Transport Agent) or a MUA (Mail User Agent) will need to be installed and configured.  Common MTAs are [[Msmtp]] and [[SSMTP]], but perhaps the easiest [[dma]] will suffice. Common MTUs are sendmail and [[Postfix]]. It is enough to simply configure [[S-nail]] if you do not want anything else, but you will need to follow [//dominicm.com/configure-email-notifications-on-arch-linux/ these instructions].
 +
 
 +
The {{ic|-M test}} option causes a test email to be sent each time the smartd daemon starts:
 +
 
 +
{{hc|/etc/smartd.conf|
 +
DEVICESCAN -m address@domain.com -M test
 +
}}
 +
 
 +
Emails can take quite a while to be delivered. To make sure you are warned immediately if your hard drive fails, you may also define a script to be executed in addition to the email sending:
 +
 
 +
{{hc|/etc/smartd.conf|
 +
DEVICESCAN -m address@domain.com -M exec /usr/local/bin/smartdnotify
 +
}}
 +
 
 +
To send an email and a system notification, put something like this into {{ic|/usr/local/bin/smartdnotify}}:
 +
 
 +
#!/bin/sh
 +
# Send email
 +
echo "$SMARTD_MESSAGE" | mail -s "$SMARTD_FAILTYPE" "$SMARTD_ADDRESS"
 +
# Notify user
 +
wall "$SMARTD_MESSAGE"
 +
 
 +
If you are running a desktop environment, you might also prefer having a popup to appear on your desktop. In this case, you can use this script (replace {{ic|''X_user''}} and {{ic|''X_userid''}} with the user and userid running X respectively) :
 +
 
 +
{{hc|/usr/local/bin/smartdnotify|2=
 +
#!/bin/sh
 +
 
 +
sudo -u ''X_user'' DISPLAY=:0 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/''X_userid''/bus notify-send "S.M.A.R.T Error ($SMARTD_FAILTYPE)" "$SMARTD_MESSAGE" --icon=dialog-warning
 +
}}
 +
 
 +
This requires {{Pkg|libnotify}} and a compatible desktop environment. See [[Desktop notifications]] for more details.
 +
 
 +
You can also put your custom scripts into {{ic|/usr/share/smartmontools/smartd_warning.d/}}:
 +
 
 +
This scripts notifies every logged in users on the system via libnotify.
 +
 
 +
{{hc|/usr/share/smartmontools/smartd_warning.d/smartdnotify|2=
 +
#!/bin/sh
 +
 
 +
IFS=$'\n'
 +
for LINE in `w -hs`
 +
do
 +
    USER=`echo $LINE <nowiki>|</nowiki> awk '{print $1}'`
 +
    USER_ID=`id -u $USER`
 +
    DISP_ID=`echo $LINE <nowiki>|</nowiki> awk '{print $8}'`
 +
    sudo -u $USER DISPLAY=$DISP_ID DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$USER_ID/bus notify-send "S.M.A.R.T Error ($SMARTD_FAILTYPE)" "$SMARTD_MESSAGE" --icon=dialog-warning
 +
done
 +
}}
 +
 
 +
This script requires {{Pkg|libnotify}} and {{Pkg|procps-ng}} and a compatible desktop environment.
 +
 
 +
You can execute your custom scripts with {{hc|/etc/smartd.conf|DEVICESCAN -m @smartdnotify}}
 +
 
 +
==== Power management ====
 +
 
 +
If you use a computer under control of power management, you should instruct smartd how to handle disks in low power mode. Usually, in response to SMART commands issued by smartd, the disk platters are spun up. So if this option is not used, then a disk which is in a low-power mode may be spun up and put into a higher-power mode when it is periodically polled by smartd.
 +
 
 +
{{hc|/etc/smartd.conf|
 +
DEVICESCAN -n standby,15,q
 +
}}
 +
 
 +
More info on [http://www.smartmontools.org/wiki/Powermode smartmontools wiki].
 +
 
 +
On some devices the -n does not work. You get the following error message in syslog:
 +
 
 +
{{hc|journalctl -u smartd|
 +
CHECK POWER MODE: incomplete response, ATA output registers missing
 +
Device: /dev/sdb [SAT], no ATA CHECK POWER STATUS support, ignoring -n Directive
 +
}}
 +
 
 +
As an alternative you can user -i option of smartd. It controls how often smartd spins the disks up to check their status. Default is 30 minutes. To change it create and edit {{ic|/etc/default/smartmontools}}.
 +
 
 +
{{hc|/etc/default/smartmontools|
 +
output=SMARTD_ARGS="-i 10800"  Check status every 10800 seconds (3 hours)
 +
}}
 +
 
 +
For more info see {{man|8|smartd}}.
 +
 
 +
==== Schedule self-tests ====
 +
 
 +
smartd can tell disks to perform self-tests on a schedule. The following {{ic|/etc/smartd.conf}} configuration will start a short self-test every day between 2-3am, and an extended self test weekly on Saturdays between 3-4am:
 +
 
 +
{{hc|/etc/smartd.conf|
 +
DEVICESCAN -s (S/../.././02&#124;L/../../6/03)
 +
}}
 +
 
 +
==== Alert on temperature changes ====
 +
 
 +
smartd can track disk temperatures and alert if they rise too quickly or hit a high limit. The following will log changes of 4 degrees or more, log when temp reaches 35 degrees, and log/email a warning when temp reaches 40:
 +
 
 +
{{hc|/etc/smartd.conf|
 +
DEVICESCAN -W 4,35,40
 +
}}
 +
 
 +
{{Tip|
 +
* You can determine the current disk temperature with the command {{ic|smartctl -A /dev/<device> {{!}} grep Temperature_Celsius}}
 +
* If you have some disks that run a lot hotter/cooler than others, remove {{ic|DEVICESCAN}} and define a separate configuration for each device with appropriate temperature settings.
 +
}}
 +
 
 +
==== Complete smartd.conf example ====
 +
 
 +
Putting together all of the above gives the following example configuration:
 +
 
 +
* {{ic|DEVICESCAN}} smartd scans for disks and monitors all it finds
 +
* {{ic|-a}} monitor all attributes
 +
* {{ic|-o on}} enable automatic offline data collection
 +
* {{ic|-S on}} enable automatic attribute autosave
 +
* {{ic|-n standby,q}} do not check if disk is in standby, and suppress log message to that effect so as not to cause a write to disk
 +
* {{ic|-s ...}} schedule short and long self-tests
 +
* {{ic|-W ...}} monitor temperature
 +
* {{ic|-m ...}} mail alerts
 +
 
 +
{{hc|/etc/smartd.conf|
 +
DEVICESCAN -a -o on -S on -n standby,q -s (S/../.././02&#124;L/../../6/03) -W 4,35,40 -m <username or email>
 +
}}
 +
 
 +
== Console Applications ==
 +
 
 +
* {{App|skdump|utility to monitor and manage SMART devices to monitor and report hard disk drive health.|http://0pointer.de/blog/projects/being-smart.html|{{Pkg|libatasmart}}}}
 +
 
 +
== GUI Applications ==
 +
 
 +
* {{App|DisKMonitor|KDE tools to monitor SMART devices and MDRaid health status.|https://github.com/papylhomme/diskmonitor|{{AUR|diskmonitor}}}}
 +
* {{App|Gnome Disks|GNOME frontend which uses {{Pkg|libatasmart}} to monitor and report hard disk drive health (part of gnome desktop which also incorporates gsd-disk-utility-notify).|https://gitlab.gnome.org/GNOME/gnome-disk-utility/|{{Pkg|gnome-disk-utility}}}}
 +
* {{App|GSmartControl|GNOME frontend for the smartctl hard disk drive health inspection tool.|https://gsmartcontrol.sourceforge.io/|{{Pkg|gsmartcontrol}}}}
 +
 
 +
== See also ==
 +
 
 +
* [https://www.smartmontools.org/ Smartmontools Homepage]
 +
* [https://help.ubuntu.com/community/Smartmontools Smartmontools on Ubuntu Wiki]
 +
* [[Gentoo: smartmontools]]

Latest revision as of 21:06, 19 October 2019

S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) is a supplementary component built into many modern storage devices through which devices monitor, store, and analyze the health of their operation. Statistics are collected (temperature, number of reallocated sectors, seek errors...) which software can use to measure the health of a device, predict possible device failure, and provide notifications on unsafe values.

Smartmontools

The smartmontools package contains two utility programs for analyzing and monitoring storage devices: smartctl and smartd. Install the smartmontools package to use these tools.

SMART support must be available and enabled on each storage device to effectively use these tools. You can use #smartctl to check for and enable SMART support. That done, you can manually #Run a test and #View test results, or you can use #smartd to automatically run tests and email notifications.

smartctl

smartctl is a command-line tool that "controls the Self-Monitoring, Analysis and Reporting Technology (SMART) system built into most ATA/SATA and SCSI/SAS hard drives and solid-state drives."

The -i/--info option prints a variety of information about a device, including whether SMART is available and enabled:

# smartctl --info /dev/sda | grep 'SMART support is:'
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

If SMART is available but not enabled, you can enable it:

# smartctl --smart=on /dev/<device>

You may need to specify a device type. For example, specifying --device=ata tells smartctl that the device type is ATA, and this prevents smartctl from issuing SCSI commands to that device.

Run a test

There are three types of self-tests that a device can execute (all are safe to user data):

  • Short: runs tests that have a high probability of detecting device problems,
  • Extended or Long: the test is the same as the short check but with no time limit and with complete disk surface examination,
  • Conveyance: identifies if damage incurred during transportation of the device.

The -c/--capabilities flag prints which tests a device supports and the approximate execution time of each test. For example:

# smartctl -c /dev/sda
...
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        (  74) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
...

Use -t/--test=<test_name> flag to run a test:

# smartctl -t short /dev/<device>
# smartctl -t long /dev/<device>
# smartctl -t conveyance /dev/<device>

View test results

You can view a device's overall health with the -H flag. "If the device reports failing health status, this means either that the device has already failed, or that it is predicting its own failure within the next 24 hours. If this happens […] get your data off the disk and to someplace safe as soon as you can."

# smartctl -H /dev/<device>

You can also view a list of recent test results and detailed information about a device:

# smartctl -l selftest /dev/<device>
# smartctl -a /dev/<device>

smartd

The smartd daemon monitors SMART statuses and emits notifications when something goes wrong. It can be managed with systemd and configured using the /etc/smartd.conf configuration file. The configuration file syntax is esoteric, and this wiki page provides only a quick reference. For more complete information, read the examples and comments within the configuration file, or read smartd.conf(5).

daemon management

To start the daemon, check its status, make it auto-start on system boot and read recent log file entries, simply start/enable the smartd.service systemd unit.

smartd respects all the usual systemctl and journalctl commands. For more information on using systemctl and journalctl, see systemd#Using units and systemd/Journal.

Define the devices to monitor

To monitor for all possible SMART errors on all disks, the following setting must be added in the configuration file.

/etc/smartd.conf
DEVICESCAN -a

Note this is the default smartd configuration and the -a parameter, which is the default parameter, may be omitted.

To monitor for all possible SMART errors on /dev/sda and /dev/sdb, and ignore all other devices:

/etc/smartd.conf
/dev/sda -a
/dev/sdb -a

To monitor for all possible SMART errors on externally connected disks (USB-backup disks spring to mind) it is prudent to tell smartd the UUID of the device since the /dev/sdX of the drive might change during a reboot.

First, you will have to get the UUID of the disk to monitor: ls -lah /dev/disk/by-uuid/ now look for the disk you want to Monitor

ls -lah /dev/disk/by-uuid/
lrwxrwxrwx 1 root root   9 Nov  5 22:41 820cdd8a-866a-444d-833c-1edb0f4becac -> ../../sde
lrwxrwxrwx 1 root root  10 Nov  5 22:41 b51b87f3-425e-4fe7-883f-f4ff1689189e -> ../../sdf2
lrwxrwxrwx 1 root root   9 Nov  5 22:42 ea2199dd-8f9f-4065-a7ba-71bde11a462c -> ../../sda
lrwxrwxrwx 1 root root  10 Nov  5 22:41 fe9e886a-8031-439f-a909-ad06c494fadb -> ../../sdf1

I know that my USB disk attached to /dev/sde during boot. Now to tell smartd to monitor that disk simply use the /dev/disk/by-uuid/ path.

/etc/smartd.conf
/dev/disk/by-uuid/820cdd8a-866a-444d-833c-1edb0f4becac -a

Now your USB disk will be monitored even if the /dev/sdX path changes during reboot.

Notifying potential problems

To have an email sent when a failure or new error occurs, use the -m option:

/etc/smartd.conf
DEVICESCAN -m address@domain.com

To be able to send the email externally (i.e. not to the root mail account) a MTA (Mail Transport Agent) or a MUA (Mail User Agent) will need to be installed and configured. Common MTAs are Msmtp and SSMTP, but perhaps the easiest dma will suffice. Common MTUs are sendmail and Postfix. It is enough to simply configure S-nail if you do not want anything else, but you will need to follow these instructions.

The -M test option causes a test email to be sent each time the smartd daemon starts:

/etc/smartd.conf
DEVICESCAN -m address@domain.com -M test

Emails can take quite a while to be delivered. To make sure you are warned immediately if your hard drive fails, you may also define a script to be executed in addition to the email sending:

/etc/smartd.conf
DEVICESCAN -m address@domain.com -M exec /usr/local/bin/smartdnotify

To send an email and a system notification, put something like this into /usr/local/bin/smartdnotify:

#!/bin/sh
# Send email
echo "$SMARTD_MESSAGE" | mail -s "$SMARTD_FAILTYPE" "$SMARTD_ADDRESS"
# Notify user
wall "$SMARTD_MESSAGE"

If you are running a desktop environment, you might also prefer having a popup to appear on your desktop. In this case, you can use this script (replace X_user and X_userid with the user and userid running X respectively) :

/usr/local/bin/smartdnotify
#!/bin/sh

sudo -u X_user DISPLAY=:0 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/X_userid/bus notify-send "S.M.A.R.T Error ($SMARTD_FAILTYPE)" "$SMARTD_MESSAGE" --icon=dialog-warning

This requires libnotify and a compatible desktop environment. See Desktop notifications for more details.

You can also put your custom scripts into /usr/share/smartmontools/smartd_warning.d/:

This scripts notifies every logged in users on the system via libnotify.

/usr/share/smartmontools/smartd_warning.d/smartdnotify
#!/bin/sh

IFS=$'\n'
for LINE in `w -hs`
do
    USER=`echo $LINE | awk '{print $1}'`
    USER_ID=`id -u $USER`
    DISP_ID=`echo $LINE | awk '{print $8}'`
    sudo -u $USER DISPLAY=$DISP_ID DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$USER_ID/bus notify-send "S.M.A.R.T Error ($SMARTD_FAILTYPE)" "$SMARTD_MESSAGE" --icon=dialog-warning
done

This script requires libnotify and procps-ng and a compatible desktop environment.

You can execute your custom scripts with

/etc/smartd.conf
DEVICESCAN -m @smartdnotify

Power management

If you use a computer under control of power management, you should instruct smartd how to handle disks in low power mode. Usually, in response to SMART commands issued by smartd, the disk platters are spun up. So if this option is not used, then a disk which is in a low-power mode may be spun up and put into a higher-power mode when it is periodically polled by smartd.

/etc/smartd.conf
DEVICESCAN -n standby,15,q

More info on smartmontools wiki.

On some devices the -n does not work. You get the following error message in syslog:

journalctl -u smartd
CHECK POWER MODE: incomplete response, ATA output registers missing
Device: /dev/sdb [SAT], no ATA CHECK POWER STATUS support, ignoring -n Directive

As an alternative you can user -i option of smartd. It controls how often smartd spins the disks up to check their status. Default is 30 minutes. To change it create and edit /etc/default/smartmontools.

/etc/default/smartmontools
SMARTD_ARGS="-i 10800"  Check status every 10800 seconds (3 hours)

For more info see smartd(8).

Schedule self-tests

smartd can tell disks to perform self-tests on a schedule. The following /etc/smartd.conf configuration will start a short self-test every day between 2-3am, and an extended self test weekly on Saturdays between 3-4am:

/etc/smartd.conf
DEVICESCAN -s (S/../.././02|L/../../6/03)

Alert on temperature changes

smartd can track disk temperatures and alert if they rise too quickly or hit a high limit. The following will log changes of 4 degrees or more, log when temp reaches 35 degrees, and log/email a warning when temp reaches 40:

/etc/smartd.conf
DEVICESCAN -W 4,35,40
Tip:
  • You can determine the current disk temperature with the command smartctl -A /dev/<device> | grep Temperature_Celsius
  • If you have some disks that run a lot hotter/cooler than others, remove DEVICESCAN and define a separate configuration for each device with appropriate temperature settings.

Complete smartd.conf example

Putting together all of the above gives the following example configuration:

  • DEVICESCAN smartd scans for disks and monitors all it finds
  • -a monitor all attributes
  • -o on enable automatic offline data collection
  • -S on enable automatic attribute autosave
  • -n standby,q do not check if disk is in standby, and suppress log message to that effect so as not to cause a write to disk
  • -s ... schedule short and long self-tests
  • -W ... monitor temperature
  • -m ... mail alerts
/etc/smartd.conf
DEVICESCAN -a -o on -S on -n standby,q -s (S/../.././02|L/../../6/03) -W 4,35,40 -m <username or email>

Console Applications

  • skdump — utility to monitor and manage SMART devices to monitor and report hard disk drive health.
http://0pointer.de/blog/projects/being-smart.html || libatasmart

GUI Applications

  • DisKMonitor — KDE tools to monitor SMART devices and MDRaid health status.
https://github.com/papylhomme/diskmonitor || diskmonitorAUR
  • Gnome Disks — GNOME frontend which uses libatasmart to monitor and report hard disk drive health (part of gnome desktop which also incorporates gsd-disk-utility-notify).
https://gitlab.gnome.org/GNOME/gnome-disk-utility/ || gnome-disk-utility
  • GSmartControl — GNOME frontend for the smartctl hard disk drive health inspection tool.
https://gsmartcontrol.sourceforge.io/ || gsmartcontrol

See also