Diff for /embedaddon/smartmontools/smartctl.8.in between versions 1.1 and 1.1.1.4

version 1.1, 2012/02/21 16:32:16 version 1.1.1.4, 2013/10/14 07:54:04
Line 1 Line 1
 .ig  .ig
 Copyright (C) 2002-10 Bruce Allen <smartmontools-support@lists.sourceforge.net>Copyright (C) 2002-10 Bruce Allen <smartmontools-support@lists.sourceforge.net>
 Copyright (C) 2004-13 Christian Franke <smartmontools-support@lists.sourceforge.net>
   
 $Id$$Id$
  
 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. 
   
 This code was originally developed as a Senior Thesis by Michael CornwellThis program is free software; you can redistribute it and/or modify
 at the Concurrent Systems Laboratory (now part of the Storage Systemsit under the terms of the GNU General Public License as published by
 Research Center), Jack Baskin School of Engineering, University ofthe Free Software Foundation; either version 2, or (at your option)
 California, Santa Cruz. http://ssrc.soe.ucsc.edu/any later version.
   
   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 SMARTCTL 8 CURRENT_SVN_DATE CURRENT_SVN_VERSION CURRENT_SVN_DATE  .TH SMARTCTL 8 CURRENT_SVN_DATE CURRENT_SVN_VERSION CURRENT_SVN_DATE
 .SH NAME  .SH NAME
Line 39  CURRENT_SVN_VERSION CURRENT_SVN_DATE CURRENT_SVN_REV Line 39  CURRENT_SVN_VERSION CURRENT_SVN_DATE CURRENT_SVN_REV
 .\"! It does not contain info specific to other platforms.]  .\"! It does not contain info specific to other platforms.]
 .\"! .PP  .\"! .PP
 .\" %ENDIF NOT OS ALL  .\" %ENDIF NOT OS ALL
\fBsmartctl\fP controls the Self\-Monitoring, Analysis and Reporting\fBsmartctl\fP controls the Self-Monitoring, Analysis and
Technology (SMART) system built into many ATA\-3 and later ATA, IDE andReporting Technology (SMART) system built into most ATA/SATA and SCSI/SAS
SCSI\-3 hard drives. The purpose of SMART is to monitor the reliabilityhard drives and solid-state drives.
of the hard drive and predict drive failures, and to carry outThe purpose of SMART is to monitor the reliability of the hard drive
different types of drive self\-tests.  This version of \fBsmartctl\fPand predict drive failures, and to carry out different types of drive
is compatible with ATA/ATAPI\-7 and earlier standards (see REFERENCESself-tests.
below)\fBsmartctl\fP also supports some features not related to SMART.
 This version of \fBsmartctl\fP is compatible with
 ACS-2, ATA8-ACS, ATA/ATAPI-7 and earlier standards
 (see \fBREFERENCES\fP below).
   
 \fBsmartctl\fP is a command line utility designed to perform SMART  
 tasks such as printing the SMART self\-test and error logs, enabling  
 and disabling SMART automatic testing, and initiating device  
 self\-tests. Note: if the user issues a SMART command that is  
 (apparently) not implemented by the device, \fBsmartctl\fP will print  
 a warning message but issue the command anyway (see the \fB\-T,  
 \-\-tolerance\fP option below).  This should not cause problems: on  
 most devices, unimplemented SMART commands issued to a drive are  
 ignored and/or return an error.  
   
 \fBsmartctl\fP also provides support for polling TapeAlert messages  \fBsmartctl\fP also provides support for polling TapeAlert messages
 from SCSI tape drives and changers.  from SCSI tape drives and changers.
   
Line 78  below. For disks behind HighPoint RocketRAID controlle Line 71  below. For disks behind HighPoint RocketRAID controlle
 \fB"/dev/sd[a\-z]"\fP.  For disks behind Areca SATA RAID controllers,  \fB"/dev/sd[a\-z]"\fP.  For disks behind Areca SATA RAID controllers,
 you need \fB"/dev/sg[2\-9]"\fP (note that smartmontools interacts with  you need \fB"/dev/sg[2\-9]"\fP (note that smartmontools interacts with
 the Areca controllers via a SCSI generic device which is different  the Areca controllers via a SCSI generic device which is different
than the SCSI device used for reading and writing data)!than the SCSI device used for reading and writing data)!  For HP Smart
 Array RAID controllers, there are three currently supported drivers: cciss,
 hpsa, and hpahcisr.  For disks accessed via the cciss driver the device nodes
 are of the form \fB"/dev/cciss/c[0\-9]d0"\fP.  For disks accessed via
 the hpahcisr and hpsa drivers, the device nodes you need are \fB"/dev/sg[0\-9]*"\fP.
 ("lsscsi \-g" is helpful in determining which scsi generic device node corresponds
 to which device.)  Use the nodes corresponding to the RAID controllers,
 not the nodes corresponding to logical drives.  See the \fB\-d\fP option below, as well.
 .\" %ENDIF OS Linux  .\" %ENDIF OS Linux
 .\" %IF OS Darwin  .\" %IF OS Darwin
 .IP \fBDARWIN\fP: 9  .IP \fBDARWIN\fP: 9
 Use the forms \fB/dev/disk[0\-9]\fP or equivalently \fBdisk[0\-9]\fP or equivalently  Use the forms \fB/dev/disk[0\-9]\fP or equivalently \fBdisk[0\-9]\fP or equivalently
 \fB/dev/rdisk[0\-9]\fP.  Long forms are also available: please use \'\-h\' to see some  \fB/dev/rdisk[0\-9]\fP.  Long forms are also available: please use \'\-h\' to see some
 examples. Note that there is currently no Darwin SCSI support.  examples. Note that there is currently no Darwin SCSI support.
   
   Use the OS X SAT SMART Driver to access SMART data on SAT capable USB and
   Firewire devices (see INSTALL file).
 .\" %ENDIF OS Darwin  .\" %ENDIF OS Darwin
 .\" %IF OS FreeBSD  .\" %IF OS FreeBSD
 .IP \fBFREEBSD\fP: 9  .IP \fBFREEBSD\fP: 9
 Use the forms \fB"/dev/ad[0\-9]+"\fP for IDE/ATA  Use the forms \fB"/dev/ad[0\-9]+"\fP for IDE/ATA
 devices and \fB"/dev/da[0\-9]+"\fP or \fB"/dev/pass[0\-9]+"\fP for SCSI devices.  devices and \fB"/dev/da[0\-9]+"\fP or \fB"/dev/pass[0\-9]+"\fP for SCSI devices.
For SATA devices on AHCI bus use \fB"/dev/ada[0\-9]+"\fP format.For SATA devices on AHCI bus use \fB"/dev/ada[0\-9]+"\fP format.  For HP Smart
 Array RAID controllers, use \fB"/dev/ciss[0\-9]"\fP (and see the \fB-d\fP option,
 below).
 .\" %ENDIF OS FreeBSD  .\" %ENDIF OS FreeBSD
 .\" %IF OS NetBSD OpenBSD  .\" %IF OS NetBSD OpenBSD
 .IP \fBNETBSD/OPENBSD\fP: 9  .IP \fBNETBSD/OPENBSD\fP: 9
Line 105  your architecture. Line 110  your architecture.
 Use the forms \fB"/dev/rdsk/c?t?d?s?"\fP for IDE/ATA and SCSI disk  Use the forms \fB"/dev/rdsk/c?t?d?s?"\fP for IDE/ATA and SCSI disk
 devices, and \fB"/dev/rmt/*"\fP for SCSI tape devices.  devices, and \fB"/dev/rmt/*"\fP for SCSI tape devices.
 .\" %ENDIF OS Solaris  .\" %ENDIF OS Solaris
 .\" %IF OS Windows  
 .IP \fBWINDOWS\ 9x/ME\fP: 9  
 Use the forms \fB"/dev/hd[a\-d]"\fP for standard IDE/ATA devices  
 accessed via SMARTVSD.VXD, and \fB"/dev/hd[e\-h]"\fP for additional devices  
 accessed via a patched SMARTVSE.VXD (see INSTALL file for details).  
 Use the form \fB"/dev/scsi[0\-9][0\-f]"\fP for SCSI devices via an aspi dll  
 on ASPI adapter 0\-9, ID 0\-15. The prefix \fB"/dev/"\fP is optional.  
 .\" %ENDIF OS Windows  
 .\" %IF OS Windows Cygwin  .\" %IF OS Windows Cygwin
.IP \fBWINDOWS\ NT4/2000/XP/2003/Vista/Win7/2008\fP: 9.IP \fBWINDOWS\fP: 9
 Use the forms \fB"/dev/sd[a\-z]"\fP for IDE/(S)ATA and SCSI disks  Use the forms \fB"/dev/sd[a\-z]"\fP for IDE/(S)ATA and SCSI disks
 "\\\\.\\PhysicalDrive[0\-25]" (where "a" maps to "0").  "\\\\.\\PhysicalDrive[0\-25]" (where "a" maps to "0").
   Use \fB"/dev/sd[a\-z][a\-z]"\fP for "\\\\.\\PhysicalDrive[26\-...]".
 These disks can also be referred to as \fB"/dev/pd[0\-255]"\fP for  These disks can also be referred to as \fB"/dev/pd[0\-255]"\fP for
 "\\\\.\\PhysicalDrive[0\-255]".  "\\\\.\\PhysicalDrive[0\-255]".
 ATA disks can also be referred to as \fB"/dev/hd[a\-z]"\fP for  ATA disks can also be referred to as \fB"/dev/hd[a\-z]"\fP for
Line 138  in the driver. Use \fB"/dev/tw_cli/stdin"\fP or \fB"/d Line 136  in the driver. Use \fB"/dev/tw_cli/stdin"\fP or \fB"/d
 to parse CLI or 3DM output from standard input or clipboard.  to parse CLI or 3DM output from standard input or clipboard.
 The option \'\-d 3ware,N\' is not necessary on Windows.  The option \'\-d 3ware,N\' is not necessary on Windows.
   
[NEW EXPERIMENTAL SMARTCTL FEATURE] For disks behind Intel Matrix RAIDFor disks behind an Intel ICHxR controller with RST driver use
driver use \fB"/dev/csmi[0\-9],N"\fP where N specifies the port behind\fB"/dev/csmi[0\-9],N"\fP where N specifies the port behind the logical
the logical scsi controller "\\\\.\\Scsi[0\-9]:".scsi controller "\\\\.\\Scsi[0\-9]:".
 
 [NEW EXPERIMENTAL SMARTCTL FEATURE] For SATA or SAS disks behind an Areca
 controller use \fB"/dev/arcmsr[0\-9]"\fP, see \'\-d areca,N[/E]\' below.
 
 The prefix \fB"/dev/"\fP is optional.  The prefix \fB"/dev/"\fP is optional.
 .\" %ENDIF OS Windows Cygwin  .\" %ENDIF OS Windows Cygwin
 .\" %IF OS Cygwin  
 .IP \fBCYGWIN\fP: 9  
 See "WINDOWS NT4/2000/XP/2003/Vista/Win7/2008" above.  
 .\" %ENDIF OS Cygwin  
 .\" %IF OS OS2  .\" %IF OS OS2
 .IP \fBOS/2,eComStation\fP: 9  .IP \fBOS/2,eComStation\fP: 9
 Use the form \fB"/dev/hd[a\-z]"\fP for IDE/ATA devices.  Use the form \fB"/dev/hd[a\-z]"\fP for IDE/ATA devices.
Line 157  interprets it's own debug output from standard input. Line 155  interprets it's own debug output from standard input.
 See \'\-r ataioctl\' below for details.  See \'\-r ataioctl\' below for details.
 .PP  .PP
 Based on the device path, \fBsmartctl\fP will guess the device type  Based on the device path, \fBsmartctl\fP will guess the device type
(ATA or SCSI).  If necessary, the \'\-d\' option can be used to over\-ride(ATA or SCSI).  If necessary, the \'\-d\' option can be used to override
 this guess  this guess
   
 Note that the printed output of \fBsmartctl\fP displays most numerical  Note that the printed output of \fBsmartctl\fP displays most numerical
Line 196  in the smartmontools database (see \'\-v\' options bel Line 194  in the smartmontools database (see \'\-v\' options bel
 drive model family may also be printed. If \'\-n\' (see below) is  drive model family may also be printed. If \'\-n\' (see below) is
 specified, the power mode of the drive is printed.  specified, the power mode of the drive is printed.
 .TP  .TP
   .B \-\-identify[=[w][nvb]]
   [ATA only] [NEW EXPERIMENTAL SMARTCTL FEATURE] Prints an annotated
   table of the IDENTIFY DEVICE data.
   By default, only valid words (words not equal to 0x0000 or 0xffff)
   and nonzero bits and bit fields are printed.
   This can be changed by the optional argument which consists of one or
   two characters from the set \'wnvb\'.
   The character \'w\' enables printing of all 256 words. The character
   \'n\' suppresses printing of bits, \'v\' enables printing of all bits
   from valid words, \'b\' enables printing of all bits.
   For example \'\-\-identify=n\' (valid words, no bits) produces the
   shortest output and \'\-\-identify=wb\' (all words, all bits) produces
   the longest output.
   .TP
 .B \-a, \-\-all  .B \-a, \-\-all
 Prints all SMART information about the disk, or TapeAlert information  Prints all SMART information about the disk, or TapeAlert information
 about the tape drive or changer.  For ATA devices this is equivalent  about the tape drive or changer.  For ATA devices this is equivalent
Line 214  and the SMART options which require support for 48-bit Line 226  and the SMART options which require support for 48-bit
 Prints all SMART and non-SMART information about the device. For ATA  Prints all SMART and non-SMART information about the device. For ATA
 devices this is equivalent to  devices this is equivalent to
 .nf  .nf
\'\-H \-i \-c \-A \-f brief \-l xerror,error \-l xselftest,selftest\'\-H \-i \-g all \-c \-A \-f brief \-l xerror,error \-l xselftest,selftest
\-l selective \-l directory \-l scttemp \-l scterc \-l sataphy\'.\-l selective \-l directory \-l scttemp \-l scterc \-l devstat \-l sataphy\'.
 .fi  .fi
 and for SCSI, this is equivalent to  and for SCSI, this is equivalent to
 .nf  .nf
Line 238  This option can be used to create a draft \fBsmartd.co Line 250  This option can be used to create a draft \fBsmartd.co
 All options after \'\-\-\' are appended to each output line.  All options after \'\-\-\' are appended to each output line.
 For example:  For example:
 .nf  .nf
smartctl --scan-open -- -a -W 4,45,50 -m admin@work > smartd.confsmartctl \-\-scan\-open \-\- \-a \-W 4,45,50 \-m admin@work > smartd.conf
 .fi  .fi
   .TP
   .B \-g NAME, \-\-get=NAME
   Get non-SMART device settings.  See \'\-s, \-\-set\' below for further info.
   
 .TP  .TP
.B RUN\-TIME BEHAVIOR OPTIONS:.B RUN-TIME BEHAVIOR OPTIONS:
 .TP  .TP
 .B \-q TYPE, \-\-quietmode=TYPE  .B \-q TYPE, \-\-quietmode=TYPE
 Specifies that \fBsmartctl\fP should run in one of the two quiet modes  Specifies that \fBsmartctl\fP should run in one of the two quiet modes
Line 250  described here.  The valid arguments to this option ar Line 265  described here.  The valid arguments to this option ar
   
 .I errorsonly  .I errorsonly
 \- only print: For the \'\-l error\' option, if nonzero, the number  \- only print: For the \'\-l error\' option, if nonzero, the number
of errors recorded in the SMART error log and the power\-on time whenof errors recorded in the SMART error log and the power-on time when
 they occurred; For the \'\-l selftest\' option, errors recorded in the device  they occurred; For the \'\-l selftest\' option, errors recorded in the device
self\-test log; For the \'\-H\' option, SMART "disk failing" status or deviceself-test log; For the \'\-H\' option, SMART "disk failing" status or device
Attributes (pre\-failure or usage) which failed either now or in theAttributes (pre-failure or usage) which failed either now or in the
past; For the \'\-A\' option, device Attributes (pre\-failure or usage)past; For the \'\-A\' option, device Attributes (pre-failure or usage)
 which failed either now or in the past.  which failed either now or in the past.
   
 .I silent  .I silent
Line 269  Specifies the type of the device. Line 284  Specifies the type of the device.
 The valid arguments to this option are:  The valid arguments to this option are:
   
 .I auto  .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  controller type info provided by the operating system or from
 a matching USB ID entry in the drive database.  a matching USB ID entry in the drive database.
 This is the default.  This is the default.
   
 .I test  .I test
- prints the guessed type, then opens the device and prints the\- prints the guessed type, then opens the device and prints the
 (possibly changed) TYPE name and then exists without performing  (possibly changed) TYPE name and then exists without performing
 any further commands.  any further commands.
   
Line 290  from issuing SCSI commands to an ATA device. Line 305  from issuing SCSI commands to an ATA device.
 \fBsmartctl\fP  \fBsmartctl\fP
 from issuing ATA commands to a SCSI device.  from issuing ATA commands to a SCSI device.
   
.I sat.I sat[,auto][,N]
 \- the device type is SCSI to ATA Translation (SAT).  \- the device type is SCSI to ATA Translation (SAT).
 This is for ATA disks that have a SCSI to ATA Translation (SAT) Layer  This is for ATA disks that have a SCSI to ATA Translation (SAT) Layer
 (SATL) between the disk and the operating system.  (SATL) between the disk and the operating system.
Line 298  SAT defines two ATA PASS THROUGH SCSI commands, one 12 Line 313  SAT defines two ATA PASS THROUGH SCSI commands, one 12
 the other 16 bytes long.  The default is the 16 byte variant which can be  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\'.  overridden with either \'\-d sat,12\' or \'\-d sat,16\'.
   
   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.
   
 .I usbcypress  .I usbcypress
 \- this device type is for ATA disks that are behind a Cypress USB to PATA  \- 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.  bridge.  This will use the ATACB proprietary scsi pass through command.
Line 305  The default SCSI operation code is 0x24, but although  Line 324  The default SCSI operation code is 0x24, but although 
 with \'\-d usbcypress,0xN\', where N is the scsi operation code,  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.  you're running the risk of damage to the device or filesystems on it.
   
.I usbjmicron.I usbjmicron[,p][,x][,PORT]
- this device type is for SATA disks that are behind a JMicron USB to\- 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\',  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  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\'.  default.  These commands can be enabled by \'\-d usbjmicron,x\'.
Line 320  CAUTION: Specifying \',x\' for a device which does not Line 339  CAUTION: Specifying \',x\' for a device which does not
 in I/O errors and may disconnect the drive.  The same applies if the specified  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.  PORT does not exist or is not connected to a disk.
   
   [NEW EXPERIMENTAL SMARTCTL 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  .I usbsunplus
 \- this device type is for SATA disks that are behind a SunplusIT USB to SATA  \- this device type is for SATA disks that are behind a SunplusIT USB to SATA
 bridge.  bridge.
Line 341  Use syntax such as: Line 367  Use syntax such as:
 .nf  .nf
 \fBsmartctl \-a \-d megaraid,0 /dev/sdb\fP  \fBsmartctl \-a \-d megaraid,0 /dev/sdb\fP
 .fi  .fi
   .nf
   \fBsmartctl \-a \-d megaraid,0 /dev/bus/0\fP
   .fi
 This interface will also work for Dell PERC controllers.  This interface will also work for Dell PERC controllers.
The following /dev/XXX entry must exist:It is possible to set RAID device name as /dev/bus/N, where N is a SCSI bus
 number.
 
 The following entry in /proc/devices must exist:
 .fi  .fi
For PERC2/3/4 controllers: \fB/dev/megadev0\fPFor PERC2/3/4 controllers: \fBmegadevN\fP
 .fi  .fi
For PERC5/6 controllers: \fB/dev/megaraid_sas_ioctl_node\fPFor PERC5/6 controllers: \fBmegaraid_sas_ioctlN\fP
   
 .\" %ENDIF OS Linux  .\" %ENDIF OS Linux
 .\" %IF OS FreeBSD Linux  .\" %IF OS FreeBSD Linux
Line 357  connected to a 3ware RAID controller.  The non-negativ Line 389  connected to a 3ware RAID controller.  The non-negativ
 is monitored.  is monitored.
 Use syntax such as:  Use syntax such as:
 .nf  .nf
\fBsmartctl \-a \-d 3ware,2 /dev/sda\fP\fBsmartctl \-a \-d 3ware,2 /dev/sda\fP  [Linux only]
 .fi  .fi
 .nf  .nf
 \fBsmartctl \-a \-d 3ware,0 /dev/twe0\fP  \fBsmartctl \-a \-d 3ware,0 /dev/twe0\fP
Line 366  Use syntax such as: Line 398  Use syntax such as:
 \fBsmartctl \-a \-d 3ware,1 /dev/twa0\fP  \fBsmartctl \-a \-d 3ware,1 /dev/twa0\fP
 .fi  .fi
 .nf  .nf
\fBsmartctl \-a \-d 3ware,1 /dev/twl0\fP\fBsmartctl \-a \-d 3ware,1 /dev/twl0\fP [Linux only]
 .fi  .fi
   .nf
   \fBsmartctl \-a \-d 3ware,1 /dev/tws0\fP [FreeBSD only]
   .fi
 The first two forms, which refer to devices /dev/sda\-z and /dev/twe0\-15,  The first two forms, which refer to devices /dev/sda\-z and /dev/twe0\-15,
 may be used with 3ware series 6000, 7000, and 8000 series controllers  may be used with 3ware series 6000, 7000, and 8000 series controllers
that use the 3x\-xxxx driver.that use the 3x-xxxx driver.
 \fBNote that the /dev/sda\-z form is deprecated\fP starting with  \fBNote that the /dev/sda\-z form is deprecated\fP starting with
 the Linux 2.6 kernel series and may not be supported by the Linux  the Linux 2.6 kernel series and may not be supported by the Linux
 kernel in the near future.  The final form, which refers to devices  kernel in the near future.  The final form, which refers to devices
 /dev/twa0\-15, must be used with 3ware 9000 series controllers, which  /dev/twa0\-15, must be used with 3ware 9000 series controllers, which
 use the 3w\-9xxx driver.  use the 3w\-9xxx driver.
   
The devices /dev/twl0\-15 must be used with the 3ware/LSI 9750 seriesThe devices /dev/twl0\-15 [Linux] or /dev/tws0\-15 [FreeBSD] must be used with the 3ware/LSI 9750 series
 controllers which use the 3w-sas driver.  controllers which use the 3w-sas driver.
   
Note that if the special character device nodes /dev/twl?, /dev/twa?Note that if the special character device nodes /dev/tw[ls]?, /dev/twa?
 and /dev/twe? do not exist, or exist with the incorrect major or minor  and /dev/twe? do not exist, or exist with the incorrect major or minor
 numbers, smartctl will recreate them on the fly.  Typically /dev/twa0  numbers, smartctl will recreate them on the fly.  Typically /dev/twa0
refers to the first 9000\-series controller, /dev/twa1 refers to therefers to the first 9000-series controller, /dev/twa1 refers to the
 second 9000 series controller, and so on.  The /dev/twl0 devices refers  second 9000 series controller, and so on.  The /dev/twl0 devices refers
 to the first 9750 series controller, /dev/twl1 resfers to the second  to the first 9750 series controller, /dev/twl1 resfers to the second
 9750 series controller, and so on.  Likewise /dev/twe0 refers to  9750 series controller, and so on.  Likewise /dev/twe0 refers to
the first 6/7/8000\-series controller, /dev/twe1 refers to the secondthe first 6/7/8000-series controller, /dev/twe1 refers to the second
 6/7/8000 series controller, and so on.  6/7/8000 series controller, and so on.
   
 Note that for the 6/7/8000 controllers, \fBany\fP of the physical  Note that for the 6/7/8000 controllers, \fBany\fP of the physical
Line 409  disk attached to it, the behavior of \fBsmartctl\fP de Line 444  disk attached to it, the behavior of \fBsmartctl\fP de
 specific controller model, firmware, Linux kernel and platform.  In  specific controller model, firmware, Linux kernel and platform.  In
 some cases you will get a warning message that the device does not  some cases you will get a warning message that the device does not
 exist.  In other cases you will be presented with \'void\' data for a  exist.  In other cases you will be presented with \'void\' data for a
non\-existent device.non-existent device.
   
Note that if the /dev/sd? addressing form is used, then older 3w\-xxxxNote that if the /dev/sd? addressing form is used, then older 3w-xxxx
 drivers do not pass the "Enable Autosave"  drivers do not pass the "Enable Autosave"
 (\'\fB\-S on\fP\') and "Enable Automatic Offline" (\'\fB\-o on\fP\')  (\'\fB\-S on\fP\') and "Enable Automatic Offline" (\'\fB\-o on\fP\')
 commands to the disk, and produce these types of harmless syslog error  commands to the disk, and produce these types of harmless syslog error
messages instead: "\fB3w\-xxxx: tw_ioctl(): Passthru size (123392) toomessages instead: "\fB3w-xxxx: tw_ioctl(): Passthru size (123392) too
 big\fP".  This can be fixed by upgrading to version 1.02.00.037 or  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 olderlater of the 3w-xxxx driver, or by applying a patch to older
 versions.  Alternatively, use the character device /dev/twe0\-15 interface.  versions.  Alternatively, use the character device /dev/twe0\-15 interface.
   
The selective self\-test functions (\'\-t select,A\-B\') are only supportedThe selective self-test functions (\'\-t select,A\-B\') are only supported
using the character device interface /dev/twl0\-15, /dev/twa0\-15 and /dev/twe0\-15.using the character device interface /dev/twl0\-15, /dev/tws0\-15, /dev/twa0\-15 and /dev/twe0\-15.
 The necessary WRITE LOG commands can not be passed through the SCSI  The necessary WRITE LOG commands can not be passed through the SCSI
 interface.  interface.
   
 .\" %ENDIF OS FreeBSD Linux  .\" %ENDIF OS FreeBSD Linux
.\" %IF OS Linux.\" %IF OS FreeBSD Linux Windows Cygwin
 .I areca,N  .I areca,N
\- [Linux only] the device consists of one or more SATA disks connected to an\- [FreeBSD, Linux, Windows and Cygwin only] the device consists of one or more SATA disks
Areca SATA RAID controller.  The positive integer N (in the range from 1 toconnected to an Areca SATA RAID controller.  The positive integer N (in the range
24 inclusive) denotes which disk on the controller is monitored.from 1 to 24 inclusive) denotes which disk on the controller is monitored.
Use syntax such as:.\" %ENDIF OS FreeBSD Linux Windows Cygwin
 .\" %IF OS Linux
 On Linux use syntax such as:
 .nf  .nf
 \fBsmartctl \-a \-d areca,2 /dev/sg2\fP  \fBsmartctl \-a \-d areca,2 /dev/sg2\fP
 .fi  .fi
 .nf  .nf
 \fBsmartctl \-a \-d areca,3 /dev/sg3\fP  \fBsmartctl \-a \-d areca,3 /dev/sg3\fP
 .fi  .fi
   .\" %ENDIF OS Linux
   .\" %IF OS FreeBSD
   On FreeBSD use syntax such as:
   .nf
   \fBsmartctl \-a \-d areca,2 /dev/arcmsr1\fP
   .fi
   .nf
   \fBsmartctl \-a \-d areca,3 /dev/arcmsr2\fP
   .fi
   .\" %ENDIF OS FreeBSD
   .\" %IF OS Windows Cygwin
   [NEW EXPERIMENTAL SMARTCTL FEATURE] On Windows and Cygwin use syntax such as:
   .nf
   \fBsmartctl \-a \-d areca,2 /dev/arcmsr0\fP
   .fi
   .nf
   \fBsmartctl \-a \-d areca,3 /dev/arcmsr1\fP
   .fi
   .\" %ENDIF OS Windows Cygwin
   .\" %IF OS FreeBSD Linux Windows Cygwin
 The first line above addresses the second disk on the first Areca RAID controller.  The first line above addresses the second disk on the first Areca RAID controller.
 The second line addresses the third disk on the second Areca RAID  The second line addresses the third disk on the second Areca RAID
controller.  To help identify the correct device, use the command:controller.  
 .\" %ENDIF OS FreeBSD Linux Windows Cygwin
 .\" %IF OS Linux
 To help identify the correct device on Linux, use the command:
 .nf  .nf
 \fBcat /proc/scsi/sg/device_hdr /proc/scsi/sg/devices\fP  \fBcat /proc/scsi/sg/device_hdr /proc/scsi/sg/devices\fP
 .fi  .fi
Line 449  to show the SCSI generic devices (one per line, starti Line 509  to show the SCSI generic devices (one per line, starti
 smartmontools are the ones with the type field equal to 3.  If the  smartmontools are the ones with the type field equal to 3.  If the
 incorrect device is addressed, please read the warning/error messages  incorrect device is addressed, please read the warning/error messages
 carefully.  They should provide hints about what devices to use.  carefully.  They should provide hints about what devices to use.
   .\" %ENDIF OS Linux
   .\" %IF OS FreeBSD Linux Windows Cygwin
   
 Important: the Areca controller must have firmware version 1.46 or  Important: the Areca controller must have firmware version 1.46 or
 later.  Lower-numbered firmware versions will give (harmless) SCSI  later.  Lower-numbered firmware versions will give (harmless) SCSI
 error messages and no SMART information.  error messages and no SMART information.
   
.\" %ENDIF OS Linux.I areca,N/E
 \- [FreeBSD, Linux, Windows and Cygwin only] [NEW EXPERIMENTAL SMARTCTL FEATURE] the
 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 Areca SAS controller firmware version 1.51 or later.
 
 .\" %ENDIF OS FreeBSD Linux Windows Cygwin
 .\" %IF OS FreeBSD Linux  .\" %IF OS FreeBSD Linux
 .I cciss,N  .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  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.  from 0 to 15 inclusive) denotes which disk on the controller is monitored.
   
If the controller firmware or driver provides a SAT Layer it may be possibleTo look at disks behind HP Smart Array controllers, use syntax
to monitor also SATA disks by specifiying \'\-d sat+cciss,N\'.such as:
 .\" %ENDIF OS FreeBSD Linux
 .\" %IF OS Linux
 .nf
 \fBsmartctl \-a \-d cciss,0 /dev/cciss/c0d0\fP    (cciss driver under Linux)
 .fi
 .nf
 \fBsmartctl \-a \-d cciss,0 /dev/sg2\fP    (hpsa or hpahcisr drivers under Linux)
 .fi
 .\" %ENDIF OS Linux
 .\" %IF OS FreeBSD
 .nf
 \fBsmartctl \-a \-d cciss,0 /dev/ciss0\fP    (under FreeBSD)
 .fi
 .\" %ENDIF OS FreeBSD
 .\" %IF OS FreeBSD Linux
   
 .I hpt,L/M/N  .I hpt,L/M/N
 \- [FreeBSD and Linux only] the device consists of one or more ATA disks  \- [FreeBSD and Linux only] the device consists of one or more ATA disks
 connected to a HighPoint RocketRAID controller.  The integer L is the  connected to a HighPoint RocketRAID controller.  The integer L is the
 controller id, the integer M is the channel number, and the integer N  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  is the PMPort number if it is available.  The allowed values of L are
from 1 to 4 inclusive, M are from 1 to 16 inclusive and N from 1 to 4from 1 to 4 inclusive, M are from 1 to 128 inclusive and N from 1 to 4
 if PMPort available.  And also these values are limited by the model  if PMPort available.  And also these values are limited by the model
 of the HighPoint RocketRAID controller.  of the HighPoint RocketRAID controller.
 Use syntax such as:  Use syntax such as:
Line 503  command failures.  Line 587  command failures. 
   
 The behavior of \fBsmartctl\fP depends upon whether the command is  The behavior of \fBsmartctl\fP depends upon whether the command is
 "\fBoptional\fP" or "\fBmandatory\fP". Here "\fBmandatory\fP" means  "\fBoptional\fP" or "\fBmandatory\fP". Here "\fBmandatory\fP" means
"required by the ATA/ATAPI\-5 Specification if the device implements"required by the ATA Specification if the device implements
 the SMART command set" and "\fBoptional\fP" means "not required by the  the SMART command set" and "\fBoptional\fP" means "not required by the
ATA/ATAPI\-5 Specification even if the device implements the SMARTATA Specification even if the device implements the SMART
 command set."  The "\fBmandatory\fP" ATA and SMART commands are: (1)  command set."  The "\fBmandatory\fP" ATA and SMART commands are: (1)
 ATA IDENTIFY DEVICE, (2) SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE, (3)  ATA IDENTIFY DEVICE, (2) SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE, (3)
 SMART ENABLE/DISABLE, and (4) SMART RETURN STATUS.  SMART ENABLE/DISABLE, and (4) SMART RETURN STATUS.
Line 528  final message, Feature X is \fBnot\fP enabled. Line 612  final message, Feature X is \fBnot\fP enabled.
 \- ignore failure(s) of \fBmandatory\fP SMART commands.  This option  \- ignore failure(s) of \fBmandatory\fP SMART commands.  This option
 may be given more than once.  Each additional use of this option will  may be given more than once.  Each additional use of this option will
 cause one more additional failure to be ignored.  Note that the use of  cause one more additional failure to be ignored.  Note that the use of
this option can lead to messages like "Feature X not implemented",this option can lead to messages like "Feature X not supported",
followed shortly by "Error: unable to enable Feature X".  In a fewfollowed shortly by "Feature X enable failed".  In a few
 such cases, contrary to the final message, Feature X \fBis\fP enabled.  such cases, contrary to the final message, Feature X \fBis\fP enabled.
   
 .I verypermissive  .I verypermissive
Line 540  Please see the note above. Line 624  Please see the note above.
 .B \-b TYPE, \-\-badsum=TYPE  .B \-b TYPE, \-\-badsum=TYPE
 [ATA only] Specifies the action \fBsmartctl\fP should take if a checksum  [ATA only] Specifies the action \fBsmartctl\fP should take if a checksum
 error is detected in the: (1) Device Identity Structure, (2) SMART  error is detected in the: (1) Device Identity Structure, (2) SMART
Self\-Test Log Structure, (3) SMART Attribute Value Structure, (4) SMARTSelf-Test Log Structure, (3) SMART Attribute Value Structure, (4) SMART
 Attribute Threshold Structure, or (5) ATA Error Log Structure.  Attribute Threshold Structure, or (5) ATA Error Log Structure.
   
 The valid arguments to this option are:  The valid arguments to this option are:
Line 557  default. Line 641  default.
 .TP  .TP
 .B \-r TYPE, \-\-report=TYPE  .B \-r TYPE, \-\-report=TYPE
 Intended primarily to help \fBsmartmontools\fP developers understand  Intended primarily to help \fBsmartmontools\fP developers understand
the behavior of \fBsmartmontools\fP on non\-conforming or poorlythe behavior of \fBsmartmontools\fP on non-conforming or poorly
 conforming hardware.  This option reports details of \fBsmartctl\fP  conforming hardware.  This option reports details of \fBsmartctl\fP
 transactions with the device.  The option can be used multiple times.  transactions with the device.  The option can be used multiple times.
 When used just once, it shows a record of the ioctl() transactions  When used just once, it shows a record of the ioctl() transactions
Line 593  behaviour. This is does not work for SCSI devices yet. Line 677  behaviour. This is does not work for SCSI devices yet.
 .TP  .TP
 .B \-n POWERMODE, \-\-nocheck=POWERMODE  .B \-n POWERMODE, \-\-nocheck=POWERMODE
 [ATA only] Specifies if \fBsmartctl\fP should exit before performing any  [ATA only] Specifies if \fBsmartctl\fP should exit before performing any
checks when the device is in a low\-power mode. It may be used to preventchecks when the device is in a low-power mode. It may be used to prevent
a disk from being spun\-up by \fBsmartctl\fP. The power mode is ignored bya disk from being spun-up by \fBsmartctl\fP. The power mode is ignored by
 default.  A nonzero exit status is returned if the device is in one of the  default.  A nonzero exit status is returned if the device is in one of the
specified low\-power modes (see RETURN VALUES below).specified low-power modes (see RETURN VALUES below).
   
 Note: If this option is used it may also be necessary to specify the device  Note: If this option is used it may also be necessary to specify the device
type with the \'-d\' option.  Otherwise the device may spin up due totype with the \'\-d\' option.  Otherwise the device may spin up due to
 commands issued during device type autodetection.  commands issued during device type autodetection.
   
 The valid arguments to this option are:  The valid arguments to this option are:
Line 637  the corresponding disable command. Line 721  the corresponding disable command.
 Enables or disables SMART on device.  The valid arguments to  Enables or disables SMART on device.  The valid arguments to
 this option are \fIon\fP and \fIoff\fP.  Note that the command \'\-s on\'  this option are \fIon\fP and \fIoff\fP.  Note that the command \'\-s on\'
 (perhaps used with with the \'\-o on\' and \'\-S on\' options) should be  (perhaps used with with the \'\-o on\' and \'\-S on\' options) should be
placed in a start\-up script for your machine, for example in rc.local orplaced in a start-up script for your machine, for example in rc.local or
 rc.sysinit. In principle the SMART feature settings are preserved over  rc.sysinit. In principle the SMART feature settings are preserved over
power\-cycling, but it doesn\'t hurt to be sure. It is not necessary (orpower-cycling, but it doesn\'t hurt to be sure. It is not necessary (or
 useful) to enable SMART to see the TapeAlert messages.  useful) to enable SMART to see the TapeAlert messages.
 .TP  .TP
 .B \-o VALUE, \-\-offlineauto=VALUE  .B \-o VALUE, \-\-offlineauto=VALUE
Line 650  and \fIoff\fP. Line 734  and \fIoff\fP.
   
 Note that the SMART automatic offline test command is listed as  Note that the SMART automatic offline test command is listed as
 "Obsolete" in every version of the ATA and ATA/ATAPI Specifications.  "Obsolete" in every version of the ATA and ATA/ATAPI Specifications.
It was originally part of the SFF\-8035i Revision 2.0 specification,It was originally part of the SFF-8035i Revision 2.0 specification,
 but was never part of any ATA specification.  However it is  but was never part of any ATA specification.  However it is
 implemented and used by many vendors. [Good documentation can be found  implemented and used by many vendors. [Good documentation can be found
 in IBM\'s Official Published Disk Specifications.  For example the IBM  in IBM\'s Official Published Disk Specifications.  For example the IBM
 Travelstar 40GNX Hard Disk Drive Specifications (Revision 1.1, 22  Travelstar 40GNX Hard Disk Drive Specifications (Revision 1.1, 22
April 2002, Publication # 1541, Document S07N\-7715\-02) page 164. YouApril 2002, Publication # 1541, Document S07N-7715-02) page 164. You
can also read the SFF\-8035i Specification \-\- see REFERENCES below.]can also read the SFF-8035i Specification -- see REFERENCES below.]
 You can tell if automatic offline testing is supported by seeing if  You can tell if automatic offline testing is supported by seeing if
 this command enables and disables it, as indicated by the \'Auto  this command enables and disables it, as indicated by the \'Auto
 Offline Data Collection\' part of the SMART capabilities report  Offline Data Collection\' part of the SMART capabilities report
Line 672  type of test can, in principle, degrade the device per Line 756  type of test can, in principle, degrade the device per
 automatically, on a regular scheduled basis.  Normally, the disk will  automatically, on a regular scheduled basis.  Normally, the disk will
 suspend offline testing while disk accesses are taking place, and then  suspend offline testing while disk accesses are taking place, and then
 automatically resume it when the disk would otherwise be idle, so in  automatically resume it when the disk would otherwise be idle, so in
practice it has little effect.  Note that a one\-time offline test canpractice it has little effect.  Note that a one-time offline test can
 also be carried out immediately upon receipt of a user command.  See  also be carried out immediately upon receipt of a user command.  See
the \'\-t offline\' option below, which causes a one\-time offline testthe \'\-t offline\' option below, which causes a one-time offline test
 to be carried out immediately.  to be carried out immediately.
   
The choice (made by the SFF\-8035i and ATA specification authors) ofThe choice (made by the SFF-8035i and ATA specification authors) of
 the word \fItesting\fP for these first two categories is unfortunate,  the word \fItesting\fP for these first two categories is unfortunate,
 and often leads to confusion.  In fact these first two categories of  and often leads to confusion.  In fact these first two categories of
 online and offline testing could have been more accurately described  online and offline testing could have been more accurately described
Line 690  Attributes will go below their failure thresholds; som Line 774  Attributes will go below their failure thresholds; som
 errors may also appear in the SMART error log. These are visible with  errors may also appear in the SMART error log. These are visible with
 the \'\-A\' and \'\-l error\' options respectively.  the \'\-A\' and \'\-l error\' options respectively.
   
Some SMART attribute values are updated only during off\-line dataSome SMART attribute values are updated only during off-line data
 collection activities; the rest are updated during normal operation of  collection activities; the rest are updated during normal operation of
the device or during both normal operation and off\-line testing.  Thethe device or during both normal operation and off-line testing.  The
 Attribute value table produced by the \'\-A\' option indicates this in  Attribute value table produced by the \'\-A\' option indicates this in
 the UPDATED column.  Attributes of the first type are labeled  the UPDATED column.  Attributes of the first type are labeled
 "Offline" and Attributes of the second type are labeled "Always".  "Offline" and Attributes of the second type are labeled "Always".
Line 701  The \fBthird\fP category of testing (and the \fIonly\f Line 785  The \fBthird\fP category of testing (and the \fIonly\f
 which the word \'testing\' is really an appropriate choice) is "self"  which the word \'testing\' is really an appropriate choice) is "self"
 testing.  This third type of test is only performed (immediately) when  testing.  This third type of test is only performed (immediately) when
 a command to run it is issued.  The \'\-t\' and \'\-X\' options can be  a command to run it is issued.  The \'\-t\' and \'\-X\' options can be
used to carry out and abort such self\-tests; please see below forused to carry out and abort such self-tests; please see below for
 further details.  further details.
   
 Any errors detected in the self testing will be shown in the  Any errors detected in the self testing will be shown in the
SMART self\-test log, which can be examined using the \'\-l selftest\'SMART self-test log, which can be examined using the \'\-l selftest\'
 option.  option.
   
 \fBNote:\fP in this manual page, the word \fB"Test"\fP is used in  \fBNote:\fP in this manual page, the word \fB"Test"\fP is used in
 connection with the second category just described, e.g. for the  connection with the second category just described, e.g. for the
"offline" testing.  The words \fB"Self\-test"\fP are used in"offline" testing.  The words \fB"Self-test"\fP are used in
 connection with the third category.  connection with the third category.
 .TP  .TP
 .B \-S VALUE, \-\-saveauto=VALUE  .B \-S VALUE, \-\-saveauto=VALUE
[ATA] Enables or disables SMART autosave of device vendor\-specific[ATA] Enables or disables SMART autosave of device vendor-specific
 Attributes. The valid arguments to this option are \fIon\fP  Attributes. The valid arguments to this option are \fIon\fP
 and \fIoff\fP.  Note that this feature is preserved across disk power  and \fIoff\fP.  Note that this feature is preserved across disk power
 cycles, so you should only need to issue it once.  cycles, so you should only need to issue it once.
Line 726  a warning if autosave is disabled. Line 810  a warning if autosave is disabled.
 [SCSI] For SCSI devices this toggles the value of the Global Logging  [SCSI] For SCSI devices this toggles the value of the Global Logging
 Target Save Disabled (GLTSD) bit in the Control Mode Page. Some disk  Target Save Disabled (GLTSD) bit in the Control Mode Page. Some disk
 manufacturers set this bit by default. This prevents error counters,  manufacturers set this bit by default. This prevents error counters,
power\-up hours and other useful data from being placed in non\-volatilepower-up hours and other useful data from being placed in non-volatile
 storage, so these values may be reset to zero the next time the device  storage, so these values may be reset to zero the next time the device
is power\-cycled.  If the GLTSD bit is set then \'smartctl \-a\' willis power-cycled.  If the GLTSD bit is set then \'smartctl \-a\' will
 issue a warning. Use \fIon\fP to clear the GLTSD bit and thus enable  issue a warning. Use \fIon\fP to clear the GLTSD bit and thus enable
saving counters to non\-volatile storage. For extreme streaming\-videosaving counters to non-volatile storage. For extreme streaming-video
 type applications you might consider using \fIoff\fP to set the GLTSD  type applications you might consider using \fIoff\fP to set the GLTSD
 bit.  bit.
   .TP
   .B \-g NAME, \-\-get=NAME, \-s NAME[,VALUE], \-\-set=NAME[,VALUE]
   Gets/sets non-SMART device settings.
   Note that the \'\-\-set\' option shares its short option \'\-s\' with
   \'\-\-smart\'.  Valid arguments are:
   
   .I all
   \- Gets all values. This is equivalent to
   .nf
   \'-g aam -g apm -g lookahead -g security -g wcache\'
   .fi
   
   .I aam[,N|off]
   \- [ATA only] Gets/sets the Automatic Acoustic Management (AAM) feature
   (if supported).  A value of 128 sets the most quiet (slowest) mode and 254
   the fastest (loudest) mode, \'off\' disables AAM.  Devices may support
   intermediate levels.  Values below 128 are defined as vendor specific (0)
   or retired (1 to 127).  Note that the AAM feature was declared obsolete in
   ATA ACS-2 Revision 4a (Dec 2010).
   
   .I apm[,N|off]
   \- [ATA only] Gets/sets the Advanced Power Management (APM) feature on
   device (if supported).  If a value between 1 and 254 is provided, it will
   attempt to enable APM and set the specified value, \'off\' disables APM.
   Note the actual behavior depends on the drive, for example some drives disable
   APM if their value is set above 128.  Values below 128 are supposed to allow
   drive spindown, values 128 and above adjust only head-parking frequency,
   although the actual behavior defined is also vendor-specific.
   
   .I lookahead[,on|off]
   \- [ATA only] Gets/sets the read look-ahead feature (if supported).
   Read look-ahead is usually enabled by default.
   
   .I security
   \- [ATA only] Gets the status of ATA Security feature (if supported).
   If ATA Security is enabled an ATA user password is set.  The drive will be
   locked on next reset then.
   
   .I security-freeze
   \- [ATA only] Sets ATA Security feature to frozen mode.  This prevents that
   the drive accepts any security commands until next reset.  Note that the
   frozen mode may already be set by BIOS or OS.
   
   .I standby,[N|off]
   \- [ATA only] Sets the standby (spindown) timer and places the drive in the
   IDLE mode.  A value of 0 or \'off\' disables the standby timer.
   Values from 1 to 240 specify timeouts from 5 seconds to 20 minutes in 5
   second increments.  Values from 241 to 251 specify timeouts from 30 minutes
   to 330 minutes in 30 minute increments.  Value 252 specifies 21 minutes.
   Value 253 specifies a vendor specific time between 8 and 12 hours.  Value
   255 specifies 21 minutes and 15 seconds.  Some drives may use a vendor
   specific interpretation for the values.  Note that there is no get option
   because ATA standards do not specify a method to read the standby timer.
   
   .I standby,now
   \- [ATA only] Places the drive in the STANDBY mode.  This usually spins down
   the drive.  The setting of the standby timer is not affected.
   
   .I wcache[,on|off]
   \- [ATA] Gets/sets the volatile write cache feature (if supported).
   The write cache is usually enabled by default.
   
   .I wcache[,on|off]
   \- [SCSI] [NEW EXPERIMENTAL SMARTCTL FEATURE]
   Gets/sets the \'Write Cache Enable\' (WCE) bit (if supported).
   The write cache is usually enabled by default.
   
   .I wcreorder[,on|off]
   \- [ATA only] [NEW EXPERIMENTAL SMARTCTL FEATURE]
   Gets/sets Write Cache Reordering.
   If it is disabled (off), disk write scheduling is executed on a 
   first-in-first-out (FIFO) basis. If Write Cache Reordering is enabled (on),
   then disk write scheduling may be reordered by the drive. If write cache is
   disabled, the current Write Cache Reordering state is remembered but has
   no effect on non-cached writes, which are always written in the order received.
   The state of Write Cache Reordering has no effect on either NCQ or LCQ queued
   commands.
   
   .I rcache[,on|off]
   \- [SCSI only] [NEW EXPERIMENTAL SMARTCTL FEATURE]
   Gets/sets the \'Read Cache Disable\' (RCE) bit. \'Off\' value disables read cache
   (if supported).
   The read cache is usually enabled by default.
   
 .TP  .TP
 .B SMART READ AND DISPLAY DATA OPTIONS:  .B SMART READ AND DISPLAY DATA OPTIONS:
 .TP  .TP
Line 742  Check: Ask the device to report its SMART health statu Line 909  Check: Ask the device to report its SMART health statu
 TapeAlert messages.  SMART status is based on  TapeAlert messages.  SMART status is based on
 information that it has gathered from online and offline  information that it has gathered from online and offline
 tests, which were used to determine/update its  tests, which were used to determine/update its
SMART vendor\-specific Attribute values. TapeAlert status is obtainedSMART vendor-specific Attribute values. TapeAlert status is obtained
 by reading the TapeAlert log page.  by reading the TapeAlert log page.
   
 If the device reports failing health status, this means  If the device reports failing health status, this means
Line 758  this happens, use the \'\-a\' option to get more infor Line 925  this happens, use the \'\-a\' option to get more infor
 show what SMART features are implemented and how the device will  show what SMART features are implemented and how the device will
 respond to some of the different SMART commands.  For example it  respond to some of the different SMART commands.  For example it
 shows if the device logs errors, if it supports offline surface  shows if the device logs errors, if it supports offline surface
scanning, and so on.  If the device can carry out self\-tests, thisscanning, and so on.  If the device can carry out self-tests, this
 option also shows the estimated time required to run those tests.  option also shows the estimated time required to run those tests.
   
Note that the time required to run the Self\-tests (listed in minutes)Note that the time required to run the Self-tests (listed in minutes)
 are fixed.  However the time required to run the Immediate Offline  are fixed.  However the time required to run the Immediate Offline
 Test (listed in seconds) is variable.  This means that if you issue a  Test (listed in seconds) is variable.  This means that if you issue a
 command to perform an Immediate Offline test with the \'\-t offline\' option,  command to perform an Immediate Offline test with the \'\-t offline\' option,
Line 778  disk been powered up. Line 945  disk been powered up.
   
 Each Attribute has a "Raw" value, printed under the heading  Each Attribute has a "Raw" value, printed under the heading
 "RAW_VALUE", and a "Normalized" value printed under the heading  "RAW_VALUE", and a "Normalized" value printed under the heading
"VALUE".  [Note: \fBsmartctl\fP prints these values in base\-10.]  In"VALUE".  [Note: \fBsmartctl\fP prints these values in base-10.]  In
 the example just given, the "Raw Value" for Attribute 12 would be the  the example just given, the "Raw Value" for Attribute 12 would be the
actual number of times that the disk has been power\-cycled, foractual number of times that the disk has been power-cycled, for
 example 365 if the disk has been turned on once per day for exactly  example 365 if the disk has been turned on once per day for exactly
 one year.  Each vendor uses their own algorithm to convert this "Raw"  one year.  Each vendor uses their own algorithm to convert this "Raw"
 value to a "Normalized" value in the range from 1 to 254.  Please keep  value to a "Normalized" value in the range from 1 to 254.  Please keep
Line 794  not specified by the SMART standard. In most cases, th Line 961  not specified by the SMART standard. In most cases, th
 by \fBsmartctl\fP are sensible.  For example the temperature Attribute  by \fBsmartctl\fP are sensible.  For example the temperature Attribute
 generally has its raw value equal to the temperature in Celsius.  generally has its raw value equal to the temperature in Celsius.
 However in some cases vendors use unusual conventions.  For example  However in some cases vendors use unusual conventions.  For example
the Hitachi disk on my laptop reports its power\-on hours in minutes,the Hitachi disk on my laptop reports its power-on hours in minutes,
 not hours. Some IBM disks track three temperatures rather than one, in  not hours. Some IBM disks track three temperatures rather than one, in
 their raw values.  And so on.  their raw values.  And so on.
   
 Each Attribute also has a Threshold value (whose range is 0 to 255)  Each Attribute also has a Threshold value (whose range is 0 to 255)
 which is printed under the heading "THRESH".  If the Normalized value  which is printed under the heading "THRESH".  If the Normalized value
 is \fBless than or equal to\fP the Threshold value, then the Attribute  is \fBless than or equal to\fP the Threshold value, then the Attribute
is said to have failed.  If the Attribute is a pre\-failure Attribute,is said to have failed.  If the Attribute is a pre-failure Attribute,
 then disk failure is imminent.  then disk failure is imminent.
   
 Each Attribute also has a "Worst" value shown under the heading  Each Attribute also has a "Worst" value shown under the heading
 "WORST".  This is the smallest (closest to failure) value that the  "WORST".  This is the smallest (closest to failure) value that the
 disk has recorded at any time during its lifetime when SMART was  disk has recorded at any time during its lifetime when SMART was
 enabled.  [Note however that some vendors firmware may actually  enabled.  [Note however that some vendors firmware may actually
\fBincrease\fP the "Worst" value for some "rate\-type" Attributes.]\fBincrease\fP the "Worst" value for some "rate-type" Attributes.]
   
 The Attribute table printed out by \fBsmartctl\fP also shows the  The Attribute table printed out by \fBsmartctl\fP also shows the
 "TYPE" of the Attribute. Attributes are one of two possible types:  "TYPE" of the Attribute. Attributes are one of two possible types:
Pre\-failure or Old age.  Pre\-failure Attributes are ones which, ifPre-failure or Old age.  Pre-failure Attributes are ones which, if
 less than or equal to their threshold values, indicate pending disk  less than or equal to their threshold values, indicate pending disk
 failure.  Old age, or usage Attributes, are ones which indicate  failure.  Old age, or usage Attributes, are ones which indicate
end\-of\-product life from old\-age or normal aging and wearout, ifend-of-product life from old-age or normal aging and wearout, if
 the Attribute value is less than or equal to the threshold.  \fBPlease  the Attribute value is less than or equal to the threshold.  \fBPlease
note\fP: the fact that an Attribute is of type 'Pre\-fail' doesnote\fP: the fact that an Attribute is of type 'Pre-fail' does
 \fBnot\fP mean that your disk is about to fail!  It only has this  \fBnot\fP mean that your disk is about to fail!  It only has this
 meaning if the Attribute\'s current Normalized value is less than or  meaning if the Attribute\'s current Normalized value is less than or
 equal to the threshold value.  equal to the threshold value.
Line 831  a dash: \'\-\') then this Attribute is OK now (not fai Line 998  a dash: \'\-\') then this Attribute is OK now (not fai
 also never failed in the past.  also never failed in the past.
   
 The table column labeled "UPDATED" shows if the SMART Attribute values  The table column labeled "UPDATED" shows if the SMART Attribute values
are updated during both normal operation and off\-line testing, orare updated during both normal operation and off-line testing, or
 only during offline testing.  The former are labeled "Always" and the  only during offline testing.  The former are labeled "Always" and the
 latter are labeled "Offline".  latter are labeled "Offline".
   
 So to summarize: the Raw Attribute values are the ones that might have  So to summarize: the Raw Attribute values are the ones that might have
 a real physical interpretation, such as "Temperature Celsius",  a real physical interpretation, such as "Temperature Celsius",
"Hours", or "Start\-Stop Cycles".  Each manufacturer converts these,"Hours", or "Start-Stop Cycles".  Each manufacturer converts these,
 using their detailed knowledge of the disk\'s operations and failure  using their detailed knowledge of the disk\'s operations and failure
 modes, to Normalized Attribute values in the range 1\-254.  The  modes, to Normalized Attribute values in the range 1\-254.  The
 current and worst (lowest measured) of these Normalized Attribute  current and worst (lowest measured) of these Normalized Attribute
Line 848  fail, or that it has exceeded its design age or aging  Line 1015  fail, or that it has exceeded its design age or aging 
 thresholds, or types, it merely reports them from the SMART data on  thresholds, or types, it merely reports them from the SMART data on
 the device.  the device.
   
Note that starting with ATA/ATAPI\-4, revision 4, the meaning of theseNote that starting with ATA/ATAPI-4, revision 4, the meaning of these
Attribute fields has been made entirely vendor\-specific.  However mostAttribute fields has been made entirely vendor-specific.  However most
ATA/ATAPI\-5 disks seem to respect their meaning, so we have retainednewer ATA/SATA disks seem to respect their meaning, so we have retained
 the option of printing the Attribute values.  the option of printing the Attribute values.
   
   Solid-state drives use different meanings for some of the attributes.
   In this case the attribute name printed by smartctl is incorrect unless
   the drive is already in the smartmontools drive database.
   
 [SCSI] For SCSI devices the "attributes" are obtained from the temperature  [SCSI] For SCSI devices the "attributes" are obtained from the temperature
and start\-stop cycle counter log pages. Certain vendor specificand start-stop cycle counter log pages. Certain vendor specific
 attributes are listed if recognised. The attributes are output in a  attributes are listed if recognised. The attributes are output in a
 relatively free format (compared with ATA disk attributes).  relatively free format (compared with ATA disk attributes).
 .TP  .TP
 .B \-f FORMAT, \-\-format=FORMAT  .B \-f FORMAT, \-\-format=FORMAT
[ATA only] Selects the output format of the attributes to one of:[ATA only] Selects the output format of the attributes:
   
 .I old  .I old
 \- Old smartctl format. This is the default unless the \'\-x\' option is  \- Old smartctl format. This is the default unless the \'\-x\' option is
Line 869  specified. Line 1040  specified.
 \- New format which fits into 80 colums (except in some rare cases).  \- New format which fits into 80 colums (except in some rare cases).
 This format also decodes four additional attribute flags.  This format also decodes four additional attribute flags.
 This is the default if the '\-x\' option is specified.  This is the default if the '\-x\' option is specified.
   
   .I hex,id
   \- Print all attribute IDs as hexadecimal numbers.
   
   .I hex,val
   \- Print all normalized values as hexadecimal numbers.
   
   .I hex
   \- Same as \'\-f hex,id \-f hex,val\'.
 .TP  .TP
 .B \-l TYPE, \-\-log=TYPE  .B \-l TYPE, \-\-log=TYPE
Prints either the SMART Error Log, the SMART Self\-Test Log, the SMARTPrints either the SMART Error Log, the SMART Self-Test Log, the SMART
Selective Self\-Test Log [ATA only], the Log Directory [ATA only], orSelective Self-Test Log [ATA only], the Log Directory [ATA only], or
 the Background Scan Results Log [SCSI only].  the Background Scan Results Log [SCSI only].
 The valid arguments to this option are:  The valid arguments to this option are:
   
 .I error  .I error
 \- [ATA] prints the Summary SMART error log.  SMART disks maintain a log  \- [ATA] prints the Summary SMART error log.  SMART disks maintain a log
of the most recent five non\-trivial errors. For each of these errors, theof the most recent five non-trivial errors. For each of these errors, the
disk power\-on lifetime at which the error occurred is recorded, as isdisk power-on lifetime at which the error occurred is recorded, as is
 the device status (idle, standby, etc) at the time of the error.  For  the device status (idle, standby, etc) at the time of the error.  For
 some common types of errors, the Error Register (ER) and Status  some common types of errors, the Error Register (ER) and Status
 Register (SR) values are decoded and printed as text. The meanings of these  Register (SR) values are decoded and printed as text. The meanings of these
Line 891  are: Line 1071  are:
    \fBEOM\fP:   \fBE\fPnd \fBO\fPf \fBM\fPedia     \fBEOM\fP:   \fBE\fPnd \fBO\fPf \fBM\fPedia
    \fBICRC\fP:  \fBI\fPnterface \fBC\fPyclic \fBR\fPedundancy \fBC\fPode (CRC) error     \fBICRC\fP:  \fBI\fPnterface \fBC\fPyclic \fBR\fPedundancy \fBC\fPode (CRC) error
    \fBIDNF\fP:  \fBID\fPentity \fBN\fPot \fBF\fPound     \fBIDNF\fP:  \fBID\fPentity \fBN\fPot \fBF\fPound
   \fBILI\fP:   (packet command\-set specific)   \fBILI\fP:   (packet command-set specific)
    \fBMC\fP:    \fBM\fPedia \fBC\fPhanged     \fBMC\fP:    \fBM\fPedia \fBC\fPhanged
    \fBMCR\fP:   \fBM\fPedia \fBC\fPhange \fBR\fPequest     \fBMCR\fP:   \fBM\fPedia \fBC\fPhange \fBR\fPequest
    \fBNM\fP:    \fBN\fPo \fBM\fPedia     \fBNM\fP:    \fBN\fPo \fBM\fPedia
Line 907  Dd+HH:MM:SS.msec where D is the number of days, HH is  Line 1087  Dd+HH:MM:SS.msec where D is the number of days, HH is 
 minutes, SS is seconds and msec is milliseconds.  [Note: this time  minutes, SS is seconds and msec is milliseconds.  [Note: this time
 stamp wraps after 2^32 milliseconds, or 49 days 17 hours 2 minutes and  stamp wraps after 2^32 milliseconds, or 49 days 17 hours 2 minutes and
 47.296 seconds.]  The key ATA disk registers are also recorded in the  47.296 seconds.]  The key ATA disk registers are also recorded in the
log.  The final column of the error log is a text\-string descriptionlog.  The final column of the error log is a text-string description
 of the ATA command defined by the Command Register (CR) and Feature  of the ATA command defined by the Command Register (CR) and Feature
 Register (FR) values.  Commands that are obsolete in the most current  Register (FR) values.  Commands that are obsolete in the most current
(ATA\-7) spec are listed like this: \fBREAD LONG (w/ retry) [OBS\-4]\fP,spec are listed like this: \fBREAD LONG (w/ retry) [OBS-4]\fP,
indicating that the command became obsolete with or in the ATA\-4indicating that the command became obsolete with or in the ATA-4
 specification.  Similarly, the notation \fB[RET\-\fP\fIN\fP\fB]\fP is  specification.  Similarly, the notation \fB[RET\-\fP\fIN\fP\fB]\fP is
used to indicate that a command was retired in the ATA\-\fIN\fPused to indicate that a command was retired in the ATA-\fIN\fP
 specification.  Some commands are not defined in any version of the  specification.  Some commands are not defined in any version of the
 ATA specification but are in common use nonetheless; these are marked  ATA specification but are in common use nonetheless; these are marked
\fB[NS]\fP, meaning non\-standard.\fB[NS]\fP, meaning non-standard.
   
The ATA Specification (ATA\-5 Revision 1c, Section 8.41.6.8.2) says:The ATA Specification (ATA-5 Revision 1c, Section 8.41.6.8.2) says:
 \fB"Error log structures shall include UNC errors, IDNF errors for  \fB"Error log structures shall include UNC errors, IDNF errors for
 which the address requested was valid, servo errors, write fault  which the address requested was valid, servo errors, write fault
 errors, etc.  Error log data structures shall not include errors  errors, etc.  Error log data structures shall not include errors
Line 931  to data which has been read from the disk, but for whi Line 1111  to data which has been read from the disk, but for whi
 Checking and Correction (ECC) codes are inconsistent.  In effect, this  Checking and Correction (ECC) codes are inconsistent.  In effect, this
 means that the data can not be read.  means that the data can not be read.
 .br  .br
\fBIDNF\fP (\fBID N\fPot \fBF\fPound): user\-accessible address could\fBIDNF\fP (\fBID N\fPot \fBF\fPound): user-accessible address could
 not be found. For READ LOG type commands, \fBIDNF\fP can also indicate  not be found. For READ LOG type commands, \fBIDNF\fP can also indicate
 that a device data log structure checksum was incorrect.  that a device data log structure checksum was incorrect.
   
 If the command that caused the error was a READ or WRITE command, then  If the command that caused the error was a READ or WRITE command, then
 the Logical Block Address (LBA) at which the error occurred will be  the Logical Block Address (LBA) at which the error occurred will be
 printed in base 10 and base 16.  The LBA is a linear address, which  printed in base 10 and base 16.  The LBA is a linear address, which
counts 512\-byte sectors on the disk, starting from zero.  (Because ofcounts 512-byte sectors on the disk, starting from zero.  (Because of
 the limitations of the SMART error log, if the LBA is greater than  the limitations of the SMART error log, if the LBA is greater than
 0xfffffff, then either no error log entry will be made, or the error  0xfffffff, then either no error log entry will be made, or the error
 log entry will have an incorrect LBA. This may happen for drives with  log entry will have an incorrect LBA. This may happen for drives with
Line 963  the contents of the 48-bit LBA register set introduced Line 1143  the contents of the 48-bit LBA register set introduced
 It also supports logs with more than one sector.  Each sector holds  It also supports logs with more than one sector.  Each sector holds
 up to 4 log entries. The actual number of log sectors is vendor  up to 4 log entries. The actual number of log sectors is vendor
 specific, typical values for HDD are 2 (Samsung), 5 (Seagate) or  specific, typical values for HDD are 2 (Samsung), 5 (Seagate) or
6 (WD).  Some recent SSD devices have much larger error logs.6 (WD).
   
 Only the 8 most recent error log entries are printed by default.  Only the 8 most recent error log entries are printed by default.
 This number can be changed by the optional parameter NUM.  This number can be changed by the optional parameter NUM.
Line 971  This number can be changed by the optional parameter N Line 1151  This number can be changed by the optional parameter N
 If ',error' is appended and the Extended Comprehensive SMART error  If ',error' is appended and the Extended Comprehensive SMART error
 log is not supported, the Summary SMART self-test log is printed.  log is not supported, the Summary SMART self-test log is printed.
   
Please note that some recent (e.g. Samsung) drives report errors onlyPlease note that recent drives may report errors only in the Extended
in the Extended Comprehensive SMART error log. The Summary SMART errorComprehensive SMART error log.  The Summary SMART error log may be reported
log can be read but is always empty.as supported but is always empty then.
   
 .I selftest  .I selftest
\- [ATA] prints the SMART self\-test log.  The disk maintains a self\-test\- [ATA] prints the SMART self-test log.  The disk maintains a self-test
 log showing the results of the self tests, which can be run using the  log showing the results of the self tests, which can be run using the
 \'\-t\' option described below.  For each of the most recent  \'\-t\' option described below.  For each of the most recent
twenty\-one self\-tests, the log shows the type of test (short ortwenty-one self-tests, the log shows the type of test (short or
extended, off\-line or captive) and the final status of the test.  Ifextended, off-line or captive) and the final status of the test.  If
 the test did not complete successfully, then the percentage of the  the test did not complete successfully, then the percentage of the
 test remaining is shown.  The time at which the test took place,  test remaining is shown.  The time at which the test took place,
 measured in hours of disk lifetime, is also printed. [Note: this time  measured in hours of disk lifetime, is also printed. [Note: this time
Line 991  smartmontools web page has instructions about how to c Line 1171  smartmontools web page has instructions about how to c
 address to the name of the disk file containing the erroneous block.  address to the name of the disk file containing the erroneous block.
   
 .I selftest  .I selftest
\- [SCSI] the self\-test log for a SCSI device has a slightly different\- [SCSI] the self-test log for a SCSI device has a slightly different
 format than for an ATA device.  For each of the most recent twenty  format than for an ATA device.  For each of the most recent twenty
self\-tests, it shows the type of test and the status (final or inself-tests, it shows the type of test and the status (final or in
 progress) of the test. SCSI standards use the terms "foreground" and  progress) of the test. SCSI standards use the terms "foreground" and
 "background" (rather than ATA\'s corresponding "captive" and  "background" (rather than ATA\'s corresponding "captive" and
"off\-line") and "short" and "long" (rather than ATA\'s corresponding"off-line") and "short" and "long" (rather than ATA\'s corresponding
 "short" and "extended") to describe the type of the test.  The printed  "short" and "extended") to describe the type of the test.  The printed
 segment number is only relevant when a test fails in the third or  segment number is only relevant when a test fails in the third or
 later test segment.  It identifies the test that failed and consists  later test segment.  It identifies the test that failed and consists
 of either the number of the segment that failed during the test, or  of either the number of the segment that failed during the test, or
 the number of the test that failed and the number of the segment in  the number of the test that failed and the number of the segment in
which the test was run, using a vendor\-specific method of putting bothwhich the test was run, using a vendor-specific method of putting both
 numbers into a single byte.  The Logical Block Address (LBA) of the  numbers into a single byte.  The Logical Block Address (LBA) of the
 first error is printed in hexadecimal notation.  On Linux systems the  first error is printed in hexadecimal notation.  On Linux systems the
 smartmontools web page has instructions about how to convert this LBA  smartmontools web page has instructions about how to convert this LBA
Line 1013  can be run using the \'\-t\' option described below (u Line 1193  can be run using the \'\-t\' option described below (u
 test terminology).  test terminology).
   
 .I xselftest[,NUM][,selftest]  .I xselftest[,NUM][,selftest]
\- [ATA only] prints the Extended SMART self\-test log (General Purpose\- [ATA only] prints the Extended SMART self-test log (General Purpose
Log address 0x07). Unlike the SMART self\-test log (see \'\-l selftest\'Log address 0x07). Unlike the SMART self-test log (see \'\-l selftest\'
 above), it supports 48-bit LBA and logs with more than one sector.  above), it supports 48-bit LBA and logs with more than one sector.
 Each sector holds up to 19 log entries. The actual number of log sectors  Each sector holds up to 19 log entries. The actual number of log sectors
 is vendor specific, typical values are 1 (Seagate) or 2 (Samsung).  is vendor specific, typical values are 1 (Seagate) or 2 (Samsung).
Line 1027  supported, the old SMART self-test log is printed. Line 1207  supported, the old SMART self-test log is printed.
   
 .I selective  .I selective
 \- [ATA only] Please see the \'\-t select\' option below for a  \- [ATA only] Please see the \'\-t select\' option below for a
description of selective self\-tests.  The selective self\-test logdescription of selective self-tests.  The selective self-test log
 shows the start/end Logical Block Addresses (LBA) of each of the five  shows the start/end Logical Block Addresses (LBA) of each of the five
 test spans, and their current test status.  If the span is being  test spans, and their current test status.  If the span is being
tested or the remainder of the disk is being read\-scanned, thetested or the remainder of the disk is being read-scanned, the
current 65536\-sector block of LBAs being tested is also displayed.current 65536-sector block of LBAs being tested is also displayed.
The selective self\-test log also shows if a read\-scan of theThe selective self-test log also shows if a read-scan of the
 remainder of the disk will be carried out after the selective  remainder of the disk will be carried out after the selective
self\-test has completed (see \'\-t afterselect\' option) and the timeself-test has completed (see \'\-t afterselect\' option) and the time
delay before restarting this read\-scan if it is interrupted (seedelay before restarting this read-scan if it is interrupted (see
\'\-t pending\' option). This is a new smartmontools feature; please\'\-t pending\' option).
report unusual or incorrect behavior to the smartmontools\-support 
mailing list. 
   
 .I directory[,gs]  .I directory[,gs]
 \- [ATA only] if the device supports the General Purpose Logging feature  \- [ATA only] if the device supports the General Purpose Logging feature
set (ATA\-6 and above) then this prints the Log Directory (the log atset (ATA-6 and above) then this prints the Log Directory (the log at
 address 0).  The Log Directory shows what logs are available and their  address 0).  The Log Directory shows what logs are available and their
 length in sectors (512 bytes).  The contents of the logs at address 1  length in sectors (512 bytes).  The contents of the logs at address 1
[Summary SMART error log] and at address 6 [SMART self\-test log] may[Summary SMART error log] and at address 6 [SMART self-test log] may
be printed using the previously\-describedbe printed using the previously-described
 .I error  .I error
 and  and
 .I selftest  .I selftest
Line 1058  SL directory by \'\-l directory,q\' or \'\-l directory Line 1236  SL directory by \'\-l directory,q\' or \'\-l directory
   
 .I background  .I background
 \- [SCSI only] the background scan results log outputs information derived  \- [SCSI only] the background scan results log outputs information derived
from Background Media Scans (BMS) done after power up and/or periodocallyfrom Background Media Scans (BMS) done after power up and/or periodically
 (e.g. every 24 hours) on recent SCSI disks. If supported, the BMS status  (e.g. every 24 hours) on recent SCSI disks. If supported, the BMS status
 is output first, indicating whether a background scan is currently  is output first, indicating whether a background scan is currently
 underway (and if so a progress percentage), the amount of time the disk  underway (and if so a progress percentage), the amount of time the disk
Line 1066  has been powered up and the number of scans already co Line 1244  has been powered up and the number of scans already co
 is a header and a line for each background scan "event". These will  is a header and a line for each background scan "event". These will
 typically be either recovered or unrecoverable errors. That latter group  typically be either recovered or unrecoverable errors. That latter group
 may need some attention. There is a description of the background scan  may need some attention. There is a description of the background scan
mechansim in section 4.18 of SBC\-3 revision 6 (see www.t10.org ).mechanism in section 4.18 of SBC-3 revision 6 (see www.t10.org ).
   
 .I scttemp, scttempsts, scttemphist  .I scttemp, scttempsts, scttemphist
 \- [ATA only] prints the disk temperature information provided by the  \- [ATA only] prints the disk temperature information provided by the
Line 1078  the SCT Data Table command, and \'scttemp\' prints bot Line 1256  the SCT Data Table command, and \'scttemp\' prints bot
 The temperature values are preserved across power cycles.  The temperature values are preserved across power cycles.
 The logging interval can be configured with the  The logging interval can be configured with the
 \'\-l scttempint,N[,p]\' option, see below.  \'\-l scttempint,N[,p]\' option, see below.
The SCT commands were introduced in ATA\-8 ACS and were alsoThe SCT commands were introduced in ATA8-ACS and were also
supported by in many ATA\-7 disks.supported by many ATA-7 disks.
   
 .I scttempint,N[,p]  .I scttempint,N[,p]
 \- [ATA only] clears the SCT temperature history table and sets the  \- [ATA only] clears the SCT temperature history table and sets the
Line 1099  than 65 are probably not supported. For RAID configura Line 1277  than 65 are probably not supported. For RAID configura
 typically set to 70,70 deciseconds.  typically set to 70,70 deciseconds.
   
 .I devstat[,PAGE]  .I devstat[,PAGE]
\- [ATA only] [NEW EXPERIMENTAL SMARTCTL FEATURE] prints values\- [ATA only] prints values and descriptions of the ATA Device Statistics
and descriptions of the ATA Device Statistics log pageslog pages (General Purpose Log address 0x04).  If no PAGE number is specified,
(General Purpose Log address 0x04).  If no PAGE number is specified, 
 entries from all supported pages are printed.  If PAGE 0 is specified,  entries from all supported pages are printed.  If PAGE 0 is specified,
 the list of supported pages is printed.  Device Statistics was  the list of supported pages is printed.  Device Statistics was
introduced in ATA\-8 ACS and is only supported by some recent devicesintroduced in ACS-2 and is only supported by some recent devices
(e.g. Intel 320 and 710 Series SSDs).(e.g. Hitachi 7K3000, Intel 320, 330, 520 and 710 Series SSDs, Crucial/Micron
 m4 SSDs).
   
 .I sataphy[,reset]  .I sataphy[,reset]
 \- [SATA only] prints values and descriptions of the SATA Phy Event  \- [SATA only] prints values and descriptions of the SATA Phy Event
 Counters (General Purpose Log address 0x11).  If \'\-l sataphy,reset\'  Counters (General Purpose Log address 0x11).  If \'\-l sataphy,reset\'
 is specified, all counters are reset after reading the values.  is specified, all counters are reset after reading the values.
   This also works for SATA devices with Packet interface like CD/DVD
   drives.
   
 .I sasphy[,reset]  .I sasphy[,reset]
 \- [SAS (SCSI) only] prints values and descriptions of the SAS (SSP)  \- [SAS (SCSI) only] prints values and descriptions of the SAS (SSP)
Line 1156  indicates the device is at the end of its lifetime as  Line 1336  indicates the device is at the end of its lifetime as 
 manufacturer. The value may reach 255.  manufacturer. The value may reach 255.
 .TP  .TP
 .B \-v ID,FORMAT[:BYTEORDER][,NAME], \-\-vendorattribute=ID,FORMAT[:BYTEORDER][,NAME]  .B \-v ID,FORMAT[:BYTEORDER][,NAME], \-\-vendorattribute=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.  BYTEORDER and an optional NAME for Attribute ID.
 This option may be used multiple times.  This option may be used multiple times.
   
Line 1165  ID, the settings for all Attributes are changed. Line 1345  ID, the settings for all Attributes are changed.
   
 The optional BYTEORDER consists of 1 to 8 characters from the  The optional BYTEORDER consists of 1 to 8 characters from the
 set \'012345rvwz\'. The characters \'0\' to \'5\' select the byte 0  set \'012345rvwz\'. The characters \'0\' to \'5\' select the byte 0
to 5 from the 48\-bit raw value, \'r\' selects the reserved byte ofto 5 from the 48-bit raw value, \'r\' selects the reserved byte of
 the attribute data block, \'v\' selects the normalized value, \'w\'  the attribute data block, \'v\' selects the normalized value, \'w\'
 selects the worst value and \'z\' inserts a zero byte.  selects the worst value and \'z\' inserts a zero byte.
The default BYTEORDER is \'543210\' for all 48\-bit formats, \'r543210\'The default BYTEORDER is \'543210\' for all 48-bit formats, \'r543210\'
for the 54\-bit formats, and \'543210wv\' for the 64\-bit formats.for the 54-bit formats, and \'543210wv\' for the 64-bit formats.
 For example, \'\-v 5,raw48:012345\' prints the raw value of  For example, \'\-v 5,raw48:012345\' prints the raw value of
 attribute 5 with big endian instead of little endian  attribute 5 with big endian instead of little endian
 byte ordering.  byte ordering.
Line 1185  then exits. Line 1365  then exits.
 Valid arguments for FORMAT are:  Valid arguments for FORMAT are:
   
 .I raw8  .I raw8
\- Print the Raw value as six 8\-bit unsigned base\-10 integers.\- Print the Raw value as six 8-bit unsigned base-10 integers.
 This may be useful for decoding the meaning of the Raw value.  This may be useful for decoding the meaning of the Raw value.
   
 .I raw16  .I raw16
\- Print the Raw value as three 16\-bit unsigned base\-10 integers.\- Print the Raw value as three 16-bit unsigned base-10 integers.
 This may be useful for decoding the meaning of the Raw value.  This may be useful for decoding the meaning of the Raw value.
   
 .I raw48  .I raw48
\- Print the Raw value as a 48\-bit unsigned base\-10 integer.\- Print the Raw value as a 48-bit unsigned base-10 integer.
 This is the default for most attributes.  This is the default for most attributes.
   
 .I hex48  .I hex48
 \- Print the Raw value as a 12 digit hexadecimal number.  \- Print the Raw value as a 12 digit hexadecimal number.
 This may be useful for decoding the meaning of the Raw value.  This may be useful for decoding the meaning of the Raw value.
   
   .I raw56
   \- Print the Raw value as a 54-bit unsigned base-10 integer.
   This includes the reserved byte which follows the 48-bit raw value.
   
   .I hex56
   \- Print the Raw value as a 14 digit hexadecimal number.
   This includes the reserved byte which follows the 48-bit raw value.
   
 .I raw64  .I raw64
\- Print the Raw value as a 64\-bit unsigned base\-10 integer.\- Print the Raw value as a 64-bit unsigned base-10 integer.
 This includes two bytes from the normalized and worst attribute value.  This includes two bytes from the normalized and worst attribute value.
This new raw format is used by some recent SSD devices.This raw format is used by some SSD devices with Indilinx controller.
   
 .I hex64  .I hex64
 \- Print the Raw value as a 16 digit hexadecimal number.  \- Print the Raw value as a 16 digit hexadecimal number.
 This includes two bytes from the normalized and worst attribute value.  This includes two bytes from the normalized and worst attribute value.
This new raw format is used by some recent SSD devices.This raw format is used by some SSD devices with Indilinx controller.
   
 .I min2hour  .I min2hour
\- Raw Attribute is power\-on time in minutes.  Its raw value\- Raw Attribute is power-on time in minutes.  Its raw value
 will be displayed in the form "Xh+Ym".  Here X is hours, and Y is  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  minutes in the range 0\-59 inclusive.  Y is always printed with two
 digits, for example "06" or "31" or "00".  digits, for example "06" or "31" or "00".
   
 .I sec2hour  .I sec2hour
\- Raw Attribute is power\-on time in seconds.  Its raw value\- Raw Attribute is power-on time in seconds.  Its raw value
 will be displayed in the form "Xh+Ym+Zs".  Here X is hours, Y is  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  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  0\-59 inclusive.  Y and Z are always printed with two digits, for
 example "06" or "31" or "00".  example "06" or "31" or "00".
   
 .I halfmin2hour  .I halfmin2hour
\- Raw Attribute is power\-on time, measured in units of 30\- Raw Attribute is power-on time, measured in units of 30
 seconds.  This format is used by some Samsung disks.  Its raw value  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  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  minutes in the range 0\-59 inclusive.  Y is always printed with two
 digits, for example "06" or "31" or "00".  digits, for example "06" or "31" or "00".
   
 .I msec24hour32  .I msec24hour32
\- Raw Attribute is power\-on time measured in 32\-bit hours and 24\-bit\- Raw Attribute is power-on time measured in 32-bit hours and 24-bit
 milliseconds since last hour update.  It will be displayed in the form  milliseconds since last hour update.  It will be displayed in the form
 "Xh+Ym+Z.Ms".  Here X is hours, Y is minutes, Z is seconds and M is  "Xh+Ym+Z.Ms".  Here X is hours, Y is minutes, Z is seconds and M is
 milliseconds.  milliseconds.
Line 1247  specific. Line 1435  specific.
 \- Raw Attribute is ten times the disk temperature in Celsius.  \- Raw Attribute is ten times the disk temperature in Celsius.
   
 .I raw16(raw16)  .I raw16(raw16)
\- Print the raw attribute as a 16\-bit value and two optional\- Print the raw attribute as a 16-bit value and two optional
16\-bit values if these words are nonzero.  This is the default16-bit values if these words are nonzero.  This is the default
 for Attributes 5 and 196.  for Attributes 5 and 196.
   
 .I raw16(avg16)  .I raw16(avg16)
Line 1256  for Attributes 5 and 196. Line 1444  for Attributes 5 and 196.
 and an optional "Average" 16-bit value if the word is nonzero.  and an optional "Average" 16-bit value if the word is nonzero.
 This is the default for Attribute 3.  This is the default for Attribute 3.
   
   .I raw24(raw8)
   \- Print the raw attribute as a 24-bit value and three optional
   8-bit values if these bytes are nonzero.  This is the default
   for Attribute 9.
   
 .I raw24/raw24  .I raw24/raw24
\- Raw Attribute contains two 24\-bit values. The first is the\- Raw Attribute contains two 24-bit values. The first is the
 number of load cycles.  The second is the number of unload cycles.  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 difference between these two values is the number of times that
 the drive was unexpectedly powered off (also called an emergency  the drive was unexpectedly powered off (also called an emergency
Line 1266  emergency unload is equivalent to that created by one  Line 1459  emergency unload is equivalent to that created by one 
 unloads.  unloads.
   
 .I raw24/raw32  .I raw24/raw32
\- Raw attribute is an error rate which consists of a 24\-bit error\- Raw attribute is an error rate which consists of a 24-bit error
count and a 32\-bit total count.count and a 32-bit total count.
   
 The following old arguments to \'\-v\' are also still valid:  The following old arguments to \'\-v\' are also still valid:
   
Line 1331  is not reset if uncorrectable sectors are reallocated Line 1524  is not reset if uncorrectable sectors are reallocated
   
 .I 220,temp  .I 220,temp
 \- same as:  \- same as:
.I 220,raw48,Temperature_Celsius..I 220,tempminmax,Temperature_Celsius.
   
 Note: a table of hard drive models, listing which Attribute  Note: a table of hard drive models, listing which Attribute
 corresponds to temperature, can be found at:  corresponds to temperature, can be found at:
Line 1339  corresponds to temperature, can be found at: Line 1532  corresponds to temperature, can be found at:
 .TP  .TP
 .B \-F TYPE, \-\-firmwarebug=TYPE  .B \-F TYPE, \-\-firmwarebug=TYPE
 [ATA only] Modifies the behavior of \fBsmartctl\fP to compensate for some  [ATA only] Modifies the behavior of \fBsmartctl\fP to compensate for some
known and understood device firmware or driver bug.  Except \'swapid\',known and understood device firmware or driver bug.  This option may be used
the arguments to this option are exclusive, so that only the finalmultiple times.  The valid arguments are:
option given is used.  The valid values are: 
   
 .I none  .I none
 \- Assume that the device firmware obeys the ATA specifications.  This  \- Assume that the device firmware obeys the ATA specifications.  This
 is the default, unless the device has presets for \'\-F\' in the  is the default, unless the device has presets for \'\-F\' in the
device database (see note below).drive database.  Using this option on the command line 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  .I samsung
 \- In some Samsung disks (example: model SV4012H Firmware Version:  \- In some Samsung disks (example: model SV4012H Firmware Version:
RM100\-08) some of the two\- and four\-byte quantities in the SMART dataRM100-08) some of the two- and four-byte quantities in the SMART data
structures are byte\-swapped (relative to the ATA specification).structures are byte-swapped (relative to the ATA specification).
 Enabling this option tells \fBsmartctl\fP to evaluate these quantities  Enabling this option tells \fBsmartctl\fP to evaluate these quantities
in byte\-reversed order.  Some signs that your disk needs this optionin 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;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;  (2) very large numbers of ATA errors reported in the ATA error log;
 (3) strange and impossible values for the ATA error log timestamps.  (3) strange and impossible values for the ATA error log timestamps.
   
 .I samsung2  .I samsung2
 \- In some Samsung disks the number of ATA errors reported is byte swapped.  \- In some Samsung disks the number of ATA errors reported is byte swapped.
 Enabling this option tells \fBsmartctl\fP to evaluate this quantity in  Enabling this option tells \fBsmartctl\fP to evaluate this quantity in
byte\-reversed order. An indication that your Samsung disk needs thisbyte-reversed order. An indication that your Samsung disk needs this
option is that the self\-test log is printed correctly, but there are aoption is that the self-test log is printed correctly, but there are a
 very large number of errors in the SMART error log.  This is because  very large number of errors in the SMART error log.  This is because
 the error count is byte swapped.  Thus a disk with five errors  the error count is byte swapped.  Thus a disk with five errors
 (0x0005) will appear to have 20480 errors (0x5000).  (0x0005) will appear to have 20480 errors (0x5000).
   
 .I samsung3  .I samsung3
\- Some Samsung disks (at least SP2514N with Firmware VF100\-37) report\- Some Samsung disks (at least SP2514N with Firmware VF100-37) report
a self\-test still in progress with 0% remaining when the test was alreadya self-test still in progress with 0% remaining when the test was already
completed. Enabling this option modifies the output of the self\-testcompleted. Enabling this option modifies the output of the self-test
 execution status (see options \'\-c\' or \'\-a\' above) accordingly.  execution status (see options \'\-c\' or \'\-a\' above) accordingly.
   
Note that an explicit \'\-F\' option on the command line will.I xerrorlba
over\-ride any preset values for \'\-F\' (see the \'\-P\' option\- Fixes LBA byte ordering in Extended Comprehensive SMART error log.
below).Some disk use little endian byte ordering instead of ATA register
 ordering to specifiy the LBA addresses in the log entries.
   
 .I swapid  .I swapid
 \- Fixes byte swapped ATA identify strings (device name, serial number,  \- Fixes byte swapped ATA identify strings (device name, serial number,
Line 1388  in the \fBsmartmontools\fP database, then the presets  Line 1587  in the \fBsmartmontools\fP database, then the presets 
   
 \fBsmartctl\fP can automatically set appropriate options for known  \fBsmartctl\fP can automatically set appropriate options for known
 drives.  For example, the Maxtor 4D080H4 uses Attribute 9 to stores  drives.  For example, the Maxtor 4D080H4 uses Attribute 9 to stores
power\-on time in minutes whereas most drives use that Attribute topower-on time in minutes whereas most drives use that Attribute to
store the power\-on time in hours.  The command\-line option \'\-vstore the power-on time in hours.  The command-line option \'\-v
 9,minutes\' ensures that \fBsmartctl\fP correctly interprets Attribute  9,minutes\' ensures that \fBsmartctl\fP correctly interprets Attribute
 9 in this case, but that option is preset for the Maxtor 4D080H4 and  9 in this case, but that option is preset for the Maxtor 4D080H4 and
 so need not be specified by the user on the \fBsmartctl\fP command  so need not be specified by the user on the \fBsmartctl\fP command
Line 1411  The valid arguments to this option are: Line 1610  The valid arguments to this option are:
   
 .I use  .I use
 \- if a drive is recognized, then use the stored presets for it.  This  \- if a drive is recognized, then use the stored presets for it.  This
is the default. Note that presets will NOT over\-ride additionalis the default. Note that presets will NOT override additional
Attribute interpretation (\'\-v N,something\') command\-line options orAttribute interpretation (\'\-v N,something\') command-line options or
explicit \'\-F\' command\-line options..explicit \'\-F\' command-line options..
   
 .I ignore  .I ignore
 \- do not use presets.  \- do not use presets.
Line 1518  Example: Line 1717  Example:
 .fi  .fi
   
 .TP  .TP
.B SMART RUN/ABORT OFFLINE TEST AND SELF\-TEST OPTIONS:.B SMART RUN/ABORT OFFLINE TEST AND self-test OPTIONS:
 .TP  .TP
 .B \-t TEST, \-\-test=TEST  .B \-t TEST, \-\-test=TEST
 Executes TEST immediately.  The \'\-C\' option can be used in  Executes TEST immediately.  The \'\-C\' option can be used in
 conjunction with this option to run the short or long (and also for  conjunction with this option to run the short or long (and also for
ATA devices, selective or conveyance) self\-tests in captive modeATA devices, selective or conveyance) self-tests in captive mode
 (known as "foreground mode" for SCSI devices).  Note that only one  (known as "foreground mode" for SCSI devices).  Note that only one
 test type can be run at a time, so only one test type should be  test type can be run at a time, so only one test type should be
 specified per command line.  Note also that if a computer is shutdown  specified per command line.  Note also that if a computer is shutdown
or power cycled during a self\-test, no harm should result.  Theor power cycled during a self-test, no harm should result.  The
self\-test will either be aborted or will resume automatically.self-test will either be aborted or will resume automatically.
   
The valid arguments to this option are:  All \'\-t TEST\' commands can be given during normal system operation
 unless captive mode (\'\-C\' option) is used.
 A running self-test can, however, degrade performance of the drive.
 Frequent I/O requests from the operating system increase the duration
 of a test.  These impacts may vary from device to device.
   
   If a test failure occurs then the device may discontinue the testing
   and report the result immediately.
   
   The valid arguments to this option are:
   
 .I offline  .I offline
 \- [ATA] runs SMART Immediate Offline Test.  This immediately  \- [ATA] runs SMART Immediate Offline Test.  This immediately
 starts the test described above.  This command can be given during  starts the test described above.  This command can be given during
Line 1562  tests.  The "Self" tests check the electrical and mech Line 1770  tests.  The "Self" tests check the electrical and mech
 performance as well as the read performance of the disk.  Their  performance as well as the read performance of the disk.  Their
 results are reported in the Self Test Error Log, readable with  results are reported in the Self Test Error Log, readable with
 the \'\-l selftest\' option.  Note that on some disks the progress of the  the \'\-l selftest\' option.  Note that on some disks the progress of the
self\-test can be monitored by watching this log during the self\-test; with other disksself-test can be monitored by watching this log during the self-test; with other disks
 use the \'\-c\' option to monitor progress.  use the \'\-c\' option to monitor progress.
   
 .I short  .I short
\- [SCSI] runs the "Background short" self\-test.\- [SCSI] runs the "Background short" self-test.
   
 .I long  .I long
 \- [ATA] runs SMART Extended Self Test (tens of minutes). This is a  \- [ATA] runs SMART Extended Self Test (tens of minutes). This is a
Line 1575  above.  Note that this command can be given during nor Line 1783  above.  Note that this command can be given during nor
 system operation (unless run in captive mode \- see the \'\-C\' option below).  system operation (unless run in captive mode \- see the \'\-C\' option below).
   
 .I long  .I long
\- [SCSI] runs the "Background long" self\-test.\- [SCSI] runs the "Background long" self-test.
   
 .I conveyance  .I conveyance
 \- [ATA only] runs a SMART Conveyance Self Test (minutes).  This  \- [ATA only] runs a SMART Conveyance Self Test (minutes).  This
self\-test routine is intended to identify damage incurred duringself-test routine is intended to identify damage incurred during
transporting of the device. This self\-test routine should take on thetransporting of the device. This self-test routine should take on the
 order of minutes to complete.  Note that this command can be given  order of minutes to complete.  Note that this command can be given
 during normal system operation (unless run in captive mode \- see the  during normal system operation (unless run in captive mode \- see the
 \'\-C\' option below).  \'\-C\' option below).
Line 1615  overlap partially or completely, for example: Line 1823  overlap partially or completely, for example:
 .nf  .nf
   smartctl \-t select,0\-10 \-t select,5\-15 \-t select,10\-20 /dev/hda    smartctl \-t select,0\-10 \-t select,5\-15 \-t select,10\-20 /dev/hda
 .fi  .fi
The results of the selective self\-test can be obtained (both duringThe results of the selective self-test can be obtained (both during
and after the test) by printing the SMART self\-test log, using theand after the test) by printing the SMART self-test log, using the
 \'\-l selftest\' option to smartctl.  \'\-l selftest\' option to smartctl.
   
 Selective self tests are particularly useful as disk capacities  Selective self tests are particularly useful as disk capacities
 increase: an extended self test (smartctl \-t long) can take several  increase: an extended self test (smartctl \-t long) can take several
hours.  Selective self\-tests are helpful if (based on SYSLOG errorhours.  Selective self-tests are helpful if (based on SYSLOG error
messages, previous failed self\-tests, or SMART error log entries) youmessages, previous failed self-tests, or SMART error log entries) you
 suspect that a disk is having problems at a particular range of  suspect that a disk is having problems at a particular range of
 Logical Block Addresses (LBAs).  Logical Block Addresses (LBAs).
   
Selective self\-tests can be run during normal system operation (unlessSelective self-tests can be run during normal system operation (unless
 done in captive mode \- see the \'\-C\' option below).  done in captive mode \- see the \'\-C\' option below).
   
The following variants of the selective self\-test command use spans basedThe following variants of the selective self-test command use spans based
 on the ranges from past tests already stored on the disk:  on the ranges from past tests already stored on the disk:
   
 .I select,redo[+SIZE]  .I select,redo[+SIZE]
Line 1681  that the last test was aborted by the host. Otherwise  Line 1889  that the last test was aborted by the host. Otherwise 
 (above) test.  (above) test.
   
 .I afterselect,on  .I afterselect,on
\- [ATA only] perform an offline read scan after a Selective Self\-test\- [ATA only] perform an offline read scan after a Selective self-test
 has completed. This option must be used together with one or more of  has completed. This option must be used together with one or more of
 the \fIselect,N\-M\fP options above. If the LBAs that have been  the \fIselect,N\-M\fP options above. If the LBAs that have been
specified in the Selective self\-test pass the test with no errorsspecified in the Selective self-test pass the test with no errors
 found, then read scan the \fBremainder\fP of the disk.  If the device  found, then read scan the \fBremainder\fP of the disk.  If the device
is powered\-cycled while this read scan is in progress, the read scanis powered-cycled while this read scan is in progress, the read scan
 will be automatically resumed after a time specified by the pending  will be automatically resumed after a time specified by the pending
 timer (see below).  The value of this option is preserved between  timer (see below).  The value of this option is preserved between
selective self\-tests.selective self-tests.
   
 .I afterselect,off  .I afterselect,off
 \- [ATA only] do not read scan the remainder of the disk after a  \- [ATA only] do not read scan the remainder of the disk after a
Selective self\-test has completed.  This option must be use togetherSelective self-test has completed.  This option must be use together
 with one or more of the \fIselect,N\-M\fP options above.  The value of this  with one or more of the \fIselect,N\-M\fP options above.  The value of this
option is preserved between selective self\-tests.option is preserved between selective self-tests.
   
 .I pending,N   .I pending,N 
 \- [ATA only] set the pending offline read scan timer to N minutes.  \- [ATA only] set the pending offline read scan timer to N minutes.
 Here N is an integer in the range from 0 to 65535 inclusive.  If the  Here N is an integer in the range from 0 to 65535 inclusive.  If the
device is powered off during a read scan after a Selective self\-test,device is powered off during a read scan after a Selective self-test,
then resume the test automatically N minutes after power\-up.  Thisthen resume the test automatically N minutes after power-up.  This
 option must be use together with one or more of the \fIselect,N\-M\fP  option must be use together with one or more of the \fIselect,N\-M\fP
 options above. The value of this option is preserved between selective  options above. The value of this option is preserved between selective
self\-tests.self-tests.
   
 .I vendor,N  .I vendor,N
 \- [ATA only] issues the ATA command SMART EXECUTE OFF-LINE IMMEDIATE  \- [ATA only] issues the ATA command SMART EXECUTE OFF-LINE IMMEDIATE
Line 1718  T13/1699-D Revision 6a (ATA8-ACS).  Note that the subc Line 1926  T13/1699-D Revision 6a (ATA8-ACS).  Note that the subc
 \fBWARNING: Only run subcommands documented by the vendor of the  \fBWARNING: Only run subcommands documented by the vendor of the
 device.\fP  device.\fP
   
Example for Intel (X18\-M/X25\-M G2 and 320 Series) SSDs only:Example for Intel (X18/X25-M G2, 320, 520 and 710 Series) SSDs only:
 The subcommand 0x40 (\'\-t vendor,0x40\') clears the timed workload  The subcommand 0x40 (\'\-t vendor,0x40\') clears the timed workload
 related SMART attributes (226, 227, 228).  Note that the raw values of  related SMART attributes (226, 227, 228).  Note that the raw values of
 these attributes are held at 65535 (0xffff) until the workload timer  these attributes are held at 65535 (0xffff) until the workload timer
 reaches 60 minutes.  reaches 60 minutes.
   
.I scttempint,N[,p].I force
\- is no longer supported, use \'\-l scttempint,N[,p]\' instead, see above.\- start new self-test even if another test is already running.
 By default a running self-test will not be interrupted to begin another
 test.
 .TP  .TP
 .B \-C, \-\-captive  .B \-C, \-\-captive
[ATA] Runs self\-tests in captive mode.  This has no effect with \'\-t[ATA] Runs self-tests in captive mode.  This has no effect with \'\-t
 offline\' or if the \'\-t\' option is not used.  offline\' or if the \'\-t\' option is not used.
   
 \fBWARNING: Tests run in captive mode may busy out the drive for the  \fBWARNING: Tests run in captive mode may busy out the drive for the
 length of the test.  Only run captive tests on drives without any  length of the test.  Only run captive tests on drives without any
 mounted partitions!\fP  mounted partitions!\fP
   
[SCSI] Runs the self\-test in "Foreground" mode.[SCSI] Runs the self-test in "Foreground" mode.
 .TP  .TP
 .B \-X, \-\-abort  .B \-X, \-\-abort
Aborts non\-captive SMART Self Tests.  Note that thisAborts non-captive SMART Self Tests.  Note that this
 command will abort the Offline Immediate Test routine only if your  command will abort the Offline Immediate Test routine only if your
 disk has the "Abort Offline collection upon new command" capability.  disk has the "Abort Offline collection upon new command" capability.
 .PP  .PP
Line 1809  Disable SMART monitoring and data log collection on dr Line 2019  Disable SMART monitoring and data log collection on dr
 .fi  .fi
 Enable SMART on drive /dev/hda, enable automatic offline  Enable SMART on drive /dev/hda, enable automatic offline
 testing every four hours, and enable autosaving of  testing every four hours, and enable autosaving of
SMART Attributes.  This is a good start\-up line for your system\'sSMART Attributes.  This is a good start-up line for your system\'s
 init files.  You can issue this command on a running system.  init files.  You can issue this command on a running system.
 .PP  .PP
 .nf  .nf
 .B smartctl \-t long /dev/hdc  .B smartctl \-t long /dev/hdc
 .fi  .fi
Begin an extended self\-test of drive /dev/hdc.  You can issue thisBegin an extended self-test of drive /dev/hdc.  You can issue this
command on a running system.  The results can be seen in the self\-testcommand on a running system.  The results can be seen in the self-test
 log visible with the \'\-l selftest\' option after it has completed.  log visible with the \'\-l selftest\' option after it has completed.
 .PP  .PP
 .nf  .nf
Line 1831  the SMART error log, which can be seen with the \'\-l  Line 2041  the SMART error log, which can be seen with the \'\-l 
 .nf  .nf
 .B smartctl \-A \-v 9,minutes /dev/hda  .B smartctl \-A \-v 9,minutes /dev/hda
 .fi  .fi
Shows the vendor Attributes, when the disk stores its power\-on timeShows the vendor Attributes, when the disk stores its power-on time
 internally in minutes rather than hours.  internally in minutes rather than hours.
 .PP  .PP
 .nf  .nf
 .B smartctl \-q errorsonly \-H \-l selftest /dev/hda  .B smartctl \-q errorsonly \-H \-l selftest /dev/hda
 .fi  .fi
 Produces output only if the device returns failing SMART status,  Produces output only if the device returns failing SMART status,
or if some of the logged self\-tests ended with errors.or if some of the logged self-tests ended with errors.
 .PP  .PP
 .nf  .nf
 .B smartctl \-q silent \-a /dev/hda  .B smartctl \-q silent \-a /dev/hda
Line 1848  printed output.  You must use the exit status (the Line 2058  printed output.  You must use the exit status (the
 .B $?  .B $?
 shell variable) to learn if any Attributes are out of bound, if the  shell variable) to learn if any Attributes are out of bound, if the
 SMART status is failing, if there are errors recorded in the  SMART status is failing, if there are errors recorded in the
self\-test log, or if there are errors recorded in the disk error log.self-test log, or if there are errors recorded in the disk error log.
 .PP  .PP
 .nf  .nf
 .B smartctl \-a \-d 3ware,0 /dev/sda  .B smartctl \-a \-d 3ware,0 /dev/sda
Line 1877  Examine all SMART data for the first SATA (not SAS) di Line 2087  Examine all SMART data for the first SATA (not SAS) di
 .nf  .nf
 .B smartctl \-t short \-d 3ware,3 /dev/sdb  .B smartctl \-t short \-d 3ware,3 /dev/sdb
 .fi  .fi
Start a short self\-test on the fourth ATA disk connected to the 3ware RAIDStart a short self-test on the fourth ATA disk connected to the 3ware RAID
 controller card which is the second SCSI device /dev/sdb.  controller card which is the second SCSI device /dev/sdb.
 .PP  .PP
 .nf  .nf
 .B smartctl \-t long \-d areca,4 /dev/sg2  .B smartctl \-t long \-d areca,4 /dev/sg2
 .fi  .fi
Start a long self\-test on the fourth SATA disk connected to an Areca RAIDStart a long self-test on the fourth SATA disk connected to an Areca RAID
 controller addressed by /dev/sg2.  controller addressed by /dev/sg2.
 .PP  .PP
 .nf  .nf
Line 1898  first HighPoint RocketRAID controller card. Line 2108  first HighPoint RocketRAID controller card.
 .B smartctl \-t short \-d hpt,1/1/2 /dev/sda    (under Linux)  .B smartctl \-t short \-d hpt,1/1/2 /dev/sda    (under Linux)
 .B smartctl \-t short \-d hpt,1/1/2 /dev/hptrr    (under FreeBSD)  .B smartctl \-t short \-d hpt,1/1/2 /dev/hptrr    (under FreeBSD)
 .fi  .fi
Start a short self\-test on the (S)ATA disk connected to second pmport on theStart a short self-test on the (S)ATA disk connected to second pmport on the
 first channel of the first HighPoint RocketRAID controller card.  first channel of the first HighPoint RocketRAID controller card.
 .PP  .PP
 .nf  .nf
 .B smartctl \-t select,10\-100 \-t select,30\-300 \-t afterselect,on \-t pending,45 /dev/hda  .B smartctl \-t select,10\-100 \-t select,30\-300 \-t afterselect,on \-t pending,45 /dev/hda
 .fi  .fi
Run a selective self\-test on LBAs 10 to 100 and 30 to 300.  After theRun a selective self-test on LBAs 10 to 100 and 30 to 300.  After the
these LBAs have been tested, read\-scan the remainder of the disk.  If the disk isthese LBAs have been tested, read-scan the remainder of the disk.  If the disk is
power\-cycled during the read\-scan, resume the scan 45 minutes after power to thepower-cycled during the read-scan, resume the scan 45 minutes after power to the
 device is restored.  device is restored.
 .PP  .PP
 .nf  .nf
Line 1919  RAID controller card. Line 2129  RAID controller card.
 The return values of \fBsmartctl\fP are defined by a bitmask.  If all  The return values of \fBsmartctl\fP are defined by a bitmask.  If all
 is well with the disk, the return value (exit status) of  is well with the disk, the return value (exit status) of
 \fBsmartctl\fP is 0 (all bits turned off).  If a problem occurs, or an  \fBsmartctl\fP is 0 (all bits turned off).  If a problem occurs, or an
error, potential error, or fault is detected, then a non\-zero statuserror, potential error, or fault is detected, then a non-zero status
 is returned.  In this case, the eight different bits in the return  is returned.  In this case, the eight different bits in the return
 value have the following meanings for ATA disks; some of these values  value have the following meanings for ATA disks; some of these values
 may also be returned for SCSI disks.  may also be returned for SCSI disks.
Line 1932  Device open failed, device did not return an IDENTIFY  Line 2142  Device open failed, device did not return an IDENTIFY 
 or device is in a low-power mode (see \'\-n\' option above).  or device is in a low-power mode (see \'\-n\' option above).
 .TP  .TP
 .B Bit 2:  .B Bit 2:
Some SMART command to the disk failed, or there was a checksum errorSome SMART or other ATA command to the disk failed, or there was a checksum
in a SMART data structure (see \'\-b\' option above).error in a SMART data structure (see \'\-b\' option above).
 .TP  .TP
 .B Bit 3:  .B Bit 3:
 SMART status check returned "DISK FAILING".  SMART status check returned "DISK FAILING".
Line 1950  past.  Line 2160  past. 
 The device error log contains records of errors.  The device error log contains records of errors.
 .TP  .TP
 .B Bit 7:  .B Bit 7:
The device self\-test log contains records of errors.The device self-test log contains records of errors.
 [ATA only] Failed self-tests outdated by a newer successful extended  [ATA only] Failed self-tests outdated by a newer successful extended
self\-test are ignored.self-test are ignored.
 .PP  .PP
 To test within the shell for whether or not the different bits are  To test within the shell for whether or not the different bits are
 turned on or off, you can use the following type of construction (this  turned on or off, you can use the following type of construction (this
Line 1982  once by \fBsmartctl\fP for each initiator for each act Line 2192  once by \fBsmartctl\fP for each initiator for each act
 condition.  condition.
   
 .PP  .PP
.SH AUTHOR.SH AUTHORS
\fBBruce Allen\fP smartmontools\-support@lists.sourceforge.net\fBBruce Allen\fP
.fi.br
 University of Wisconsin \- Milwaukee Physics Department  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  .PP
 .SH CONTRIBUTORS  .SH CONTRIBUTORS
 The following have made large contributions to smartmontools:  The following have made large contributions to smartmontools:
 .nf  .nf
 \fBCasper Dik\fP (Solaris SCSI interface)  \fBCasper Dik\fP (Solaris SCSI interface)
 \fBChristian Franke\fP (Windows interface, C++ redesign, USB support, ...)  
 \fBDouglas Gilbert\fP (SCSI subsystem)  \fBDouglas Gilbert\fP (SCSI subsystem)
 \fBGuido Guenther\fP (Autoconf/Automake packaging)  \fBGuido Guenther\fP (Autoconf/Automake packaging)
 \fBGeoffrey Keating\fP (Darwin ATA interface)  \fBGeoffrey Keating\fP (Darwin ATA interface)
Line 2014  Many other individuals have made smaller contributions Line 2228  Many other individuals have made smaller contributions
 .fi  .fi
 This code was derived from the smartsuite package, written by Michael  This code was derived from the smartsuite package, written by Michael
 Cornwell, and from the previous UCSC smartsuite package.  It extends  Cornwell, and from the previous UCSC smartsuite package.  It extends
these to cover ATA\-5 disks.  This code was originally developed as athese to cover ATA-5 disks.  This code was originally developed as a
 Senior Thesis by Michael Cornwell at the Concurrent Systems Laboratory  Senior Thesis by Michael Cornwell at the Concurrent Systems Laboratory
 (now part of the Storage Systems Research Center), Jack Baskin School  (now part of the Storage Systems Research Center), Jack Baskin School
 of Engineering, University of California, Santa  of Engineering, University of California, Santa
Line 2033  REFERENCES FOR SMART Line 2247  REFERENCES FOR SMART
 .fi  .fi
 An introductory article about smartmontools is \fIMonitoring Hard  An introductory article about smartmontools is \fIMonitoring Hard
 Disks with SMART\fP, by Bruce Allen, Linux Journal, January 2004,  Disks with SMART\fP, by Bruce Allen, Linux Journal, January 2004,
pages 74\-77. This is \fBhttp://www.linuxjournal.com/article/6983\fPpages 74-77. This is \fBhttp://www.linuxjournal.com/article/6983\fP
 online.  online.
   
 If you would like to understand better how SMART works, and what it  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  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)volume of the \'AT Attachment with Packet Interface-7\' (ATA/ATAPI-7)
 specification Revision 4b.  This documents the SMART functionality which the  specification Revision 4b.  This documents the SMART functionality which the
 \fBsmartmontools\fP utilities provide access to.  \fBsmartmontools\fP utilities provide access to.
   
 .fi  .fi
The functioning of SMART was originally defined by the SFF\-8035iThe functioning of SMART was originally defined by the SFF-8035i
revision 2 and the SFF\-8055i revision 1.4 specifications.  These arerevision 2 and the SFF-8055i revision 1.4 specifications.  These are
 publications of the Small Form Factors (SFF) Committee.  publications of the Small Form Factors (SFF) Committee.
   
 Links to these and other documents may be found on the Links page of the  Links to these and other documents may be found on the Links page of the

Removed from v.1.1  
changed lines
  Added in v.1.1.1.4


FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>