1SMARTD.CONF(5) 2010-10-16 SMARTD.CONF(5)
2
6 smartd.conf - SMART Disk Monitoring Daemon Configuration File
7
10 /etc/smartd.conf
11
14 smartmontools-5.40 2010-10-16 r3189
15
18 /etc/smartd.conf is the configuration file for the smartd daemon, which
19 monitors the Self-Monitoring, Analysis and Reporting Technology (SMART)
20 system built into many ATA-3 and later ATA, IDE and SCSI-3 hard drives.
21 If the configuration file /etc/smartd.conf is present, smartd reads it
23 at startup, before fork(2)ing into the background. If smartd subse‐
24 quently receives a HUP signal, it will then re-read the configuration
25 file. If smartd is running in debug mode, then an INT signal will also
26 make it re-read the configuration file. This signal can be generated by
27 typing <CONTROL-C> in the terminal window where smartd is running.
28
32 In the absence of a configuration file, under Linux smartd will try to
33 open the 20 ATA devices /dev/hd[a-t] and the 26 SCSI devices /dev/sd[a-
34 z]. Under FreeBSD, smartd will try to open all existing ATA devices
35 (with entries in /dev) /dev/ad[0-9]+ and all existing SCSI devices
36 (using CAM subsystem). Under NetBSD/OpenBSD, smartd will try to open
37 all existing ATA devices (with entries in /dev) /dev/wd[0-9]+c and all
38 existing SCSI devices /dev/sd[0-9]+c. Under Solaris smartd will try to
39 open all entries "/dev/rdsk/c?t?d?s?" for IDE/ATA and SCSI disk
40 devices, and entries "/dev/rmt/*" for SCSI tape devices. Under Windows
41 smartd will try to open all entries "/dev/hd[a-j]" ("\\.\Physi‐
42 calDrive[0-9]") for IDE/ATA devices on WinNT4/2000/XP, "/dev/hd[a-d]"
43 (bitmask from "\\.\SMARTVSD") for IDE/ATA devices on Win95/98/98SE/ME,
44 and "/dev/scsi[0-9][0-7]" (ASPI adapter 0-9, ID 0-7) for SCSI devices
45 on all versions of Windows. Under Darwin, smartd will open any ATA
46 block storage device.
47 This can be annoying if you have an ATA or SCSI device that hangs or
49 misbehaves when receiving SMART commands. Even if this causes no prob‐
50 lems, you may be annoyed by the string of error log messages about
51 block-major devices that can´t be found, and SCSI devices that can´t be
52 opened.
53 One can avoid this problem, and gain more control over the types of
55 events monitored by smartd, by using the configuration file
56 /etc/smartd.conf. This file contains a list of devices to monitor,
57 with one device per line. An example file is included with the smart‐
58 montools distribution. You will find this sample configuration file in
59 /usr/share/doc/smartmontools/. For security, the configuration file
60 should not be writable by anyone but root. The syntax of the file is as
61 follows:
62 · There should be one device listed per line, although you may have
64 lines that are entirely comments or white space.
65 · Any text following a hash sign ´#´ and up to the end of the line is
67 taken to be a comment, and ignored.
68 · Lines may be continued by using a backslash ´\´ as the last non-
70 whitespace or non-comment item on a line.
71 · Note: a line whose first character is a hash sign ´#´ is treated as
73 a white-space blank line, not as a non-existent line, and will end
74 a continuation line.
75 Here is an example configuration file. It´s for illustrative purposes
77 only; please don´t copy it onto your system without reading to the end
78 of the DIRECTIVES Section below!
79 ################################################
81 # This is an example smartd startup config file
82 # /etc/smartd.conf for monitoring three
83 # ATA disks, three SCSI disks, six ATA disks
84 # behind two 3ware controllers, three SATA disks
85 # directly connected to the HighPoint Rocket-
86 # RAID controller, two SATA disks connected to
87 # the HighPoint RocketRAID controller via a pmport
88 # device, four SATA disks connected to an Areca
89 # RAID controller, and one SATA disk.
90 #
91 # First ATA disk on two different interfaces. On
92 # the second disk, start a long self-test every
93 # Sunday between 3 and 4 am.
94 #
95 /dev/hda -a -m admin@example.com,root@localhost
96 /dev/hdc -a -I 194 -I 5 -i 12 -s L/../../7/03
97 #
98 # SCSI disks. Send a TEST warning email to admin on
99 # startup.
100 #
101 /dev/sda
102 /dev/sdb -m admin@example.com -M test
103 #
104 # Strange device. It´s SCSI. Start a scheduled
105 # long self test between 5 and 6 am Monday/Thursday
106 /dev/weird -d scsi -s L/../../(1|4)/05
107 #
108 # An ATA disk may appear as a SCSI device to the
109 # OS. If a SCSI to ATA Translation (SAT) layer
110 # is between the OS and the device then this can be
111 # flagged with the '-d sat' option. This situation
112 # may become common with SATA disks in SAS and FC
113 # environments.
114 /dev/sda -a -d sat
115 #
116 # Three disks connected to a MegaRAID controller
117 # Start short self-tests daily between 1-2, 2-3, and
118 # 3-4 am.
119 /dev/sda -d megaraid,0 -a -s S/../.././01
120 /dev/sda -d megaraid,1 -a -s S/../.././02
121 /dev/sda -d megaraid,2 -a -s S/../.././03
122 #
123 # Four ATA disks on a 3ware 6/7/8000 controller.
124 # Start short self-tests daily between midnight and 1am,
125 # 1-2, 2-3, and 3-4 am. Starting with the Linux 2.6
126 # kernel series, /dev/sdX is deprecated in favor of
127 # /dev/tweN. For example replace /dev/sdc by /dev/twe0
128 # and /dev/sdd by /dev/twe1.
129 /dev/sdc -d 3ware,0 -a -s S/../.././00
130 /dev/sdc -d 3ware,1 -a -s S/../.././01
131 /dev/sdd -d 3ware,2 -a -s S/../.././02
132 /dev/sdd -d 3ware,3 -a -s S/../.././03
133 #
134 # Two ATA disks on a 3ware 9000 controller.
135 # Start long self-tests Sundays between midnight and
136 # 1am and 2-3 am
137 /dev/twa0 -d 3ware,0 -a -s L/../../7/00
138 /dev/twa0 -d 3ware,1 -a -s L/../../7/02
139 #
140 # Two SATA (not SAS) disks on a 3ware 9750 controller.
141 # Start long self-tests Sundays between midnight and
142 # 1am and 2-3 am
143 /dev/twl0 -d 3ware,0 -a -s L/../../7/00
144 /dev/twl0 -d 3ware,1 -a -s L/../../7/02
145 #
146 # Three SATA disks on a HighPoint RocketRAID controller.
147 # Start short self-tests daily between 1-2, 2-3, and
148 # 3-4 am.
149 # under Linux
150 /dev/sde -d hpt,1/1 -a -s S/../.././01
151 /dev/sde -d hpt,1/2 -a -s S/../.././02
152 /dev/sde -d hpt,1/3 -a -s S/../.././03
153 # or under FreeBSD
154 # /dev/hptrr -d hpt,1/1 -a -s S/../.././01
155 # /dev/hptrr -d hpt,1/2 -a -s S/../.././02
156 # /dev/hptrr -d hpt,1/3 -a -s S/../.././03
157 #
158 # Two SATA disks connected to a HighPoint RocketRAID
159 # via a pmport device. Start long self-tests Sundays
160 # between midnight and 1am and 2-3 am.
161 # under Linux
162 /dev/sde -d hpt,1/4/1 -a -s L/../../7/00
163 /dev/sde -d hpt,1/4/2 -a -s L/../../7/02
164 # or under FreeBSD
165 # /dev/hptrr -d hpt,1/4/1 -a -s L/../../7/00
166 # /dev/hptrr -d hpt,1/4/2 -a -s L/../../7/02
167 #
168 # Three SATA disks connected to an Areca
169 # RAID controller. Start long self-tests Sundays
170 # between midnight and 3 am.
171 /dev/sg2 -d areca,1 -a -s L/../../7/00
172 /dev/sg2 -d areca,2 -a -s L/../../7/01
173 /dev/sg2 -d areca,3 -a -s L/../../7/02
174 #
175 # The following line enables monitoring of the
176 # ATA Error Log and the Self-Test Error Log.
177 # It also tracks changes in both Prefailure
178 # and Usage Attributes, apart from Attributes
179 # 9, 194, and 231, and shows continued lines:
180 #
181 /dev/hdd -l error \
182 -l selftest \
183 -t \ # Attributes not tracked:
184 -I 194 \ # temperature
185 -I 231 \ # also temperature
186 -I 9 # power-on hours
187 #
188 ################################################
189
192 If a non-comment entry in the configuration file is the text string
193 DEVICESCAN in capital letters, then smartd will ignore any remaining
194 lines in the configuration file, and will scan for devices. DEVICESCAN
195 may optionally be followed by Directives that will apply to all devices
196 that are found in the scan. Please see below for additional details.
197 The following are the Directives that may appear following the device
201 name or DEVICESCAN on any line of the /etc/smartd.conf configuration
202 file. Note that these are NOT command-line options for smartd. The
203 Directives below may appear in any order, following the device name.
204 For an ATA device, if no Directives appear, then the device will be
206 monitored as if the ´-a´ Directive (monitor all SMART properties) had
207 been given.
208 If a SCSI disk is listed, it will be monitored at the maximum imple‐
210 mented level: roughly equivalent to using the ´-H -l selftest´ options
211 for an ATA disk. So with the exception of ´-d´, ´-m´, ´-l selftest´,
212 ´-s´, and ´-M´, the Directives below are ignored for SCSI disks. For
213 SCSI disks, the ´-m´ Directive sends a warning email if the SMART sta‐
214 tus indicates a disk failure or problem, if the SCSI inquiry about disk
215 status fails, or if new errors appear in the self-test log.
216 If a 3ware controller is used then the corresponding SCSI (/dev/sd?) or
218 character device (/dev/twe?, /dev/twa? or /dev/twl?) must be listed,
219 along with the ´-d 3ware,N´ Directive (see below). The individual ATA
220 disks hosted by the 3ware controller appear to smartd as normal ATA
221 devices. Hence all the ATA directives can be used for these disks (but
222 see note below).
223 If an Areca controller is used then the corresponding SCSI generic
225 device (/dev/sg?) must be listed, along with the ´-d areca,N´ Direc‐
226 tive (see below). The individual SATA disks hosted by the Areca con‐
227 troller appear to smartd as normal ATA devices. Hence all the ATA
228 directives can be used for these disks. Areca firmware version 1.46 or
229 later which supports smartmontools must be used; Please see the
230 smartctl(8) man page for further details.
231 -d TYPE
233 Specifies the type of the device. This Directive may be used
234 multiple times for one device, but the arguments ata, scsi, sat,
235 marvell, cciss,N, areca,N, megaraid,N and 3ware,N are mutually-
236 exclusive. If more than one is given then smartd will use the
237 last one which appears.
238 If none of these three arguments is given, then smartd will
240 first attempt to guess the device type by looking at whether the
241 sixth character in the device name is an ´s´ or an ´h´. This
242 will work for device names like /dev/hda or /dev/sdb, and corre‐
243 sponds to choosing ata or scsi respectively. If smartd can´t
244 guess from this sixth character, then it will simply try to
245 access the device using first ATA and then SCSI ioctl()s.
246 The valid arguments to this Directive are:
248 ata - the device type is ATA. This prevents smartd from issuing
250 SCSI commands to an ATA device.
251 scsi - the device type is SCSI. This prevents smartd from issu‐
253 ing ATA commands to a SCSI device.
254 sat - the device type is SCSI to ATA Translation (SAT). smartd
256 will generate ATA (smart) commands and then package them in the
257 SAT defined ATA PASS THROUGH SCSI commands. The commands are
258 then routed through the SCSI pass through interface to the oper‐
259 ating system. There are two types of ATA PASS THROUGH SCSI com‐
260 mands: a 12 byte and 16 byte variant. smartd can use either and
261 defaults to the 16 byte variant. This can be overridden with
262 this syntax: ´-d sat,12´ or ´-d sat,16´.
263 marvell - Under Linux, interact with SATA disks behind Marvell
265 chip-set controllers (using the Marvell rather than libata
266 driver).
267 megaraid,N - the device consists of one or more SCSI/SAS/SATA
269 disks connected to a MegaRAID controller. The non-negative
270 integer N (in the range of 0 to 127 inclusive) denotes which
271 disk on the controller is monitored. In log files and email
272 messages this disk will be identified as megaraid_disk_XXX with
273 XXX in the range from 000 to 127 inclusive.
274 3ware,N - the device consists of one or more ATA disks connected
276 to a 3ware RAID controller. The non-negative integer N (in the
277 range from 0 to 127 inclusive) denotes which disk on the con‐
278 troller is monitored. In log files and email messages this disk
279 will be identified as 3ware_disk_XXX with XXX in the range from
280 000 to 127 inclusive.
281 This Directive may at first appear confusing, because the 3ware
283 controller is a SCSI device (such as /dev/sda) and should be
284 listed as such in the the configuration file. However when the
285 ´-d 3ware,N´ Directive is used, then the corresponding disk is
286 addressed using native ATA commands which are ´passed through´
287 the SCSI driver. All ATA Directives listed in this man page may
288 be used. Note that while you may use any of the 3ware SCSI log‐
289 ical devices /dev/sd? to address any of the physical disks
290 (3ware ports), error and log messages will make the most sense
291 if you always list the 3ware SCSI logical device corresponding
292 to the particular physical disks. Please see the smartctl(8)
293 man page for further details.
294 ATA disks behind 3ware controllers may alternatively be accessed
296 via a character device interface /dev/twe0-15 (3ware
297 6000/7000/8000 controllers), /dev/twa0-15 (3ware 9000 series
298 controllers) and /dev/twl0-15 (3ware 9750 series controllers).
299 Note that the 9000 series controllers may only be accessed using
300 the character device interface /dev/twa0-15 and not the SCSI
301 device interface /dev/sd?. Please see the smartctl(8) man page
302 for further details.
303 Note that older 3w-xxxx drivers do not pass the ´Enable
305 Autosave´ (-S on) and ´Enable Automatic Offline´ (-o on) com‐
306 mands to the disk, if the SCSI interface is used, and produce
307 these types of harmless syslog error messages instead: ´3w-xxxx:
308 tw_ioctl(): Passthru size (123392) too big´. This can be fixed
309 by upgrading to version 1.02.00.037 or later of the 3w-xxxx
310 driver, or by applying a patch to older versions. See
311 http://smartmontools.sourceforge.net/ for instructions. Alter‐
312 natively use the character device interfaces /dev/twe0-15 (3ware
313 6/7/8000 series controllers), /dev/twa0-15 (3ware 9000 series
314 controllers) or /dev/twl0-15 (3ware 9750 series controllers).
315 areca,N - the device consists of one or more SATA disks con‐
317 nected to an Areca SATA RAID controller. The positive integer N
318 (in the range from 1 to 24 inclusive) denotes which disk on the
319 controller is monitored. In log files and email messages this
320 disk will be identifed as areca_disk_XX with XX in the range
321 from 01 to 24 inclusive.
322 cciss,N - the device consists of one or more SCSI disks con‐
324 nected to a cciss RAID controller. The non-negative integer N
325 (in the range from 0 to 15 inclusive) denotes which disk on the
326 controller is monitored. In log files and email messages this
327 disk will be identified as cciss_disk_XX with XX in the range
328 from 00 to 15 inclusive.
329 3ware, MegaRAID, Areca and cciss controllers are currently ONLY
331 supported under Linux.
332 hpt,L/M/N - the device consists of one or more ATA disks con‐
334 nected to a HighPoint RocketRAID controller. The integer L is
335 the controller id, the integer M is the channel number, and the
336 integer N is the PMPort number if it is available. The allowed
337 values of L are from 1 to 4 inclusive, M are from 1 to 8 inclu‐
338 sive and N from 1 to 4 if PMPort available. And also these val‐
339 ues are limited by the model of the HighPoint RocketRAID con‐
340 troller. In log files and email messages this disk will be
341 identified as hpt_X/X/X and X/X/X is the same as L/M/N, note if
342 no N indicated, N set to the default value 1.
343 HighPoint RocketRAID controllers are currently ONLY supported
345 under Linux and FreeBSD.
346 removable - the device or its media is removable. This indi‐
348 cates to smartd that it should continue (instead of exiting,
349 which is the default behavior) if the device does not appear to
350 be present when smartd is started. This Directive may be used
351 in conjunction with the other ´-d´ Directives.
352 -n POWERMODE[,N][,q]
354 This ´nocheck´ Directive is used to prevent a disk from being
355 spun-up when it is periodically polled by smartd.
356 ATA disks have five different power states. In order of increas‐
358 ing power consumption they are: ´OFF´, ´SLEEP´, ´STANDBY´,
359 ´IDLE´, and ´ACTIVE´. Typically in the OFF, SLEEP, and STANDBY
360 modes the disk´s platters are not spinning. But usually, in
361 response to SMART commands issued by smartd, the disk platters
362 are spun up. So if this option is not used, then a disk which
363 is in a low-power mode may be spun up and put into a
364 higher-power mode when it is periodically polled by smartd.
365 Note that if the disk is in SLEEP mode when smartd is started,
367 then it won't respond to smartd commands, and so the disk won't
368 be registered as a device for smartd to monitor. If a disk is in
369 any other low-power mode, then the commands issued by smartd to
370 register the disk will probably cause it to spin-up.
371 The ´-n´ (nocheck) Directive specifies if smartd´s periodic
373 checks should still be carried out when the device is in a
374 low-power mode. It may be used to prevent a disk from being
375 spun-up by periodic smartd polling. The allowed values of POW‐
376 ERMODE are:
377 never - smartd will poll (check) the device regardless of its
379 power mode. This may cause a disk which is spun-down to be
380 spun-up when smartd checks it. This is the default behavior if
381 the '-n' Directive is not given.
382 sleep - check the device unless it is in SLEEP mode.
384 standby - check the device unless it is in SLEEP or STANDBY
386 mode. In these modes most disks are not spinning, so if you
387 want to prevent a laptop disk from spinning up each time that
388 smartd polls, this is probably what you want.
389 idle - check the device unless it is in SLEEP, STANDBY or IDLE
391 mode. In the IDLE state, most disks are still spinning, so this
392 is probably not what you want.
393 Maximum number of skipped checks (in a row) can be specified by
395 appending positive number ´,N´ to POWERMODE (like ´-n
396 standby,15´). After N checks are skipped in a row, powermode is
397 ignored and the check is performed anyway.
398 When a periodic test is skipped, smartd normally writes an
400 informal log message. The message can be suppressed by appending
401 the option ´,q´ to POWERMODE (like ´-n standby,q´). This pre‐
402 vents a laptop disk from spinning up due to this message.
403 Both ´,N´ and ´,q´ can be specified together.
405 -T TYPE
407 Specifies how tolerant smartd should be of SMART command fail‐
408 ures. The valid arguments to this Directive are:
409 normal - do not try to monitor the disk if a mandatory SMART
411 command fails, but continue if an optional SMART command fails.
412 This is the default.
413 permissive - try to monitor the disk even if it appears to lack
415 SMART capabilities. This may be required for some old disks
416 (prior to ATA-3 revision 4) that implemented SMART before the
417 SMART standards were incorporated into the ATA/ATAPI Specifica‐
418 tions. This may also be needed for some Maxtor disks which fail
419 to comply with the ATA Specifications and don't properly indi‐
420 cate support for error- or self-test logging.
421 [Please see the smartctl -T command-line option.]
423 -o VALUE
425 Enables or disables SMART Automatic Offline Testing when smartd
426 starts up and has no further effect. The valid arguments to
427 this Directive are on and off.
428 The delay between tests is vendor-specific, but is typically
430 four hours.
431 Note that SMART Automatic Offline Testing is not part of the ATA
433 Specification. Please see the smartctl -o command-line option
434 documentation for further information about this feature.
435 -S VALUE
437 Enables or disables Attribute Autosave when smartd starts up and
438 has no further effect. The valid arguments to this Directive
439 are on and off. Also affects SCSI devices. [Please see the
440 smartctl -S command-line option.]
441 -H Check the SMART health status of the disk. If any Prefailure
443 Attributes are less than or equal to their threshold values,
444 then disk failure is predicted in less than 24 hours, and a mes‐
445 sage at loglevel ´LOG_CRIT´ will be logged to syslog. [Please
446 see the smartctl -H command-line option.]
447 -l TYPE
449 Reports increases in the number of errors in one of three SMART
450 logs. The valid arguments to this Directive are:
451 error - report if the number of ATA errors reported in the Sum‐
453 mary SMART error log has increased since the last check.
454 xerror - [NEW EXPERIMENTAL SMARTD FEATURE] report if the number
456 of ATA errors reported in the Extended Comprehensive SMART error
457 log has increased since the last check.
458 If both ´-l error´ and ´-l xerror´ are specified, smartd checks
460 the maximum of both values.
461 [Please see the smartctl -l xerror command-line option.]
463 selftest - report if the number of failed tests reported in the
465 SMART Self-Test Log has increased since the last check, or if
466 the timestamp associated with the most recent failed test has
467 increased. Note that such errors will only be logged if you run
468 self-tests on the disk (and it fails a test!). Self-Tests can
469 be run automatically by smartd: please see the ´-s´ Directive
470 below. Self-Tests can also be run manually by using the
471 ´-t short´ and ´-t long´ options of smartctl and the results of
472 the testing can be observed using the smartctl ´-l selftest´
473 command-line option.]
474 [Please see the smartctl -l and -t command-line options.]
476 -s REGEXP
478 Run Self-Tests or Offline Immediate Tests, at scheduled times.
479 A Self- or Offline Immediate Test will be run at the end of
480 periodic device polling, if all 12 characters of the string
481 T/MM/DD/d/HH match the extended regular expression REGEXP. Here:
482 T is the type of the test. The values that smartd will try to
484 match (in turn) are: ´L´ for a Long Self-Test, ´S´ for a
485 Short Self-Test, ´C´ for a Conveyance Self-Test (ATA only),
486 and ´O´ for an Offline Immediate Test (ATA only). As soon
487 as a match is found, the test will be started and no addi‐
488 tional matches will be sought for that device and that
489 polling cycle.
490 [NEW EXPERIMENTAL SMARTD FEATURE] To run scheduled Selective
492 Self-Tests, use ´n´ for next span, ´r´ to redo last span, or
493 ´c´ to continue with next span or redo last span based on
494 status of last test. The LBA range is based on the first
495 span from the last test. See the smartctl -t
496 select,[next|redo|cont] options for further info.
497 MM is the month of the year, expressed with two decimal digits.
500 The range is from 01 (January) to 12 (December) inclusive.
501 Do not use a single decimal digit or the match will always
502 fail!
503 DD is the day of the month, expressed with two decimal digits.
505 The range is from 01 to 31 inclusive. Do not use a single
506 decimal digit or the match will always fail!
507 d is the day of the week, expressed with one decimal digit.
509 The range is from 1 (Monday) to 7 (Sunday) inclusive.
510 HH is the hour of the day, written with two decimal digits, and
512 given in hours after midnight. The range is 00 (midnight to
513 just before 1am) to 23 (11pm to just before midnight) inclu‐
514 sive. Do not use a single decimal digit or the match will
515 always fail!
516 Some examples follow. In reading these, keep in mind that in
518 extended regular expressions a dot ´.´ matches any single char‐
519 acter, and a parenthetical expression such as ´(A|B|C)´ denotes
520 any one of the three possibilities A, B, or C.
521 To schedule a short Self-Test between 2-3am every morning, use:
523 -s S/../.././02
524 To schedule a long Self-Test between 4-5am every Sunday morning,
525 use:
526 -s L/../../7/04
527 To schedule a long Self-Test between 10-11pm on the first and
528 fifteenth day of each month, use:
529 -s L/../(01|15)/./22
530 To schedule an Offline Immediate test after every midnight, 6am,
531 noon,and 6pm, plus a Short Self-Test daily at 1-2am and a Long
532 Self-Test every Saturday at 3-4am, use:
533 -s (O/../.././(00|06|12|18)|S/../.././01|L/../../6/03)
534 If Long Self-Tests of a large disks take longer than the system
535 uptime, a full disk test can be performed by several Selective
536 Self-Tests. To setup a full test of a 1TB disk within 20 days
537 (one 50GB span each day), run this command once:
538 smartctl -t select,0-99999999 /dev/sda
539 To run the next test spans on Monday-Friday between 12-13am, run
540 smartd with this directive:
541 -s n/../../[1-5]/12
542 Scheduled tests are run immediately following the regularly-
545 scheduled device polling, if the current local date, time, and
546 test type, match REGEXP. By default the regularly-scheduled
547 device polling occurs every thirty minutes after starting
548 smartd. Take caution if you use the ´-i´ option to make this
549 polling interval more than sixty minutes: the poll times may
550 fail to coincide with any of the testing times that you have
551 specified with REGEXP. In this case the test will be run fol‐
552 lowing the next device polling.
553 Before running an offline or self-test, smartd checks to be sure
555 that a self-test is not already running. If a self-test is
556 already running, then this running self test will not be inter‐
557 rupted to begin another test.
558 smartd will not attempt to run any type of test if another test
560 was already started or run in the same hour.
561 To avoid performance problems during system boot, smartd will
563 not attempt to run any scheduled tests following the very first
564 device polling (unless ´-q onecheck´ is specified).
565 Each time a test is run, smartd will log an entry to SYSLOG.
567 You can use these or the '-q showtests' command-line option to
568 verify that you constructed REGEXP correctly. The matching
569 order (L before S before C before O) ensures that if multiple
570 test types are all scheduled for the same hour, the longer test
571 type has precedence. This is usually the desired behavior.
572 If the scheduled tests are used in conjunction with state per‐
574 sistence (´-s´ option), smartd will also try to match the hours
575 since last shutdown (or 90 days at most). If any test would have
576 been started during downtime, the longest (see above) of these
577 tests is run after second device polling.
578 If the ´-n´ directive is used and any test would have been
580 started during disk standby time, the longest of these tests is
581 run when the disk is active again.
582 Unix users: please beware that the rules for extended regular
584 expressions [regex(7)] are not the same as the rules for
585 file-name pattern matching by the shell [glob(7)]. smartd will
586 issue harmless informational warning messages if it detects
587 characters in REGEXP that appear to indicate that you have made
588 this mistake.
589 -m ADD Send a warning email to the email address ADD if the ´-H´, ´-l´,
591 ´-f´, ´-C´, or ´-O´ Directives detect a failure or a new error,
592 or if a SMART command to the disk fails. This Directive only
593 works in conjunction with these other Directives (or with the
594 equivalent default ´-a´ Directive).
595 To prevent your email in-box from getting filled up with warning
597 messages, by default only a single warning will be sent for each
598 of the enabled alert types, ´-H´, ´-l´, ´-f´, ´-C´, or ´-O´ even
599 if more than one failure or error is detected or if the failure
600 or error persists. [This behavior can be modified; see the ´-M´
601 Directive below.]
602 To send email to more than one user, please use the following
604 "comma separated" form for the address:
605 user1@add1,user2@add2,...,userN@addN (with no spaces).
606 To test that email is being sent correctly, use the ´-M test´
608 Directive described below to send one test email message on
609 smartd startup.
610 By default, email is sent using the system mail command. In
612 order that smartd find the mail command (normally /bin/mail) an
613 executable named ´mail´ must be in the path of the shell or
614 environment from which smartd was started. If you wish to spec‐
615 ify an explicit path to the mail executable (for example
616 /usr/local/bin/mail) or a custom script to run, please use the
617 ´-M exec´ Directive below.
618 Note that by default under Solaris, in the previous paragraph,
620 ´mailx´ and ´/bin/mailx´ are used, since Solaris ´/bin/mail´
621 does not accept a ´-s´ (Subject) command-line argument.
622 On Windows, the ´Blat´ mailer (http://blat.sourceforge.net/) is
624 used by default. This mailer uses a different command line syn‐
625 tax, see ´-M exec´ below.
626 Note also that there is a special argument <nomailer> which can
628 be given to the ´-m´ Directive in conjunction with the ´-M exec´
629 Directive. Please see below for an explanation of its effect.
630 If the mailer or the shell running it produces any STDERR/STDOUT
632 output, then a snippet of that output will be copied to SYSLOG.
633 The remainder of the output is discarded. If problems are
634 encountered in sending mail, this should help you to understand
635 and fix them. If you have mail problems, we recommend running
636 smartd in debug mode with the ´-d´ flag, using the ´-M test´
637 Directive described below.
638 The following extension is available on Windows: By specifying
640 ´msgbox´ as a mail address, a warning "email" is displayed as a
641 message box on the screen. Using both ´msgbox´ and regular mail
642 addresses is possible, if ´msgbox´ is the first word in the
643 comma separated list. With ´sysmsgbox´, a system modal (always
644 on top) message box is used. If running as a service, a service
645 notification message box (always shown on current visible desk‐
646 top) is used.
647 -M TYPE
649 These Directives modify the behavior of the smartd email warn‐
650 ings enabled with the ´-m´ email Directive described above.
651 These ´-M´ Directives only work in conjunction with the ´-m´
652 Directive and can not be used without it.
653 Multiple -M Directives may be given. If more than one of the
655 following three -M Directives are given (example: -M once -M
656 daily) then the final one (in the example, -M daily) is used.
657 The valid arguments to the -M Directive are (one of the follow‐
659 ing three):
660 once - send only one warning email for each type of disk problem
662 detected. This is the default.
663 daily - send additional warning reminder emails, once per day,
665 for each type of disk problem detected.
666 diminishing - send additional warning reminder emails, after a
668 one-day interval, then a two-day interval, then a four-day
669 interval, and so on for each type of disk problem detected. Each
670 interval is twice as long as the previous interval.
671 In addition, one may add zero or more of the following Direc‐
673 tives:
674 test - send a single test email immediately upon smartd startup.
676 This allows one to verify that email is delivered correctly.
677 Note that if this Directive is used, smartd will also send the
678 normal email warnings that were enabled with the ´-m´ Directive,
679 in addition to the single test email!
680 exec PATH - run the executable PATH instead of the default mail
682 command, when smartd needs to send email. PATH must point to an
683 executable binary file or script.
684 By setting PATH to point to a customized script, you can make
686 smartd perform useful tricks when a disk problem is detected
687 (beeping the console, shutting down the machine, broadcasting
688 warnings to all logged-in users, etc.) But please be careful.
689 smartd will block until the executable PATH returns, so if your
690 executable hangs, then smartd will also hang. Some sample
691 scripts are included in /usr/share/doc/smartmontools/example‐
692 scripts/.
693 The return status of the executable is recorded by smartd in
695 SYSLOG. The executable is not expected to write to STDOUT or
696 STDERR. If it does, then this is interpreted as indicating that
697 something is going wrong with your executable, and a fragment of
698 this output is logged to SYSLOG to help you to understand the
699 problem. Normally, if you wish to leave some record behind, the
700 executable should send mail or write to a file or device.
701 Before running the executable, smartd sets a number of environ‐
703 ment variables. These environment variables may be used to con‐
704 trol the executable´s behavior. The environment variables
705 exported by smartd are:
706 SMARTD_MAILER
708 is set to the argument of -M exec, if present or else to
709 ´mail´ (examples: /bin/mail, mail).
710 SMARTD_DEVICE
712 is set to the device path (examples: /dev/hda, /dev/sdb).
713 SMARTD_DEVICETYPE
715 is set to the device type specified by ´-d´ directive or
716 ´auto´ if none.
717 SMARTD_DEVICESTRING
719 is set to the device description. For SMARTD_DEVICETYPE of
720 ata or scsi, this is the same as SMARTD_DEVICE. For 3ware
721 RAID controllers, the form used is ´/dev/sdc
722 [3ware_disk_01]´. For HighPoint RocketRAID controller, the
723 form is ´/dev/sdd [hpt_1/1/1]´ under Linux or ´/dev/hptrr
724 [hpt_1/1/1]´ under FreeBSD. For Areca controllers, the form
725 is ´/dev/sg2 [areca_disk_09]´. In these cases the device
726 string contains a space and is NOT quoted. So to use
727 $SMARTD_DEVICESTRING in a bash script you should probably
728 enclose it in double quotes.
729 SMARTD_FAILTYPE
731 gives the reason for the warning or message email. The pos‐
732 sible values that it takes and their meanings are:
733 EmailTest: this is an email test message.
734 Health: the SMART health status indicates imminent failure.
735 Usage: a usage Attribute has failed.
736 SelfTest: the number of self-test failures has increased.
737 ErrorCount: the number of errors in the ATA error log has
738 increased.
739 CurrentPendingSector: one of more disk sectors could not be
740 read and are marked to be reallocated (replaced with spare
741 sectors).
742 OfflineUncorrectableSector: during off-line testing, or
743 self-testing, one or more disk sectors could not be read.
744 Temperature: Temperature reached critical limit (see -W
745 directive).
746 FailedHealthCheck: the SMART health status command failed.
747 FailedReadSmartData: the command to read SMART Attribute
748 data failed.
749 FailedReadSmartErrorLog: the command to read the SMART error
750 log failed.
751 FailedReadSmartSelfTestLog: the command to read the SMART
752 self-test log failed.
753 FailedOpenDevice: the open() command to the device failed.
754 SMARTD_ADDRESS
756 is determined by the address argument ADD of the ´-m´ Direc‐
757 tive. If ADD is <nomailer>, then SMARTD_ADDRESS is not set.
758 Otherwise, it is set to the comma-separated-list of email
759 addresses given by the argument ADD, with the commas
760 replaced by spaces (example:admin@example.com root). If
761 more than one email address is given, then this string will
762 contain space characters and is NOT quoted, so to use it in
763 a bash script you may want to enclose it in double quotes.
764 SMARTD_MESSAGE
766 is set to the one sentence summary warning email message
767 string from smartd. This message string contains space
768 characters and is NOT quoted. So to use $SMARTD_MESSAGE in a
769 bash script you should probably enclose it in double quotes.
770 SMARTD_FULLMESSAGE
772 is set to the contents of the entire email warning message
773 string from smartd. This message string contains space and
774 return characters and is NOT quoted. So to use
775 $SMARTD_FULLMESSAGE in a bash script you should probably
776 enclose it in double quotes.
777 SMARTD_TFIRST
779 is a text string giving the time and date at which the first
780 problem of this type was reported. This text string contains
781 space characters and no newlines, and is NOT quoted. For
782 example:
783 Sun Feb 9 14:58:19 2003 CST
784 SMARTD_TFIRSTEPOCH
786 is an integer, which is the unix epoch (number of seconds
787 since Jan 1, 1970) for SMARTD_TFIRST.
788 The shell which is used to run PATH is system-dependent. For
790 vanilla Linux/glibc it´s bash. For other systems, the man page
791 for popen(3) should say what shell is used.
792 If the ´-m ADD´ Directive is given with a normal address argu‐
794 ment, then the executable pointed to by PATH will be run in a
795 shell with STDIN receiving the body of the email message, and
796 with the same command-line arguments:
797 -s "$SMARTD_SUBJECT" $SMARTD_ADDRESS
798 that would normally be provided to ´mail´. Examples include:
799 -m user@home -M exec /bin/mail
800 -m admin@work -M exec /usr/local/bin/mailto
801 -m root -M exec /Example_1/bash/script/below
802 Note that on Windows, the syntax of the ´Blat´ mailer is used:
804 - -q -subject "$SMARTD_SUBJECT" -to "$SMARTD_ADDRESS"
805 If the ´-m ADD´ Directive is given with the special address
807 argument <nomailer> then the executable pointed to by PATH is
808 run in a shell with no STDIN and no command-line arguments, for
809 example:
810 -m <nomailer> -M exec /Example_2/bash/script/below
811 If the executable produces any STDERR/STDOUT output, then smartd
812 assumes that something is going wrong, and a snippet of that
813 output will be copied to SYSLOG. The remainder of the output is
814 then discarded.
815 Some EXAMPLES of scripts that can be used with the ´-M exec´
817 Directive are given below. Some sample scripts are also included
818 in /usr/share/doc/smartmontools/examplescripts/.
819 -f Check for ´failure´ of any Usage Attributes. If these
821 Attributes are less than or equal to the threshold, it does NOT
822 indicate imminent disk failure. It "indicates an advisory con‐
823 dition where the usage or age of the device has exceeded its
824 intended design life period." [Please see the smartctl -A com‐
825 mand-line option.]
826 -p Report anytime that a Prefail Attribute has changed its value
828 since the last check, 30 minutes ago. [Please see the smartctl
829 -A command-line option.]
830 -u Report anytime that a Usage Attribute has changed its value
832 since the last check, 30 minutes ago. [Please see the smartctl
833 -A command-line option.]
834 -t Equivalent to turning on the two previous flags ´-p´ and ´-u´.
836 Tracks changes in all device Attributes (both Prefailure and
837 Usage). [Please see the smartctl -A command-line option.]
838 -i ID Ignore device Attribute number ID when checking for failure of
840 Usage Attributes. ID must be a decimal integer in the range
841 from 1 to 255. This Directive modifies the behavior of the ´-f´
842 Directive and has no effect without it.
843 This is useful, for example, if you have a very old disk and
845 don´t want to keep getting messages about the hours-on-lifetime
846 Attribute (usually Attribute 9) failing. This Directive may
847 appear multiple times for a single device, if you want to ignore
848 multiple Attributes.
849 -I ID Ignore device Attribute ID when tracking changes in the
851 Attribute values. ID must be a decimal integer in the range
852 from 1 to 255. This Directive modifies the behavior of the
853 ´-p´, ´-u´, and ´-t´ tracking Directives and has no effect with‐
854 out one of them.
855 This is useful, for example, if one of the device Attributes is
857 the disk temperature (usually Attribute 194 or 231). It´s annoy‐
858 ing to get reports each time the temperature changes. This
859 Directive may appear multiple times for a single device, if you
860 want to ignore multiple Attributes.
861 -r ID[!]
863 When tracking, report the Raw value of Attribute ID along with
864 its (normally reported) Normalized value. ID must be a decimal
865 integer in the range from 1 to 255. This Directive modifies the
866 behavior of the ´-p´, ´-u´, and ´-t´ tracking Directives and has
867 no effect without one of them. This Directive may be given mul‐
868 tiple times.
869 A common use of this Directive is to track the device Tempera‐
871 ture (often ID=194 or 231).
872 If the optional flag ´!´ is appended, a change of the Normalized
874 value is considered critical. The report will be logged as
875 LOG_CRIT and a warning email will be sent if ´-m´ is specified.
876 -R ID[!]
878 When tracking, report whenever the Raw value of Attribute ID
879 changes. (Normally smartd only tracks/reports changes of the
880 Normalized Attribute values.) ID must be a decimal integer in
881 the range from 1 to 255. This Directive modifies the behavior
882 of the ´-p´, ´-u´, and ´-t´ tracking Directives and has no
883 effect without one of them. This Directive may be given multi‐
884 ple times.
885 If this Directive is given, it automatically implies the ´-r´
887 Directive for the same Attribute, so that the Raw value of the
888 Attribute is reported.
889 A common use of this Directive is to track the device Tempera‐
891 ture (often ID=194 or 231). It is also useful for understanding
892 how different types of system behavior affects the values of
893 certain Attributes.
894 If the optional flag ´!´ is appended, a change of the Raw value
896 is considered critical. The report will be logged as LOG_CRIT
897 and a warning email will be sent if ´-m´ is specified. An exam‐
898 ple is ´-R 5!´ to warn when new sectors are reallocated.
899 -C ID[+]
901 [ATA only] Report if the current number of pending sectors is
902 non-zero. Here ID is the id number of the Attribute whose raw
903 value is the Current Pending Sector count. The allowed range of
904 ID is 0 to 255 inclusive. To turn off this reporting, use
905 ID = 0. If the -C ID option is not given, then it defaults to
906 -C 197 (since Attribute 197 is generally used to monitor pending
907 sectors). If the name of this Attribute is changed by a ´-v
908 197,FORMAT,NAME´ directive, the default is changed to -C 0.
909 If ´+´ is specified, a report is only printed if the number of
911 sectors has increased between two check cycles. Some disks do
912 not reset this attribute when a bad sector is reallocated. See
913 also ´-v 197,increasing´ below.
914 A pending sector is a disk sector (containing 512 bytes of your
916 data) which the device would like to mark as ``bad" and reallo‐
917 cate. Typically this is because your computer tried to read
918 that sector, and the read failed because the data on it has been
919 corrupted and has inconsistent Error Checking and Correction
920 (ECC) codes. This is important to know, because it means that
921 there is some unreadable data on the disk. The problem of fig‐
922 uring out what file this data belongs to is operating system and
923 file system specific. You can typically force the sector to
924 reallocate by writing to it (translation: make the device sub‐
925 stitute a spare good sector for the bad one) but at the price of
926 losing the 512 bytes of data stored there.
927 -U ID[+]
929 [ATA only] Report if the number of offline uncorrectable sectors
930 is non-zero. Here ID is the id number of the Attribute whose
931 raw value is the Offline Uncorrectable Sector count. The
932 allowed range of ID is 0 to 255 inclusive. To turn off this
933 reporting, use ID = 0. If the -U ID option is not given, then
934 it defaults to -U 198 (since Attribute 198 is generally used to
935 monitor offline uncorrectable sectors). If the name of this
936 Attribute is changed by a ´-v 198,FORMAT,NAME´ (except ´-v
937 198,FORMAT,Offline_Scan_UNC_SectCt´), directive, the default is
938 changed to -U 0.
939 If ´+´ is specified, a report is only printed if the number of
941 sectors has increased since the last check cycle. Some disks do
942 not reset this attribute when a bad sector is reallocated. See
943 also ´-v 198,increasing´ below.
944 An offline uncorrectable sector is a disk sector which was not
946 readable during an off-line scan or a self-test. This is impor‐
947 tant to know, because if you have data stored in this disk sec‐
948 tor, and you need to read it, the read will fail. Please see
949 the previous ´-C´ option for more details.
950 -W DIFF[,INFO[,CRIT]]
952 Report if the current temperature had changed by at least DIFF
953 degrees since last report, or if new min or max temperature is
954 detected. Report or Warn if the temperature is greater or equal
955 than one of INFO or CRIT degrees Celsius. If the limit CRIT is
956 reached, a message with loglevel ´LOG_CRIT´ will be logged to
957 syslog and a warning email will be send if '-m' is specified. If
958 only the limit INFO is reached, a message with loglevel
959 ´LOG_INFO´ will be logged.
960 If this directive is used in conjunction with state persistence
962 (´-s´ option), the min and max temperature values are preserved
963 across boot cycles. The minimum temperature value is not updated
964 during the first 30 minutes after startup.
965 To disable any of the 3 reports, set the corresponding limit to
967 0. Trailing zero arguments may be omitted. By default, all tem‐
968 perature reports are disabled (´-W 0´).
969 To track temperature changes of at least 2 degrees, use:
971 -W 2
972 To log informal messages on temperatures of at least 40 degrees,
973 use:
974 -W 0,40
975 For warning messages/mails on temperatures of at least 45
976 degrees, use:
977 -W 0,0,45
978 To combine all of the above reports, use:
979 -W 2,40,45
980 For ATA devices, smartd interprets Attribute 194 as Temperature
982 Celsius by default. This can be changed to Attribute 9 or 220 by
983 the drive database or by the ´-v´ directive, see below.
984 -F TYPE
986 [ATA only] Modifies the behavior of smartd to compensate for
987 some known and understood device firmware bug. The arguments to
988 this Directive are exclusive, so that only the final Directive
989 given is used. The valid values are:
990 none - Assume that the device firmware obeys the ATA specifica‐
992 tions. This is the default, unless the device has presets for
993 ´-F´ in the device database.
994 samsung - In some Samsung disks (example: model SV4012H Firmware
996 Version: RM100-08) some of the two- and four-byte quantities in
997 the SMART data structures are byte-swapped (relative to the ATA
998 specification). Enabling this option tells smartd to evaluate
999 these quantities in byte-reversed order. Some signs that your
1000 disk needs this option are (1) no self-test log printed, even
1001 though you have run self-tests; (2) very large numbers of ATA
1002 errors reported in the ATA error log; (3) strange and impossible
1003 values for the ATA error log timestamps.
1004 samsung2 - In some Samsung disks the number of ATA errors
1006 reported is byte swapped. Enabling this option tells smartd to
1007 evaluate this quantity in byte-reversed order.
1008 samsung3 - Some Samsung disks (at least SP2514N with Firmware
1010 VF100-37) report a self-test still in progress with 0% remaining
1011 when the test was already completed. If this directive is speci‐
1012 fied, smartd will not skip the next scheduled self-test (see
1013 Directive ´-s´ above) in this case.
1014 Note that an explicit ´-F´ Directive will over-ride any preset
1016 values for ´-F´ (see the ´-P´ option below).
1017 [Please see the smartctl -F command-line option.]
1020 -v ID,FORMAT[:BYTEORDER][,NAME]
1022 [ATA only] Sets a vendor-specific raw value print FORMAT, an
1023 optional BYTEORDER and an optional NAME for Attribute ID. This
1024 directive may be used multiple times. Please see smartctl -v
1025 command-line option for further details.
1026 The following arguments affect smartd warning output:
1028 197,increasing - Raw Attribute number 197 (Current Pending Sec‐
1030 tor Count) is not reset if uncorrectable sectors are reallo‐
1031 cated. This sets ´-C 197+´ if no other ´-C´ directive is speci‐
1032 fied.
1033 198,increasing - Raw Attribute number 198 (Offline Uncorrectable
1035 Sector Count) is not reset if uncorrectable sector are reallo‐
1036 cated. This sets ´-U 198+´ if no other ´-U´ directive is speci‐
1037 fied.
1038 -P TYPE
1040 Specifies whether smartd should use any preset options that are
1041 available for this drive. The valid arguments to this Directive
1042 are:
1043 use - use any presets that are available for this drive. This
1045 is the default.
1046 ignore - do not use any presets for this drive.
1048 show - show the presets listed for this drive in the database.
1050 showall - show the presets that are available for all drives and
1052 then exit.
1053 [Please see the smartctl -P command-line option.]
1055 -a Equivalent to turning on all of the following Directives: ´-H´
1057 to check the SMART health status, ´-f´ to report failures of
1058 Usage (rather than Prefail) Attributes, ´-t´ to track changes in
1059 both Prefailure and Usage Attributes, ´-l selftest´ to report
1060 increases in the number of Self-Test Log errors, ´-l error´ to
1061 report increases in the number of ATA errors, ´-C 197´ to report
1062 nonzero values of the current pending sector count, and ´-U 198´
1063 to report nonzero values of the offline pending sector count.
1064 Note that -a is the default for ATA devices. If none of these
1066 other Directives is given, then -a is assumed.
1067 # Comment: ignore the remainder of the line.
1069 \ Continuation character: if this is the last non-white or non-
1071 comment character on a line, then the following line is a con‐
1072 tinuation of the current one.
1073 If you are not sure which Directives to use, I suggest experimenting
1075 for a few minutes with smartctl to see what SMART functionality your
1076 disk(s) support(s). If you do not like voluminous syslog messages, a
1077 good choice of smartd configuration file Directives might be:
1078 -H -l selftest -l error -f.
1079 If you want more frequent information, use: -a.
1080 ADDITIONAL DETAILS ABOUT DEVICESCAN
1083 If a non-comment entry in the configuration file is the text
1084 string DEVICESCAN in capital letters, then smartd will ignore
1085 any remaining lines in the configuration file, and will scan for
1086 devices.
1087 [NEW EXPERIMENTAL SMARTD FEATURE] Configuration entries for
1089 devices not found by the platform-specific device scanning may
1090 precede the DEVICESCAN entry.
1091 If DEVICESCAN is not followed by any Directives, then smartd
1093 will scan for both ATA and SCSI devices, and will monitor all
1094 possible SMART properties of any devices that are found.
1095 DEVICESCAN may optionally be followed by any valid Directives,
1097 which will be applied to all devices that are found in the scan.
1098 For example
1099 DEVICESCAN -m root@example.com
1100 will scan for all devices, and then monitor them. It will send
1101 one email warning per device for any problems that are found.
1102 DEVICESCAN -d ata -m root@example.com
1103 will do the same, but restricts the scan to ATA devices only.
1104 DEVICESCAN -H -d ata -m root@example.com
1105 will do the same, but only monitors the SMART health status of
1106 the devices, (rather than the default -a, which monitors all
1107 SMART properties).
1108 EXAMPLES OF SHELL SCRIPTS FOR ´-M exec´
1111 These are two examples of shell scripts that can be used with
1112 the ´-M exec PATH´ Directive described previously. The paths to
1113 these scripts and similar executables is the PATH argument to
1114 the ´-M exec PATH´ Directive.
1115 Example 1: This script is for use with ´-m ADDRESS -M exec
1117 PATH´. It appends the output of smartctl -a to the output of
1118 the smartd email warning message and sends it to ADDRESS.
1119 #! /bin/bash
1121 # Save the email message (STDIN) to a file:
1123 cat > /root/msg
1124 # Append the output of smartctl -a to the message:
1126 /usr/sbin/smartctl -a -d $SMART_DEVICETYPE $SMARTD_DEVICE >> /root/msg
1127 # Now email the message to the user at address ADD:
1129 /bin/mail -s "$SMARTD_SUBJECT" $SMARTD_ADDRESS < /root/msg
1130 Example 2: This script is for use with ´-m <nomailer> -M exec
1132 PATH´. It warns all users about a disk problem, waits 30 sec‐
1133 onds, and then powers down the machine.
1134 #! /bin/bash
1136 # Warn all users of a problem
1138 wall ´Problem detected with disk: ´ "$SMARTD_DEVICESTRING"
1139 wall ´Warning message from smartd is: ´ "$SMARTD_MESSAGE"
1140 wall ´Shutting down machine in 30 seconds... ´
1141 # Wait half a minute
1143 sleep 30
1144 # Power down the machine
1146 /sbin/shutdown -hf now
1147 Some example scripts are distributed with the smartmontools
1149 package, in /usr/share/doc/smartmontools/examplescripts/.
1150 Please note that these scripts typically run as root, so any
1152 files that they read/write should not be writable by ordinary
1153 users or reside in directories like /tmp that are writable by
1154 ordinary users and may expose your system to symlink attacks.
1155 As previously described, if the scripts write to STDOUT or
1157 STDERR, this is interpreted as indicating that there was an
1158 internal error within the script, and a snippet of STDOUT/STDERR
1159 is logged to SYSLOG. The remainder is flushed.
1160
1164 Bruce Allen smartmontools-support@lists.sourceforge.net
1165 University of Wisconsin - Milwaukee Physics Department
1166
1169 The following have made large contributions to smartmontools:
1170 Casper Dik (Solaris SCSI interface)
1171 Christian Franke (Windows interface, C++ redesign, USB support, ...)
1172 Douglas Gilbert (SCSI subsystem)
1173 Guido Guenther (Autoconf/Automake packaging)
1174 Geoffrey Keating (Darwin ATA interface)
1175 Eduard Martinescu (FreeBSD interface)
1176 Frederic L. W. Meunier (Web site and Mailing list)
1177 Gabriele Pohl (Web site and Wiki, conversion from CVS to SVN)
1178 Keiji Sawada (Solaris ATA interface)
1179 Manfred Schwarb (Drive database)
1180 Sergey Svishchev (NetBSD interface)
1181 David Snyder and Sergey Svishchev (OpenBSD interface)
1182 Phil Williams (User interface and drive database)
1183 Shengfeng Zhou (Linux/FreeBSD HighPoint RocketRAID interface)
1184 Many other individuals have made smaller contributions and corrections.
1185
1188 This code was derived from the smartsuite package, written by Michael
1189 Cornwell, and from the previous UCSC smartsuite package. It extends
1190 these to cover ATA-5 disks. This code was originally developed as a
1191 Senior Thesis by Michael Cornwell at the Concurrent Systems Laboratory
1192 (now part of the Storage Systems Research Center), Jack Baskin School
1193 of Engineering, University of California, Santa Cruz.
1194 http://ssrc.soe.ucsc.edu/ .
1195
1197 Please see the following web site for updates, further documentation,
1198 bug reports and patches: http://smartmontools.sourceforge.net/
1199
1202 smartd(8), smartctl(8), syslogd(8), syslog.conf(5), badblocks(8),
1203 ide-smart(8), regex(7).
1204
1207 $Id: smartd.conf.5.in 3186 2010-10-16 13:09:11Z chrfranke $
1208smartmontools-5.40 2010-10-16 SMARTD.CONF(5)