.ig
Copyright (C) 2002-10 Bruce Allen <smartmontools-support@lists.sourceforge.net>
+Copyright (C) 2004-13 Christian Franke <smartmontools-support@lists.sourceforge.net>
-$Id: smartd.conf.5.in 3561 2012-06-05 19:49:31Z chrfranke $
+$Id: smartd.conf.5.in 3741 2013-01-02 17:06:54Z chrfranke $
-This program is free software; you can redistribute it and/or modify it
-under the terms of the GNU General Public License as published by the Free
-Software Foundation; either version 2, or (at your option) any later
-version.
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2, or (at your option)
+any later version.
-You should have received a copy of the GNU General Public License (for
-example COPYING); if not, write to the Free Software Foundation, Inc., 675
-Mass Ave, Cambridge, MA 02139, USA.
+You should have received a copy of the GNU General Public License
+(for example COPYING); If not, see <http://www.gnu.org/licenses/>.
This code was originally developed as a Senior Thesis by Michael Cornwell
at the Concurrent Systems Laboratory (now part of the Storage Systems
Research Center), Jack Baskin School of Engineering, University of
California, Santa Cruz. http://ssrc.soe.ucsc.edu/
+
..
.TH SMARTD.CONF 5 CURRENT_SVN_DATE CURRENT_SVN_VERSION CURRENT_SVN_DATE
.SH NAME
.\"! .PP
.\" %ENDIF NOT OS ALL
\fB/usr/local/etc/smartd.conf\fP is the configuration file for the \fBsmartd\fP
-daemon, which monitors the Self-Monitoring, Analysis and Reporting
-Technology (SMART) system built into many ATA-3 and later ATA, IDE and
-SCSI-3 hard drives.
+daemon.
If the configuration file \fB/usr/local/etc/smartd.conf\fP is present,
\fBsmartd\fP reads it at startup, before \fBfork\fP(2)ing into the
\fB\<CONTROL-C\>\fP in the terminal window where \fBsmartd\fP is
running.
-.SH CONFIGURATION FILE /usr/local/etc/smartd.conf
In the absence of a configuration file
-\fBsmartd\fP will try to open all available devices.
-.\" %IF OS Linux
-Under linux \fBsmartd\fP will try to open the 20 ATA devices
-.B /dev/hd[a-t]
-and the 26 SCSI devices
-.B /dev/sd[a-z].
-.\" %ENDIF OS Linux
-.\" %IF OS FreeBSD
-Under FreeBSD,
-\fBsmartd\fP
-will try to open all existing ATA/SATA devices (using ATA subsystem)
-.B /dev/ad[0-9]+
-and all existing SCSI/SAS/AHCI devices (using CAM subsystem).
-.\" %ENDIF OS FreeBSD
-.\" %IF OS NetBSD OpenBSD
-Under NetBSD/OpenBSD,
-\fBsmartd\fP
-will try to open all existing ATA devices (with entries in /dev)
-.B /dev/wd[0-9]+c
-and all existing SCSI devices
-.B /dev/sd[0-9]+c.
-.\" %ENDIF OS NetBSD OpenBSD
-.\" %IF OS Solaris
-Under Solaris \fBsmartd\fP will try to open all entries \fB"/dev/rdsk/c?t?d?s?"\fP for IDE/ATA and SCSI disk
-devices, and entries \fB"/dev/rmt/*"\fP for SCSI tape devices.
-.\" %ENDIF OS Solaris
-.\" %IF OS Windows
-Under Windows \fBsmartd\fP will try to open all entries \fB"/dev/hd[a-j]"\fP ("\\\\.\\PhysicalDrive[0-9]")
-for IDE/ATA devices on WinNT4/2000/XP, \fB"/dev/hd[a-d]"\fP
-(bitmask from "\\\\.\\SMARTVSD") for IDE/ATA devices on Win95/98/98SE/ME,
-and \fB"/dev/scsi[0-9][0-7]"\fP (ASPI adapter 0-9, ID 0-7) for SCSI
-devices on all versions of Windows.
-.\" %ENDIF OS Windows
-.\" %IF OS Darwin
-Under Darwin, \fBsmartd\fP will open any ATA block storage device.
-.\" %ENDIF OS Darwin
+\fBsmartd\fP will try to open all available devices
+(see \fBsmartd\fP(8) man page).
+A configuration file with a single line \fB\'DEVICESCAN \-a'\fP
+would have the same effect.
This can be annoying if you have an ATA or SCSI device that hangs or
misbehaves when receiving SMART commands. Even if this causes no
-problems, you may be annoyed by the string of error log messages about
-block-major devices that can\'t be found, and SCSI devices that can\'t
-be opened.
+problems, you may be annoyed by the string of error log messages about devices
+that can\'t be opened.
One can avoid this problem, and gain more control over the types of
events monitored by
.B \ \ /dev/sda -d megaraid,0 -a -s S/../.././01
.B \ \ /dev/sda -d megaraid,1 -a -s S/../.././02
.B \ \ /dev/sda -d megaraid,2 -a -s S/../.././03
+.B \ \ /dev/bus/0 -d megaraid,2 -a -s S/../.././03
.B
.B #
.\" %ENDIF OS Linux
.B # Two SATA (not SAS) disks on a 3ware 9750 controller.
.B # Start long self-tests Sundays between midnight and
.B # 1am and 2-3 am
+.\" %IF OS Linux
.B \ \ /dev/twl0 -d 3ware,0 -a -s L/../../7/00
.B \ \ /dev/twl0 -d 3ware,1 -a -s L/../../7/02
+.\" %ENDIF OS Linux
+.\" %IF OS FreeBSD
+.B \ \ /dev/tws0 -d 3ware,0 -a -s L/../../7/00
+.B \ \ /dev/tws0 -d 3ware,1 -a -s L/../../7/02
+.\" %ENDIF OS FreeBSD
.B #
.nf
.B # Three SATA disks on a HighPoint RocketRAID controller.
.B If a 3ware controller is used
then the corresponding SCSI (/dev/sd?) or character device (/dev/twe?,
-/dev/twa? or /dev/twl?) must be listed, along with the \'\-d 3ware,N\'
+/dev/twa?, /dev/twl? or /dev/tws?) must be listed, along with the \'\-d 3ware,N\'
Directive (see below). The individual ATA disks hosted by the 3ware
controller appear to \fBsmartd\fP as normal ATA devices. Hence all
the ATA directives can be used for these disks (but see note below).
The valid arguments to this directive are:
.I auto
-- attempt to guess the device type from the device name or from
+\- attempt to guess the device type from the device name or from
controller type info provided by the operating system or from
a matching USB ID entry in the drive database.
This is the default.
the other 16 bytes long. The default is the 16 byte variant which can be
overridden with either \'\-d sat,12\' or \'\-d sat,16\'.
-[NEW EXPERIMENTAL SMARTD FEATURE] If \'-d sat,auto\' is specified,
-device type SAT (for ATA/SATA disks) is
+If \'\-d sat,auto\' is specified, device type SAT (for ATA/SATA disks) is
only used if the SCSI INQUIRY data reports a SATL (VENDOR: "ATA ").
Otherwise device type SCSI (for SCSI/SAS disks) is used.
with \'\-d usbcypress,0xN\', where N is the scsi operation code,
you're running the risk of damage to the device or filesystems on it.
-.I usbjmicron
-- this device type is for SATA disks that are behind a JMicron USB to
+.I usbjmicron[,p][,x][,PORT]
+\- this device type is for SATA disks that are behind a JMicron USB to
PATA/SATA bridge. The 48-bit ATA commands (required e.g. for \'\-l xerror\',
see below) do not work with all of these bridges and are therefore disabled by
default. These commands can be enabled by \'\-d usbjmicron,x\'.
in I/O errors and may disconnect the drive. The same applies if the specified
PORT does not exist or is not connected to a disk.
+[NEW EXPERIMENTAL SMARTD FEATURE]
+The Prolific PL2507/3507 USB bridges with older firmware support a pass-through
+command similar to JMicron and work with \'\-d usbjmicron,0\'.
+Newer Prolific firmware requires a modified command which can be selected by
+\'\-d usbjmicron,p\'.
+Note that this does not yet support the SMART status command.
+
.I usbsunplus
\- this device type is for SATA disks that are behind a SunplusIT USB to SATA
bridge.
This interface will also work for Dell PERC controllers.
In log files and email messages this disk will be identified as
megaraid_disk_XXX with XXX in the range from 000 to 127 inclusive.
+It is possible to set RAID device name as /dev/bus/N, where N is a SCSI bus
+number.
Please see the \fBsmartctl\fP(8) man page for further details.
.\" %ENDIF OS Linux
.I areca,N/E
\- [FreeBSD, Linux, Windows and Cygwin only] [NEW EXPERIMENTAL SMARTD FEATURE] the
-device consists of one or more SATA disks connected to an Areca SAS RAID controller.
+device consists of one or more SATA or SAS disks connected to an Areca SAS RAID controller.
The integer N (range 1 to 128) denotes the channel (slot) and E (range
1 to 8) denotes the enclosure.
-Important: This requires upcoming Areca SAS controller firmware version 1.51 or a
-recent beta version.
+Important: This requires Areca SAS controller firmware version 1.51 or later.
.\" %ENDIF OS FreeBSD Linux Windows Cygwin
.\" %IF OS FreeBSD Linux
.I cciss,N
-\- [FreeBSD and Linux only] the device consists of one or more SCSI/SAS disks
+\- [FreeBSD and Linux only] the device consists of one or more SCSI/SAS or SATA disks
connected to a cciss RAID controller. The non-negative integer N (in the range
from 0 to 15 inclusive) denotes which disk on the controller is monitored.
In log files and email messages this disk will be identified as cciss_disk_XX
Please see the \fBsmartctl\fP(8) man page for further details.
.\" %ENDIF OS FreeBSD Linux
+.I ignore
+\- [NEW EXPERIMENTAL SMARTD FEATURE]
+the device specified by this configuration entry should be ignored.
+This allows to ignore specific devices which are detected by a following
+DEVICESCAN configuration line.
+It may also be used to temporary disable longer multi-line configuration entries.
+This Directive may be used in conjunction with the other \'\-d\' Directives.
+
.I removable
\- the device or its media is removable. This indicates to
\fBsmartd\fP
and \'ACTIVE\'. Typically in the OFF, SLEEP, and STANDBY modes the
disk\'s platters are not spinning. But usually, in response to SMART
commands issued by \fBsmartd\fP, the disk platters are spun up. So if
-this option is not used, then a disk which is in a low\-power mode may
-be spun up and put into a higher\-power mode when it is periodically
+this option is not used, then a disk which is in a low-power mode may
+be spun up and put into a higher-power mode when it is periodically
polled by \fBsmartd\fP.
Note that if the disk is in SLEEP mode when \fBsmartd\fP is started,
then it won't respond to \fBsmartd\fP commands, and so the disk won't
be registered as a device for \fBsmartd\fP to monitor. If a disk is in
-any other low\-power mode, then the commands issued by \fBsmartd\fP to
-register the disk will probably cause it to spin\-up.
+any other low-power mode, then the commands issued by \fBsmartd\fP to
+register the disk will probably cause it to spin-up.
The \'\fB\-n\fP\' (nocheck) Directive specifies if \fBsmartd\fP\'s
periodic checks should still be carried out when the device is in a
-low\-power mode. It may be used to prevent a disk from being spun\-up
+low-power mode. It may be used to prevent a disk from being spun-up
by periodic \fBsmartd\fP polling. The allowed values of POWERMODE
are:
.I never
\- \fBsmartd\fP will poll (check) the device regardless of its power
-mode. This may cause a disk which is spun\-down to be spun\-up when
+mode. This may cause a disk which is spun-down to be spun-up when
\fBsmartd\fP checks it. This is the default behavior if the '\-n'
Directive is not given.
.I permissive
\- try to monitor the disk even if it appears to lack SMART
capabilities. This may be required for some old disks (prior to
-ATA\-3 revision 4) that implemented SMART before the SMART standards
-were incorporated into the ATA/ATAPI Specifications. This may also be
-needed for some Maxtor disks which fail to comply with the ATA
-Specifications and don't properly indicate support for error\- or
-self\-test logging.
-
+ATA-3 revision 4) that implemented SMART before the SMART standards
+were incorporated into the ATA/ATAPI Specifications.
[Please see the \fBsmartctl \-T\fP command-line option.]
.TP
.B \-o VALUE
options.]
[ATA only] Failed self-tests outdated by a newer successful extended
-self\-test are ignored. The warning email counter is reset if the
+self-test are ignored. The warning email counter is reset if the
number of failed self tests dropped to 0. This typically happens when
-an extended self\-test is run after all bad sectors have been reallocated.
+an extended self-test is run after all bad sectors have been reallocated.
.I offlinests[,ns]
\- [ATA only] report if the Offline Data Collection status has changed
[Please see the \fBsmartctl \-l scterc\fP command-line option.]
.TP
-.B -e NAME[,VALUE]
-[NEW EXPERIMENTAL SMARTD FEATURE] Sets non\-SMART device settings
-when \fBsmartd\fP starts up and has no further effect.
+.B \-e NAME[,VALUE]
+Sets non-SMART device settings when \fBsmartd\fP starts up and has no
+further effect.
[Please see the \fBsmartctl \-\-set\fP command-line option.]
Valid arguments are:
Unix users: please beware that the rules for extended regular
expressions [regex(7)] are \fBnot\fP the same as the rules for
-file\-name pattern matching by the shell [glob(7)]. \fBsmartd\fP will
+file-name pattern matching by the shell [glob(7)]. \fBsmartd\fP will
issue harmless informational warning messages if it detects characters
in \fBREGEXP\fP that appear to indicate that you have made this
mistake.
you have mail problems, we recommend running \fBsmartd\fP in debug
mode with the \'-d\' flag, using the \'-M test\' Directive described
below.
+.\" %IF NOT OS Windows
+
+[NEW EXPERIMENTAL SMARTD FEATURE]
+If a word of the comma separated list has the form \'@plugin\', a custom
+script /usr/local/etc/smartd_warning.d/plugin is run and the word is
+removed from the list before sending mail. The string \'plugin\' may be any
+valid name except \'ALL\'.
+If \'@ALL\' is specified, all scripts in /usr/local/etc/smartd_warning.d/*
+are run instead.
+This is handled by the script /usr/local/etc/smartd_warning.sh
+(see also \'\-M exec\' below).
+.\" %ENDIF NOT OS Windows
.\" %IF OS Windows
-The following extension is available on Windows:
-By specifying \'\fBmsgbox\fP\' as a mail address, a warning
-"email" is displayed as a message box on the screen.
-Using both \'\fBmsgbox\fP\' and regular mail addresses is possible,
-if \'\fBmsgbox\fP\' is the first word in the comma separated list.
-With \'\fBsysmsgbox\fP\', a system modal (always on top) message box
-is used.
-
-If running as a service, a service notification message box
-(always shown on current visible desktop) is used. Please note that
-service notification message boxes are no longer supported on Windows
-Vista/2008 or later.
+[Windows only] [NEW EXPERIMENTAL SMARTD FEATURE]
+If one of the following words are used as the first address in the
+comma separated list, warning messages are sent via WTSSendMessage().
+This displays message boxes on the desktops of the selected sessions.
+Address \'\fBconsole\fP\' specifies the console session only,
+\'\fBactive\fP\' specifies the console session and all active remote
+sessions, and \'\fBconnected\fP\' specifies the console session and
+all connected (active or waiting for login) remote sessions.
+This is handled by the script EXEDIR/smartd_warning.cmd which runs
+the tool EXEDIR/wtssendmsg.exe (see also \'\-M exec\' below).
+The addresses \'\fBmsgbox\fP\' and \'\fBsysmsgbox\fP\' are now
+deprecated and have the same effect as \'\fBconsole\fP\'.
.\" %ENDIF OS Windows
.TP
.B \-M TYPE
\fBsmartd\fP
needs to send email. PATH must point to an executable binary file or
script.
+.\" %IF OS Windows
+
+[Windows only] The PATH may contain space characters.
+Then it must be included in double quotes.
+.\" %ENDIF OS Windows
By setting PATH to point to a customized script, you can make
\fBsmartd\fP perform useful tricks when a disk problem is detected
(beeping the console, shutting down the machine, broadcasting warnings
to all logged-in users, etc.) But please be careful. \fBsmartd\fP
will \fBblock\fP until the executable PATH returns, so if your
-executable hangs, then \fBsmartd\fP will also hang. Some sample
-scripts are included in
+executable hangs, then \fBsmartd\fP will also hang.
+.\" %IF NOT OS Windows
+Some sample scripts are included in
/usr/local/share/doc/smartmontools/examplescripts/.
+.\" %ENDIF NOT OS Windows
The return status of the executable is recorded by \fBsmartd\fP in
SYSLOG. The executable is not expected to write to STDOUT or
form is \'/dev/sg2 [areca_disk_09]\' on Linux or \'/dev/arcmsr0 [areca_disk_09]\' on FreeBSD. In these cases the device string
contains a space and is NOT quoted. So to use $SMARTD_DEVICESTRING in a
bash script you should probably enclose it in double quotes.
+.IP \fBSMARTD_DEVICEINFO\fP 4
+is set to device identify information. It includes most of the info printed
+by \fBsmartctl \-i\fP but uses a brief single line format.
+This device info is also logged when \fBsmartd\fP starts up.
+The string contains space characters and is NOT quoted.
.IP \fBSMARTD_FAILTYPE\fP 4
gives the reason for the warning or message email. The possible values that
it takes and their meanings are:
read and are marked to be reallocated (replaced with spare sectors).
.nf
.fi
-\fIOfflineUncorrectableSector\fP: during off\-line testing, or self\-testing,
+\fIOfflineUncorrectableSector\fP: during off-line testing, or self-testing,
one or more disk sectors could not be read.
.nf
.fi
given, then this string will contain space characters and is NOT
quoted, so to use it in a bash script you may want to enclose it in
double quotes.
+.\" %IF OS Windows
+.IP \fBSMARTD_ADDRCSV\fP 4
+[Windows only] is set to a comma-separated list of the addresses from
+SMARTD_ADDRESS.
+.\" %ENDIF OS Windows
.IP \fBSMARTD_MESSAGE\fP 4
is set to the one sentence summary warning email message string from
\fBsmartd\fP.
This message string contains space characters and is NOT quoted. So to
use $SMARTD_MESSAGE in a bash script you should probably enclose it in
double quotes.
+.\" %IF NOT OS Windows
.IP \fBSMARTD_FULLMESSAGE\fP 4
is set to the contents of the entire email warning message string from
\fBsmartd\fP.
This message string contains space and return characters and is NOT quoted. So to
use $SMARTD_FULLMESSAGE in a bash script you should probably enclose it in
double quotes.
+.\" %ENDIF NOT OS Windows
+.\" %IF OS Windows
+.IP \fBSMARTD_FULLMSGFILE\fP 4
+[Windows only] is the path to a temporary file containing the full message.
+The path may contain space characters and is NOT quoted.
+The file is created by the smartd_warning.cmd script and removed when
+the mailer or command exits.
+.\" %ENDIF OS Windows
.IP \fBSMARTD_TFIRST\fP 4
is a text string giving the time and date at which the first problem
of this type was reported. This text string contains space characters
.IP \fBSMARTD_TFIRSTEPOCH\fP 4
is an integer, which is the unix epoch (number of seconds since Jan 1,
1970) for \fBSMARTD_TFIRST\fP.
+.IP \fBSMARTD_PREVCNT\fP 4
+is an integer specifying the number of previous messages sent.
+It is set to \'0\' for the first message.
+.IP \fBSMARTD_NEXTDAYS\fP 4
+is an integer specifying the number of days until the next message will be sent.
+It it set to empty on \'\-M once\' and set to \'1\' on \'\-M daily\'.
.RE
.\" The following two lines are a workaround for a man2html bug. Please leave them.
.\" They define a non-existent option; useful because man2html can't correctly reset the margins.
.fi
.\" %IF OS Windows
-Note that on Windows, the syntax of the \'\fBBlat\fP\' mailer is
+[Windows only] On Windows, the syntax of the \'\fBBlat\fP\' mailer is
used:
.nf
-- -q -subject "$SMARTD_SUBJECT" -to "$SMARTD_ADDRESS"
+- -q -subject "%SMARTD_SUBJECT%" -to %SMARTD_ADDRCSV%
.fi
.\" %ENDIF OS Windows
discarded.
Some EXAMPLES of scripts that can be used with the \'\-M exec\'
-Directive are given below. Some sample scripts are also included in
+Directive are given below.
+.\" %IF NOT OS Windows
+Some sample scripts are also included in
/usr/local/share/doc/smartmontools/examplescripts/.
+.\" %ENDIF NOT OS Windows
+
+[NEW EXPERIMENTAL SMARTD FEATURE] The executable is run by the script
+.\" %IF NOT OS Windows
+/usr/local/etc/smartd_warning.sh.
+.\" %ENDIF NOT OS Windows
+.\" %IF OS ALL
+(Windows: EXEDIR/smartd_warning.cmd)
+.\" %ENDIF OS ALL
+.\" %IF OS Windows
+.\"! EXEDIR/smartd_warning.cmd.
+.\" %ENDIF OS Windows
+This script formats subject and full message based on SMARTD_MESSAGE and other
+environment variables set by \fBsmartd\fP.
+The environment variables
+.\" %IF NOT OS Windows
+SMARTD_SUBJECT and SMARTD_FULLMESSAGE
+.\" %ENDIF NOT OS Windows
+.\" %IF OS ALL
+(Windows: SMARTD_SUBJECT, SMARTD_FULLMSGFILE and SMARTD_ADDRCSV)
+.\" %ENDIF OS ALL
+.\" %IF OS Windows
+.\"! SMARTD_SUBJECT, SMARTD_FULLMSGFILE and SMARTD_ADDRCSV
+.\" %ENDIF OS Windows
+are set by the script before running the executable.
+
.TP
.B \-f
[ATA only] Check for \'failure\' of any Usage Attributes. If these
If the optional flag \'!\' is appended, a change of the Normalized
value is considered critical. The report will be logged as LOG_CRIT
-and a warning email will be sent if \'-m\' is specified.
+and a warning email will be sent if \'\-m\' is specified.
.TP
.B \-R ID[!]
[ATA only] When tracking, report whenever the \fIRaw\fP value of Attribute
If the optional flag \'!\' is appended, a change of the Raw
value is considered critical. The report will be logged as
-LOG_CRIT and a warning email will be sent if \'-m\' is specified.
+LOG_CRIT and a warning email will be sent if \'\-m\' is specified.
An example is \'-R 5!\' to warn when new sectors are reallocated.
.TP
.B \-C ID[+]
sectors have been reallocated or could be read again.
An offline uncorrectable sector is a disk sector which was not
-readable during an off\-line scan or a self\-test. This is important
+readable during an off-line scan or a self-test. This is important
to know, because if you have data stored in this disk sector, and you
need to read it, the read will fail. Please see the previous \'\-C\'
option for more details.
\fBINFO\fP or \fBCRIT\fP degrees Celsius.
If the limit \fBCRIT\fP is reached, a message with loglevel
\fB\'LOG_CRIT\'\fP will be logged to syslog and a warning email
-will be send if '-m' is specified. If only the limit \fBINFO\fP is
+will be send if \'\-m\' is specified. If only the limit \fBINFO\fP is
reached, a message with loglevel \fB\'LOG_INFO\'\fP will be logged.
The warning email counter is reset if the temperature dropped below
.B \-W 2,40,45
.fi
-For ATA devices, smartd interprets Attribute 194 as Temperature Celsius
+For ATA devices, smartd interprets Attribute 194 or 190 as Temperature Celsius
by default. This can be changed to Attribute 9 or 220 by the drive
-database or by the \'-v\' directive, see below.
+database or by the \'\-v 9,temp\' or \'\-v 220,temp\' directive.
.TP
.B \-F TYPE
-[ATA only] Modifies the behavior of \fBsmartd\fP to compensate for
-some known and understood device firmware bug. The arguments to this
-Directive are exclusive, so that only the final Directive given is
-used. The valid values are:
+[ATA only] Modifies the behavior of \fBsmartd\fP to compensate for some
+known and understood device firmware bug. This directive may be used
+multiple times. The valid arguments are:
.I none
\- Assume that the device firmware obeys the ATA specifications. This
is the default, unless the device has presets for \'\-F\' in the
-device database.
+drive database. Using this directive will over-ride any preset values.
+
+.I nologdir
+\- Suppresses read attempts of SMART or GP Log Directory.
+Support for all standard logs is assumed without an actual check.
+Some Intel SSDs may freeze if log address 0 is read.
.I samsung
\- In some Samsung disks (example: model SV4012H Firmware Version:
-RM100\-08) some of the two\- and four\-byte quantities in the SMART data
-structures are byte\-swapped (relative to the ATA specification).
+RM100-08) some of the two- and four-byte quantities in the SMART data
+structures are byte-swapped (relative to the ATA specification).
Enabling this option tells \fBsmartd\fP to evaluate these quantities
-in byte\-reversed order. Some signs that your disk needs this option
-are (1) no self\-test log printed, even though you have run self\-tests;
+in byte-reversed order. Some signs that your disk needs this option
+are (1) no self-test log printed, even though you have run self-tests;
(2) very large numbers of ATA errors reported in the ATA error log;
(3) strange and impossible values for the ATA error log timestamps.
.I samsung2
\- In some Samsung disks the number of ATA errors reported is byte swapped.
Enabling this option tells \fBsmartd\fP to evaluate this quantity in
-byte\-reversed order.
+byte-reversed order.
.I samsung3
-\- Some Samsung disks (at least SP2514N with Firmware VF100\-37) report
-a self\-test still in progress with 0% remaining when the test was already
+\- Some Samsung disks (at least SP2514N with Firmware VF100-37) report
+a self-test still in progress with 0% remaining when the test was already
completed. If this directive is specified, \fBsmartd\fP will not skip the
-next scheduled self\-test (see Directive \'\-s\' above) in this case.
-
-Note that an explicit \'\-F\' Directive will over\-ride any preset
-values for \'\-F\' (see the \'\-P\' option below).
+next scheduled self-test (see Directive \'\-s\' above) in this case.
+.I xerrorlba
+\- This only affects \fBsmartctl\fP.
[Please see the \fBsmartctl \-F\fP command-line option.]
.TP
.B \-v ID,FORMAT[:BYTEORDER][,NAME]
-[ATA only] Sets a vendor\-specific raw value print FORMAT, an optional
+[ATA only] Sets a vendor-specific raw value print FORMAT, an optional
BYTEORDER and an optional NAME for Attribute ID.
This directive may be used multiple times.
Please see \fBsmartctl -v\fP command-line option for further details.
If a non-comment entry in the configuration file is the text
string \fBDEVICESCAN\fP in capital letters, then \fBsmartd\fP will
ignore any remaining lines in the configuration file, and will scan
-for devices.
-
-Configuration entries for devices not found by the platform\-specific
-device scanning may precede the \fBDEVICESCAN\fP entry.
+for devices (see also \fBsmartd\fP(8) man page).
If \fBDEVICESCAN\fP is not followed by any Directives, then smartd
will scan for both ATA and SCSI devices, and will monitor all possible
devices, (rather than the default \-a, which monitors all SMART
properties).
+[NEW EXPERIMENTAL SMARTD FEATURE]
+Configuration entries for specific devices may precede the \fBDEVICESCAN\fP entry.
+For example
+.nf
+.B DEFAULT -m root@example.com
+.B /dev/sda -s S/../.././02
+.B /dev/sdc -d ignore
+.B DEVICESCAN -s L/../.././02
+.fi
+will scan for all devices except /dev/sda and /dev/sdc, monitor them, and run a long
+test between 2-3am every morning. Device /dev/sda will also be monitored, but
+only a short test will be run. Device /dev/sdc will be ignored.
+Warning emails will be sent for all monitored devices.
+
.TP
.B EXAMPLES OF SHELL SCRIPTS FOR \'\-M exec\'
These are two examples of shell scripts that can be used with the \'\-M
The remainder is flushed.
.PP
-.SH AUTHOR
-\fBBruce Allen\fP smartmontools\-support@lists.sourceforge.net
-.fi
+.SH AUTHORS
+\fBBruce Allen\fP
+.br
University of Wisconsin \- Milwaukee Physics Department
+.br
+\fBChristian Franke\fP (Windows interface, C++ redesign, most enhancements
+since 2009)
+.br
+\fBsmartmontools\-support@lists.sourceforge.net\fP
.PP
.SH CONTRIBUTORS
The following have made large contributions to smartmontools:
.nf
\fBCasper Dik\fP (Solaris SCSI interface)
-\fBChristian Franke\fP (Windows interface, C++ redesign, USB support, ...)
\fBDouglas Gilbert\fP (SCSI subsystem)
\fBGuido Guenther\fP (Autoconf/Automake packaging)
\fBGeoffrey Keating\fP (Darwin ATA interface)
.fi
This code was derived from the smartsuite package, written by Michael
Cornwell, and from the previous UCSC smartsuite package. It extends
-these to cover ATA\-5 disks. This code was originally developed as a
+these to cover ATA-5 disks. This code was originally developed as a
Senior Thesis by Michael Cornwell at the Concurrent Systems Laboratory
(now part of the Storage Systems Research Center), Jack Baskin School
of Engineering, University of California, Santa
.SH
SVN ID OF THIS PAGE:
-$Id: smartd.conf.5.in 3561 2012-06-05 19:49:31Z chrfranke $
+$Id: smartd.conf.5.in 3741 2013-01-02 17:06:54Z chrfranke $
projects / mirror_smartmontools-debian.git / blobdiff