1SMARTD.CONF(5) 2016-09-28 SMARTD.CONF(5)
2
6 smartd.conf - SMART Disk Monitoring Daemon Configuration File
7
10 /etc/smartd.conf
11
14 smartmontools-5.43 2016-09-28 r4347
15
18 [This man page is generated for the Linux version of smartmontools. It
19 does not contain info specific to other platforms.]
20 /etc/smartd.conf is the configuration file for the smartd daemon, which
22 monitors the Self-Monitoring, Analysis and Reporting Technology (SMART)
23 system built into many ATA-3 and later ATA, IDE and SCSI-3 hard drives.
24 If the configuration file /etc/smartd.conf is present, smartd reads it
26 at startup, before fork(2)ing into the background. If smartd subse‐
27 quently receives a HUP signal, it will then re-read the configuration
28 file. If smartd is running in debug mode, then an INT signal will also
29 make it re-read the configuration file. This signal can be generated by
30 typing <CONTROL-C> in the terminal window where smartd is running.
31
34 In the absence of a configuration file smartd will try to open all
35 available devices. Under linux smartd will try to open the 20 ATA
36 devices /dev/hd[a-t] and the 26 SCSI devices /dev/sd[a-z].
37 This can be annoying if you have an ATA or SCSI device that hangs or
39 misbehaves when receiving SMART commands. Even if this causes no prob‐
40 lems, you may be annoyed by the string of error log messages about
41 block-major devices that can´t be found, and SCSI devices that can´t be
42 opened.
43 One can avoid this problem, and gain more control over the types of
45 events monitored by smartd, by using the configuration file
46 /etc/smartd.conf. This file contains a list of devices to monitor,
47 with one device per line. An example file is included with the smart‐
48 montools distribution. You will find this sample configuration file in
49 /usr/share/doc/smartmontools/. For security, the configuration file
50 should not be writable by anyone but root. The syntax of the file is as
51 follows:
52 · There should be one device listed per line, although you may have
54 lines that are entirely comments or white space.
55 · Any text following a hash sign ´#´ and up to the end of the line is
57 taken to be a comment, and ignored.
58 · Lines may be continued by using a backslash ´\´ as the last non-
60 whitespace or non-comment item on a line.
61 · Note: a line whose first character is a hash sign ´#´ is treated as
63 a white-space blank line, not as a non-existent line, and will end
64 a continuation line.
65 Here is an example configuration file. It´s for illustrative purposes
67 only; please don´t copy it onto your system without reading to the end
68 of the DIRECTIVES Section below!
69 ################################################
71 # This is an example smartd startup config file
72 # /etc/smartd.conf for monitoring three
73 # ATA disks, three SCSI disks, six ATA disks
74 # behind two 3ware controllers, three SATA disks
75 # directly connected to the HighPoint Rocket-
76 # RAID controller, two SATA disks connected to
77 # the HighPoint RocketRAID controller via a pmport
78 # device, four SATA disks connected to an Areca
79 # RAID controller, and one SATA disk.
80 #
81 # First ATA disk on two different interfaces. On
82 # the second disk, start a long self-test every
83 # Sunday between 3 and 4 am.
84 #
85 /dev/hda -a -m admin@example.com,root@localhost
86 /dev/hdc -a -I 194 -I 5 -i 12 -s L/../../7/03
87 #
88 # SCSI disks. Send a TEST warning email to admin on
89 # startup.
90 #
91 /dev/sda
92 /dev/sdb -m admin@example.com -M test
93 #
94 # Strange device. It´s SCSI. Start a scheduled
95 # long self test between 5 and 6 am Monday/Thursday
96 /dev/weird -d scsi -s L/../../(1|4)/05
97 #
98 # An ATA disk may appear as a SCSI device to the
99 # OS. If a SCSI to ATA Translation (SAT) layer
100 # is between the OS and the device then this can be
101 # flagged with the '-d sat' option. This situation
102 # may become common with SATA disks in SAS and FC
103 # environments.
104 /dev/sda -a -d sat
105 #
106 # Three disks connected to a MegaRAID controller
107 # Start short self-tests daily between 1-2, 2-3, and
108 # 3-4 am.
109 /dev/sda -d megaraid,0 -a -s S/../.././01
110 /dev/sda -d megaraid,1 -a -s S/../.././02
111 /dev/sda -d megaraid,2 -a -s S/../.././03
112 #
113 # Four ATA disks on a 3ware 6/7/8000 controller.
114 # Start short self-tests daily between midnight and 1am,
115 # 1-2, 2-3, and 3-4 am. Starting with the Linux 2.6
116 # kernel series, /dev/sdX is deprecated in favor of
117 # /dev/tweN. For example replace /dev/sdc by /dev/twe0
118 # and /dev/sdd by /dev/twe1.
119 /dev/sdc -d 3ware,0 -a -s S/../.././00
120 /dev/sdc -d 3ware,1 -a -s S/../.././01
121 /dev/sdd -d 3ware,2 -a -s S/../.././02
122 /dev/sdd -d 3ware,3 -a -s S/../.././03
123 #
124 # Two ATA disks on a 3ware 9000 controller.
125 # Start long self-tests Sundays between midnight and
126 # 1am and 2-3 am
127 /dev/twa0 -d 3ware,0 -a -s L/../../7/00
128 /dev/twa0 -d 3ware,1 -a -s L/../../7/02
129 #
130 # Two SATA (not SAS) disks on a 3ware 9750 controller.
131 # Start long self-tests Sundays between midnight and
132 # 1am and 2-3 am
133 /dev/twl0 -d 3ware,0 -a -s L/../../7/00
134 /dev/twl0 -d 3ware,1 -a -s L/../../7/02
135 #
136 # Three SATA disks on a HighPoint RocketRAID controller.
137 # Start short self-tests daily between 1-2, 2-3, and
138 # 3-4 am.
139 # under Linux
140 /dev/sde -d hpt,1/1 -a -s S/../.././01
141 /dev/sde -d hpt,1/2 -a -s S/../.././02
142 /dev/sde -d hpt,1/3 -a -s S/../.././03
143 #
144 # Two SATA disks connected to a HighPoint RocketRAID
145 # via a pmport device. Start long self-tests Sundays
146 # between midnight and 1am and 2-3 am.
147 # under Linux
148 /dev/sde -d hpt,1/4/1 -a -s L/../../7/00
149 /dev/sde -d hpt,1/4/2 -a -s L/../../7/02
150 # Three SATA disks connected to an Areca
151 # RAID controller. Start long self-tests Sundays
152 # between midnight and 3 am.
153 /dev/sg2 -d areca,1 -a -s L/../../7/00
154 /dev/sg2 -d areca,2 -a -s L/../../7/01
155 /dev/sg2 -d areca,3 -a -s L/../../7/02
156 #
157 # The following line enables monitoring of the
158 # ATA Error Log and the Self-Test Error Log.
159 # It also tracks changes in both Prefailure
160 # and Usage Attributes, apart from Attributes
161 # 9, 194, and 231, and shows continued lines:
162 #
163 /dev/hdd -l error \
164 -l selftest \
165 -t \ # Attributes not tracked:
166 -I 194 \ # temperature
167 -I 231 \ # also temperature
168 -I 9 # power-on hours
169 #
170 ################################################
171
174 If a non-comment entry in the configuration file is the text string
175 DEVICESCAN in capital letters, then smartd will ignore any remaining
176 lines in the configuration file, and will scan for devices. DEVICESCAN
177 may optionally be followed by Directives that will apply to all devices
178 that are found in the scan. Please see below for additional details.
179 [NEW EXPERIMENTAL SMARTD FEATURE] If an entry in the configuration file
181 starts with DEFAULT instead of a device name, then all directives in
182 this entry are set as defaults for the next device entries.
183 This configuration:
185 DEFAULT -a -R5! -W 2,40,45 -I 194 -s L/../../7/00 -m admin@example.com
187 /dev/sda
188 /dev/sdb
189 /dev/sdc
190 DEFAULT -H -m admin@example.com
191 /dev/sdd
192 /dev/sde -d removable
193 has the same effect as:
195 /dev/sda -a -R5! -W 2,40,45 -I 194 -s L/../../7/00 -m admin@example.com
197 /dev/sdb -a -R5! -W 2,40,45 -I 194 -s L/../../7/00 -m admin@example.com
198 /dev/sdc -a -R5! -W 2,40,45 -I 194 -s L/../../7/00 -m admin@example.com
199 /dev/sdd -H -m admin@example.com
200 /dev/sde -d removable -H -m admin@example.com
201 The following are the Directives that may appear following the device
205 name or DEVICESCAN or DEFAULT on any line of the /etc/smartd.conf con‐
206 figuration file. Note that these are NOT command-line options for
207 smartd. The Directives below may appear in any order, following the
208 device name.
209 For an ATA device, if no Directives appear, then the device will be
211 monitored as if the ´-a´ Directive (monitor all SMART properties) had
212 been given.
213 If a SCSI disk is listed, it will be monitored at the maximum imple‐
215 mented level: roughly equivalent to using the ´-H -l selftest´ options
216 for an ATA disk. So with the exception of ´-d´, ´-m´, ´-l selftest´,
217 ´-s´, and ´-M´, the Directives below are ignored for SCSI disks. For
218 SCSI disks, the ´-m´ Directive sends a warning email if the SMART sta‐
219 tus indicates a disk failure or problem, if the SCSI inquiry about disk
220 status fails, or if new errors appear in the self-test log.
221 If a 3ware controller is used then the corresponding SCSI (/dev/sd?) or
223 character device (/dev/twe?, /dev/twa? or /dev/twl?) must be listed,
224 along with the ´-d 3ware,N´ Directive (see below). The individual ATA
225 disks hosted by the 3ware controller appear to smartd as normal ATA
226 devices. Hence all the ATA directives can be used for these disks (but
227 see note below).
228 If an Areca controller is used then the corresponding device (SCSI
230 /dev/sg? on Linux or /dev/arcmsr0 on FreeBSD) must be listed, along
231 with the ´-d areca,N´ Directive (see below). The individual SATA disks
232 hosted by the Areca controller appear to smartd as normal ATA devices.
233 Hence all the ATA directives can be used for these disks. Areca
234 firmware version 1.46 or later which supports smartmontools must be
235 used; Please see the smartctl(8) man page for further details.
236 -d TYPE
238 Specifies the type of the device. The valid arguments to this
239 directive are:
240 auto - attempt to guess the device type from the device name or
242 from controller type info provided by the operating system or
243 from a matching USB ID entry in the drive database. This is the
244 default.
245 ata - the device type is ATA. This prevents smartd from issuing
247 SCSI commands to an ATA device.
248 scsi - the device type is SCSI. This prevents smartd from issu‐
250 ing ATA commands to a SCSI device.
251 sat[,auto][,N] - the device type is SCSI to ATA Translation
253 (SAT). This is for ATA disks that have a SCSI to ATA Transla‐
254 tion (SAT) Layer (SATL) between the disk and the operating sys‐
255 tem. SAT defines two ATA PASS THROUGH SCSI commands, one 12
256 bytes long and the other 16 bytes long. The default is the 16
257 byte variant which can be overridden with either ´-d sat,12´ or
258 ´-d sat,16´.
259 [NEW EXPERIMENTAL SMARTD FEATURE] If ´-d sat,auto´ is specified,
261 device type SAT (for ATA/SATA disks) is only used if the SCSI
262 INQUIRY data reports a SATL (VENDOR: "ATA "). Otherwise
263 device type SCSI (for SCSI/SAS disks) is used.
264 usbcypress - this device type is for ATA disks that are behind a
266 Cypress USB to PATA bridge. This will use the ATACB proprietary
267 scsi pass through command. The default SCSI operation code is
268 0x24, but although it can be overridden with ´-d usbcy‐
269 press,0xN´, where N is the scsi operation code, you're running
270 the risk of damage to the device or filesystems on it.
271 usbjmicron - this device type is for SATA disks that are behind
273 a JMicron USB to PATA/SATA bridge. The 48-bit ATA commands
274 (required e.g. for ´-l xerror´, see below) do not work with all
275 of these bridges and are therefore disabled by default. These
276 commands can be enabled by ´-d usbjmicron,x´. If two disks are
277 connected to a bridge with two ports, an error message is
278 printed if no PORT is specified. The port can be specified by
279 ´-d usbjmicron[,x],PORT´ where PORT is 0 (master) or 1 (slave).
280 This is not necessary if the device uses a port multiplier to
281 connect multiple disks to one port. The disks appear under sep‐
282 arate /dev/ice names then. CAUTION: Specifying ´,x´ for a
283 device which does not support it results in I/O errors and may
284 disconnect the drive. The same applies if the specified PORT
285 does not exist or is not connected to a disk.
286 usbsunplus - this device type is for SATA disks that are behind
288 a SunplusIT USB to SATA bridge.
289 marvell - [Linux only] interact with SATA disks behind Marvell
291 chip-set controllers (using the Marvell rather than libata
292 driver).
293 megaraid,N - [Linux only] the device consists of one or more
295 SCSI/SAS disks connected to a MegaRAID controller. The non-neg‐
296 ative integer N (in the range of 0 to 127 inclusive) denotes
297 which disk on the controller is monitored. This interface will
298 also work for Dell PERC controllers. In log files and email
299 messages this disk will be identified as megaraid_disk_XXX with
300 XXX in the range from 000 to 127 inclusive. Please see the
301 smartctl(8) man page for further details.
302 3ware,N - [FreeBSD and Linux only] the device consists of one or
304 more ATA disks connected to a 3ware RAID controller. The non-
305 negative integer N (in the range from 0 to 127 inclusive)
306 denotes which disk on the controller is monitored. In log files
307 and email messages this disk will be identified as
308 3ware_disk_XXX with XXX in the range from 000 to 127 inclusive.
309 Note that while you may use any of the 3ware SCSI logical
311 devices /dev/tw* to address any of the physical disks (3ware
312 ports), error and log messages will make the most sense if you
313 always list the 3ware SCSI logical device corresponding to the
314 particular physical disks. Please see the smartctl(8) man page
315 for further details.
316 areca,N - [FreeBSD, Linux, Windows and Cygwin only] the device
318 consists of one or more SATA disks connected to an Areca SATA
319 RAID controller. The positive integer N (in the range from 1 to
320 24 inclusive) denotes which disk on the controller is monitored.
321 In log files and email messages this disk will be identifed as
322 areca_disk_XX with XX in the range from 01 to 24 inclusive.
323 Please see the smartctl(8) man page for further details.
324 areca,N/E - [FreeBSD, Linux, Windows and Cygwin only] [NEW
326 EXPERIMENTAL SMARTD FEATURE] the device consists of one or more
327 SATA disks connected to an Areca SAS RAID controller. The inte‐
328 ger N (range 1 to 128) denotes the channel (slot) and E (range 1
329 to 8) denotes the enclosure. Important: This requires upcoming
330 Areca SAS controller firmware version 1.51 or a recent beta ver‐
331 sion.
332 cciss,N - [FreeBSD and Linux only] the device consists of one or
334 more SCSI/SAS or SATA disks connected to a cciss RAID con‐
335 troller. The non-negative integer N (in the range from 0 to 15
336 inclusive) denotes which disk on the controller is monitored.
337 In log files and email messages this disk will be identified as
338 cciss_disk_XX with XX in the range from 00 to 15 inclusive.
339 Please see the smartctl(8) man page for further details.
340 hpt,L/M/N - [FreeBSD and Linux only] the device consists of one
342 or more ATA disks connected to a HighPoint RocketRAID con‐
343 troller. The integer L is the controller id, the integer M is
344 the channel number, and the integer N is the PMPort number if it
345 is available. The allowed values of L are from 1 to 4 inclu‐
346 sive, M are from 1 to 16 inclusive and N from 1 to 4 if PMPort
347 available. And also these values are limited by the model of
348 the HighPoint RocketRAID controller. In log files and email
349 messages this disk will be identified as hpt_X/X/X and X/X/X is
350 the same as L/M/N, note if no N indicated, N set to the default
351 value 1. Please see the smartctl(8) man page for further
352 details.
353 removable - the device or its media is removable. This indi‐
355 cates to smartd that it should continue (instead of exiting,
356 which is the default behavior) if the device does not appear to
357 be present when smartd is started. This Directive may be used
358 in conjunction with the other ´-d´ Directives.
359 -n POWERMODE[,N][,q]
361 [ATA only] This ´nocheck´ Directive is used to prevent a disk
362 from being spun-up when it is periodically polled by smartd.
363 ATA disks have five different power states. In order of increas‐
365 ing power consumption they are: ´OFF´, ´SLEEP´, ´STANDBY´,
366 ´IDLE´, and ´ACTIVE´. Typically in the OFF, SLEEP, and STANDBY
367 modes the disk´s platters are not spinning. But usually, in
368 response to SMART commands issued by smartd, the disk platters
369 are spun up. So if this option is not used, then a disk which
370 is in a low-power mode may be spun up and put into a
371 higher-power mode when it is periodically polled by smartd.
372 Note that if the disk is in SLEEP mode when smartd is started,
374 then it won't respond to smartd commands, and so the disk won't
375 be registered as a device for smartd to monitor. If a disk is in
376 any other low-power mode, then the commands issued by smartd to
377 register the disk will probably cause it to spin-up.
378 The ´-n´ (nocheck) Directive specifies if smartd´s periodic
380 checks should still be carried out when the device is in a
381 low-power mode. It may be used to prevent a disk from being
382 spun-up by periodic smartd polling. The allowed values of POW‐
383 ERMODE are:
384 never - smartd will poll (check) the device regardless of its
386 power mode. This may cause a disk which is spun-down to be
387 spun-up when smartd checks it. This is the default behavior if
388 the '-n' Directive is not given.
389 sleep - check the device unless it is in SLEEP mode.
391 standby - check the device unless it is in SLEEP or STANDBY
393 mode. In these modes most disks are not spinning, so if you
394 want to prevent a laptop disk from spinning up each time that
395 smartd polls, this is probably what you want.
396 idle - check the device unless it is in SLEEP, STANDBY or IDLE
398 mode. In the IDLE state, most disks are still spinning, so this
399 is probably not what you want.
400 Maximum number of skipped checks (in a row) can be specified by
402 appending positive number ´,N´ to POWERMODE (like ´-n
403 standby,15´). After N checks are skipped in a row, powermode is
404 ignored and the check is performed anyway.
405 When a periodic test is skipped, smartd normally writes an
407 informal log message. The message can be suppressed by appending
408 the option ´,q´ to POWERMODE (like ´-n standby,q´). This pre‐
409 vents a laptop disk from spinning up due to this message.
410 Both ´,N´ and ´,q´ can be specified together.
412 -T TYPE
414 Specifies how tolerant smartd should be of SMART command fail‐
415 ures. The valid arguments to this Directive are:
416 normal - do not try to monitor the disk if a mandatory SMART
418 command fails, but continue if an optional SMART command fails.
419 This is the default.
420 permissive - try to monitor the disk even if it appears to lack
422 SMART capabilities. This may be required for some old disks
423 (prior to ATA-3 revision 4) that implemented SMART before the
424 SMART standards were incorporated into the ATA/ATAPI Specifica‐
425 tions. This may also be needed for some Maxtor disks which fail
426 to comply with the ATA Specifications and don't properly indi‐
427 cate support for error- or self-test logging.
428 [Please see the smartctl -T command-line option.]
430 -o VALUE
432 [ATA only] Enables or disables SMART Automatic Offline Testing
433 when smartd starts up and has no further effect. The valid
434 arguments to this Directive are on and off.
435 The delay between tests is vendor-specific, but is typically
437 four hours.
438 Note that SMART Automatic Offline Testing is not part of the ATA
440 Specification. Please see the smartctl -o command-line option
441 documentation for further information about this feature.
442 -S VALUE
444 Enables or disables Attribute Autosave when smartd starts up and
445 has no further effect. The valid arguments to this Directive
446 are on and off. Also affects SCSI devices. [Please see the
447 smartctl -S command-line option.]
448 -H [ATA only] Check the SMART health status of the disk. If any
450 Prefailure Attributes are less than or equal to their threshold
451 values, then disk failure is predicted in less than 24 hours,
452 and a message at loglevel ´LOG_CRIT´ will be logged to syslog.
453 [Please see the smartctl -H command-line option.]
454 -l TYPE
456 Reports increases in the number of errors in one of three SMART
457 logs. The valid arguments to this Directive are:
458 error - [ATA only] report if the number of ATA errors reported
460 in the Summary SMART error log has increased since the last
461 check.
462 xerror - [ATA only] report if the number of ATA errors reported
464 in the Extended Comprehensive SMART error log has increased
465 since the last check.
466 If both ´-l error´ and ´-l xerror´ are specified, smartd checks
468 the maximum of both values.
469 [Please see the smartctl -l xerror command-line option.]
471 selftest - report if the number of failed tests reported in the
473 SMART Self-Test Log has increased since the last check, or if
474 the timestamp associated with the most recent failed test has
475 increased. Note that such errors will only be logged if you run
476 self-tests on the disk (and it fails a test!). Self-Tests can
477 be run automatically by smartd: please see the ´-s´ Directive
478 below. Self-Tests can also be run manually by using the
479 ´-t short´ and ´-t long´ options of smartctl and the results of
480 the testing can be observed using the smartctl ´-l selftest´
481 command-line option. [Please see the smartctl -l and -t com‐
482 mand-line options.]
483 [ATA only] Failed self-tests outdated by a newer successful
485 extended self-test are ignored. The warning email counter is
486 reset if the number of failed self tests dropped to 0. This
487 typically happens when an extended self-test is run after all
488 bad sectors have been reallocated.
489 offlinests[,ns] - [ATA only] report if the Offline Data Collec‐
491 tion status has changed since the last check. The report will
492 be logged as LOG_CRIT if the new status indicates an error.
493 With some drives the status often changes, therefore ´-l
494 offlinests´ is not enabled by '-a´ Directive. Appending ´,ns´
495 (no standby) to this directive is not implemented on Linux.
496 selfteststs[,ns] - [ATA only] report if the Self-Test execution
498 status has changed since the last check. The report will be
499 logged as LOG_CRIT if the new status indicates an error.
500 Appending ´,ns´ (no standby) to this directive is not imple‐
501 mented on Linux.
502 scterc,READTIME,WRITETIME - [ATA only] sets the SCT Error Recov‐
504 ery Control settings to the specified values (deciseconds) when
505 smartd starts up and has no further effect. Values of 0 disable
506 the feature, other values less than 65 are probably not sup‐
507 ported. For RAID configurations, this is typically set to 70,70
508 deciseconds. [Please see the smartctl -l scterc command-line
509 option.]
510 -e NAME[,VALUE]
513 [NEW EXPERIMENTAL SMARTD FEATURE] Sets non-SMART device settings
514 when smartd starts up and has no further effect. [Please see
515 the smartctl --set command-line option.] Valid arguments are:
516 aam,[N|off] - [ATA only] Sets the Automatic Acoustic Management
518 (AAM) feature.
519 apm,[N|off] - [ATA only] Sets the Advanced Power Management
521 (APM) feature.
522 lookahead,[on|off] - [ATA only] Sets the read look-ahead fea‐
524 ture.
525 security-freeze - [ATA only] Sets ATA Security feature to frozen
527 mode.
528 standby,[N|off] - [ATA only] Sets the standby (spindown) timer
530 and places the drive in the IDLE mode.
531 wcache,[on|off] - [ATA only] Sets the volatile write cache fea‐
533 ture.
534 -s REGEXP
537 Run Self-Tests or Offline Immediate Tests, at scheduled times.
538 A Self- or Offline Immediate Test will be run at the end of
539 periodic device polling, if all 12 characters of the string
540 T/MM/DD/d/HH match the extended regular expression REGEXP. Here:
541 T is the type of the test. The values that smartd will try to
543 match (in turn) are: ´L´ for a Long Self-Test, ´S´ for a
544 Short Self-Test, ´C´ for a Conveyance Self-Test (ATA only),
545 and ´O´ for an Offline Immediate Test (ATA only). As soon
546 as a match is found, the test will be started and no addi‐
547 tional matches will be sought for that device and that
548 polling cycle.
549 To run scheduled Selective Self-Tests, use ´n´ for next
551 span, ´r´ to redo last span, or ´c´ to continue with next
552 span or redo last span based on status of last test. The
553 LBA range is based on the first span from the last test.
554 See the smartctl -t select,[next|redo|cont] options for fur‐
555 ther info.
556 Some disks (e.g. WD) do not preserve the selective self test
558 log accross power cycles. If state persistence (´-s´
559 option) is enabled, the last test span is preserved by
560 smartd and used if (and only if) the selective self test log
561 is empty.
562 MM is the month of the year, expressed with two decimal digits.
565 The range is from 01 (January) to 12 (December) inclusive.
566 Do not use a single decimal digit or the match will always
567 fail!
568 DD is the day of the month, expressed with two decimal digits.
570 The range is from 01 to 31 inclusive. Do not use a single
571 decimal digit or the match will always fail!
572 d is the day of the week, expressed with one decimal digit.
574 The range is from 1 (Monday) to 7 (Sunday) inclusive.
575 HH is the hour of the day, written with two decimal digits, and
577 given in hours after midnight. The range is 00 (midnight to
578 just before 1am) to 23 (11pm to just before midnight) inclu‐
579 sive. Do not use a single decimal digit or the match will
580 always fail!
581 Some examples follow. In reading these, keep in mind that in
583 extended regular expressions a dot ´.´ matches any single char‐
584 acter, and a parenthetical expression such as ´(A|B|C)´ denotes
585 any one of the three possibilities A, B, or C.
586 To schedule a short Self-Test between 2-3am every morning, use:
588 -s S/../.././02
589 To schedule a long Self-Test between 4-5am every Sunday morning,
590 use:
591 -s L/../../7/04
592 To schedule a long Self-Test between 10-11pm on the first and
593 fifteenth day of each month, use:
594 -s L/../(01|15)/./22
595 To schedule an Offline Immediate test after every midnight, 6am,
596 noon,and 6pm, plus a Short Self-Test daily at 1-2am and a Long
597 Self-Test every Saturday at 3-4am, use:
598 -s (O/../.././(00|06|12|18)|S/../.././01|L/../../6/03)
599 If Long Self-Tests of a large disks take longer than the system
600 uptime, a full disk test can be performed by several Selective
601 Self-Tests. To setup a full test of a 1TB disk within 20 days
602 (one 50GB span each day), run this command once:
603 smartctl -t select,0-99999999 /dev/sda
604 To run the next test spans on Monday-Friday between 12-13am, run
605 smartd with this directive:
606 -s n/../../[1-5]/12
607 Scheduled tests are run immediately following the regularly-
610 scheduled device polling, if the current local date, time, and
611 test type, match REGEXP. By default the regularly-scheduled
612 device polling occurs every thirty minutes after starting
613 smartd. Take caution if you use the ´-i´ option to make this
614 polling interval more than sixty minutes: the poll times may
615 fail to coincide with any of the testing times that you have
616 specified with REGEXP. In this case the test will be run fol‐
617 lowing the next device polling.
618 Before running an offline or self-test, smartd checks to be sure
620 that a self-test is not already running. If a self-test is
621 already running, then this running self test will not be inter‐
622 rupted to begin another test.
623 smartd will not attempt to run any type of test if another test
625 was already started or run in the same hour.
626 To avoid performance problems during system boot, smartd will
628 not attempt to run any scheduled tests following the very first
629 device polling (unless ´-q onecheck´ is specified).
630 Each time a test is run, smartd will log an entry to SYSLOG.
632 You can use these or the '-q showtests' command-line option to
633 verify that you constructed REGEXP correctly. The matching
634 order (L before S before C before O) ensures that if multiple
635 test types are all scheduled for the same hour, the longer test
636 type has precedence. This is usually the desired behavior.
637 If the scheduled tests are used in conjunction with state per‐
639 sistence (´-s´ option), smartd will also try to match the hours
640 since last shutdown (or 90 days at most). If any test would have
641 been started during downtime, the longest (see above) of these
642 tests is run after second device polling.
643 If the ´-n´ directive is used and any test would have been
645 started during disk standby time, the longest of these tests is
646 run when the disk is active again.
647 Unix users: please beware that the rules for extended regular
649 expressions [regex(7)] are not the same as the rules for
650 file-name pattern matching by the shell [glob(7)]. smartd will
651 issue harmless informational warning messages if it detects
652 characters in REGEXP that appear to indicate that you have made
653 this mistake.
654 -m ADD Send a warning email to the email address ADD if the ´-H´, ´-l´,
656 ´-f´, ´-C´, or ´-O´ Directives detect a failure or a new error,
657 or if a SMART command to the disk fails. This Directive only
658 works in conjunction with these other Directives (or with the
659 equivalent default ´-a´ Directive).
660 To prevent your email in-box from getting filled up with warning
662 messages, by default only a single warning will be sent for each
663 of the enabled alert types, ´-H´, ´-l´, ´-f´, ´-C´, or ´-O´ even
664 if more than one failure or error is detected or if the failure
665 or error persists. [This behavior can be modified; see the ´-M´
666 Directive below.]
667 To send email to more than one user, please use the following
669 "comma separated" form for the address:
670 user1@add1,user2@add2,...,userN@addN (with no spaces).
671 To test that email is being sent correctly, use the ´-M test´
673 Directive described below to send one test email message on
674 smartd startup.
675 By default, email is sent using the system mail command. In
677 order that smartd find the mail command (normally /bin/mail) an
678 executable named ´mail´ must be in the path of the shell or
679 environment from which smartd was started. If you wish to spec‐
680 ify an explicit path to the mail executable (for example
681 /usr/local/bin/mail) or a custom script to run, please use the
682 ´-M exec´ Directive below.
683 Note also that there is a special argument <nomailer> which can
685 be given to the ´-m´ Directive in conjunction with the ´-M exec´
686 Directive. Please see below for an explanation of its effect.
687 If the mailer or the shell running it produces any STDERR/STDOUT
689 output, then a snippet of that output will be copied to SYSLOG.
690 The remainder of the output is discarded. If problems are
691 encountered in sending mail, this should help you to understand
692 and fix them. If you have mail problems, we recommend running
693 smartd in debug mode with the ´-d´ flag, using the ´-M test´
694 Directive described below.
695 -M TYPE
697 These Directives modify the behavior of the smartd email warn‐
698 ings enabled with the ´-m´ email Directive described above.
699 These ´-M´ Directives only work in conjunction with the ´-m´
700 Directive and can not be used without it.
701 Multiple -M Directives may be given. If more than one of the
703 following three -M Directives are given (example: -M once -M
704 daily) then the final one (in the example, -M daily) is used.
705 The valid arguments to the -M Directive are (one of the follow‐
707 ing three):
708 once - send only one warning email for each type of disk problem
710 detected. This is the default unless state persistence (´-s´
711 option) is enabled.
712 daily - send additional warning reminder emails, once per day,
714 for each type of disk problem detected. This is the default if
715 state persistence (´-s´ option) is enabled.
716 diminishing - send additional warning reminder emails, after a
718 one-day interval, then a two-day interval, then a four-day
719 interval, and so on for each type of disk problem detected. Each
720 interval is twice as long as the previous interval.
721 If a disk problem is no longer detected, the internal email
723 counter is reset. If the problem reappears a new warning email
724 is sent immediately.
725 In addition, one may add zero or more of the following Direc‐
727 tives:
728 test - send a single test email immediately upon smartd startup.
730 This allows one to verify that email is delivered correctly.
731 Note that if this Directive is used, smartd will also send the
732 normal email warnings that were enabled with the ´-m´ Directive,
733 in addition to the single test email!
734 exec PATH - run the executable PATH instead of the default mail
736 command, when smartd needs to send email. PATH must point to an
737 executable binary file or script.
738 By setting PATH to point to a customized script, you can make
740 smartd perform useful tricks when a disk problem is detected
741 (beeping the console, shutting down the machine, broadcasting
742 warnings to all logged-in users, etc.) But please be careful.
743 smartd will block until the executable PATH returns, so if your
744 executable hangs, then smartd will also hang. Some sample
745 scripts are included in /usr/share/doc/smartmontools/example‐
746 scripts/.
747 The return status of the executable is recorded by smartd in
749 SYSLOG. The executable is not expected to write to STDOUT or
750 STDERR. If it does, then this is interpreted as indicating that
751 something is going wrong with your executable, and a fragment of
752 this output is logged to SYSLOG to help you to understand the
753 problem. Normally, if you wish to leave some record behind, the
754 executable should send mail or write to a file or device.
755 Before running the executable, smartd sets a number of environ‐
757 ment variables. These environment variables may be used to con‐
758 trol the executable´s behavior. The environment variables
759 exported by smartd are:
760 SMARTD_MAILER
762 is set to the argument of -M exec, if present or else to
763 ´mail´ (examples: /bin/mail, mail).
764 SMARTD_DEVICE
766 is set to the device path (examples: /dev/hda, /dev/sdb).
767 SMARTD_DEVICETYPE
769 is set to the device type specified by ´-d´ directive or
770 ´auto´ if none.
771 SMARTD_DEVICESTRING
773 is set to the device description. For SMARTD_DEVICETYPE of
774 ata or scsi, this is the same as SMARTD_DEVICE. For 3ware
775 RAID controllers, the form used is ´/dev/sdc
776 [3ware_disk_01]´. For HighPoint RocketRAID controller, the
777 form is ´/dev/sdd [hpt_1/1/1]´ under Linux or ´/dev/hptrr
778 [hpt_1/1/1]´ under FreeBSD. For Areca controllers, the form
779 is ´/dev/sg2 [areca_disk_09]´ on Linux or ´/dev/arcmsr0
780 [areca_disk_09]´ on FreeBSD. In these cases the device
781 string contains a space and is NOT quoted. So to use
782 $SMARTD_DEVICESTRING in a bash script you should probably
783 enclose it in double quotes.
784 SMARTD_FAILTYPE
786 gives the reason for the warning or message email. The pos‐
787 sible values that it takes and their meanings are:
788 EmailTest: this is an email test message.
789 Health: the SMART health status indicates imminent failure.
790 Usage: a usage Attribute has failed.
791 SelfTest: the number of self-test failures has increased.
792 ErrorCount: the number of errors in the ATA error log has
793 increased.
794 CurrentPendingSector: one of more disk sectors could not be
795 read and are marked to be reallocated (replaced with spare
796 sectors).
797 OfflineUncorrectableSector: during off-line testing, or
798 self-testing, one or more disk sectors could not be read.
799 Temperature: Temperature reached critical limit (see -W
800 directive).
801 FailedHealthCheck: the SMART health status command failed.
802 FailedReadSmartData: the command to read SMART Attribute
803 data failed.
804 FailedReadSmartErrorLog: the command to read the SMART error
805 log failed.
806 FailedReadSmartSelfTestLog: the command to read the SMART
807 self-test log failed.
808 FailedOpenDevice: the open() command to the device failed.
809 SMARTD_ADDRESS
811 is determined by the address argument ADD of the ´-m´ Direc‐
812 tive. If ADD is <nomailer>, then SMARTD_ADDRESS is not set.
813 Otherwise, it is set to the comma-separated-list of email
814 addresses given by the argument ADD, with the commas
815 replaced by spaces (example:admin@example.com root). If
816 more than one email address is given, then this string will
817 contain space characters and is NOT quoted, so to use it in
818 a bash script you may want to enclose it in double quotes.
819 SMARTD_MESSAGE
821 is set to the one sentence summary warning email message
822 string from smartd. This message string contains space
823 characters and is NOT quoted. So to use $SMARTD_MESSAGE in a
824 bash script you should probably enclose it in double quotes.
825 SMARTD_FULLMESSAGE
827 is set to the contents of the entire email warning message
828 string from smartd. This message string contains space and
829 return characters and is NOT quoted. So to use
830 $SMARTD_FULLMESSAGE in a bash script you should probably
831 enclose it in double quotes.
832 SMARTD_TFIRST
834 is a text string giving the time and date at which the first
835 problem of this type was reported. This text string contains
836 space characters and no newlines, and is NOT quoted. For
837 example:
838 Sun Feb 9 14:58:19 2003 CST
839 SMARTD_TFIRSTEPOCH
841 is an integer, which is the unix epoch (number of seconds
842 since Jan 1, 1970) for SMARTD_TFIRST.
843 The shell which is used to run PATH is system-dependent. For
845 vanilla Linux/glibc it´s bash. For other systems, the man page
846 for popen(3) should say what shell is used.
847 If the ´-m ADD´ Directive is given with a normal address argu‐
849 ment, then the executable pointed to by PATH will be run in a
850 shell with STDIN receiving the body of the email message, and
851 with the same command-line arguments:
852 -s "$SMARTD_SUBJECT" $SMARTD_ADDRESS
853 that would normally be provided to ´mail´. Examples include:
854 -m user@home -M exec /bin/mail
855 -m admin@work -M exec /usr/local/bin/mailto
856 -m root -M exec /Example_1/bash/script/below
857 If the ´-m ADD´ Directive is given with the special address
859 argument <nomailer> then the executable pointed to by PATH is
860 run in a shell with no STDIN and no command-line arguments, for
861 example:
862 -m <nomailer> -M exec /Example_2/bash/script/below
863 If the executable produces any STDERR/STDOUT output, then smartd
864 assumes that something is going wrong, and a snippet of that
865 output will be copied to SYSLOG. The remainder of the output is
866 then discarded.
867 Some EXAMPLES of scripts that can be used with the ´-M exec´
869 Directive are given below. Some sample scripts are also included
870 in /usr/share/doc/smartmontools/examplescripts/.
871 -f [ATA only] Check for ´failure´ of any Usage Attributes. If
873 these Attributes are less than or equal to the threshold, it
874 does NOT indicate imminent disk failure. It "indicates an advi‐
875 sory condition where the usage or age of the device has exceeded
876 its intended design life period." [Please see the smartctl -A
877 command-line option.]
878 -p [ATA only] Report anytime that a Prefail Attribute has changed
880 its value since the last check. [Please see the smartctl -A com‐
881 mand-line option.]
882 -u [ATA only] Report anytime that a Usage Attribute has changed its
884 value since the last check. [Please see the smartctl -A command-
885 line option.]
886 -t [ATA only] Equivalent to turning on the two previous flags ´-p´
888 and ´-u´. Tracks changes in all device Attributes (both Pre‐
889 failure and Usage). [Please see the smartctl -A command-line
890 option.]
891 -i ID [ATA only] Ignore device Attribute number ID when checking for
893 failure of Usage Attributes. ID must be a decimal integer in
894 the range from 1 to 255. This Directive modifies the behavior
895 of the ´-f´ Directive and has no effect without it.
896 This is useful, for example, if you have a very old disk and
898 don´t want to keep getting messages about the hours-on-lifetime
899 Attribute (usually Attribute 9) failing. This Directive may
900 appear multiple times for a single device, if you want to ignore
901 multiple Attributes.
902 -I ID [ATA only] Ignore device Attribute ID when tracking changes in
904 the Attribute values. ID must be a decimal integer in the range
905 from 1 to 255. This Directive modifies the behavior of the
906 ´-p´, ´-u´, and ´-t´ tracking Directives and has no effect with‐
907 out one of them.
908 This is useful, for example, if one of the device Attributes is
910 the disk temperature (usually Attribute 194 or 231). It´s annoy‐
911 ing to get reports each time the temperature changes. This
912 Directive may appear multiple times for a single device, if you
913 want to ignore multiple Attributes.
914 -r ID[!]
916 [ATA only] When tracking, report the Raw value of Attribute ID
917 along with its (normally reported) Normalized value. ID must be
918 a decimal integer in the range from 1 to 255. This Directive
919 modifies the behavior of the ´-p´, ´-u´, and ´-t´ tracking
920 Directives and has no effect without one of them. This Direc‐
921 tive may be given multiple times.
922 A common use of this Directive is to track the device Tempera‐
924 ture (often ID=194 or 231).
925 If the optional flag ´!´ is appended, a change of the Normalized
927 value is considered critical. The report will be logged as
928 LOG_CRIT and a warning email will be sent if ´-m´ is specified.
929 -R ID[!]
931 [ATA only] When tracking, report whenever the Raw value of
932 Attribute ID changes. (Normally smartd only tracks/reports
933 changes of the Normalized Attribute values.) ID must be a deci‐
934 mal integer in the range from 1 to 255. This Directive modifies
935 the behavior of the ´-p´, ´-u´, and ´-t´ tracking Directives and
936 has no effect without one of them. This Directive may be given
937 multiple times.
938 If this Directive is given, it automatically implies the ´-r´
940 Directive for the same Attribute, so that the Raw value of the
941 Attribute is reported.
942 A common use of this Directive is to track the device Tempera‐
944 ture (often ID=194 or 231). It is also useful for understanding
945 how different types of system behavior affects the values of
946 certain Attributes.
947 If the optional flag ´!´ is appended, a change of the Raw value
949 is considered critical. The report will be logged as LOG_CRIT
950 and a warning email will be sent if ´-m´ is specified. An exam‐
951 ple is ´-R 5!´ to warn when new sectors are reallocated.
952 -C ID[+]
954 [ATA only] Report if the current number of pending sectors is
955 non-zero. Here ID is the id number of the Attribute whose raw
956 value is the Current Pending Sector count. The allowed range of
957 ID is 0 to 255 inclusive. To turn off this reporting, use
958 ID = 0. If the -C ID option is not given, then it defaults to
959 -C 197 (since Attribute 197 is generally used to monitor pending
960 sectors). If the name of this Attribute is changed by a ´-v
961 197,FORMAT,NAME´ directive, the default is changed to -C 0.
962 If ´+´ is specified, a report is only printed if the number of
964 sectors has increased between two check cycles. Some disks do
965 not reset this attribute when a bad sector is reallocated. See
966 also ´-v 197,increasing´ below.
967 The warning email counter is reset if the number of pending sec‐
969 tors dropped to 0. This typically happens when all pending sec‐
970 tors have been reallocated or could be read again.
971 A pending sector is a disk sector (containing 512 bytes of your
973 data) which the device would like to mark as ``bad" and reallo‐
974 cate. Typically this is because your computer tried to read
975 that sector, and the read failed because the data on it has been
976 corrupted and has inconsistent Error Checking and Correction
977 (ECC) codes. This is important to know, because it means that
978 there is some unreadable data on the disk. The problem of fig‐
979 uring out what file this data belongs to is operating system and
980 file system specific. You can typically force the sector to
981 reallocate by writing to it (translation: make the device sub‐
982 stitute a spare good sector for the bad one) but at the price of
983 losing the 512 bytes of data stored there.
984 -U ID[+]
986 [ATA only] Report if the number of offline uncorrectable sectors
987 is non-zero. Here ID is the id number of the Attribute whose
988 raw value is the Offline Uncorrectable Sector count. The
989 allowed range of ID is 0 to 255 inclusive. To turn off this
990 reporting, use ID = 0. If the -U ID option is not given, then
991 it defaults to -U 198 (since Attribute 198 is generally used to
992 monitor offline uncorrectable sectors). If the name of this
993 Attribute is changed by a ´-v 198,FORMAT,NAME´ (except ´-v
994 198,FORMAT,Offline_Scan_UNC_SectCt´), directive, the default is
995 changed to -U 0.
996 If ´+´ is specified, a report is only printed if the number of
998 sectors has increased since the last check cycle. Some disks do
999 not reset this attribute when a bad sector is reallocated. See
1000 also ´-v 198,increasing´ below.
1001 The warning email counter is reset if the number of offline
1003 uncorrectable sectors dropped to 0. This typically happens when
1004 all offline uncorrectable sectors have been reallocated or could
1005 be read again.
1006 An offline uncorrectable sector is a disk sector which was not
1008 readable during an off-line scan or a self-test. This is impor‐
1009 tant to know, because if you have data stored in this disk sec‐
1010 tor, and you need to read it, the read will fail. Please see
1011 the previous ´-C´ option for more details.
1012 -W DIFF[,INFO[,CRIT]]
1014 Report if the current temperature had changed by at least DIFF
1015 degrees since last report, or if new min or max temperature is
1016 detected. Report or Warn if the temperature is greater or equal
1017 than one of INFO or CRIT degrees Celsius. If the limit CRIT is
1018 reached, a message with loglevel ´LOG_CRIT´ will be logged to
1019 syslog and a warning email will be send if '-m' is specified. If
1020 only the limit INFO is reached, a message with loglevel
1021 ´LOG_INFO´ will be logged.
1022 The warning email counter is reset if the temperature dropped
1024 below INFO or CRIT-5 if INFO is not specified.
1025 If this directive is used in conjunction with state persistence
1027 (´-s´ option), the min and max temperature values are preserved
1028 across boot cycles. The minimum temperature value is not updated
1029 during the first 30 minutes after startup.
1030 To disable any of the 3 reports, set the corresponding limit to
1032 0. Trailing zero arguments may be omitted. By default, all tem‐
1033 perature reports are disabled (´-W 0´).
1034 To track temperature changes of at least 2 degrees, use:
1036 -W 2
1037 To log informal messages on temperatures of at least 40 degrees,
1038 use:
1039 -W 0,40
1040 For warning messages/mails on temperatures of at least 45
1041 degrees, use:
1042 -W 0,0,45
1043 To combine all of the above reports, use:
1044 -W 2,40,45
1045 For ATA devices, smartd interprets Attribute 194 as Temperature
1047 Celsius by default. This can be changed to Attribute 9 or 220 by
1048 the drive database or by the ´-v´ directive, see below.
1049 -F TYPE
1051 [ATA only] Modifies the behavior of smartd to compensate for
1052 some known and understood device firmware bug. The arguments to
1053 this Directive are exclusive, so that only the final Directive
1054 given is used. The valid values are:
1055 none - Assume that the device firmware obeys the ATA specifica‐
1057 tions. This is the default, unless the device has presets for
1058 ´-F´ in the device database.
1059 samsung - In some Samsung disks (example: model SV4012H Firmware
1061 Version: RM100-08) some of the two- and four-byte quantities in
1062 the SMART data structures are byte-swapped (relative to the ATA
1063 specification). Enabling this option tells smartd to evaluate
1064 these quantities in byte-reversed order. Some signs that your
1065 disk needs this option are (1) no self-test log printed, even
1066 though you have run self-tests; (2) very large numbers of ATA
1067 errors reported in the ATA error log; (3) strange and impossible
1068 values for the ATA error log timestamps.
1069 samsung2 - In some Samsung disks the number of ATA errors
1071 reported is byte swapped. Enabling this option tells smartd to
1072 evaluate this quantity in byte-reversed order.
1073 samsung3 - Some Samsung disks (at least SP2514N with Firmware
1075 VF100-37) report a self-test still in progress with 0% remaining
1076 when the test was already completed. If this directive is speci‐
1077 fied, smartd will not skip the next scheduled self-test (see
1078 Directive ´-s´ above) in this case.
1079 Note that an explicit ´-F´ Directive will over-ride any preset
1081 values for ´-F´ (see the ´-P´ option below).
1082 [Please see the smartctl -F command-line option.]
1085 -v ID,FORMAT[:BYTEORDER][,NAME]
1087 [ATA only] Sets a vendor-specific raw value print FORMAT, an
1088 optional BYTEORDER and an optional NAME for Attribute ID. This
1089 directive may be used multiple times. Please see smartctl -v
1090 command-line option for further details.
1091 The following arguments affect smartd warning output:
1093 197,increasing - Raw Attribute number 197 (Current Pending Sec‐
1095 tor Count) is not reset if uncorrectable sectors are reallo‐
1096 cated. This sets ´-C 197+´ if no other ´-C´ directive is speci‐
1097 fied.
1098 198,increasing - Raw Attribute number 198 (Offline Uncorrectable
1100 Sector Count) is not reset if uncorrectable sector are reallo‐
1101 cated. This sets ´-U 198+´ if no other ´-U´ directive is speci‐
1102 fied.
1103 -P TYPE
1105 [ATA only] Specifies whether smartd should use any preset
1106 options that are available for this drive. The valid arguments
1107 to this Directive are:
1108 use - use any presets that are available for this drive. This
1110 is the default.
1111 ignore - do not use any presets for this drive.
1113 show - show the presets listed for this drive in the database.
1115 showall - show the presets that are available for all drives and
1117 then exit.
1118 [Please see the smartctl -P command-line option.]
1120 -a Equivalent to turning on all of the following Directives: ´-H´
1122 to check the SMART health status, ´-f´ to report failures of
1123 Usage (rather than Prefail) Attributes, ´-t´ to track changes in
1124 both Prefailure and Usage Attributes, ´-l error´ to report
1125 increases in the number of ATA errors, ´-l selftest´ to report
1126 increases in the number of Self-Test Log errors, ´-l selftest‐
1127 sts´ to report changes of Self-Test execution status, ´-C 197´
1128 to report nonzero values of the current pending sector count,
1129 and ´-U 198´ to report nonzero values of the offline pending
1130 sector count.
1131 Note that -a is the default for ATA devices. If none of these
1133 other Directives is given, then -a is assumed.
1134 # Comment: ignore the remainder of the line.
1136 \ Continuation character: if this is the last non-white or non-
1138 comment character on a line, then the following line is a con‐
1139 tinuation of the current one.
1140 If you are not sure which Directives to use, I suggest experimenting
1142 for a few minutes with smartctl to see what SMART functionality your
1143 disk(s) support(s). If you do not like voluminous syslog messages, a
1144 good choice of smartd configuration file Directives might be:
1145 -H -l selftest -l error -f.
1146 If you want more frequent information, use: -a.
1147 ADDITIONAL DETAILS ABOUT DEVICESCAN
1150 If a non-comment entry in the configuration file is the text
1151 string DEVICESCAN in capital letters, then smartd will ignore
1152 any remaining lines in the configuration file, and will scan for
1153 devices.
1154 Configuration entries for devices not found by the platform-spe‐
1156 cific device scanning may precede the DEVICESCAN entry.
1157 If DEVICESCAN is not followed by any Directives, then smartd
1159 will scan for both ATA and SCSI devices, and will monitor all
1160 possible SMART properties of any devices that are found.
1161 DEVICESCAN may optionally be followed by any valid Directives,
1163 which will be applied to all devices that are found in the scan.
1164 For example
1165 DEVICESCAN -m root@example.com
1166 will scan for all devices, and then monitor them. It will send
1167 one email warning per device for any problems that are found.
1168 DEVICESCAN -d ata -m root@example.com
1169 will do the same, but restricts the scan to ATA devices only.
1170 DEVICESCAN -H -d ata -m root@example.com
1171 will do the same, but only monitors the SMART health status of
1172 the devices, (rather than the default -a, which monitors all
1173 SMART properties).
1174 EXAMPLES OF SHELL SCRIPTS FOR ´-M exec´
1177 These are two examples of shell scripts that can be used with
1178 the ´-M exec PATH´ Directive described previously. The paths to
1179 these scripts and similar executables is the PATH argument to
1180 the ´-M exec PATH´ Directive.
1181 Example 1: This script is for use with ´-m ADDRESS -M exec
1183 PATH´. It appends the output of smartctl -a to the output of
1184 the smartd email warning message and sends it to ADDRESS.
1185 #! /bin/bash
1187 # Save the email message (STDIN) to a file:
1189 cat > /root/msg
1190 # Append the output of smartctl -a to the message:
1192 /usr/sbin/smartctl -a -d $SMART_DEVICETYPE $SMARTD_DEVICE >> /root/msg
1193 # Now email the message to the user at address ADD:
1195 /bin/mail -s "$SMARTD_SUBJECT" $SMARTD_ADDRESS < /root/msg
1196 Example 2: This script is for use with ´-m <nomailer> -M exec
1198 PATH´. It warns all users about a disk problem, waits 30 sec‐
1199 onds, and then powers down the machine.
1200 #! /bin/bash
1202 # Warn all users of a problem
1204 wall ´Problem detected with disk: ´ "$SMARTD_DEVICESTRING"
1205 wall ´Warning message from smartd is: ´ "$SMARTD_MESSAGE"
1206 wall ´Shutting down machine in 30 seconds... ´
1207 # Wait half a minute
1209 sleep 30
1210 # Power down the machine
1212 /sbin/shutdown -hf now
1213 Some example scripts are distributed with the smartmontools
1215 package, in /usr/share/doc/smartmontools/examplescripts/.
1216 Please note that these scripts typically run as root, so any
1218 files that they read/write should not be writable by ordinary
1219 users or reside in directories like /tmp that are writable by
1220 ordinary users and may expose your system to symlink attacks.
1221 As previously described, if the scripts write to STDOUT or
1223 STDERR, this is interpreted as indicating that there was an
1224 internal error within the script, and a snippet of STDOUT/STDERR
1225 is logged to SYSLOG. The remainder is flushed.
1226
1229 Bruce Allen smartmontools-support@lists.sourceforge.net
1230 University of Wisconsin - Milwaukee Physics Department
1231
1234 The following have made large contributions to smartmontools:
1235 Casper Dik (Solaris SCSI interface)
1236 Christian Franke (Windows interface, C++ redesign, USB support, ...)
1237 Douglas Gilbert (SCSI subsystem)
1238 Guido Guenther (Autoconf/Automake packaging)
1239 Geoffrey Keating (Darwin ATA interface)
1240 Eduard Martinescu (FreeBSD interface)
1241 Frédéric L. W. Meunier (Web site and Mailing list)
1242 Gabriele Pohl (Web site and Wiki, conversion from CVS to SVN)
1243 Keiji Sawada (Solaris ATA interface)
1244 Manfred Schwarb (Drive database)
1245 Sergey Svishchev (NetBSD interface)
1246 David Snyder and Sergey Svishchev (OpenBSD interface)
1247 Phil Williams (User interface and drive database)
1248 Shengfeng Zhou (Linux/FreeBSD HighPoint RocketRAID interface)
1249 Many other individuals have made smaller contributions and corrections.
1250
1253 This code was derived from the smartsuite package, written by Michael
1254 Cornwell, and from the previous UCSC smartsuite package. It extends
1255 these to cover ATA-5 disks. This code was originally developed as a
1256 Senior Thesis by Michael Cornwell at the Concurrent Systems Laboratory
1257 (now part of the Storage Systems Research Center), Jack Baskin School
1258 of Engineering, University of California, Santa Cruz.
1259 http://ssrc.soe.ucsc.edu/ .
1260
1262 Please see the following web site for updates, further documentation,
1263 bug reports and patches: http://smartmontools.sourceforge.net/
1264
1267 smartd(8), smartctl(8), syslogd(8), syslog.conf(5), badblocks(8),
1268 ide-smart(8), regex(7).
1269
1272 $Id: smartd.conf.5.in 3566 2012-06-19 21:26:28Z chrfranke $
1273smartmontools-5.43 2016-09-28 SMARTD.CONF(5)