.ig
-Copyright (C) 2002-6 Bruce Allen <smartmontools-support@lists.sourceforge.net>
+Copyright (C) 2002-10 Bruce Allen <smartmontools-support@lists.sourceforge.net>
-$Id: smartd.8.in,v 1.113 2006/12/20 07:30:43 sxzzsf Exp $
+$Id: smartd.8.in 3284 2011-03-04 21:33:35Z 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
Systems Research Center), Jack Baskin School of Engineering,
University of California, Santa Cruz. http://ssrc.soe.ucsc.edu/
..
-.TH SMARTD 8 CURRENT_CVS_DATE CURRENT_CVS_VERSION CURRENT_CVS_DATE
+.TH SMARTD 8 CURRENT_SVN_DATE CURRENT_SVN_VERSION CURRENT_SVN_DATE
.SH NAME
\fBsmartd\fP \- SMART Disk Monitoring Daemon
.B /usr/local/sbin/smartd
.SH PACKAGE VERSION
-CURRENT_CVS_VERSION released CURRENT_CVS_DATE at CURRENT_CVS_TIME
+CURRENT_SVN_VERSION CURRENT_SVN_DATE CURRENT_SVN_REV
.SH DESCRIPTION
\fBsmartd\fP is a daemon that monitors the Self-Monitoring, Analysis
(equivalent to \fBsmartctl -s on\fP) and polls these and SCSI devices
every 30 minutes (configurable), logging SMART errors and changes of
SMART Attributes via the SYSLOG interface. The default location for
-these SYSLOG notifications and warnings is \fB/var/log/messages\fP.
+these SYSLOG notifications and warnings is system-dependent
+(typically \fB/var/log/messages\fP or \fB/var/log/syslog\fP).
To change this default location, please see the \fB\'-l\'\fP
command-line option described below.
details.
\fBsmartd\fP can be configured at start-up using the configuration
-file \fB/usr/local/etc/smartd.conf\fP (Windows: \fB./smartd.conf\fP).
+file \fB/usr/local/etc/smartd.conf\fP (Windows: \fBEXEDIR/smartd.conf\fP).
If the configuration file is subsequently modified, \fBsmartd\fP
can be told to re-read the configuration file by sending it a
\fBHUP\fP signal, for example with the command:
devices that support SMART. The scanning is done as follows:
.IP \fBLINUX:\fP 9
Examine all entries \fB"/dev/hd[a-t]"\fP for IDE/ATA
-devices, and \fB"/dev/sd[a-z]"\fP for SCSI devices.
+devices, and \fB"/dev/sd[a-z]"\fP, \fB"/dev/sd[a-c][a-z]"\fP
+for SCSI or SATA devices.
.IP \fBFREEBSD:\fP 9
-Examine all entries \fB"/dev/ad[0-9]+"\fP for IDE/ATA
-devices and \fB"/dev/da[0-9]+"\fP for SCSI devices.
+Authoritative list of disk devices is obtained from SCSI (CAM) and ATA subsystems.
.IP \fBNETBSD/OPENBSD:\fP 9
Authoritative list of disk devices is obtained from sysctl
\'hw.disknames\'.
devices, and entries \fB"/dev/rmt/*"\fP for SCSI tape devices.
.IP \fBDARWIN:\fP 9
The IOService plane is scanned for ATA block storage devices.
-.IP \fBWINDOWS:\fP 9
-Examine 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.
-Examines all entries \fB"/dev/scsi[0\-9][0\-f]"\fP for SCSI devices
+.IP \fBWINDOWS\ 9x/ME\fP: 9
+Examine all entries \fB"/dev/hd[a-d]"\fP (bitmask
+from "\\\\.\\SMARTVSD") for IDE/ATA devices.
+Examine all entries \fB"/dev/scsi[0\-9][0\-f]"\fP for SCSI devices
on ASPI adapter 0\-9, ID 0\-15.
+.IP \fBWINDOWS\ NT4/2000/XP/2003/Vista/Win7/2008\fP: 9
+Examine all entries \fB"/dev/sd[a-j]"\fP ("\\\\.\\PhysicalDrive[0-9]")
+for IDE/(S)ATA and SCSI disk devices
+
If a 3ware 9000 controller is installed, examine all entries
-\fB"/dev/hdX,N"\fP for the first logical drive (\'unit\'
-\fB"/dev/hdX"\fP) and all physical disks (\'ports\' \fB",N"\fP)
+\fB"/dev/sdX,N"\fP for the first logical drive (\'unit\'
+\fB"/dev/sdX"\fP) and all physical disks (\'ports\' \fB",N"\fP)
detected behind this controller. Same for a second controller if present.
-The following forms are not scanned for but can be given explicitly in the
-configuration file and only apply to WinNT4/2000/XP/2003. The
-form \fB"/dev/sd[a\-z]"\fP can be given for SCSI
-disks "\\\\.\\PhysicalDrive[0\-25]" (where "a" maps to "0"). Additionally
-the form \fB"/dev/pd[0\-255]"\fP can be given for SCSI
-disks "\\\\.\\PhysicalDrive[0\-255]". The form \fB"/dev/tape[0\-255]"\fP
-can be given for SCSI tape drives "\\\\.\\Tape[0\-255]".
+[NEW EXPERIMENTAL SMARTD FEATURE] If directive \'\-d csmi\' is specified,
+examine all entries \fB"/dev/csmi[0\-9],N"\fP for drives behind Intel
+Matrix RAID driver.
.IP \fBCYGWIN\fP: 9
-See "WINDOWS" above.
+See "WINDOWS NT4/2000/XP/2003/Vista/Win7/2008" above.
.IP \fBOS/2,eComStation\fP: 9
Use the form \fB"/dev/hd[a\-z]"\fP for IDE/ATA devices.
.PP
.SH
OPTIONS
-Long options are not supported on all systems. Use \fB\'smartd
-\-h\'\fP to see the available options.
+
+.TP
+.B \-A PREFIX, \-\-attributelog=PREFIX
+[ATA only] Writes \fBsmartd\fP attribute information (normalized and raw
+attribute values) to files \'PREFIX\'\'MODEL\-SERIAL.ata.csv\'. At each
+check cycle attributes are logged as a line of semicolon separated triplets
+of the form "attribute-ID;attribute-norm-value;attribute-raw-value;".
+Each line is led by a date string of the form "yyyy-mm-dd HH:MM:SS" (in UTC).
+
+.\" BEGIN ENABLE_ATTRIBUTELOG
+If this option is not specified, attribute information is written to files
+\'/usr/local/var/lib/smartmontools/attrlog.MODEL\-SERIAL.ata.csv\'.
+To disable attribute log files, specify this option with an empty string
+argument: \'-A ""\'.
+.\" END ENABLE_ATTRIBUTELOG
+MODEL and SERIAL are build from drive identify information, invalid
+characters are replaced by underline.
+
+If the PREFIX has the form \'/path/dir/\' (e.g. \'/var/lib/smartd/\'), then
+files \'MODEL\-SERIAL.ata.csv\' are created in directory \'/path/dir\'.
+If the PREFIX has the form \'/path/name\' (e.g. \'/var/lib/misc/attrlog\-\'),
+then files 'nameMODEL\-SERIAL.ata.csv' are created in directory '/path/'.
+The path must be absolute, except if debug mode is enabled.
+.TP
+.B \-B [+]FILE, \-\-drivedb=[+]FILE
+[ATA only] Read the drive database from FILE. The new database replaces
+the built in database by default. If \'+\' is specified, then the new entries
+prepend the built in entries.
+Please see the \fBsmartctl\fP(8) man page for further details.
.TP
.B \-c FILE, \-\-configfile=FILE
-
Read \fBsmartd\fP configuration Directives from FILE, instead of from
-the default location \fB/usr/local/etc/smartd.conf\fP (Windows: \fB./smartd.conf\fP).
+the default location \fB/usr/local/etc/smartd.conf\fP (Windows: \fBEXEDIR/smartd.conf\fP).
If FILE does \fBnot\fP exist, then \fBsmartd\fP will print an error
message and exit with nonzero status. Thus, \'\-c /usr/local/etc/smartd.conf\'
can be used to verify the existence of the default configuration file.
.B echo /dev/hdb \-m user@home \-M test | smartd \-c \- \-q onecheck
.fi
to perform quick and simple checks without a configuration file.
+.\" BEGIN ENABLE_CAPABILITIES
+.TP
+.B \-C, \-\-capabilities
+Use \fBcapabilities(7)\fP (EXPERIMENTAL).
+Warning: Mail notification does not work when used.
+.\" END ENABLE_CAPABILITIES
.TP
.B \-d, \-\-debug
Runs \fBsmartd\fP in "debug" mode. In this mode, it displays status
for the same purpose.
.fi
(Windows: See NOTES below.)
-
.TP
.B \-l FACILITY, \-\-logfacility=FACILITY
Uses syslog facility FACILITY to log the messages from \fBsmartd\fP.
\fIdaemon\fP.
If you would like to have \fBsmartd\fP messages logged somewhere other
-than the default \fB/var/log/messages\fP location, this can typically
-be accomplished with (for example) the following steps:
+than the default location, this can typically be accomplished with
+(for example) the following steps:
.RS 7
.IP \fB[1]\fP 4
Modify the script that starts \fBsmartd\fP to include the \fBsmartd\fP
messages from the event viewer. Use \'\fBsyslogevt -r smartd\fP\'
to register, \'\fBsyslogevt -u smartd\fP\' to unregister and
\'\fBsyslogevt\fP\' for more help.
+.TP
+.B \-n, \-\-no\-fork
+Do not fork into background; this is useful when executed from modern
+init methods like initng, minit or supervise.
+On Cygwin, this allows running \fBsmartd\fP as service via cygrunsrv,
+see NOTES below.
+
+On Windows, this option is not available, use \'\-\-service\' instead.
.TP
.B \-p NAME, \-\-pidfile=NAME
Writes pidfile \fINAME\fP containing the \fBsmartd\fP Process ID
comma then the integer with no spaces. For example, \fIataioctl,2\fP
The default level is 1, so \'\-r ataioctl,1\' and \'\-r ataioctl\' are
equivalent.
-
+.TP
+.B \-s PREFIX, \-\-savestates=PREFIX
+[ATA only] Reads/writes \fBsmartd\fP state information from/to files
+\'PREFIX\'\'MODEL\-SERIAL.ata.state\'. This preserves SMART attributes, drive
+min and max temperatures (\-W directive), info about last sent warning email
+(\-m directive), and the time of next check of the self-test REGEXP
+(\-s directive) across boot cycles.
+
+.\" BEGIN ENABLE_SAVESTATES
+If this option is not specified, state information is maintained in files
+\'/usr/local/var/lib/smartmontools/smartd.MODEL\-SERIAL.ata.state\'.
+To disable state files, specify this option with an empty string
+argument: \'-s ""\'.
+.\" END ENABLE_SAVESTATES
+MODEL and SERIAL are build from drive identify information, invalid
+characters are replaced by underline.
+
+If the PREFIX has the form \'/path/dir/\' (e.g. \'/var/lib/smartd/\'), then
+files \'MODEL\-SERIAL.ata.state\' are created in directory \'/path/dir\'.
+If the PREFIX has the form \'/path/name\' (e.g. \'/var/lib/misc/smartd\-\'),
+then files 'nameMODEL\-SERIAL.ata.state' are created in directory '/path/'.
+The path must be absolute, except if debug mode is enabled.
+
+The state information files are read on smartd startup. The files are
+always (re)written after reading the configuration file, before rereading
+the configuration file (SIGHUP), before smartd shutdown, and after a check
+forced by SIGUSR1. After a normal check cycle, a file is only rewritten if
+an important change (which usually results in a SYSLOG output) occurred.
.TP
.B \-\-service
Cygwin and Windows only: Enables \fBsmartd\fP to run as a Windows service.
-On Cygwin, this option simply prevents forking into background mode to
-allow running \fBsmartd\fP as service via cygrunsrv, see NOTES below.
+On Cygwin, this option is kept for backward compatibility only.
+It has the same effect as \'\-n, \-\-no\-fork\', see above.
On Windows, this option enables the buildin service support.
The option must be specified in the service command line as the first
argument. It should not be used from console.
See NOTES below for details.
-
.TP
.B \-V, \-\-version, \-\-license, \-\-copyright
-Prints license, copyright, and CVS version information onto
-STDOUT and then exits. Please include this information if you are
-reporting bugs, or have specific questions about the behavior of
-\fBsmartd\fP.
+Prints version, copyright, license, home page and SVN revision
+information for your copy of \fBsmartd\fP to STDOUT and then exits.
+Please include this information if you are reporting bugs or problems.
.SH EXAMPLES
.fi
Runs the daemon in forked mode. This is the normal way to run
\fBsmartd\fP.
-Entries are logged to SYSLOG (by default
-.B /var/log/messages.)
+Entries are logged to SYSLOG.
.B
smartd -d -i 30
and stop it by using the command:
.nf
.B /usr/local/etc/rc.d/init.d/smartd stop
-
-.fi
-If you want \fBsmartd\fP to start running whenever your machine is
-booted, this can be enabled by using the command:
-.nf
-.B /sbin/chkconfig --add smartd
-.fi
-and disabled using the command:
-.nf
-.B /sbin/chkconfig --del smartd
.fi
.\" DO NOT MODIFY THIS OR THE FOLLOWING TWO LINES. THIS MATERIAL
\fBsmartd\fP
will try to open all existing ATA devices (with entries in /dev)
.B /dev/ad[0-9]+
-and all existing SCSI devices
-.B /dev/da[0-9]+.
+and all existing SCSI devices (using CAM subsystem).
Under NetBSD/OpenBSD,
\fBsmartd\fP
will try to open all existing ATA devices (with entries in /dev)
line. An example file is included with the
.B smartmontools
distribution. You will find this sample configuration file in
-\fB/usr/local/share/doc/smartmontools-5.1/\fP. For security, the configuration file
+\fB/usr/local/share/doc/smartmontools/\fP. For security, the configuration file
should not be writable by anyone but root. The syntax of the file is as
follows:
.IP \(bu 4
.B # /usr/local/etc/smartd.conf for monitoring three
.B # ATA disks, three SCSI disks, six ATA disks
.B # behind two 3ware controllers, three SATA disks
-.B # directly connected to the highpoint rocket-
-.B # raid controller, two SATA disks connected to
-.B # the highpoint rocketraid controller via a pmport
-.B # device and one SATA disk.
+.B # directly connected to the HighPoint Rocket-
+.B # RAID controller, two SATA disks connected to
+.B # the HighPoint RocketRAID controller via a pmport
+.B # device, four SATA disks connected to an Areca
+.B # RAID controller, and one SATA disk.
.B #
.nf
.B # First ATA disk on two different interfaces. On
.B \ \ /dev/sda -a -d sat
.B #
.nf
+.B # Three disks connected to a MegaRAID controller
+.B # Start short self-tests daily between 1-2, 2-3, and
+.B # 3-4 am.
+.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
+.B #
+.nf
.B # Four ATA disks on a 3ware 6/7/8000 controller.
.B # Start short self-tests daily between midnight and 1am,
.B # 1-2, 2-3, and 3-4 am. Starting with the Linux 2.6
.B #
.nf
.B # Two ATA disks on a 3ware 9000 controller.
-.B # Start long self-tests Sundays between midnight and
+.B # Start long self-tests Sundays between midnight and
.B # 1am and 2-3 am
.B \ \ /dev/twa0 -d 3ware,0 -a -s L/../../7/00
.B \ \ /dev/twa0 -d 3ware,1 -a -s L/../../7/02
.B #
.nf
-.B # Three SATA disks on a highpoint rocketraid controller.
+.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
+.B \ \ /dev/twl0 -d 3ware,0 -a -s L/../../7/00
+.B \ \ /dev/twl0 -d 3ware,1 -a -s L/../../7/02
+.B #
+.nf
+.B # Three SATA disks on a HighPoint RocketRAID controller.
.B # Start short self-tests daily between 1-2, 2-3, and
.B # 3-4 am.
+.B # under Linux
.B \ \ /dev/sde -d hpt,1/1 -a -s S/../.././01
.B \ \ /dev/sde -d hpt,1/2 -a -s S/../.././02
.B \ \ /dev/sde -d hpt,1/3 -a -s S/../.././03
+.B # or under FreeBSD
+.B # /dev/hptrr -d hpt,1/1 -a -s S/../.././01
+.B # /dev/hptrr -d hpt,1/2 -a -s S/../.././02
+.B # /dev/hptrr -d hpt,1/3 -a -s S/../.././03
.B #
.nf
-.B # Two SATA disks connected to a highpoint rocketraid
+.B # Two SATA disks connected to a HighPoint RocketRAID
.B # via a pmport device. Start long self-tests Sundays
.B # between midnight and 1am and 2-3 am.
+.B # under Linux
.B \ \ /dev/sde -d hpt,1/4/1 -a -s L/../../7/00
.B \ \ /dev/sde -d hpt,1/4/2 -a -s L/../../7/02
+.B # or under FreeBSD
+.B # /dev/hptrr -d hpt,1/4/1 -a -s L/../../7/00
+.B # /dev/hptrr -d hpt,1/4/2 -a -s L/../../7/02
+.B #
+.nf
+.B # Three SATA disks connected to an Areca
+.B # RAID controller. Start long self-tests Sundays
+.B # between midnight and 3 am.
+.B \ \ /dev/sg2 -d areca,1 -a -s L/../../7/00
+.B \ \ /dev/sg2 -d areca,2 -a -s L/../../7/01
+.B \ \ /dev/sg2 -d areca,3 -a -s L/../../7/02
.B #
.nf
.B # The following line enables monitoring of the
.SH CONFIGURATION FILE DIRECTIVES
.PP
-If the first non-comment entry in the configuration file is the text
-string
+If a non-comment entry in the configuration file is the text string
.B DEVICESCAN
in capital letters, then
\fBsmartd\fP
status fails, or if new errors appear in the self-test log.
.B If a 3ware controller is used
-then the corresponding SCSI (/dev/sd?) or character device (/dev/twe?
-or /dev/twa?) 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).
-
+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\'
+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).
+
+.B If an Areca controller is used
+then the corresponding SCSI generic device (/dev/sg?) must be listed,
+along with the \'\-d areca,N\' Directive (see below). The individual
+SATA disks hosted by the Areca controller appear to \fBsmartd\fP as
+normal ATA devices. Hence all the ATA directives can be used for
+these disks. Areca firmware version 1.46 or later which supports
+smartmontools must be used; Please see the \fBsmartctl\fP(8) man page
+for further details.
.TP
.B \-d TYPE
-Specifies the type of the device. This Directive may be used multiple
-times for one device, but the arguments \fIata\fP, \fIscsi\fP, \fIsat\fP,
-\fImarvell\fP, \fIcciss,N\fP and \fI3ware,N\fP are mutually-exclusive. If more
-than one is given then \fBsmartd\fP will use the last one which appears.
-
-If none of these three arguments is given, then \fBsmartd\fP will
-first attempt to guess the device type by looking at whether the sixth
-character in the device name is an \'s\' or an \'h\'. This will work for
-device names like /dev/hda or /dev/sdb, and corresponds to choosing
-\fIata\fP or \fIscsi\fP respectively. If
-\fBsmartd\fP
-can\'t guess from this sixth character, then it will simply try to
-access the device using first ATA and then SCSI ioctl()s.
+Specifies the type of the device.
+The valid arguments to this directive are:
-The valid arguments to this Directive are:
+.I auto
+- 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.
.I ata
\- the device type is ATA. This prevents
.I sat
\- the device type is SCSI to ATA Translation (SAT).
-\fBsmartd\fP
-will generate ATA (smart) commands and then package them in
-the SAT defined ATA PASS THROUGH SCSI commands. The commands
-are then routed through the SCSI pass through interface to the
-operating system. There are two types of ATA PASS THROUGH
-SCSI commands: a 12 byte and 16 byte variant.
-\fBsmartd\fP
-can use either and defaults to the 16 byte variant. This can
-be overridden with this syntax: \'\-d sat,12\' or \'\-d sat,16\'.
+This is for ATA disks that have a SCSI to ATA Translation (SAT) Layer
+(SATL) between the disk and the operating system.
+SAT defines two ATA PASS THROUGH SCSI commands, one 12 bytes long and
+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\'.
+
+.I usbcypress
+\- this device type is for ATA disks that are behind a Cypress USB to PATA
+bridge. This will use the ATACB proprietary scsi pass through command.
+The default SCSI operation code is 0x24, but although it can be overridden
+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
+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\'.
+If two disks are connected to a bridge with two ports, an error message is printed
+if no PORT is specified.
+The port can be specified by \'\-d usbjmicron[,x],PORT\' where PORT is 0
+(master) or 1 (slave). This is not necessary if the device uses a port
+multiplier to connect multiple disks to one port. The disks appear under
+separate /dev/ice names then.
+CAUTION: Specifying \',x\' for a device which does not support it results
+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.
+
+.I usbsunplus
+\- this device type is for SATA disks that are behind a SunplusIT USB to SATA
+bridge.
.I marvell
-\- Under Linux, interact with SATA disks behind Marvell chip-set
+\- [Linux only] interact with SATA disks behind Marvell chip-set
controllers (using the Marvell rather than libata driver).
-.I 3ware,N
-\- the device consists of one or more ATA disks connected to a 3ware
-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 3ware_disk_XX
-with XX in the range from 00 to 15 inclusive.
+.I megaraid,N
+\- [Linux only] the device consists of one or more SCSI/SAS disks connected
+to a MegaRAID controller. The non-negative integer N (in the range of 0 to
+127 inclusive) denotes which disk on the controller is monitored.
+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.
+Please see the \fBsmartctl\fP(8) man page for further details.
-This Directive may at first appear confusing, because the 3ware
-controller is a SCSI device (such as /dev/sda) and should be listed as
-such in the the configuration file.
-However when the \'\-d 3ware,N\'
-Directive is used, then the corresponding disk is addressed using
-native ATA commands which are \'passed through\' the SCSI driver. All
-ATA Directives listed in this man page may be used. Note that while
-you may use \fBany\fP of the 3ware SCSI logical devices /dev/sd? to
-address \fBany\fP of the physical disks (3ware ports), error and log
+.I 3ware,N
+\- [FreeBSD and Linux only] the device consists of one or more ATA disks
+connected to a 3ware RAID controller. The non-negative integer N
+(in the range from 0 to 127 inclusive) denotes which disk on the controller
+is monitored.
+In log files and email messages this disk will be identified as 3ware_disk_XXX
+with XXX in the range from 000 to 127 inclusive.
+
+Note that while you may use \fBany\fP of the 3ware SCSI logical devices /dev/tw*
+to address \fBany\fP of the physical disks (3ware ports), error and log
messages will make the most sense if you always list the 3ware SCSI
-logical device corresponding to the particular physical disks. Please
-see the \fBsmartctl\fP man page for further details.
-
-ATA disks behind 3ware controllers may alternatively be accessed via a
-character device interface /dev/twe0-15 (3ware 6000/7000/8000
-controllers) and /dev/twa0-15 (3ware 9000 series controllers). Note
-that the 9000 series controllers may \fBonly\fP be accessed using the
-character device interface /dev/twa0-15 and not the SCSI device
-interface /dev/sd?. Please see the \fBsmartctl\fP man page for
-further details.
-
-Note that older 3w-xxxx drivers do not pass the \'Enable Autosave\'
-(\fB-S on\fP) and \'Enable Automatic Offline\' (\fB-o on\fP) commands
-to the disk, if the SCSI interface is used, and produce these types of
-harmless syslog error messages instead: \fB\'3w-xxxx: tw_ioctl():
-Passthru size (123392) too big\'\fP. This can be fixed by upgrading to
-version 1.02.00.037 or later of the 3w-xxxx driver, or by applying a
-patch to older versions. See
-\fBhttp://smartmontools.sourceforge.net/\fP for instructions.
-Alternatively use the character device interfaces /dev/twe0-15 (3ware
-6/7/8000 series controllers) or /dev/twa0-15 (3ware 9000 series
-controllers).
+logical device corresponding to the particular physical disks.
+Please see the \fBsmartctl\fP(8) man page for further details.
+
+.I areca,N
+\- [Linux only] the device consists of one or more SATA disks connected to an
+Areca SATA RAID controller. The positive integer N (in the range from 1 to
+24 inclusive) denotes which disk on the controller is monitored.
+In log files and email messages this disk will be identifed as
+areca_disk_XX with XX in the range from 01 to 24 inclusive.
+Please see the \fBsmartctl\fP(8) man page for further details.
.I cciss,N
-\- the device consists of one or more SCSI 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
+\- [FreeBSD and Linux only] the device consists of one or more SCSI/SAS 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
with XX in the range from 00 to 15 inclusive.
-
-.B 3ware and cciss controllers are currently ONLY supported under Linux.
+Please see the \fBsmartctl\fP(8) man page for further details.
.I hpt,L/M/N
-\- the device consists of one or more ATA disks connected to a HighPoint
-RocketRAID controller. The integer L is the controller id, the integer M
-is the channel number, and the integer N is the PMPort number if it is
-available. The allowed values of L are from 1 to 4 inclusive, M are from
-1 to 8 inclusive and N from 1 to 4 if PMPort available. And also these
-values are limited by the model of the HighPoint RocketRAID controller.
+\- [FreeBSD and Linux only] the device consists of one or more ATA disks
+connected to a HighPoint RocketRAID controller. The integer L is the
+controller id, the integer M is the channel number, and the integer N
+is the PMPort number if it is available. The allowed values of L are
+from 1 to 4 inclusive, M are from 1 to 8 inclusive and N from 1 to 4
+if PMPort available. And also these values are limited by the model
+of the HighPoint RocketRAID controller.
In log files and email messages this disk will be identified as
hpt_X/X/X and X/X/X is the same as L/M/N, note if no N indicated, N set
to the default value 1.
-
-.B HighPoint RocketRAID controllers are currently ONLY supported under Linux.
+Please see the \fBsmartctl\fP(8) man page for further details.
.I removable
\- the device or its media is removable. This indicates to
behavior) if the device does not appear to be present when
\fBsmartd\fP is started. This Directive may be used in conjunction
with the other \'\-d\' Directives.
-
.TP
-.B \-n POWERMODE[,q]
-This \'nocheck\' Directive is used to prevent a disk from being
-spun-up when it is periodically polled by \fBsmartd\fP.
+.B \-n POWERMODE[,N][,q]
+[ATA only] This \'nocheck\' Directive is used to prevent a disk from
+being spun-up when it is periodically polled by \fBsmartd\fP.
ATA disks have five different power states. In order of increasing
power consumption they are: \'OFF\', \'SLEEP\', \'STANDBY\', \'IDLE\',
In the IDLE state, most disks are still spinning, so this is probably
not what you want.
-When a self test is scheduled (see \'\-s\' Directive below), the
-\'\fB\-n\fP\' Directive is ignored, and all tests are carried out.
+Maximum number of skipped checks (in a row) can be specified by
+appending positive number \',N\' to POWERMODE (like \'\-n standby,15\').
+After N checks are skipped in a row, powermode is ignored and the
+check is performed anyway.
When a periodic test is skipped, \fBsmartd\fP normally writes an
informal log message. The message can be suppressed by appending
the option \',q\' to POWERMODE (like \'\-n standby,q\').
This prevents a laptop disk from spinning up due to this message.
+Both \',N\' and \',q\' can be specified together.
.TP
.B \-T TYPE
Specifies how tolerant
[Please see the \fBsmartctl \-T\fP command-line option.]
.TP
.B \-o VALUE
-Enables or disables SMART Automatic Offline Testing when
+[ATA only] Enables or disables SMART Automatic Offline Testing when
\fBsmartd\fP
starts up and has no further effect. The valid arguments to this
Directive are \fIon\fP and \fIoff\fP.
[Please see the \fBsmartctl \-S\fP command-line option.]
.TP
.B \-H
-Check the SMART health status of the disk. If any Prefailure
+[ATA only] Check the SMART health status of the disk. If any Prefailure
Attributes are less than or equal to their threshold values, then disk
failure is predicted in less than 24 hours, and a message at loglevel
-.B \'LOG_CRITICAL\'
+.B \'LOG_CRIT\'
will be logged to syslog. [Please see the
.B smartctl \-H
command-line option.]
.TP
.B \-l TYPE
-Reports increases in the number of errors in one of the two SMART logs. The
+Reports increases in the number of errors in one of three SMART logs. The
valid arguments to this Directive are:
.I error
-\- report if the number of ATA errors reported in the ATA Error Log
-has increased since the last check.
+\- [ATA only] report if the number of ATA errors reported in the Summary SMART
+error log has increased since the last check.
+
+.I xerror
+\- [ATA only] [NEW EXPERIMENTAL SMARTD FEATURE] report if the number of ATA
+errors reported in the Extended Comprehensive SMART error log has increased
+since the last check.
+
+If both \'\-l error\' and \'\-l xerror\' are specified, smartd checks
+the maximum of both values.
+
+[Please see the \fBsmartctl \-l xerror\fP command-line option.]
.I selftest
\- report if the number of failed tests reported in the SMART
Self-Tests can also be run manually by using the \fB\'\-t\ short\'\fP
and \fB\'\-t\ long\'\fP options of \fBsmartctl\fP and the results of
the testing can be observed using the \fBsmartctl \'\-l\ selftest\'\fP
-command-line option.]
-
+command-line option.
[Please see the \fBsmartctl \-l\fP and \fB\-t\fP command-line
options.]
+
+[ATA only] Failed self-tests outdated by a newer successful extended
+self\-test are ignored.
+
+.I scterc,READTIME,WRITETIME
+\- [ATA only] [NEW EXPERIMENTAL SMARTD FEATURE] sets the SCT Error
+Recovery Control settings to the specified values (deciseconds)
+when \fBsmartd\fP starts up and has no further effect.
+Values of 0 disable the feature, other values less than 65 are probably
+not supported. For RAID configurations, this is typically set to
+70,70 deciseconds.
+[Please see the \fBsmartctl \-l scterc\fP command-line option.]
+
.TP
.B \-s REGEXP
Run Self-Tests or Offline Immediate Tests, at scheduled times. A
only), and \'O\' for an \fBO\fPffline Immediate Test (ATA only). As
soon as a match is found, the test will be started and no additional
matches will be sought for that device and that polling cycle.
+
+To run scheduled Selective Self-Tests, use \'n\' for \fBn\fPext span,
+\'r\' to \fBr\fPedo last span, or \'c\' to \fBc\fPontinue with next span
+or redo last span based on status of last test.
+The LBA range is based on the first span from the last test.
+See the \fBsmartctl \-t select,[next|redo|cont]\fP options for
+further info.
+
+[NEW EXPERIMENTAL SMARTD FEATURE] Some disks (e.g. WD) do not preserve
+the selective self test log accross power cycles. If state persistence
+(\'\-s\' option) is enabled, the last test span is preserved by smartd
+and used if (and only if) the selective self test log is empty.
+
.IP \fBMM\fP 4
is the month of the year, expressed with two decimal digits. The
range is from 01 (January) to 12 (December) inclusive. Do \fBnot\fP
.nf
\fB \-s (O/../.././(00|06|12|18)|S/../.././01|L/../../6/03)\fP
.fi
+If Long Self-Tests of a large disks take longer than the system uptime,
+a full disk test can be performed by several Selective Self-Tests.
+To setup a full test of a 1TB disk within 20 days (one 50GB span
+each day), run this command once:
+.nf
+ smartctl -t select,0-99999999 /dev/sda
+.fi
+To run the next test spans on Monday-Friday between 12-13am, run smartd
+with this directive:
+.nf
+\fB \-s n/../../[1-5]/12\fP
+.fi
+
Scheduled tests are run immediately following the regularly-scheduled
device polling, if the current local date, time, and test type, match
occurs every thirty minutes after starting \fBsmartd\fP. Take caution
if you use the \'\-i\' option to make this polling interval more than
sixty minutes: the poll times may fail to coincide with any of the
-testing times that you have specified with \fBREGEXP\fP, and so the
-self tests may not take place as you wish.
+testing times that you have specified with \fBREGEXP\fP. In this case
+the test will be run following the next device polling.
Before running an offline or self-test, \fBsmartd\fP checks to be sure
that a self-test is not already running. If a self-test \fBis\fP
\fBsmartd\fP will not attempt to run \fBany\fP type of test if another
test was already started or run in the same hour.
+To avoid performance problems during system boot, \fBsmartd\fP will
+not attempt to run any scheduled tests following the very first
+device polling (unless \'\-q onecheck\' is specified).
+
Each time a test is run, \fBsmartd\fP will log an entry to SYSLOG.
You can use these or the '-q showtests' command-line option to verify
that you constructed \fBREGEXP\fP correctly. The matching order
if multiple test types are all scheduled for the same hour, the
longer test type has precedence. This is usually the desired behavior.
+If the scheduled tests are used in conjunction with state persistence
+(\'\-s\' option), smartd will also try to match the hours since last
+shutdown (or 90 days at most). If any test would have been started
+during downtime, the longest (see above) of these tests is run after
+second device polling.
+
+If the \'\-n\' directive is used and any test would have been started
+during disk standby time, the longest of these tests is run when the
+disk is active again.
+
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
issue harmless informational warning messages if it detects characters
in \fBREGEXP\fP that appear to indicate that you have made this
mistake.
-
.TP
.B \-m ADD
Send a warning email to the email address \fBADD\fP if the \'\-H\',
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.
-
.TP
.B \-M TYPE
These Directives modify the behavior of the
.I once
\- send only one warning email for each type of disk problem detected. This
-is the default.
+is the default unless state persistence (\'\-s\' option) is enabled.
.I daily
\- send additional warning reminder emails, once per day, for each type
-of disk problem detected.
+of disk problem detected. This is the default if state persistence
+(\'\-s\' option) is enabled.
.I diminishing
\- send additional warning reminder emails, after a one-day interval,
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
-/usr/local/share/doc/smartmontools-5.1/examplescripts/.
+/usr/local/share/doc/smartmontools/examplescripts/.
The return status of the executable is recorded by \fBsmartd\fP in
SYSLOG. The executable is not expected to write to STDOUT or
.IP \fBSMARTD_DEVICE\fP 4
is set to the device path (examples: /dev/hda, /dev/sdb).
.IP \fBSMARTD_DEVICETYPE\fP 4
-is set to the device type (possible values: ata, scsi, 3ware,N, hpt,L/M/N).
-Here N=0,...,15 denotes the ATA disk behind a 3ware RAID controller and
-L/M/N denotes the SATA disk behind a HighPoint RocketRAID controller.
+is set to the device type specified by \'-d\' directive or
+\'auto\' if none.
.IP \fBSMARTD_DEVICESTRING\fP 4
is set to the device description. For SMARTD_DEVICETYPE of ata or
scsi, this is the same as SMARTD_DEVICE. For 3ware RAID controllers,
-the form used is \'/dev/sdc [3ware_disk_01]\'. For HighPoint RocketRAID
-controller, the form is \'/dev/sdd [hpt_1/1/1]\'. 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.
+the form used is \'/dev/sdc [3ware_disk_01]\'. For HighPoint
+RocketRAID controller, the form is \'/dev/sdd [hpt_1/1/1]\' under Linux
+or \'/dev/hptrr [hpt_1/1/1]\' under FreeBSD. For Areca controllers, the
+form is \'/dev/sg2 [areca_disk_09]\'. 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_FAILTYPE\fP 4
gives the reason for the warning or message email. The possible values that
it takes and their meanings are:
one or more disk sectors could not be read.
.nf
.fi
+\fITemperature\fP: Temperature reached critical limit (see \-W directive).
+.nf
+.fi
\fIFailedHealthCheck\fP: the SMART health status command failed.
.nf
.fi
Some EXAMPLES of scripts that can be used with the \'\-M exec\'
Directive are given below. Some sample scripts are also included in
-/usr/local/share/doc/smartmontools-5.1/examplescripts/.
-
+/usr/local/share/doc/smartmontools/examplescripts/.
.TP
.B \-f
-Check for \'failure\' of any Usage Attributes. If these Attributes are
-less than or equal to the threshold, it does NOT indicate imminent
-disk failure. It "indicates an advisory condition where the usage or
-age of the device has exceeded its intended design life period."
+[ATA only] Check for \'failure\' of any Usage Attributes. If these
+Attributes are less than or equal to the threshold, it does NOT indicate
+imminent disk failure. It "indicates an advisory condition where the usage
+or age of the device has exceeded its intended design life period."
[Please see the \fBsmartctl \-A\fP command-line option.]
.TP
.B \-p
-Report anytime that a Prefail Attribute has changed
+[ATA only] Report anytime that a Prefail Attribute has changed
its value since the last check, 30 minutes ago. [Please see the
.B smartctl \-A
command-line option.]
.TP
.B \-u
-Report anytime that a Usage Attribute has changed its value
+[ATA only] Report anytime that a Usage Attribute has changed its value
since the last check, 30 minutes ago. [Please see the
.B smartctl \-A
command-line option.]
.TP
.B \-t
-Equivalent to turning on the two previous flags \'\-p\' and \'\-u\'.
+[ATA only] Equivalent to turning on the two previous flags \'\-p\' and \'\-u\'.
Tracks changes in \fIall\fP device Attributes (both Prefailure and
Usage). [Please see the \fBsmartctl\fP \-A command-line option.]
.TP
.B \-i ID
-Ignore device Attribute number \fBID\fP when checking for failure of
-Usage Attributes. \fBID\fP must be a decimal integer in the range
+[ATA only] Ignore device Attribute number \fBID\fP when checking for failure
+of Usage Attributes. \fBID\fP must be a decimal integer in the range
from 1 to 255. This Directive modifies the behavior of the \'\-f\'
Directive and has no effect without it.
times for a single device, if you want to ignore multiple Attributes.
.TP
.B \-I ID
-Ignore device Attribute \fBID\fP when tracking changes in the
+[ATA only] Ignore device Attribute \fBID\fP when tracking changes in the
Attribute values. \fBID\fP must be a decimal integer in the range
from 1 to 255. This Directive modifies the behavior of the \'\-p\',
\'\-u\', and \'\-t\' tracking Directives and has no effect without one
each time the temperature changes. This Directive may appear multiple
times for a single device, if you want to ignore multiple Attributes.
.TP
-.B \-r ID
-When tracking, report the \fIRaw\fP value of Attribute \fBID\fP along
-with its (normally reported) \fINormalized\fP value. \fBID\fP must be
-a decimal integer in the range from 1 to 255. This Directive modifies
+.B \-r ID[!]
+[ATA only] When tracking, report the \fIRaw\fP value of Attribute \fBID\fP
+along with its (normally reported) \fINormalized\fP value. \fBID\fP must
+be a decimal integer in the range from 1 to 255. This Directive modifies
the behavior of the \'\-p\', \'\-u\', and \'\-t\' tracking Directives
and has no effect without one of them. This Directive may be given
multiple times.
A common use of this Directive is to track the device Temperature
(often ID=194 or 231).
+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.
.TP
-.B \-R ID
-When tracking, report whenever the \fIRaw\fP value of Attribute
+.B \-R ID[!]
+[ATA only] When tracking, report whenever the \fIRaw\fP value of Attribute
\fBID\fP changes. (Normally \fBsmartd\fP only tracks/reports changes
of the \fINormalized\fP Attribute values.) \fBID\fP must be a decimal
integer in the range from 1 to 255. This Directive modifies the
different types of system behavior affects the values of certain
Attributes.
+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.
+An example is \'-R 5!\' to warn when new sectors are reallocated.
.TP
-.B \-C ID
+.B \-C ID[+]
[ATA only] Report if the current number of pending sectors is
non-zero. Here \fBID\fP is the id number of the Attribute whose raw
value is the Current Pending Sector count. The allowed range of
\fBID\fP is 0 to 255 inclusive. To turn off this reporting, use
ID\ =\ 0. If the \fB\-C ID\fP option is not given, then it defaults to
\fB\-C 197\fP (since Attribute 197 is generally used to monitor
-pending sectors).
+pending sectors). If the name of this Attribute is changed by a
+\'\-v 197,FORMAT,NAME\' directive, the default is changed to
+\fB\-C 0\fP.
+
+If \'+\' is specified, a report is only printed if the number of sectors
+has increased between two check cycles. Some disks do not reset this
+attribute when a bad sector is reallocated.
+See also \'\-v 197,increasing\' below.
A pending sector is a disk sector (containing 512 bytes of your data)
which the device would like to mark as ``bad" and reallocate.
force the sector to reallocate by writing to it (translation: make the
device substitute a spare good sector for the bad one) but at the
price of losing the 512 bytes of data stored there.
-
.TP
-.B \-U ID
+.B \-U ID[+]
[ATA only] Report if the number of offline uncorrectable sectors is
non-zero. Here \fBID\fP is the id number of the Attribute whose raw
value is the Offline Uncorrectable Sector count. The allowed range of
\fBID\fP is 0 to 255 inclusive. To turn off this reporting, use
ID\ =\ 0. If the \fB\-U ID\fP option is not given, then it defaults to
\fB\-U 198\fP (since Attribute 198 is generally used to monitor
-offline uncorrectable sectors).
+offline uncorrectable sectors). If the name of this Attribute is changed
+by a \'\-v 198,FORMAT,NAME\' (except \'\-v 198,FORMAT,Offline_Scan_UNC_SectCt\'),
+directive, the default is changed to \fB\-U 0\fP.
+If \'+\' is specified, a report is only printed if the number of sectors
+has increased since the last check cycle. Some disks do not reset this
+attribute when a bad sector is reallocated.
+See also \'\-v 198,increasing\' below.
An offline uncorrectable sector is a disk sector which was not
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.
-
.TP
.B \-W DIFF[,INFO[,CRIT]]
Report if the current temperature had changed by at least \fBDIFF\fP
-degrees since last report. Report or Warn if the temperature is greater
-or equal than one of \fBINFO\fP or \fBCRIT\fP degrees Celsius. If the
-limit \fBCRIT\fP is reached, a message with loglevel
-\fB\'LOG_CRITICAL\'\fP will be logged to syslog and a warning email
+degrees since last report, or if new min or max temperature is detected.
+Report or Warn if the temperature is greater or equal than one of
+\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
reached, a message with loglevel \fB\'LOG_INFO\'\fP will be logged.
+If this directive is used in conjunction with state persistence
+(\'\-s\' option), the min and max temperature values are preserved
+across boot cycles. The minimum temperature value is not updated
+during the first 30 minutes after startup.
+
To disable any of the 3 reports, set the corresponding limit to 0.
Trailing zero arguments may be omitted. By default, all temperature
reports are disabled (\'-W 0\').
For ATA devices, smartd interprets Attribute 194 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.
-
.TP
.B \-F TYPE
[ATA only] Modifies the behavior of \fBsmartd\fP to compensate for
used. The valid values 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.
+\- Assume that the device firmware obeys the ATA specifications. This
+is the default, unless the device has presets for \'\-F\' in the
+device database.
.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 more recent Samsung disks (firmware revisions ending in "\-23") the
-number of ATA errors reported is byte swapped. Enabling this option
-tells \fBsmartd\fP to evaluate this quantity in byte-reversed order.
+\- 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.
+
+.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
+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
+Note that an explicit \'\-F\' Directive will over\-ride any preset
values for \'\-F\' (see the \'\-P\' option below).
[Please see the \fBsmartctl \-F\fP command-line option.]
-
.TP
-.B \-v N,OPTION
-Modifies the labeling for Attribute N, for disks which use
-non-standard Attribute definitions. This is useful in connection with
-the Attribute tracking/reporting Directives.
-
-This Directive may appear multiple times. Valid arguments to this
-Directive are:
-
-.I 9,minutes
-\- Raw Attribute number 9 is power-on time in minutes. Its raw value
-will be displayed in the form \'Xh+Ym\'. Here X is hours, and Y is
-minutes in the range 0-59 inclusive. Y is always printed with two
-digits, for example \'06\' or \'31\' or \'00\'.
-
-.I 9,seconds
-\- Raw Attribute number 9 is power-on time in seconds. Its raw value
-will be displayed in the form \'Xh+Ym+Zs\'. Here X is hours, Y is
-minutes in the range 0-59 inclusive, and Z is seconds in the range
-0-59 inclusive. Y and Z are always printed with two digits, for
-example \'06\' or \'31\' or \'00\'.
-
-.I 9,halfminutes
-\- Raw Attribute number 9 is power-on time, measured in units of 30
-seconds. This format is used by some Samsung disks. Its raw value
-will be displayed in the form \'Xh+Ym\'. Here X is hours, and Y is
-minutes in the range 0-59 inclusive. Y is always printed with two
-digits, for example \'06\' or \'31\' or \'00\'.
-
-.I 9,temp
-\- Raw Attribute number 9 is the disk temperature in Celsius.
-
-.I 192,emergencyretractcyclect
-\- Raw Attribute number 192 is the Emergency Retract Cycle Count.
-
-.I 193,loadunload
-\- Raw Attribute number 193 contains two values. The first is the
-number of load cycles. The second is the number of unload cycles.
-The difference between these two values is the number of times that
-the drive was unexpectedly powered off (also called an emergency
-unload). As a rule of thumb, the mechanical stress created by one
-emergency unload is equivalent to that created by one hundred normal
-unloads.
-
-.I 194,10xCelsius
-\- Raw Attribute number 194 is ten times the disk temperature in
-Celsius. This is used by some Samsung disks (example: model SV1204H
-with RK100-13 firmware).
-
-.I 194,unknown
-\- Raw Attribute number 194 is NOT the disk temperature, and its
-interpretation is unknown. This is primarily useful for the -P
-(presets) Directive.
-
-.I 198,offlinescanuncsectorct
-\- Raw Attribute number 198 is the Offline Scan UNC Sector Count.
-
-.I 200,writeerrorcount
-\- Raw Attribute number 200 is the Write Error Count.
-
-.I 201,detectedtacount
-\- Raw Attribute number 201 is the Detected TA Count.
-
-.I 220,temp
-\- Raw Attribute number 220 is the disk temperature in Celsius.
-
-Note: a table of hard drive models, listing which Attribute
-corresponds to temperature, can be found at:
-\fBhttp://www.guzu.net/linux/hddtemp.db\fP
-
-.I N,raw8
-\- Print the Raw value of Attribute N as six 8-bit unsigned base-10
-integers. This may be useful for decoding the meaning of the Raw
-value. The form \'N,raw8\' prints Raw values for ALL Attributes in this
-form. The form (for example) \'123,raw8\' only prints the Raw value for
-Attribute 123 in this form.
-
-.I N,raw16
-\- Print the Raw value of Attribute N as three 16-bit unsigned base-10
-integers. This may be useful for decoding the meaning of the Raw
-value. The form \'N,raw16\' prints Raw values for ALL Attributes in this
-form. The form (for example) \'123,raw16\' only prints the Raw value for
-Attribute 123 in this form.
-
-.I N,raw48
-\- Print the Raw value of Attribute N as a 48-bit unsigned base-10
-integer. This may be useful for decoding the meaning of the Raw
-value. The form \'N,raw48\' prints Raw values for ALL Attributes in
-this form. The form (for example) \'123,raw48\' only prints the Raw
-value for Attribute 123 in this form.
-
+.B \-v ID,FORMAT[:BYTEORDER][,NAME]
+[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.
+
+The following arguments affect smartd warning output:
+
+.I 197,increasing
+\- Raw Attribute number 197 (Current Pending Sector Count) is not
+reset if uncorrectable sectors are reallocated. This sets \'-C 197+\'
+if no other \'-C\' directive is specified.
+
+.I 198,increasing
+\- Raw Attribute number 198 (Offline Uncorrectable Sector Count) is not
+reset if uncorrectable sector are reallocated. This sets \'-U 198+\'
+if no other \'-U\' directive is specified.
.TP
.B \-P TYPE
-Specifies whether
-\fBsmartd\fP
-should use any preset options that are available for this drive. The
-valid arguments to this Directive are:
+[ATA only] Specifies whether \fBsmartd\fP should use any preset options
+that are available for this drive.
+The valid arguments to this Directive are:
.I use
\- use any presets that are available for this drive. This is the default.
[Please see the
.B smartctl \-P
command-line option.]
-
.TP
.B \-a
Equivalent to turning on all of the following Directives:
Note that \-a is the default for ATA devices. If none of these other
Directives is given, then \-a is assumed.
-
.TP
.B #
Comment: ignore the remainder of the line.
.TP
.B ADDITIONAL DETAILS ABOUT DEVICESCAN
-If the first non-comment entry in the configuration file is the text
+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.
+[NEW EXPERIMENTAL SMARTD FEATURE] Configuration entries for devices
+not found by the platform\-specific device scanning may precede the
+\fBDEVICESCAN\fP entry.
+
If \fBDEVICESCAN\fP is not followed by any Directives, then smartd
will scan for both ATA and SCSI devices, and will monitor all possible
SMART properties of any devices that are found.
.fi
Some example scripts are distributed with the smartmontools package,
-in /usr/local/share/doc/smartmontools-5.1/examplescripts/.
+in /usr/local/share/doc/smartmontools/examplescripts/.
Please note that these scripts typically run as root, so any files
that they read/write should not be writable by ordinary users or
.PP
.SH AUTHOR
-\fBBruce Allen\fP smartmontools-support@lists.sourceforge.net
+\fBBruce Allen\fP smartmontools\-support@lists.sourceforge.net
.fi
University of Wisconsin \- Milwaukee Physics Department
The following have made large contributions to smartmontools:
.nf
\fBCasper Dik\fP (Solaris SCSI interface)
-\fBChristian Franke\fP (Windows interface and Cygwin package)
+\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)
\fBEduard Martinescu\fP (FreeBSD interface)
\fBFr\*'ed\*'eric L. W. Meunier\fP (Web site and Mailing list)
+\fBGabriele Pohl\fP (Web site and Wiki, conversion from CVS to SVN)
\fBKeiji Sawada\fP (Solaris ATA interface)
+\fBManfred Schwarb\fP (Drive database)
\fBSergey Svishchev\fP (NetBSD interface)
\fBDavid Snyder and Sergey Svishchev\fP (OpenBSD interface)
\fBPhil Williams\fP (User interface and drive database)
-\fBShengfeng Zhou\fP (Linux Highpoint RocketRaid interface)
+\fBShengfeng Zhou\fP (Linux/FreeBSD HighPoint RocketRAID interface)
.fi
Many other individuals have made smaller contributions and corrections.
.SH CREDITS
.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
+Cornwell, and from the previous UCSC smartsuite package. It extends
+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
Please see the following web site for updates, further documentation, bug
reports and patches: \fBhttp://smartmontools.sourceforge.net/\fP
-.SH SEE ALSO:
+.SH
+SEE ALSO:
\fBsmartd.conf\fP(5), \fBsmartctl\fP(8), \fBsyslogd\fP(8),
\fBsyslog.conf\fP(5), \fBbadblocks\fP(8), \fBide\-smart\fP(8), \fBregex\fP(7).
.fi
An introductory article about smartmontools is \fIMonitoring Hard
Disks with SMART\fP, by Bruce Allen, Linux Journal, January 2004,
-pages 74-77. This is \fBhttp://www.linuxjournal.com/article.php?sid=6983\fP
+pages 74\-77. This is \fBhttp://www.linuxjournal.com/article/6983\fP
online.
If you would like to understand better how SMART works, and what it
does, a good place to start is with Sections 4.8 and 6.54 of the first
-volume of the \'AT Attachment with Packet Interface-7\' (ATA/ATAPI-7)
-specification. This documents the SMART functionality which the
-\fBsmartmontools\fP utilities provide access to. You can find
-Revision 4b of this document at
-\fBhttp://www.t13.org/docs2004/d1532v1r4b-ATA-ATAPI-7.pdf\fP .
-Earlier and later versions of this Specification are available from
+volume of the \'AT Attachment with Packet Interface\-7\' (ATA/ATAPI\-7)
+specification Revision 4b. This documents the SMART functionality which the
+\fBsmartmontools\fP utilities provide access to.
+This and other versions of this Specification are available from
the T13 web site \fBhttp://www.t13.org/\fP .
.fi
-The functioning of SMART was originally defined by the SFF-8035i
-revision 2 and the SFF-8055i revision 1.4 specifications. These are
-publications of the Small Form Factors (SFF) Committee. Links to
-these documents may be found in the References section of the
-smartmontools home page at \fBhttp://smartmontools.sourceforge.net/#references\fP .
+The functioning of SMART was originally defined by the SFF\-8035i
+revision 2 and the SFF\-8055i revision 1.4 specifications. These are
+publications of the Small Form Factors (SFF) Committee.
+
+Links to these and other documents may be found on the Links page of the
+\fBsmartmontools\fP Wiki at
+\fBhttp://sourceforge.net/apps/trac/smartmontools/wiki/Links\fP .
.SH
-CVS ID OF THIS PAGE:
-$Id: smartd.8.in,v 1.113 2006/12/20 07:30:43 sxzzsf Exp $
+SVN ID OF THIS PAGE:
+$Id: smartd.8.in 3284 2011-03-04 21:33:35Z chrfranke $
projects / mirror_smartmontools-debian.git / blobdiff