smartctl.8.in

硬盘各项性能的测试,如温度容量版本健康度型号

.B 3ware controllers are supported under Linux, FreeBSD and Windows.

To look at (S)ATA disks behind HighPoint RocketRAID controllers, use syntax
such as:
.nf
\fBsmartctl \-a \-d hpt,1/3 /dev/sda\fP
.fi
or
.nf
\fBsmartctl \-a \-d hpt,1/2/3 /dev/sda\fP
.fi
where in the argument \fIhpt,L/M\fP or \fIhpt,L/M/N\fP, the integer L is the
controller id, the integer M is the channel number, and the integer N is the
PMPort number if it is available. The allowed values of L are from 1 to 4
inclusive, M are from 1 to 8 inclusive and N from 1 to 4 if PMPort available.
Note that the /dev/sda\-z form should be the device node which stands for
the disks derived from the HighPoint RocketRAID controllers.  And also
these values are limited by the model of the HighPoint RocketRAID controller.

.B HighPoint RocketRAID controllers are currently ONLY supported under Linux.

.B cciss controllers are currently ONLY supported under Linux.

.TP
.B \-T TYPE, \-\-tolerance=TYPE
Specifies how tolerant \fBsmartctl\fP should be of ATA and SMART command
failures. 

The behavior of \fBsmartctl\fP depends upon whether the command is
"\fBoptional\fP" or "\fBmandatory\fP". Here "\fBmandatory\fP" means
"required by the ATA/ATAPI\-5 Specification if the device implements
the SMART command set" and "\fBoptional\fP" means "not required by the
ATA/ATAPI\-5 Specification even if the device implements the SMART
command set."  The "\fBmandatory\fP" ATA and SMART commands are: (1)
ATA IDENTIFY DEVICE, (2) SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE, (3)
SMART ENABLE/DISABLE, and (4) SMART RETURN STATUS.

The valid arguments to this option are:

.I normal
\- exit on failure of any \fBmandatory\fP SMART command, and ignore
all failures of \fBoptional\fP SMART commands.  This is the default.
Note that on some devices, issuing unimplemented optional SMART
commands doesn\'t cause an error.  This can result in misleading
\fBsmartctl\fP messages such as "Feature X not implemented", followed
shortly by "Feature X: enabled".  In most such cases, contrary to the
final message, Feature X is \fBnot\fP enabled.

.I conservative
\- exit on failure of any \fBoptional\fP SMART command.

.I permissive
\- ignore failure(s) of \fBmandatory\fP SMART commands.  This option
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
this option can lead to messages like "Feature X not implemented",
followed shortly by "Error: unable to enable Feature X".  In a few
such cases, contrary to the final message, Feature X \fBis\fP enabled.

.I verypermissive
\- equivalent to giving a large number of \'\-T permissive\' options:
ignore failures of \fBany number\fP of \fBmandatory\fP SMART commands.
Please see the note above.

.TP
.B \-b TYPE, \-\-badsum=TYPE
Specifies the action \fBsmartctl\fP should take if a checksum error is
detected in the: (1) Device Identity Structure, (2) SMART Self\-Test
Log Structure, (3) SMART Attribute Value Structure, (4) SMART
Attribute Threshold Structure, or (5) ATA Error Log Structure.

The valid arguments to this option are:

.I warn
\- report the incorrect checksum but carry on in spite of it.  This is the
default.

.I exit
\- exit \fBsmartctl\fP.

.I ignore
\- continue silently without issuing a warning.

.TP
.B \-r TYPE, \-\-report=TYPE
Intended primarily to help \fBsmartmontools\fP developers understand
the behavior of \fBsmartmontools\fP on non\-conforming or poorly
conforming hardware.  This option reports details of \fBsmartctl\fP
transactions with the device.  The option can be used multiple times.
When used just once, it shows a record of the ioctl() transactions
with the device.  When used more than once, the detail of these
ioctl() transactions are reported in greater detail.  The valid
arguments to this option are:

.I ioctl
\- report all ioctl() transactions.

.I ataioctl
\- report only ioctl() transactions with ATA devices.

.I scsiioctl
\- report only ioctl() transactions with SCSI devices. Invoking this once
shows the SCSI commands in hex and the corresponding status. Invoking
it a second time adds a hex listing of the first 64 bytes of data send to, 
or received from the device.

Any argument may include a positive integer to specify the level of detail
that should be reported.  The argument should be followed by a comma then
the integer with no spaces.  For example, 
.I ataioctl,2
The default
level is 1, so \'\-r ataioctl,1\' and \'\-r ataioctl\' are equivalent.

For testing purposes, the output of \'\-r ataioctl,2\' can later be parsed
by \fBsmartctl\fP itself if \'\-\' is used as device path argument.
The ATA command input parameters, sector data and return values are
reconstructed from the debug report read from stdin.
Then \fBsmartctl\fP internally simulates an ATA device with the same
behaviour. This is does not work for SCSI devices yet.

.TP
.B \-n POWERMODE, \-\-nocheck=POWERMODE
Specifieds if \fBsmartctl\fP should exit before performing any checks
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 by
default. The allowed values of POWERMODE are:

.I never
\- check the device always, but print the power mode if \'\-i\' is
specified.

.I sleep
\- check the device unless it is in SLEEP mode.

.I standby
\- check the device unless it is in SLEEP or STANDBY mode.  In
these modes most disks are not spinning, so if you want to prevent
a disk from spinning up, this is probably what you want.

.I idle
\- check the device unless it is in SLEEP, STANDBY or IDLE mode.
In the IDLE state, most disks are still spinning, so this is probably
not what you want.

.TP
.B SMART FEATURE ENABLE/DISABLE COMMANDS:
.IP
.B Note: 
if multiple options are used to both enable and disable a
feature, then 
.B both
the enable and disable commands will be issued.  The enable command
will always be issued
.B before
the corresponding disable command.
.TP
.B \-s VALUE, \-\-smart=VALUE 
Enables or disables SMART on device.  The valid arguments to
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 placed
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
power\-cycling, but it doesn\'t hurt to be sure. It is not necessary (or
useful) to enable SMART to see the TapeAlert messages.
.TP
.B \-o VALUE, \-\-offlineauto=VALUE
Enables or disables SMART automatic offline test, which scans the drive
every four hours for disk defects. This command can be given during normal
system operation.  The valid arguments to this option are \fIon\fP
and \fIoff\fP.

Note that the SMART automatic offline test command is listed as
"Obsolete" in every version of the ATA and ATA/ATAPI Specifications.
It was originally part of the SFF\-8035i Revision 2.0 specification,
but was never part of any ATA specification.  However it is
implemented and used by many vendors. [Good documentation can be found
in IBM\'s Official Published Disk Specifications.  For example the IBM
Travelstar 40GNX Hard Disk Drive Specifications (Revision 1.1, 22
April 2002, Publication # 1541, Document S07N\-7715\-02) page 164. You
can also read the SFF\-8035i Specification \-\- see REFERENCES below.]
You can tell if automatic offline testing is supported by seeing if
this command enables and disables it, as indicated by the \'Auto
Offline Data Collection\' part of the SMART capabilities report
(displayed with \'\-c\').

SMART provides \fBthree\fP basic categories of testing.  The
\fBfirst\fP category, called "online" testing, has no effect on the
performance of the device.  It is turned on by the \'\-s on\' option.

The \fBsecond\fP category of testing is called "offline" testing. This
type of test can, in principle, degrade the device performance.  The
\'\-o on\' option causes this offline testing to be carried out,
automatically, on a regular scheduled basis.  Normally, the disk will
suspend offline testing while disk accesses are taking place, and then
automatically resume it when the disk would otherwise be idle, so in
practice it has little effect.  Note that a one\-time offline test can
also be carried out immediately upon receipt of a user command.  See
the \'\-t offline\' option below, which causes a one\-time offline test
to be carried out immediately.

The choice (made by the SFF\-8035i and ATA specification authors) of
the word \fItesting\fP for these first two categories is unfortunate,
and often leads to confusion.  In fact these first two categories of
online and offline testing could have been more accurately described
as online and offline \fBdata collection\fP.

The results of this automatic or immediate offline testing (data
collection) are reflected in the values of the SMART Attributes.
Thus, if problems or errors are detected, the values of these
Attributes will go below their failure thresholds; some types of
errors may also appear in the SMART error log. These are visible with
the \'\-A\' and \'\-l error\' options respectively.

Some SMART attribute values are updated only during off\-line data
collection activities; the rest are updated during normal operation of
the device or during both normal operation and off\-line testing.  The
Attribute value table produced by the \'\-A\' option indicates this in
the UPDATED column.  Attributes of the first type are labeled
"Offline" and Attributes of the second type are labeled "Always".

The \fBthird\fP category of testing (and the \fIonly\fP category for
which the word \'testing\' is really an appropriate choice) is "self"
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
used to carry out and abort such self\-tests; please see below for
further details.

Any errors detected in the self testing will be shown in the
SMART self\-test log, which can be examined using the \'\-l selftest\'
option.

\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
"offline" testing.  The words \fB"Self\-test"\fP are used in
connection with the third category.
.TP
.B \-S VALUE, \-\-saveauto=VALUE
Enables or disables SMART autosave of device vendor\-specific
Attributes. The valid arguments to this option are \fIon\fP
and \fIoff\fP.  Note that this feature is preserved across disk power
cycles, so you should only need to issue it once.

For SCSI devices this toggles the value of the Global Logging Target
Save Disabled (GLTSD) bit in the Control Mode Page. Some disk
manufacturers set this bit by default. This prevents error counters,
power\-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
is 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
saving counters to non\-volatile storage. For extreme streaming\-video
type applications you might consider using \fIoff\fP to set the GLTSD
bit.

.TP
.B SMART READ AND DISPLAY DATA OPTIONS:
.TP
.B \-H, \-\-health
Check: Ask the device to report its SMART health status or pending
TapeAlert messages.  SMART status is based on
information that it has gathered from online and offline
tests, which were used to determine/update its
SMART vendor\-specific Attribute values. TapeAlert status is obtained
by reading the TapeAlert log page.

If the device reports failing health status, this means
.B either
that the device has already failed, 
.B or 
that it is predicting its own failure within the next 24 hours.  If
this happens, use the \'\-a\' option to get more information, and
.B get your data off the disk and to someplace safe as soon as you can.
.TP
.B \-c, \-\-capabilities
Prints only the generic SMART capabilities.  These show
what SMART features are implemented and how the device will
respond to some of the different SMART commands.  For example it
shows if the device logs errors, if it supports offline surface
scanning, and so on.  If the device can carry out self\-tests, this
option also shows the estimated time required to run those tests.

Note that the time required to run the Self\-tests (listed in minutes)
are fixed.  However the time required to run the Immediate Offline
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,
then the time may jump to a larger value and then count down as the
Immediate Offline Test is carried out.  Please see REFERENCES below
for further information about the the flags and capabilities described
by this option.
.TP
.B \-A, \-\-attributes
Prints only the vendor specific SMART Attributes.  The Attributes are
numbered from 1 to 253 and have specific names and ID numbers. For
example Attribute 12 is "power cycle count": how many times has the
disk been powered up.