1SMARTCTL(8) 2006/12/20 SMARTCTL(8)
2
6 smartctl - Control and Monitor Utility for SMART Disks
7
10 smartctl [options] device
11
14 /usr/sbin/smartctl
15
18 smartmontools-5.37 released 2006/12/20 at 20:37:59 UTC
19
22 smartctl controls the Self-Monitoring, Analysis and Reporting Technol‐
23 ogy (SMART) system built into many ATA-3 and later ATA, IDE and SCSI-3
24 hard drives. The purpose of SMART is to monitor the reliability of the
25 hard drive and predict drive failures, and to carry out different types
26 of drive self-tests. This version of smartctl is compatible with
27 ATA/ATAPI-7 and earlier standards (see REFERENCES below)
28 smartctl is a command line utility designed to perform SMART tasks such
30 as printing the SMART self-test and error logs, enabling and disabling
31 SMART automatic testing, and initiating device self-tests. Note: if the
32 user issues a SMART command that is (apparently) not implemented by the
33 device, smartctl will print a warning message but issue the command
34 anyway (see the -T, --tolerance option below). This should not cause
35 problems: on most devices, unimplemented SMART commands issued to a
36 drive are ignored and/or return an error.
37 smartctl also provides support for polling TapeAlert messages from SCSI
39 tape drives and changers.
40 The user must specify the device to be controlled or interrogated as
42 the final argument to smartctl. Device paths are as follows:
43 LINUX: Use the forms "/dev/hd[a-t]" for IDE/ATA devices, and
45 "/dev/sd[a-z]" for SCSI devices. For SCSI Tape Drives and
46 Changers with TapeAlert support use the devices "/dev/nst*"
47 and "/dev/sg*". For SATA disks accessed with libata, use
48 "/dev/sd[a-z]" and append "-d ata". For disks behind 3ware
49 controllers you may need "/dev/sd[a-z]" or "/dev/twe[0-9]" or
50 "/dev/twa[0-9]": see details below. For disks behind HighPoint
51 RocketRAID controllers you may need "/dev/sd[a-z]". More gen‐
52 eral paths (such as devfs ones) may also be specified.
53 DARWIN: Use the forms /dev/disk[0-9] or equivalently disk[0-9] or
55 equivalently /dev/rdisk[0-9]. Long forms are also available:
56 please use ´-h´ to see some examples. Note that there is cur‐
57 rently no Darwin SCSI support.
58 FREEBSD: Use the forms "/dev/ad[0-9]+" for IDE/ATA devices and
60 "/dev/da[0-9]+" for SCSI devices.
61 NETBSD/OPENBSD:
63 Use the form "/dev/wd[0-9]+c" for IDE/ATA devices. For SCSI
64 disk and tape devices, use the device names "/dev/sd[0-9]+c"
65 and "/dev/st[0-9]+c" respectively. Be sure to specify the
66 correct "whole disk" partition letter for your architecture.
67 SOLARIS: Use the forms "/dev/rdsk/c?t?d?s?" for IDE/ATA and SCSI disk
69 devices, and "/dev/rmt/*" for SCSI tape devices.
70 WINDOWS: Use the form "/dev/hd[a-j]" for IDE/ATA devices "\\.\Physi‐
72 calDrive[0-9]" on WinNT4/2000/XP/2003. For IDE/ATA devices on
73 Win95/98/98SE/ME, use "/dev/hd[a-d]" for standard devices
74 accessed via SMARTVSD.VXD, and "/dev/hd[e-h]" for additional
75 devices accessed via a patched SMARTVSE.VXD (see INSTALL file
76 for details). Use the form "/dev/scsi[0-9][0-f]" for SCSI
77 devices via an aspi dll on ASPI adapter 0-9, ID 0-15. Alterna‐
78 tively use "/dev/sd[a-z]" for SCSI disks "\\.\Physi‐
79 calDrive[0-25]" on WinNT4/2000/XP/2003 (where "a" maps to
80 "0"). SCSI disks can also be referred to as "/dev/pd[0-255]"
81 for "\\.\PhysicalDrive[0-255]" on WinNT4/2000/XP/2003. Use the
82 form "/dev/tape[0-255]" for SCSI tape drives "\\.\Tape[0-255]"
83 on WinNT4/2000/XP/2003. For disks behind 3ware 9000 con‐
84 trollers use "/dev/hd[a-j],N" where N specifies the disk num‐
85 ber (3ware ´port´) behind the controller providing the logical
86 drive (´unit´) specified by "/dev/hd[a-j]". Alternatively,
87 use "/dev/tw_cli/cx/py" for controller x, port y to run the
88 ´tw_cli´ tool and parse the output. This provides limited mon‐
89 itoring (´-i´, ´-c´, ´-A´ below) if SMART support is missing
90 in the driver. Use "/dev/tw_cli/stdin" or "/dev/tw_cli/clip"
91 to parse CLI or 3DM output from standard input or clipboard.
92 The option ´-d 3ware,N´ is not necessary on Windows. The pre‐
93 fix "/dev/" is optional.
94 CYGWIN: See "WINDOWS" above.
96 OS/2,eComStation:
98 Use the form "/dev/hd[a-z]" for IDE/ATA devices.
99 Based on the device path, smartctl will guess the device type (ATA or
101 SCSI). If necessary, the ´-d´ option can be used to over-ride this
102 guess
103 Note that the printed output of smartctl displays most numerical values
105 in base 10 (decimal), but some values are displayed in base 16 (hexa‐
106 decimal). To distinguish them, the base 16 values are always displayed
107 with a leading "0x", for example: "0xff". This man page follows the
108 same convention.
109
112 The options are grouped below into several categories. smartctl will
113 execute the corresponding commands in the order: INFORMATION,
114 ENABLE/DISABLE, DISPLAY DATA, RUN/ABORT TESTS.
115 SCSI devices only accept the options -h, -V, -i, -a, -A, -d, -s, -S,-H,
117 -t, -C, -l background, -l error, -l selftest, -r, and -X. TapeAlert
118 devices only accept the options -h, -V, -i, -a, -A, -d, -s, -S, -t, -l
119 error, -l selftest, -r, and -H.
120 Long options are not supported on all systems. Use ´smartctl
122 -h´ to see the available options.
123 SHOW INFORMATION OPTIONS:
126 -h, --help, --usage
128 Prints a usage message to STDOUT and exits.
129 -V, --version, --copyright, --license
131 Prints version, copyright, license, home page and CVS-id infor‐
132 mation for your copy of smartctl to STDOUT and then exits.
133 Please include this information if you are reporting bugs or
134 problems.
135 -i, --info
137 Prints the device model number, serial number, firmware version,
138 and ATA Standard version/revision information. Says if the
139 device supports SMART, and if so, whether SMART support is cur‐
140 rently enabled or disabled. If the device supports Logical
141 Block Address mode (LBA mode) print current user drive capacity
142 in bytes. (If drive is has a user protected area reserved, or is
143 "clipped", this may be smaller than the potential maximum drive
144 capacity.) Indicates if the drive is in the smartmontools data‐
145 base (see ´-v´ options below). If so, the drive model family
146 may also be printed. If ´-n´ (see below) is specified, the power
147 mode of the drive is printed.
148 -a, --all
150 Prints all SMART information about the disk, or TapeAlert infor‐
151 mation about the tape drive or changer. For ATA devices this is
152 equivalent to
153 ´-H -i -c -A -l error -l selftest -l selective´
154 and for SCSI, this is equivalent to
155 ´-H -i -A -l error -l selftest´.
156 Note that for ATA disks this does not enable the ´-l directory´
157 option.
158 RUN-TIME BEHAVIOR OPTIONS:
161 -q TYPE, --quietmode=TYPE
163 Specifies that smartctl should run in one of the two quiet modes
164 described here. The valid arguments to this option are:
165 errorsonly - only print: For the ´-l error´ option, if nonzero,
167 the number of errors recorded in the SMART error log and the
168 power-on time when they occurred; For the ´-l selftest´ option,
169 errors recorded in the device self-test log; For the ´-H´
170 option, SMART "disk failing" status or device Attributes
171 (pre-failure or usage) which failed either now or in the past;
172 For the ´-A´ option, device Attributes (pre-failure or usage)
173 which failed either now or in the past.
174 silent - print no output. The only way to learn about what was
176 found is to use the exit status of smartctl (see RETURN VALUES
177 below).
178 -d TYPE, --device=TYPE
180 Specifies the type of the device. The valid arguments to this
181 option are ata, scsi, sat, marvell, 3ware,N, and hpt,L/M,
182 cciss,N or hpt,L/M/N. If this option is not used then smartctl
183 will attempt to guess the device type from the device name.
184 The ´sat´ device type is for ATA disks that have a SCSI to ATA
186 Translation (SAT) Layer (SATL) between the disk and the operat‐
187 ing system. SAT defines two ATA PASS THROUGH SCSI commands, one
188 12 bytes long and the other 16 bytes long that smartctl will
189 utilize when this device type is selected. The default is the 16
190 byte variant which can be overridden with either ´-d sat,12´ or
191 ´-d sat,16´.
192 Under Linux, to look at SATA disks behind Marvell SATA con‐
194 trollers (using Marvell's ´linuxIAL´ driver rather than libata
195 driver) use ´-d marvell´. Such controllers show up as Marvell
196 Technology Group Ltd. SATA I or II controllers using lspci, or
197 using lspci -n show a vendor ID 0x11ab and a device ID of either
198 0x5040, 0x5041, 0x5080, 0x5081, 0x6041 or 0x6081. The ´linuxIAL´
199 driver seems not (yet?) available in the Linux kernel source
200 tree, but should be available from system vendors
201 (ftp://ftp.aslab.com/ is known to provide a patch with the
202 driver).
203 Under Linux and FreeBSD, to look at ATA disks behind 3ware SCSI
205 RAID controllers, use syntax such as:
206 smartctl -a -d 3ware,2 /dev/sda
207 smartctl -a -d 3ware,0 /dev/twe0
208 smartctl -a -d 3ware,1 /dev/twa0
209 where in the argument 3ware,N, the integer N is the disk number
210 (3ware ´port´) within the 3ware ATA RAID controller. The
211 allowed values of N are from 0 to 15 inclusive. The first two
212 forms, which refer to devices /dev/sda-z and /dev/twe0-15, may
213 be used with 3ware series 6000, 7000, and 8000 series con‐
214 trollers that use the 3x-xxxx driver. Note that the /dev/sda-z
215 form is deprecated starting with the Linux 2.6 kernel series and
216 may not be supported by the Linux kernel in the near future. The
217 final form, which refers to devices /dev/twa0-15, must be used
218 with 3ware 9000 series controllers, which use the 3w-9xxx
219 driver.
220 Note that if the special character device nodes /dev/twa? and
222 /dev/twe? do not exist, or exist with the incorrect major or
223 minor numbers, smartctl will recreate them on the fly. Typi‐
224 cally /dev/twa0 refers to the first 9000-series controller,
225 /dev/twa1 refers to the second 9000 series controller, and so
226 on. Likewise /dev/twe0 refers to the first 6/7/8000-series con‐
227 troller, /dev/twa1 refers to the second 6/7/8000 series con‐
228 troller, and so on.
229 Note that for the 6/7/8000 controllers, any of the physical
231 disks can be queried or examined using any of the 3ware's SCSI
232 logical device /dev/sd? entries. Thus, if logical device
233 /dev/sda is made up of two physical disks (3ware ports zero and
234 one) and logical device /dev/sdb is made up of two other physi‐
235 cal disks (3ware ports two and three) then you can examine the
236 SMART data on any of the four physical disks using either SCSI
237 device /dev/sda or /dev/sdb. If you need to know which logical
238 SCSI device a particular physical disk (3ware port) is associ‐
239 ated with, use the dmesg or SYSLOG output to show which SCSI ID
240 corresponds to a particular 3ware unit, and then use the 3ware
241 CLI or 3dm tool to determine which ports (physical disks) corre‐
242 spond to particular 3ware units.
243 If the value of N corresponds to a port that does not exist on
245 the 3ware controller, or to a port that does not physically have
246 a disk attached to it, the behavior of smartctl depends upon the
247 specific controller model, firmware, Linux kernel and platform.
248 In some cases you will get a warning message that the device
249 does not exist. In other cases you will be presented with ´void´
250 data for a non-existent device.
251 Note that if the /dev/sd? addressing form is used, then older
253 3w-xxxx drivers do not pass the "Enable Autosave" (´-S on´) and
254 "Enable Automatic Offline" (´-o on´) commands to the disk, and
255 produce these types of harmless syslog error messages instead:
256 "3w-xxxx: tw_ioctl(): Passthru size (123392) too big". This can
257 be fixed by upgrading to version 1.02.00.037 or later of the
258 3w-xxxx driver, or by applying a patch to older versions. See
259 http://smartmontools.sourceforge.net/ for instructions. Alter‐
260 natively, use the character device /dev/twe0-15 interface.
261 The selective self-test functions (´-t select,A-B´) are only
263 supported using the character device interface /dev/twa0-15 and
264 /dev/twe0-15. The necessary WRITE LOG commands can not be
265 passed through the SCSI interface.
266 3ware controllers are supported under Linux, FreeBSD and Win‐
268 dows.
269 To look at (S)ATA disks behind HighPoint RocketRAID controllers,
271 use syntax such as:
272 smartctl -a -d hpt,1/3 /dev/sda
273 or
274 smartctl -a -d hpt,1/2/3 /dev/sda
275 where in the argument hpt,L/M or hpt,L/M/N, the integer L is the
276 controller id, the integer M is the channel number, and the
277 integer N is the PMPort number if it is available. The allowed
278 values of L are from 1 to 4 inclusive, M are from 1 to 8 inclu‐
279 sive and N from 1 to 4 if PMPort available. Note that the
280 /dev/sda-z form should be the device node which stands for the
281 disks derived from the HighPoint RocketRAID controllers. And
282 also these values are limited by the model of the HighPoint
283 RocketRAID controller.
284 HighPoint RocketRAID controllers are currently ONLY supported
286 under Linux.
287 cciss controllers are currently ONLY supported under Linux.
289 -T TYPE, --tolerance=TYPE
292 Specifies how tolerant smartctl should be of ATA and SMART com‐
293 mand failures.
294 The behavior of smartctl depends upon whether the command is
296 "optional" or "mandatory". Here "mandatory" means "required by
297 the ATA/ATAPI-5 Specification if the device implements the SMART
298 command set" and "optional" means "not required by the
299 ATA/ATAPI-5 Specification even if the device implements the
300 SMART command set." The "mandatory" ATA and SMART commands are:
301 (1) ATA IDENTIFY DEVICE, (2) SMART ENABLE/DISABLE ATTRIBUTE
302 AUTOSAVE, (3) SMART ENABLE/DISABLE, and (4) SMART RETURN STATUS.
303 The valid arguments to this option are:
305 normal - exit on failure of any mandatory SMART command, and
307 ignore all failures of optional SMART commands. This is the
308 default. Note that on some devices, issuing unimplemented
309 optional SMART commands doesn´t cause an error. This can result
310 in misleading smartctl messages such as "Feature X not imple‐
311 mented", followed shortly by "Feature X: enabled". In most such
312 cases, contrary to the final message, Feature X is not enabled.
313 conservative - exit on failure of any optional SMART command.
315 permissive - ignore failure(s) of mandatory SMART commands.
317 This option may be given more than once. Each additional use of
318 this option will cause one more additional failure to be
319 ignored. Note that the use of this option can lead to messages
320 like "Feature X not implemented", followed shortly by "Error:
321 unable to enable Feature X". In a few such cases, contrary to
322 the final message, Feature X is enabled.
323 verypermissive - equivalent to giving a large number of ´-T per‐
325 missive´ options: ignore failures of any number of mandatory
326 SMART commands. Please see the note above.
327 -b TYPE, --badsum=TYPE
330 Specifies the action smartctl should take if a checksum error is
331 detected in the: (1) Device Identity Structure, (2) SMART
332 Self-Test Log Structure, (3) SMART Attribute Value Structure,
333 (4) SMART Attribute Threshold Structure, or (5) ATA Error Log
334 Structure.
335 The valid arguments to this option are:
337 warn - report the incorrect checksum but carry on in spite of
339 it. This is the default.
340 exit - exit smartctl.
342 ignore - continue silently without issuing a warning.
344 -r TYPE, --report=TYPE
347 Intended primarily to help smartmontools developers understand
348 the behavior of smartmontools on non-conforming or poorly con‐
349 forming hardware. This option reports details of smartctl
350 transactions with the device. The option can be used multiple
351 times. When used just once, it shows a record of the ioctl()
352 transactions with the device. When used more than once, the
353 detail of these ioctl() transactions are reported in greater
354 detail. The valid arguments to this option are:
355 ioctl - report all ioctl() transactions.
357 ataioctl - report only ioctl() transactions with ATA devices.
359 scsiioctl - report only ioctl() transactions with SCSI devices.
361 Invoking this once shows the SCSI commands in hex and the corre‐
362 sponding status. Invoking it a second time adds a hex listing of
363 the first 64 bytes of data send to, or received from the device.
364 Any argument may include a positive integer to specify the level
366 of detail that should be reported. The argument should be fol‐
367 lowed by a comma then the integer with no spaces. For example,
368 ataioctl,2 The default level is 1, so ´-r ataioctl,1´ and ´-r
369 ataioctl´ are equivalent.
370 -n POWERMODE, --nocheck=POWERMODE
373 Specifieds if smartctl should exit before performing any checks
374 when the device is in a low-power mode. It may be used to pre‐
375 vent a disk from being spun-up by smartctl. The power mode is
376 ignored by default. The allowed values of POWERMODE are:
377 never - check the device always, but print the power mode if
379 ´-i´ is specified.
380 sleep - check the device unless it is in SLEEP mode.
382 standby - check the device unless it is in SLEEP or STANDBY
384 mode. In these modes most disks are not spinning, so if you
385 want to prevent a disk from spinning up, this is probably what
386 you want.
387 idle - check the device unless it is in SLEEP, STANDBY or IDLE
389 mode. In the IDLE state, most disks are still spinning, so this
390 is probably not what you want.
391 SMART FEATURE ENABLE/DISABLE COMMANDS:
394 Note: if multiple options are used to both enable and disable a
396 feature, then both the enable and disable commands will be
397 issued. The enable command will always be issued before the
398 corresponding disable command.
399 -s VALUE, --smart=VALUE
401 Enables or disables SMART on device. The valid arguments to
402 this option are on and off. Note that the command ´-s on´ (per‐
403 haps used with with the ´-o on´ and ´-S on´ options) should be
404 placed in a start-up script for your machine, for example in
405 rc.local or rc.sysinit. In principle the SMART feature settings
406 are preserved over power-cycling, but it doesn´t hurt to be
407 sure. It is not necessary (or useful) to enable SMART to see the
408 TapeAlert messages.
409 -o VALUE, --offlineauto=VALUE
411 Enables or disables SMART automatic offline test, which scans
412 the drive every four hours for disk defects. This command can be
413 given during normal system operation. The valid arguments to
414 this option are on and off.
415 Note that the SMART automatic offline test command is listed as
417 "Obsolete" in every version of the ATA and ATA/ATAPI Specifica‐
418 tions. It was originally part of the SFF-8035i Revision 2.0
419 specification, but was never part of any ATA specification.
420 However it is implemented and used by many vendors. [Good docu‐
421 mentation can be found in IBM´s Official Published Disk Specifi‐
422 cations. For example the IBM Travelstar 40GNX Hard Disk Drive
423 Specifications (Revision 1.1, 22 April 2002, Publication # 1541,
424 Document S07N-7715-02) page 164. You can also read the SFF-8035i
425 Specification -- see REFERENCES below.] You can tell if auto‐
426 matic offline testing is supported by seeing if this command
427 enables and disables it, as indicated by the ´Auto Offline Data
428 Collection´ part of the SMART capabilities report (displayed
429 with ´-c´).
430 SMART provides three basic categories of testing. The first
432 category, called "online" testing, has no effect on the perfor‐
433 mance of the device. It is turned on by the ´-s on´ option.
434 The second category of testing is called "offline" testing. This
436 type of test can, in principle, degrade the device performance.
437 The ´-o on´ option causes this offline testing to be carried
438 out, automatically, on a regular scheduled basis. Normally, the
439 disk will suspend offline testing while disk accesses are taking
440 place, and then automatically resume it when the disk would oth‐
441 erwise be idle, so in practice it has little effect. Note that
442 a one-time offline test can also be carried out immediately upon
443 receipt of a user command. See the ´-t offline´ option below,
444 which causes a one-time offline test to be carried out immedi‐
445 ately.
446 The choice (made by the SFF-8035i and ATA specification authors)
448 of the word testing for these first two categories is unfortu‐
449 nate, and often leads to confusion. In fact these first two
450 categories of online and offline testing could have been more
451 accurately described as online and offline data collection.
452 The results of this automatic or immediate offline testing (data
454 collection) are reflected in the values of the SMART Attributes.
455 Thus, if problems or errors are detected, the values of these
456 Attributes will go below their failure thresholds; some types of
457 errors may also appear in the SMART error log. These are visible
458 with the ´-A´ and ´-l error´ options respectively.
459 Some SMART attribute values are updated only during off-line
461 data collection activities; the rest are updated during normal
462 operation of the device or during both normal operation and
463 off-line testing. The Attribute value table produced by the
464 ´-A´ option indicates this in the UPDATED column. Attributes of
465 the first type are labeled "Offline" and Attributes of the sec‐
466 ond type are labeled "Always".
467 The third category of testing (and the only category for which
469 the word ´testing´ is really an appropriate choice) is "self"
470 testing. This third type of test is only performed (immedi‐
471 ately) when a command to run it is issued. The ´-t´ and ´-X´
472 options can be used to carry out and abort such self-tests;
473 please see below for further details.
474 Any errors detected in the self testing will be shown in the
476 SMART self-test log, which can be examined using the ´-l self‐
477 test´ option.
478 Note: in this manual page, the word "Test" is used in connection
480 with the second category just described, e.g. for the "offline"
481 testing. The words "Self-test" are used in connection with the
482 third category.
483 -S VALUE, --saveauto=VALUE
485 Enables or disables SMART autosave of device vendor-specific
486 Attributes. The valid arguments to this option are on and off.
487 Note that this feature is preserved across disk power cycles, so
488 you should only need to issue it once.
489 For SCSI devices this toggles the value of the Global Logging
491 Target Save Disabled (GLTSD) bit in the Control Mode Page. Some
492 disk manufacturers set this bit by default. This prevents error
493 counters, power-up hours and other useful data from being placed
494 in non-volatile storage, so these values may be reset to zero
495 the next time the device is power-cycled. If the GLTSD bit is
496 set then ´smartctl -a´ will issue a warning. Use on to clear the
497 GLTSD bit and thus enable saving counters to non-volatile stor‐
498 age. For extreme streaming-video type applications you might
499 consider using off to set the GLTSD bit.
500 SMART READ AND DISPLAY DATA OPTIONS:
503 -H, --health
505 Check: Ask the device to report its SMART health status or pend‐
506 ing TapeAlert messages. SMART status is based on information
507 that it has gathered from online and offline tests, which were
508 used to determine/update its SMART vendor-specific Attribute
509 values. TapeAlert status is obtained by reading the TapeAlert
510 log page.
511 If the device reports failing health status, this means either
513 that the device has already failed, or that it is predicting its
514 own failure within the next 24 hours. If this happens, use the
515 ´-a´ option to get more information, and get your data off the
516 disk and someplace safe as soon as you can.
517 -c, --capabilities
519 Prints only the generic SMART capabilities. These show what
520 SMART features are implemented and how the device will respond
521 to some of the different SMART commands. For example it shows
522 if the device logs errors, if it supports offline surface scan‐
523 ning, and so on. If the device can carry out self-tests, this
524 option also shows the estimated time required to run those
525 tests.
526 Note that the time required to run the Self-tests (listed in
528 minutes) are fixed. However the time required to run the Imme‐
529 diate Offline Test (listed in seconds) is variable. This means
530 that if you issue a command to perform an Immediate Offline test
531 with the ´-t offline´ option, then the time may jump to a larger
532 value and then count down as the Immediate Offline Test is car‐
533 ried out. Please see REFERENCES below for further information
534 about the the flags and capabilities described by this option.
535 -A, --attributes
537 Prints only the vendor specific SMART Attributes. The
538 Attributes are numbered from 1 to 253 and have specific names
539 and ID numbers. For example Attribute 12 is "power cycle count":
540 how many times has the disk been powered up.
541 Each Attribute has a "Raw" value, printed under the heading
543 "RAW_VALUE", and a "Normalized" value printed under the heading
544 "VALUE". [Note: smartctl prints these values in base-10.] In
545 the example just given, the "Raw Value" for Attribute 12 would
546 be the actual number of times that the disk has been
547 power-cycled, for example 365 if the disk has been turned on
548 once per day for exactly one year. Each vendor uses their own
549 algorithm to convert this "Raw" value to a "Normalized" value in
550 the range from 1 to 254. Please keep in mind that smartctl only
551 reports the different Attribute types, values, and thresholds as
552 read from the device. It does not carry out the conversion
553 between "Raw" and "Normalized" values: this is done by the
554 disk´s firmware.
555 The conversion from Raw value to a quantity with physical units
557 is not specified by the SMART standard. In most cases, the val‐
558 ues printed by smartctl are sensible. For example the tempera‐
559 ture Attribute generally has its raw value equal to the tempera‐
560 ture in Celsius. However in some cases vendors use unusual con‐
561 ventions. For example the Hitachi disk on my laptop reports its
562 power-on hours in minutes, not hours. Some IBM disks track three
563 temperatures rather than one, in their raw values. And so on.
564 Each Attribute also has a Threshold value (whose range is 0 to
566 255) which is printed under the heading "THRESH". If the Nor‐
567 malized value is less than or equal to the Threshold value, then
568 the Attribute is said to have failed. If the Attribute is a
569 pre-failure Attribute, then disk failure is imminent.
570 Each Attribute also has a "Worst" value shown under the heading
572 "WORST". This is the smallest (closest to failure) value that
573 the disk has recorded at any time during its lifetime when SMART
574 was enabled. [Note however that some vendors firmware may actu‐
575 ally increase the "Worst" value for some "rate-type"
576 Attributes.]
577 The Attribute table printed out by smartctl also shows the
579 "TYPE" of the Attribute. Attributes are one of two possible
580 types: Pre-failure or Old age. Pre-failure Attributes are ones
581 which, if less than or equal to their threshold values, indicate
582 pending disk failure. Old age, or usage Attributes, are ones
583 which indicate end-of-product life from old-age or normal aging
584 and wearout, if the Attribute value is less than or equal to the
585 threshold. Please note: the fact that an Attribute is of type
586 'Pre-fail' does not mean that your disk is about to fail! It
587 only has this meaning if the Attribute´s current Normalized
588 value is less than or equal to the threshold value.
589 If the Attribute´s current Normalized value is less than or
591 equal to the threshold value, then the "WHEN_FAILED" column will
592 display "FAILING_NOW". If not, but the worst recorded value is
593 less than or equal to the threshold value, then this column will
594 display "In_the_past". If the "WHEN_FAILED" column has no entry
595 (indicated by a dash: ´-´) then this Attribute is OK now (not
596 failing) and has also never failed in the past.
597 The table column labeled "UPDATED" shows if the SMART Attribute
599 values are updated during both normal operation and off-line
600 testing, or only during offline testing. The former are labeled
601 "Always" and the latter are labeled "Offline".
602 So to summarize: the Raw Attribute values are the ones that
604 might have a real physical interpretation, such as "Temperature
605 Celsius", "Hours", or "Start-Stop Cycles". Each manufacturer
606 converts these, using their detailed knowledge of the disk´s
607 operations and failure modes, to Normalized Attribute values in
608 the range 1-254. The current and worst (lowest measured) of
609 these Normalized Attribute values are stored on the disk, along
610 with a Threshold value that the manufacturer has determined will
611 indicate that the disk is going to fail, or that it has exceeded
612 its design age or aging limit. smartctl does not calculate any
613 of the Attribute values, thresholds, or types, it merely reports
614 them from the SMART data on the device.
615 Note that starting with ATA/ATAPI-4, revision 4, the meaning of
617 these Attribute fields has been made entirely vendor-specific.
618 However most ATA/ATAPI-5 disks seem to respect their meaning, so
619 we have retained the option of printing the Attribute values.
620 For SCSI devices the "attributes" are obtained from the tempera‐
622 ture and start-stop cycle counter log pages. Certain vendor spe‐
623 cific attributes are listed if recognised. The attributes are
624 output in a relatively free format (compared with ATA disk
625 attributes).
626 -l TYPE, --log=TYPE
628 Prints either the SMART Error Log, the SMART Self-Test Log, the
629 SMART Selective Self-Test Log [ATA only], the Log Directory [ATA
630 only], or the Background Scan Results Log [SCSI only]. The
631 valid arguments to this option are:
632 error - prints only the SMART error log. SMART disks maintain a
634 log of the most recent five non-trivial errors. For each of
635 these errors, the disk power-on lifetime at which the error
636 occurred is recorded, as is the device status (idle, standby,
637 etc) at the time of the error. For some common types of errors,
638 the Error Register (ER) and Status Register (SR) values are
639 decoded and printed as text. The meanings of these are:
640 ABRT: Command ABoRTed
641 AMNF: Address Mark Not Found
642 CCTO: Command Completion Timed Out
643 EOM: End Of Media
644 ICRC: Interface Cyclic Redundancy Code (CRC) error
645 IDNF: IDentity Not Found
646 ILI: (packet command-set specific)
647 MC: Media Changed
648 MCR: Media Change Request
649 NM: No Media
650 obs: obsolete
651 TK0NF: TracK 0 Not Found
652 UNC: UNCorrectable Error in Data
653 WP: Media is Write Protected
654 In addition, up to the last five commands that preceded the
655 error are listed, along with a timestamp measured from the start
656 of the corresponding power cycle. This is displayed in the form
657 Dd+HH:MM:SS.msec where D is the number of days, HH is hours, MM
658 is minutes, SS is seconds and msec is milliseconds. [Note: this
659 time stamp wraps after 2^32 milliseconds, or 49 days 17 hours 2
660 minutes and 47.296 seconds.] The key ATA disk registers are
661 also recorded in the log. The final column of the error log is
662 a text-string description of the ATA command defined by the Com‐
663 mand Register (CR) and Feature Register (FR) values. Commands
664 that are obsolete in the most current (ATA-7) spec are listed
665 like this: READ LONG (w/ retry) [OBS-4], indicating that the
666 command became obsolete with or in the ATA-4 specification.
667 Similarly, the notation [RET-N] is used to indicate that a com‐
668 mand was retired in the ATA-N specification. Some commands are
669 not defined in any version of the ATA specification but are in
670 common use nonetheless; these are marked [NS], meaning non-stan‐
671 dard.
672 The ATA Specification (ATA-5 Revision 1c, Section 8.41.6.8.2)
674 says: "Error log structures shall include UNC errors, IDNF
675 errors for which the address requested was valid, servo errors,
676 write fault errors, etc. Error log data structures shall not
677 include errors attributed to the receipt of faulty commands such
678 as command codes not implemented by the device or requests with
679 invalid parameters or invalid addresses." The definitions of
680 these terms are:
681 UNC (UNCorrectable): data is uncorrectable. This refers to data
682 which has been read from the disk, but for which the Error
683 Checking and Correction (ECC) codes are inconsistent. In
684 effect, this means that the data can not be read.
685 IDNF (ID Not Found): user-accessible address could not be found.
686 For READ LOG type commands, IDNF can also indicate that a device
687 data log structure checksum was incorrect.
688 If the command that caused the error was a READ or WRITE com‐
690 mand, then the Logical Block Address (LBA) at which the error
691 occurred will be printed in base 10 and base 16. The LBA is a
692 linear address, which counts 512-byte sectors on the disk,
693 starting from zero. (Because of the limitations of the SMART
694 error log, if the LBA is greater than 0xfffffff, then either no
695 error log entry will be made, or the error log entry will have
696 an incorrect LBA. This may happen for drives with a capacity
697 greater than 128 GiB or 137 GB.) On Linux systems the smartmon‐
698 tools web page has instructions about how to convert the LBA
699 address to the name of the disk file containing the erroneous
700 disk sector.
701 Please note that some manufacturers ignore the ATA specifica‐
703 tions, and make entries in the error log if the device receives
704 a command which is not implemented or is not valid.
705 error [SCSI] - prints the error counter log pages for reads,
707 write and verifies. The verify row is only output if it has an
708 element other than zero.
709 selftest - prints the SMART self-test log. The disk maintains a
711 self-test log showing the results of the self tests, which can
712 be run using the ´-t´ option described below. For each of the
713 most recent twenty-one self-tests, the log shows the type of
714 test (short or extended, off-line or captive) and the final sta‐
715 tus of the test. If the test did not complete successfully,
716 then the percentage of the test remaining is shown. The time at
717 which the test took place, measured in hours of disk lifetime,
718 is also printed. If any errors were detected, the Logical Block
719 Address (LBA) of the first error is printed in decimal notation.
720 On Linux systems the smartmontools web page has instructions
721 about how to convert this LBA address to the name of the disk
722 file containing the erroneous block.
723 selftest [SCSI] - the self-test log for a SCSI device has a
725 slightly different format than for an ATA device. For each of
726 the most recent twenty self-tests, it shows the type of test and
727 the status (final or in progress) of the test. SCSI standards
728 use the terms "foreground" and "background" (rather than ATA´s
729 corresponding "captive" and "off-line") and "short" and "long"
730 (rather than ATA´s corresponding "short" and "extended") to
731 describe the type of the test. The printed segment number is
732 only relevant when a test fails in the third or later test seg‐
733 ment. It identifies the test that failed and consists of either
734 the number of the segment that failed during the test, or the
735 number of the test that failed and the number of the segment in
736 which the test was run, using a vendor-specific method of
737 putting both numbers into a single byte. The Logical Block
738 Address (LBA) of the first error is printed in hexadecimal nota‐
739 tion. On Linux systems the smartmontools web page has instruc‐
740 tions about how to convert this LBA address to the name of the
741 disk file containing the erroneous block. If provided, the SCSI
742 Sense Key (SK), Additional Sense Code (ASC) and Additional Sense
743 Code Qualifier (ASQ) are also printed. The self tests can be run
744 using the ´-t´ option described below (using the ATA test termi‐
745 nology).
746 selective [ATA] - Some ATA-7 disks (example: Maxtor) also main‐
748 tain a selective self-test log. Please see the ´-t select´
749 option below for a description of selective self-tests. The
750 selective self-test log shows the start/end Logical Block
751 Addresses (LBA) of each of the five test spans, and their cur‐
752 rent test status. If the span is being tested or the remainder
753 of the disk is being read-scanned, the current 65536-sector
754 block of LBAs being tested is also displayed. The selective
755 self-test log also shows if a read-scan of the remainder of the
756 disk will be carried out after the selective self-test has com‐
757 pleted (see ´-t afterselect´ option) and the time delay before
758 restarting this read-scan if it is interrupted (see ´-t pending´
759 option). This is a new smartmontools feature; please report
760 unusual or incorrect behavior to the smartmontools-support mail‐
761 ing list.
762 directory - if the device supports the General Purpose Logging
764 feature set (ATA-6 and ATA-7 only) then this prints the Log
765 Directory (the log at address 0). The Log Directory shows what
766 logs are available and their length in sectors (512 bytes). The
767 contents of the logs at address 1 [Summary SMART error log] and
768 at address 6 [SMART self-test log] may be printed using the pre‐
769 viously-described error and selftest arguments to this option.
770 [Please note: this is a new, experimental feature. We would
771 like to add support for printing the contents of extended and
772 comprehensive SMART self-test and error logs. If your disk sup‐
773 ports these, and you would like to assist, please contact the
774 smartmontools developers.]
775 background [SCSI] - the background scan results log outputs
777 information derived from Background Media Scans (BMS) done after
778 power up and/or periodocally (e.g. every 24 hours) on recent
779 SCSI disks. If supported, the BMS status is output first, indi‐
780 cating whether a background scan is currently underway (and if
781 so a progress percentage), the amount of time the disk has been
782 powered up and the number of scans already completed. Then there
783 is a header and a line for each background scan "event". These
784 will typically be either recovered or unrecoverable errors. That
785 latter group may need some attention. There is a description of
786 the background scan mechansim in section 4.18 of SBC-3 revision
787 6 (see www.t10.org ).
788 -v N,OPTION, --vendorattribute=N,OPTION
791 Sets a vendor-specific display OPTION for Attribute N. This
792 option may be used multiple times. Valid arguments to this
793 option are:
794 help - Prints (to STDOUT) a list of all valid arguments to this
796 option, then exits.
797 9,minutes - Raw Attribute number 9 is power-on time in minutes.
799 Its raw value will be displayed in the form "Xh+Ym". Here X is
800 hours, and Y is minutes in the range 0-59 inclusive. Y is
801 always printed with two digits, for example "06" or "31" or
802 "00".
803 9,seconds - Raw Attribute number 9 is power-on time in seconds.
805 Its raw value will be displayed in the form "Xh+Ym+Zs". Here X
806 is hours, Y is minutes in the range 0-59 inclusive, and Z is
807 seconds in the range 0-59 inclusive. Y and Z are always printed
808 with two digits, for example "06" or "31" or "00".
809 9,halfminutes - Raw Attribute number 9 is power-on time, mea‐
811 sured in units of 30 seconds. This format is used by some Sam‐
812 sung disks. Its raw value will be displayed in the form
813 "Xh+Ym". Here X is hours, and Y is minutes in the range 0-59
814 inclusive. Y is always printed with two digits, for example
815 "06" or "31" or "00".
816 9,temp - Raw Attribute number 9 is the disk temperature in Cel‐
818 sius.
819 192,emergencyretractcyclect - Raw Attribute number 192 is the
821 Emergency Retract Cycle Count.
822 193,loadunload - Raw Attribute number 193 contains two values.
824 The first is the number of load cycles. The second is the num‐
825 ber of unload cycles. The difference between these two values
826 is the number of times that the drive was unexpectedly powered
827 off (also called an emergency unload). As a rule of thumb, the
828 mechanical stress created by one emergency unload is equivalent
829 to that created by one hundred normal unloads.
830 194,10xCelsius - Raw Attribute number 194 is ten times the disk
832 temperature in Celsius. This is used by some Samsung disks
833 (example: model SV1204H with RK100-13 firmware).
834 194,unknown - Raw Attribute number 194 is NOT the disk tempera‐
836 ture, and its interpretation is unknown. This is primarily use‐
837 ful for the -P (presets) option.
838 198,offlinescanuncsectorct - Raw Attribute number 198 is the
840 Offline Scan UNC Sector Count.
841 200,writeerrorcount - Raw Attribute number 200 is the Write
843 Error Count.
844 201,detectedtacount - Raw Attribute number 201 is the Detected
846 TA Count.
847 220,temp - Raw Attribute number 220 is the disk temperature in
849 Celsius.
850 Note: a table of hard drive models, listing which Attribute cor‐
852 responds to temperature, can be found at:
853 http://www.guzu.net/linux/hddtemp.db
854 N,raw8 - Print the Raw value of Attribute N as six 8-bit
856 unsigned base-10 integers. This may be useful for decoding the
857 meaning of the Raw value. The form ´N,raw8´ prints Raw values
858 for ALL Attributes in this form. The form (for example)
859 ´123,raw8´ only prints the Raw value for Attribute 123 in this
860 form.
861 N,raw16 - Print the Raw value of Attribute N as three 16-bit
863 unsigned base-10 integers. This may be useful for decoding the
864 meaning of the Raw value. The form ´N,raw16´ prints Raw values
865 for ALL Attributes in this form. The form (for example)
866 ´123,raw16´ only prints the Raw value for Attribute 123 in this
867 form.
868 N,raw48 - Print the Raw value of Attribute N as a 48-bit
870 unsigned base-10 integer. This may be useful for decoding the
871 meaning of the Raw value. The form ´N,raw48´ prints Raw values
872 for ALL Attributes in this form. The form (for example)
873 ´123,raw48´ only prints the Raw value for Attribute 123 in this
874 form.
875 -F TYPE, --firmwarebug=TYPE
878 Modifies the behavior of smartctl to compensate for some known
879 and understood device firmware bug. The arguments to this
880 option are exclusive, so that only the final option given is
881 used. The valid values are:
882 none - Assume that the device firmware obeys the ATA specifica‐
884 tions. This is the default, unless the device has presets for
885 ´-F´ in the device database (see note below).
886 samsung - In some Samsung disks (example: model SV4012H Firmware
888 Version: RM100-08) some of the two- and four-byte quantities in
889 the SMART data structures are byte-swapped (relative to the ATA
890 specification). Enabling this option tells smartctl to evaluate
891 these quantities in byte-reversed order. Some signs that your
892 disk needs this option are (1) no self-test log printed, even
893 though you have run self-tests; (2) very large numbers of ATA
894 errors reported in the ATA error log; (3) strange and impossible
895 values for the ATA error log timestamps.
896 samsung2 - In more recent Samsung disks (firmware revisions end‐
898 ing in "-23") the number of ATA errors reported is byte swapped.
899 Enabling this option tells smartctl to evaluate this quantity in
900 byte-reversed order. An indication that your Samsung disk needs
901 this option is that the self-test log is printed correctly, but
902 there are a very large number of errors in the SMART error log.
903 This is because the error count is byte swapped. Thus a disk
904 with five errors (0x0005) will appear to have 20480 errors
905 (0x5000).
906 Note that an explicit ´-F´ option on the command line will
908 over-ride any preset values for ´-F´ (see the ´-P´ option
909 below).
910 -P TYPE, --presets=TYPE
913 Specifies whether smartctl should use any preset options that
914 are available for this drive. By default, if the drive is recog‐
915 nized in the smartmontools database, then the presets are used.
916 smartctl can automatically set appropriate options for known
918 drives. For example, the Maxtor 4D080H4 uses Attribute 9 to
919 stores power-on time in minutes whereas most drives use that
920 Attribute to store the power-on time in hours. The command-line
921 option ´-v 9,minutes´ ensures that smartctl correctly interprets
922 Attribute 9 in this case, but that option is preset for the Max‐
923 tor 4D080H4 and so need not be specified by the user on the
924 smartctl command line.
925 The argument show will show any preset options for your drive
927 and the argument showall will show all known drives in the
928 smartmontools database, along with their preset options. If
929 there are no presets for your drive and you think there should
930 be (for example, a -v or -F option is needed to get smartctl to
931 display correct values) then please contact the smartmontools
932 developers so that this information can be added to the smart‐
933 montools database. Contact information is at the end of this
934 man page.
935 The valid arguments to this option are:
937 use - if a drive is recognized, then use the stored presets for
939 it. This is the default. Note that presets will NOT over-ride
940 additional Attribute interpretation (´-v N,something´) com‐
941 mand-line options or explicit ´-F´ command-line options..
942 ignore - do not use presets.
944 show - show if the drive is recognized in the database, and if
946 so, its presets, then exit.
947 showall - list all recognized drives, and the presets that are
949 set for them, then exit.
950 The ´-P showall´ option takes up to two optional arguments to
952 match a specific drive type and firmware version. The command:
953 smartctl -P showall
954 lists all entries, the command:
955 smartctl -P showall ´MODEL´
956 lists all entries matching MODEL, and the command:
957 smartctl -P showall ´MODEL´ ´FIRMWARE´
958 lists all entries for this MODEL and a specific FIRMWARE ver‐
959 sion.
960 SMART RUN/ABORT OFFLINE TEST AND SELF-TEST OPTIONS:
963 -t TEST, --test=TEST
965 Executes TEST immediately. The ´-C´ option can be used in con‐
966 junction with this option to run the short or long (and also for
967 ATA devices, selective or conveyance) self-tests in captive mode
968 (known as "foreground mode" for SCSI devices). Note that only
969 one test type can be run at a time, so only one test type should
970 be specified per command line. Note also that if a computer is
971 shutdown or power cycled during a self-test, no harm should
972 result. The self-test will either be aborted or will resume
973 automatically.
974 The valid arguments to this option are:
976 offline - runs SMART Immediate Offline Test. This immediately
978 starts the test described above. This command can be given dur‐
979 ing normal system operation. The effects of this test are visi‐
980 ble only in that it updates the SMART Attribute values, and if
981 errors are found they will appear in the SMART error log, visi‐
982 ble with the ´-l error´ option. [In the case of SCSI devices
983 runs the default self test in foreground. No entry is placed in
984 the self test log.]
985 If the ´-c´ option to smartctl shows that the device has the
987 "Suspend Offline collection upon new command" capability then
988 you can track the progress of the Immediate Offline test using
989 the ´-c´ option to smartctl. If the ´-c´ option show that the
990 device has the "Abort Offline collection upon new command" capa‐
991 bility then most commands will abort the Immediate Offline Test,
992 so you should not try to track the progress of the test with
993 ´-c´, as it will abort the test.
994 short - runs SMART Short Self Test (usually under ten minutes).
996 [Note: in the case of SCSI devices, this command option runs the
997 "Background short" self-test.] This command can be given during
998 normal system operation (unless run in captive mode - see the
999 ´-C´ option below). This is a test in a different category than
1000 the immediate or automatic offline tests. The "Self" tests
1001 check the electrical and mechanical performance as well as the
1002 read performance of the disk. Their results are reported in the
1003 Self Test Error Log, readable with the ´-l selftest´ option.
1004 Note that on some disks the progress of the self-test can be
1005 monitored by watching this log during the self-test; with other
1006 disks use the ´-c´ option to monitor progress.
1007 long - runs SMART Extended Self Test (tens of minutes). [Note:
1009 in the case of SCSI devices, this command option runs the "Back‐
1010 ground long" self-test.] This is a longer and more thorough
1011 version of the Short Self Test described above. Note that this
1012 command can be given during normal system operation (unless run
1013 in captive mode - see the ´-C´ option below).
1014 conveyance - [ATA ONLY] runs a SMART Conveyance Self Test (min‐
1016 utes). This self-test routine is intended to identify damage
1017 incurred during transporting of the device. This self-test rou‐
1018 tine should take on the order of minutes to complete. Note that
1019 this command can be given during normal system operation (unless
1020 run in captive mode - see the ´-C´ option below).
1021 select,N-M - [ATA ONLY] [NEW EXPERIMENTAL SMARTCTL FEATURE] runs
1023 a SMART Selective Self Test, to test a range of disk Logical
1024 Block Addresses (LBAs), rather than the entire disk. Each range
1025 of LBAs that is checked is called a "span" and is specified by a
1026 starting LBA (N) and an ending LBA (M) with N less than or equal
1027 to M. For example the command:
1028 smartctl -t select,10-20 /dev/hda
1029 runs a self test on one span consisting of LBAs ten to twenty
1030 (inclusive). The ´-t´ option can be given up to five times, to
1031 test up to five spans. For example the command:
1032 smartctl -t select,0-100 -t select,1000-2000 /dev/hda
1033 runs a self test on two spans. The first span consists of 101
1034 LBAs and the second span consists of 1001 LBAs. Note that the
1035 spans can overlap partially or completely, for example:
1036 smartctl -t select,0-10 -t select,5-15 -t select,10-20 /dev/hda
1037 The results of the selective self-test can be obtained (both
1038 during and after the test) by printing the SMART self-test log,
1039 using the ´-l selftest´ option to smartctl.
1040 Selective self tests are particularly useful as disk capacities
1042 increase: an extended self test (smartctl -t long) can take sev‐
1043 eral hours. Selective self-tests are helpful if (based on SYS‐
1044 LOG error messages, previous failed self-tests, or SMART error
1045 log entries) you suspect that a disk is having problems at a
1046 particular range of Logical Block Addresses (LBAs).
1047 Selective self-tests can be run during normal system operation
1049 (unless done in captive mode - see the ´-C´ option below).
1050 [Note: this new experimental smartmontools feature is currently
1052 only available under Linux. The Linux kernel must be compiled
1053 with the configuration option CONFIG_IDE_TASKFILE_IO enabled.
1054 Please report unusual or incorrect behavior to the smartmon‐
1055 tools-support mailing list.]
1056 afterselect,on - [ATA ONLY] perform an offline read scan after a
1058 Selective Self-test has completed. This option must be used
1059 together with one or more of the select,N-M options above. If
1060 the LBAs that have been specified in the Selective self-test
1061 pass the test with no errors found, then read scan the remainder
1062 of the disk. If the device is powered-cycled while this read
1063 scan is in progress, the read scan will be automatically resumed
1064 after a time specified by the pending timer (see below). The
1065 value of this option is preserved between selective self-tests.
1066 afterselect,off - [ATA ONLY] do not read scan the remainder of
1068 the disk after a Selective self-test has completed. This option
1069 must be use together with one or more of the select,N-M options
1070 above. The value of this option is preserved between selective
1071 self-tests.
1072 pending,N - [ATA ONLY] set the pending offline read scan timer
1074 to N minutes. Here N is an integer in the range from 0 to 65535
1075 inclusive. If the device is powered off during a read scan
1076 after a Selective self-test, then resume the test automatically
1077 N minutes after power-up. This option must be use together with
1078 one or more of the select,N-M options above. The value of this
1079 option is preserved between selective self-tests.
1080 -C, --captive
1083 Runs self-tests in captive mode. This has no effect with ´-t
1084 offline´ or if the ´-t´ option is not used. [Note: in the case
1085 of SCSI devices, this command option runs the self-test in
1086 "Foreground" mode.]
1087 WARNING: Tests run in captive mode may busy out the drive for
1089 the length of the test. Only run captive tests on drives with‐
1090 out any mounted partitions!
1091 -X, --abort
1094 Aborts non-captive SMART Self Tests. Note that this command
1095 will abort the Offline Immediate Test routine only if your disk
1096 has the "Abort Offline collection upon new command" capability.
1097
1099 smartctl -a /dev/hda
1100 Print all SMART information for drive /dev/hda (Primary Master).
1101 smartctl -s off /dev/hdd
1103 Disable SMART on drive /dev/hdd (Secondary Slave).
1104 smartctl --smart=on --offlineauto=on --saveauto=on /dev/hda
1106 Enable SMART on drive /dev/hda, enable automatic offline testing every
1107 four hours, and enable autosaving of SMART Attributes. This is a good
1108 start-up line for your system´s init files. You can issue this command
1109 on a running system.
1110 smartctl -t long /dev/hdc
1112 Begin an extended self-test of drive /dev/hdc. You can issue this com‐
1113 mand on a running system. The results can be seen in the self-test log
1114 visible with the ´-l selftest´ option after it has completed.
1115 smartctl -s on -t offline /dev/hda
1117 Enable SMART on the disk, and begin an immediate offline test of drive
1118 /dev/hda. You can issue this command on a running system. The results
1119 are only used to update the SMART Attributes, visible with the ´-A´
1120 option. If any device errors occur, they are logged to the SMART error
1121 log, which can be seen with the ´-l error´ option.
1122 smartctl -A -v 9,minutes /dev/hda
1124 Shows the vendor Attributes, when the disk stores its power-on time
1125 internally in minutes rather than hours.
1126 smartctl -q errorsonly -H -l selftest /dev/hda
1128 Produces output only if the device returns failing SMART status, or if
1129 some of the logged self-tests ended with errors.
1130 smartctl -q silent -a /dev/hda
1132 Examine all SMART data for device /dev/hda, but produce no printed out‐
1133 put. You must use the exit status (the $? shell variable) to learn if
1134 any Attributes are out of bound, if the SMART status is failing, if
1135 there are errors recorded in the self-test log, or if there are errors
1136 recorded in the disk error log.
1137 smartctl -a -d 3ware,0 /dev/sda
1139 Examine all SMART data for the first ATA disk connected to a 3ware RAID
1140 controller card.
1141 smartctl -a -d 3ware,0 /dev/twe0
1143 Examine all SMART data for the first ATA disk connected to a 3ware RAID
1144 6000/7000/8000 controller card.
1145 smartctl -a -d 3ware,0 /dev/twa0
1147 Examine all SMART data for the first ATA disk connected to a 3ware RAID
1148 9000 controller card.
1149 smartctl -t short -d 3ware,3 /dev/sdb
1151 Start a short self-test on the fourth ATA disk connected to the 3ware
1152 RAID controller card which is the second SCSI device /dev/sdb.
1153 smartctl -a -d hpt,1/3 /dev/sda
1155 Examine all SMART data for the (S)ATA disk directly connected to the
1156 third channel of the first HighPoint RocketRAID controller card.
1157 smartctl -t short -d hpt,1/1/2 /dev/sda
1159 Start a short self-test on the (S)ATA disk connected to second pmport
1160 on the first channel of the first HighPoint RocketRAID controller card.
1161 smartctl -t select,10-100 -t select,30-300 -t afterselect,on -t pending,45 /dev/hda
1163 Run a selective self-test on LBAs 10 to 100 and 30 to 300. After the
1164 these LBAs have been tested, read-scan the remainder of the disk. If
1165 the disk is power-cycled during the read-scan, resume the scan 45 min‐
1166 utes after power to the device is restored.
1167 smartctl -a -d cciss,0 /dev/cciss/c0d0
1169 Examine all SMART data for the first SCSI disk connected to a cciss
1170 RAID controller card.
1171
1173 The return values of smartctl are defined by a bitmask. If all is well
1174 with the disk, the return value (exit status) of smartctl is 0 (all
1175 bits turned off). If a problem occurs, or an error, potential error,
1176 or fault is detected, then a non-zero status is returned. In this
1177 case, the eight different bits in the return value have the following
1178 meanings for ATA disks; some of these values may also be returned for
1179 SCSI disks.
1180 Bit 0: Command line did not parse.
1182 Bit 1: Device open failed, or device did not return an IDENTIFY DEVICE
1184 structure.
1185 Bit 2: Some SMART command to the disk failed, or there was a checksum
1187 error in a SMART data structure (see ´-b´ option above).
1188 Bit 3: SMART status check returned "DISK FAILING".
1190 Bit 4: SMART status check returned "DISK OK" but we found prefail
1192 Attributes <= threshold.
1193 Bit 5: SMART status check returned "DISK OK" but we found that some
1195 (usage or prefail) Attributes have been <= threshold at some
1196 time in the past.
1197 Bit 6: The device error log contains records of errors.
1199 Bit 7: The device self-test log contains records of errors.
1201 To test within the shell for whether or not the different bits
1203 are turned on or off, you can use the following type of con‐
1204 struction (this is bash syntax):
1205 smartstat=$(($? & 8))
1206 This looks at only at bit 3 of the exit status $? (since
1207 8=2^3). The shell variable $smartstat will be nonzero if SMART
1208 status check returned "disk failing" and zero otherwise.
1209
1212 The TapeAlert log page flags are cleared for the initiator when the
1213 page is read. This means that each alert condition is reported only
1214 once by smartctl for each initiator for each activation of the condi‐
1215 tion.
1216
1219 Bruce Allen smartmontools-support@lists.sourceforge.net
1220 University of Wisconsin - Milwaukee Physics Department
1221
1224 The following have made large contributions to smartmontools:
1225 Casper Dik (Solaris SCSI interface)
1226 Christian Franke (Windows interface and Cygwin package)
1227 Douglas Gilbert (SCSI subsystem)
1228 Guido Guenther (Autoconf/Automake packaging)
1229 Geoffrey Keating (Darwin ATA interface)
1230 Eduard Martinescu (FreeBSD interface)
1231 Frederic L. W. Meunier (Web site and Mailing list)
1232 Keiji Sawada (Solaris ATA interface)
1233 Sergey Svishchev (NetBSD interface)
1234 David Snyder and Sergey Svishchev (OpenBSD interface)
1235 Phil Williams (User interface and drive database)
1236 Yuri Dario (OS/2, eComStation interface)
1237 Shengfeng Zhou (Linux Highpoint RocketRaid interface)
1238 Many other individuals have made smaller contributions and corrections.
1239
1242 This code was derived from the smartsuite package, written by Michael
1243 Cornwell, and from the previous UCSC smartsuite package. It extends
1244 these to cover ATA-5 disks. This code was originally developed as a
1245 Senior Thesis by Michael Cornwell at the Concurrent Systems Laboratory
1246 (now part of the Storage Systems Research Center), Jack Baskin School
1247 of Engineering, University of California, Santa Cruz.
1248 http://ssrc.soe.ucsc.edu/ .
1249
1251 Please see the following web site for updates, further documentation,
1252 bug reports and patches: http://smartmontools.sourceforge.net/
1253
1256 smartd(8), badblocks(8), ide-smart(8).
1257
1259 An introductory article about smartmontools is Monitoring Hard Disks
1260 with SMART, by Bruce Allen, Linux Journal, January 2004, pages 74-77.
1261 This is http://www.linuxjournal.com/article.php?sid=6983 online.
1262 If you would like to understand better how SMART works, and what it
1264 does, a good place to start is with Sections 4.8 and 6.54 of the first
1265 volume of the ´AT Attachment with Packet Interface-7´ (ATA/ATAPI-7)
1266 specification. This documents the SMART functionality which the smart‐
1267 montools utilities provide access to. You can find Revision 4b of this
1268 document at http://www.t13.org/docs2004/d1532v1r4b-ATA-ATAPI-7.pdf .
1269 Earlier and later versions of this Specification are available from the
1270 T13 web site http://www.t13.org/ .
1271 The functioning of SMART was originally defined by the SFF-8035i revi‐
1273 sion 2 and the SFF-8055i revision 1.4 specifications. These are publi‐
1274 cations of the Small Form Factors (SFF) Committee. Links to these doc‐
1275 uments may be found in the References section of the smartmontools home
1276 page at http://smartmontools.sourceforge.net/ .
1277
1280 $Id: smartctl.8.in,v 1.90 2006/12/20 07:30:43 sxzzsf Exp $
1281smartmontools-5.37 2006/12/20 SMARTCTL(8)