]>
Commit | Line | Data |
---|---|---|
4d59bff9 GG |
1 | .ig |
2 | Copyright (C) 2002-6 Bruce Allen <smartmontools-support@lists.sourceforge.net> | |
3 | ||
4 | $Id: smartctl.8.in,v 1.83 2006/09/15 08:03:52 sxzzsf Exp $ | |
5 | ||
6 | This program is free software; you can redistribute it and/or modify it | |
7 | under the terms of the GNU General Public License as published by the Free | |
8 | Software Foundation; either version 2, or (at your option) any later | |
9 | version. | |
10 | ||
11 | You should have received a copy of the GNU General Public License (for | |
12 | example COPYING); if not, write to the Free Software Foundation, Inc., 675 | |
13 | Mass Ave, Cambridge, MA 02139, USA. | |
14 | ||
15 | This code was originally developed as a Senior Thesis by Michael Cornwell | |
16 | at the Concurrent Systems Laboratory (now part of the Storage Systems | |
17 | Research Center), Jack Baskin School of Engineering, University of | |
18 | California, Santa Cruz. http://ssrc.soe.ucsc.edu/ | |
19 | ||
20 | .. | |
21 | .TH SMARTCTL 8 CURRENT_CVS_DATE CURRENT_CVS_VERSION CURRENT_CVS_DATE | |
22 | .SH NAME | |
23 | \fBsmartctl\fP \- Control and Monitor Utility for SMART Disks | |
24 | ||
25 | .SH SYNOPSIS | |
26 | .B smartctl [options] device | |
27 | ||
28 | .SH FULL PATH | |
29 | .B /usr/local/sbin/smartctl | |
30 | ||
31 | .SH PACKAGE VERSION | |
32 | CURRENT_CVS_VERSION released CURRENT_CVS_DATE at CURRENT_CVS_TIME | |
33 | ||
34 | .SH DESCRIPTION | |
35 | \fBsmartctl\fP controls the Self\-Monitoring, Analysis and Reporting | |
36 | Technology (SMART) system built into many ATA\-3 and later ATA, IDE and | |
37 | SCSI\-3 hard drives. The purpose of SMART is to monitor the reliability | |
38 | of the hard drive and predict drive failures, and to carry out | |
39 | different types of drive self\-tests. This version of \fBsmartctl\fP | |
40 | is compatible with ATA/ATAPI\-7 and earlier standards (see REFERENCES | |
41 | below) | |
42 | ||
43 | \fBsmartctl\fP is a command line utility designed to perform SMART | |
44 | tasks such as printing the SMART self\-test and error logs, enabling | |
45 | and disabling SMART automatic testing, and initiating device | |
46 | self\-tests. Note: if the user issues a SMART command that is | |
47 | (apparently) not implemented by the device, \fBsmartctl\fP will print | |
48 | a warning message but issue the command anyway (see the \fB\-T, | |
49 | \-\-tolerance\fP option below). This should not cause problems: on | |
50 | most devices, unimplemented SMART commands issued to a drive are | |
51 | ignored and/or return an error. | |
52 | ||
53 | \fBsmartctl\fP also provides support for polling TapeAlert messages | |
54 | from SCSI tape drives and changers. | |
55 | ||
56 | The user must specify the device to be controlled or interrogated as | |
57 | the final argument to \fBsmartctl\fP. Device paths are as follows: | |
58 | .IP \fBLINUX\fP: 9 | |
59 | Use the forms \fB"/dev/hd[a\-t]"\fP for IDE/ATA | |
60 | devices, and \fB"/dev/sd[a\-z]"\fP for SCSI devices. For | |
61 | SCSI Tape Drives and Changers with TapeAlert support use the devices | |
62 | \fB"/dev/nst*"\fP and \fB"/dev/sg*"\fP. | |
63 | For SATA disks accessed with libata, use \fB"/dev/sd[a\-z]"\fP | |
64 | and append \fB"\-d ata"\fP. For disks behind 3ware controllers | |
65 | you may need \fB"/dev/sd[a\-z]"\fP or \fB"/dev/twe[0\-9]"\fP | |
66 | or \fB"/dev/twa[0\-9]"\fP: see details below. For disks behind | |
67 | HighPoint RocketRAID controllers you may need \fB"/dev/sd[a\-z]"\fP. | |
68 | More general paths (such as devfs ones) may also be specified. | |
69 | .IP \fBDARWIN\fP: 9 | |
70 | Use the forms \fB/dev/disk[0\-9]\fP or equivalently \fBdisk[0\-9]\fP or equivalently | |
71 | \fB/dev/rdisk[0\-9]\fP. Long forms are also available: please use \'\-h\' to see some | |
72 | examples. Note that there is currently no Darwin SCSI support. | |
73 | .IP \fBFREEBSD\fP: 9 | |
74 | Use the forms \fB"/dev/ad[0\-9]+"\fP for IDE/ATA | |
75 | devices and \fB"/dev/da[0\-9]+"\fP for SCSI devices. | |
76 | .IP \fBNETBSD/OPENBSD\fP: 9 | |
77 | Use the form \fB"/dev/wd[0\-9]+c"\fP for IDE/ATA | |
78 | devices. For SCSI disk and tape devices, use the device names | |
79 | \fB"/dev/sd[0\-9]+c"\fP and \fB"/dev/st[0\-9]+c"\fP respectively. | |
80 | Be sure to specify the correct "whole disk" partition letter for | |
81 | your architecture. | |
82 | .IP \fBSOLARIS\fP: 9 | |
83 | Use the forms \fB"/dev/rdsk/c?t?d?s?"\fP for IDE/ATA and SCSI disk | |
84 | devices, and \fB"/dev/rmt/*"\fP for SCSI tape devices. | |
85 | .IP \fBWINDOWS\fP: 9 | |
86 | Use the forms \fB"/dev/hd[a\-j]"\fP for IDE/ATA devices | |
87 | "\\\\.\\PhysicalDrive[0\-9]" on WinNT4/2000/XP/2003, | |
88 | and \fB"/dev/scsi[0\-9][0\-f]"\fP for SCSI devices on ASPI adapter 0\-9, ID 0\-15. | |
89 | For IDE/ATA devices on Win95/98/98SE/ME, use \fB"/dev/hd[a\-d]"\fP for standard devices | |
90 | accessed via SMARTVSD.VXD, and \fB"/dev/hd[e\-h]"\fP for additional devices | |
91 | accessed via a patched SMARTVSE.VXD (see INSTALL file for details). | |
92 | The prefix \fB"/dev/"\fP is optional. | |
93 | .IP \fBCYGWIN\fP: 9 | |
94 | See "WINDOWS" above. | |
95 | .IP \fBOS/2,eComStation\fP: 9 | |
96 | Use the form \fB"/dev/hd[a\-z]"\fP for IDE/ATA devices. | |
97 | .PP | |
98 | Based on the device path, \fBsmartctl\fP will guess the device type | |
99 | (ATA or SCSI). If necessary, the \'\-d\' option can be used to over\-ride | |
100 | this guess | |
101 | ||
102 | Note that the printed output of \fBsmartctl\fP displays most numerical | |
103 | values in base 10 (decimal), but some values are displayed in base 16 | |
104 | (hexidecimal). To distinguish them, the base 16 values are always | |
105 | displayed with a leading \fB"0x"\fP, for example: "0xff". This man | |
106 | page follows the same convention. | |
107 | ||
108 | .PP | |
109 | .SH OPTIONS | |
110 | .PP | |
111 | The options are grouped below into several categories. \fBsmartctl\fP | |
112 | will execute the corresponding commands in the order: INFORMATION, | |
113 | ENABLE/DISABLE, DISPLAY DATA, RUN/ABORT TESTS. | |
114 | ||
115 | SCSI devices only accept the options \fB\-h, \-V, \-i, \-a, \-A, \-d, | |
116 | \-s, \-S,\-H, \-t, \-C, \-l selftest, \-l error, \-r,\fP and | |
117 | \fB\-X\fP. TapeAlert devices only accept the options \fB\-h, \-V, | |
118 | \-i, \-a, \-A, \-d, \-s, \-S, \-t, \-l selftest, \-l error, \-r,\fP | |
119 | and \fB\-H\fP. | |
120 | ||
121 | Long options are not supported on all systems. Use | |
122 | .B \'smartctl \-h\' | |
123 | to see the available options. | |
124 | ||
125 | .TP | |
126 | .B SHOW INFORMATION OPTIONS: | |
127 | .TP | |
128 | .B \-h, \-\-help, \-\-usage | |
129 | Prints a usage message to STDOUT and exits. | |
130 | .TP | |
131 | .B \-V, \-\-version, \-\-copyright, \-\-license | |
132 | Prints version, copyright, license, home page and CVS\-id information | |
133 | for your copy of \fBsmartctl\fP to STDOUT and then exits. Please | |
134 | include this information if you are reporting bugs or problems. | |
135 | .TP | |
136 | .B \-i, \-\-info | |
137 | Prints the device model number, serial number, firmware version, and | |
138 | ATA Standard version/revision information. Says if the device | |
139 | supports SMART, and if so, whether SMART support is currently enabled | |
140 | or disabled. If the device supports Logical Block Address mode (LBA | |
141 | mode) print current user drive capacity in bytes. (If drive is has a | |
142 | user protected area reserved, or is "clipped", this may be smaller | |
143 | than the potential maximum drive capacity.) Indicates if the drive is | |
144 | in the smartmontools database (see \'\-v\' options below). If so, the | |
145 | drive model family may also be printed. If \'\-n\' (see below) is | |
146 | specified, the power mode of the drive is printed. | |
147 | .TP | |
148 | .B \-a, \-\-all | |
149 | Prints all SMART information about the disk, or TapeAlert information | |
150 | about the tape drive or changer. For ATA devices this is equivalent | |
151 | to | |
152 | .nf | |
153 | \'\-H \-i \-c \-A \-l error \-l selftest -l selective\' | |
154 | .fi | |
155 | and for SCSI, this is equivalent to | |
156 | .nf | |
157 | \'\-H \-i \-A \-l error \-l selftest\'. | |
158 | .fi | |
159 | Note that for ATA disks this does \fBnot\fP enable the \'\-l | |
160 | directory\' option. | |
161 | ||
162 | .TP | |
163 | .B RUN\-TIME BEHAVIOR OPTIONS: | |
164 | .TP | |
165 | .B \-q TYPE, \-\-quietmode=TYPE | |
166 | Specifies that \fBsmartctl\fP should run in one of the two quiet modes | |
167 | described here. The valid arguments to this option are: | |
168 | ||
169 | .I errorsonly | |
170 | \- only print: For the \'\-l error\' option, if nonzero, the number | |
171 | of errors recorded in the SMART error log and the power\-on time when | |
172 | they occurred; For the \'\-l selftest\' option, errors recorded in the device | |
173 | self\-test log; For the \'\-H\' option, SMART "disk failing" status or device | |
174 | Attributes (pre\-failure or usage) which failed either now or in the | |
175 | past; For the \'\-A\' option, device Attributes (pre\-failure or usage) | |
176 | which failed either now or in the past. | |
177 | ||
178 | .I silent | |
179 | \- print no output. The only way to learn about what was found is to | |
180 | use the exit status of \fBsmartctl\fP (see RETURN VALUES below). | |
181 | .TP | |
182 | .B \-d TYPE, \-\-device=TYPE | |
183 | Specifies the type of the device. The valid arguments to this option | |
184 | are \fIata\fP, \fIscsi\fP, \fIsat\fP, \fImarvell\fP, \fI3ware,N\fP, and \fIhpt,L/M\fP | |
185 | or \fIhpt,L/M/N\fP. If this option is not used then \fBsmartctl\fP will attempt to | |
186 | guess the device type from the device name. | |
187 | ||
188 | The \'sat\' device type is for ATA disks that have a SCSI to ATA | |
189 | Translation (SAT) Layer (SATL) between the disk and the operating system. | |
190 | SAT defines two ATA PASS THROUGH SCSI commands, one 12 bytes long and | |
191 | the other 16 bytes long that \fBsmartctl\fP will utilize when this device | |
192 | type is selected. The default is the 16 byte variant which can be | |
193 | overridden with either \'\-d sat,12\' or \'\-d sat,16\'. | |
194 | ||
195 | Under Linux, to look at SATA disks behind Marvell SATA controllers | |
196 | (using Marvell's \'linuxIAL\' driver rather than libata driver) use \'\-d marvell\'. Such | |
197 | controllers show up as Marvell Technology Group Ltd. SATA I or II controllers | |
198 | using lspci, or using lspci -n show a vendor ID 0x11ab and a device ID of | |
199 | either 0x5040, 0x5041, 0x5080, 0x5081, 0x6041 or 0x6081. The \'linuxIAL\' driver | |
200 | seems not (yet?) available in the Linux kernel source tree, but should be available | |
201 | from system vendors (ftp://ftp.aslab.com/ is known to provide a patch with the driver). | |
202 | ||
203 | To look at ATA disks behind 3ware SCSI RAID controllers, use syntax | |
204 | such as: | |
205 | .nf | |
206 | \fBsmartctl \-a \-d 3ware,2 /dev/sda\fP | |
207 | .fi | |
208 | .nf | |
209 | \fBsmartctl \-a \-d 3ware,0 /dev/twe0\fP | |
210 | .fi | |
211 | .nf | |
212 | \fBsmartctl \-a \-d 3ware,1 /dev/twa0\fP | |
213 | .fi | |
214 | where in the argument \fI3ware,N\fP, the integer N is the disk number | |
215 | (3ware \'port\') within the 3ware ATA RAID controller. The allowed | |
216 | values of N are from 0 to 15 inclusive. The first two forms, which | |
217 | refer to devices /dev/sda-z and /dev/twe0-15, may be used with 3ware | |
218 | series 6000, 7000, and 8000 series controllers that use the 3x-xxxx | |
219 | driver. \fBNote that the /dev/sda-z form is deprecated\fP starting | |
220 | with the Linux 2.6 kernel series and may not be supported by the Linux | |
221 | kernel in the near future. The final form, which refers to devices | |
222 | /dev/twa0-15, must be used with 3ware 9000 series controllers, which | |
223 | use the 3w-9xxx driver. | |
224 | ||
225 | Note that if the special character device nodes /dev/twa? and | |
226 | /dev/twe? do not exist, or exist with the incorrect major or minor | |
227 | numbers, smartctl will recreate them on the fly. Typically /dev/twa0 | |
228 | refers to the first 9000-series controller, /dev/twa1 refers to the | |
229 | second 9000 series controller, and so on. Likewise /dev/twe0 refers to | |
230 | the first 6/7/8000-series controller, /dev/twa1 refers to the second | |
231 | 6/7/8000 series controller, and so on. | |
232 | ||
233 | Note that for the 6/7/8000 controllers, \fBany\fP of the physical | |
234 | disks can be queried or examined using \fBany\fP of the 3ware's SCSI | |
235 | logical device /dev/sd? entries. Thus, if logical device /dev/sda is | |
236 | made up of two physical disks (3ware ports zero and one) and logical | |
237 | device /dev/sdb is made up of two other physical disks (3ware ports | |
238 | two and three) then you can examine the SMART data on \fBany\fP of the | |
239 | four physical disks using \fBeither\fP SCSI device /dev/sda \fBor\fP | |
240 | /dev/sdb. If you need to know which logical SCSI device a particular | |
241 | physical disk (3ware port) is associated with, use the dmesg or SYSLOG | |
242 | output to show which SCSI ID corresponds to a particular 3ware unit, | |
243 | and then use the 3ware CLI or 3dm tool to determine which ports | |
244 | (physical disks) correspond to particular 3ware units. | |
245 | ||
246 | If the value of N corresponds to a port that does \fBnot\fP exist on | |
247 | the 3ware controller, or to a port that does not physically have a | |
248 | disk attached to it, the behavior of \fBsmartctl\fP depends upon the | |
249 | specific controller model, firmware, Linux kernel and platform. In | |
250 | some cases you will get a warning message that the device does not | |
251 | exist. In other cases you will be presented with \'void\' data for a | |
252 | non\-existent device. | |
253 | ||
254 | Note that if the /dev/sd? addressing form is used, then older 3w\-xxxx | |
255 | drivers do not pass the "Enable Autosave" | |
256 | (\'\fB\-S on\fP\') and "Enable Automatic Offline" (\'\fB\-o on\fP\') | |
257 | commands to the disk, and produce these types of harmless syslog error | |
258 | messages instead: "\fB3w\-xxxx: tw_ioctl(): Passthru size (123392) too | |
259 | big\fP". This can be fixed by upgrading to version 1.02.00.037 or | |
260 | later of the 3w\-xxxx driver, or by applying a patch to older | |
261 | versions. See \fBhttp://smartmontools.sourceforge.net/\fP for | |
262 | instructions. Alternatively, use the character device /dev/twe0-15 interface. | |
263 | ||
264 | The selective self\-test functions (\'\-t select,A\-B\') are only supported | |
265 | using the character device interface /dev/twa0\-15 and /dev/twe0\-15. | |
266 | The necessary WRITE LOG commands can not be passed through the SCSI | |
267 | interface. | |
268 | ||
269 | .B 3ware controllers are currently ONLY supported under Linux and FreeBSD. | |
270 | ||
271 | To look at (S)ATA disks behind HighPoint RocketRAID controllers, use syntax | |
272 | such as: | |
273 | .nf | |
274 | \fBsmartctl \-a \-d hpt,1/3 /dev/sda\fP | |
275 | .fi | |
276 | or | |
277 | .nf | |
278 | \fBsmartctl \-a \-d hpt,1/2/3 /dev/sda\fP | |
279 | .fi | |
280 | where in the argument \fIhpt,L/M\fP or \fIhpt,L/M/N\fP, the integer L is the | |
281 | controller id, the integer M is the channel number, and the integer N is the | |
282 | PMPort number if it is available. The allowed values of L are from 1 to 4 | |
283 | inclusive, M are from 1 to 8 inclusive and N from 1 to 4 if PMPort available. | |
284 | Note that the /dev/sda-z form should be the device node which stands for | |
285 | the disks derived from the HighPoint RocketRAID controllers. And also | |
286 | these values are limited by the model of the HighPoint RocketRAID controller. | |
287 | ||
288 | .B HighPoint RocketRAID controllers are currently ONLY supported under Linux. | |
289 | ||
290 | .TP | |
291 | .B \-T TYPE, \-\-tolerance=TYPE | |
292 | Specifies how tolerant \fBsmartctl\fP should be of ATA and SMART command | |
293 | failures. | |
294 | ||
295 | The behavior of \fBsmartctl\fP depends upon whether the command is | |
296 | "\fBoptional\fP" or "\fBmandatory\fP". Here "\fBmandatory\fP" means | |
297 | "required by the ATA/ATAPI\-5 Specification if the device implements | |
298 | the SMART command set" and "\fBoptional\fP" means "not required by the | |
299 | ATA/ATAPI\-5 Specification even if the device implements the SMART | |
300 | command set." The "\fBmandatory\fP" ATA and SMART commands are: (1) | |
301 | ATA IDENTIFY DEVICE, (2) SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE, (3) | |
302 | SMART ENABLE/DISABLE, and (4) SMART RETURN STATUS. | |
303 | ||
304 | The valid arguments to this option are: | |
305 | ||
306 | .I normal | |
307 | \- exit on failure of any \fBmandatory\fP SMART command, and ignore | |
308 | all failures of \fBoptional\fP SMART commands. This is the default. | |
309 | Note that on some devices, issuing unimplemented optional SMART | |
310 | commands doesn\'t cause an error. This can result in misleading | |
311 | \fBsmartctl\fP messages such as "Feature X not implemented", followed | |
312 | shortly by "Feature X: enabled". In most such cases, contrary to the | |
313 | final message, Feature X is \fBnot\fP enabled. | |
314 | ||
315 | .I conservative | |
316 | \- exit on failure of any \fBoptional\fP SMART command. | |
317 | ||
318 | .I permissive | |
319 | \- ignore failure(s) of \fBmandatory\fP SMART commands. This option | |
320 | may be given more than once. Each additional use of this option will | |
321 | cause one more additional failure to be ignored. Note that the use of | |
322 | this option can lead to messages like "Feature X not implemented", | |
323 | followed shortly by "Error: unable to enable Feature X". In a few | |
324 | such cases, contrary to the final message, Feature X \fBis\fP enabled. | |
325 | ||
326 | .I verypermissive | |
327 | \- equivalent to giving a large number of \'\-T permissive\' options: | |
328 | ignore failures of \fBany number\fP of \fBmandatory\fP SMART commands. | |
329 | Please see the note above. | |
330 | ||
331 | .TP | |
332 | .B \-b TYPE, \-\-badsum=TYPE | |
333 | Specifies the action \fBsmartctl\fP should take if a checksum error is | |
334 | detected in the: (1) Device Identity Structure, (2) SMART Self\-Test | |
335 | Log Structure, (3) SMART Attribute Value Structure, (4) SMART | |
336 | Attribute Threshold Structure, or (5) ATA Error Log Structure. | |
337 | ||
338 | The valid arguments to this option are: | |
339 | ||
340 | .I warn | |
341 | \- report the incorrect checksum but carry on in spite of it. This is the | |
342 | default. | |
343 | ||
344 | .I exit | |
345 | \- exit \fBsmartctl\fP. | |
346 | ||
347 | .I ignore | |
348 | \- continue silently without issuing a warning. | |
349 | ||
350 | .TP | |
351 | .B \-r TYPE, \-\-report=TYPE | |
352 | Intended primarily to help \fBsmartmontools\fP developers understand | |
353 | the behavior of \fBsmartmontools\fP on non\-conforming or poorly | |
354 | conforming hardware. This option reports details of \fBsmartctl\fP | |
355 | transactions with the device. The option can be used multiple times. | |
356 | When used just once, it shows a record of the ioctl() transactions | |
357 | with the device. When used more than once, the detail of these | |
358 | ioctl() transactions are reported in greater detail. The valid | |
359 | arguments to this option are: | |
360 | ||
361 | .I ioctl | |
362 | \- report all ioctl() transactions. | |
363 | ||
364 | .I ataioctl | |
365 | \- report only ioctl() transactions with ATA devices. | |
366 | ||
367 | .I scsiioctl | |
368 | \- report only ioctl() transactions with SCSI devices. Invoking this once | |
369 | shows the SCSI commands in hex and the corresponding status. Invoking | |
370 | it a second time adds a hex listing of the first 64 bytes of data send to, | |
371 | or received from the device. | |
372 | ||
373 | Any argument may include a positive integer to specify the level of detail | |
374 | that should be reported. The argument should be followed by a comma then | |
375 | the integer with no spaces. For example, | |
376 | .I ataioctl,2 | |
377 | The default | |
378 | level is 1, so \'\-r ataioctl,1\' and \'\-r ataioctl\' are equivalent. | |
379 | ||
380 | .TP | |
381 | .B \-n POWERMODE, \-\-nocheck=POWERMODE | |
382 | Specifieds if \fBsmartctl\fP should exit before performing any checks | |
383 | when the device is in a low\-power mode. It may be used to prevent a disk | |
384 | from being spun\-up by \fBsmartctl\fP. The power mode is ignored by | |
385 | default. The allowed values of POWERMODE are: | |
386 | ||
387 | .I never | |
388 | \- check the device always, but print the power mode if \'\-i\' is | |
389 | specified. | |
390 | ||
391 | .I sleep | |
392 | \- check the device unless it is in SLEEP mode. | |
393 | ||
394 | .I standby | |
395 | \- check the device unless it is in SLEEP or STANDBY mode. In | |
396 | these modes most disks are not spinning, so if you want to prevent | |
397 | a disk from spinning up, this is probably what you want. | |
398 | ||
399 | .I idle | |
400 | \- check the device unless it is in SLEEP, STANDBY or IDLE mode. | |
401 | In the IDLE state, most disks are still spinning, so this is probably | |
402 | not what you want. | |
403 | ||
404 | .TP | |
405 | .B SMART FEATURE ENABLE/DISABLE COMMANDS: | |
406 | .IP | |
407 | .B Note: | |
408 | if multiple options are used to both enable and disable a | |
409 | feature, then | |
410 | .B both | |
411 | the enable and disable commands will be issued. The enable command | |
412 | will always be issued | |
413 | .B before | |
414 | the corresponding disable command. | |
415 | .TP | |
416 | .B \-s VALUE, \-\-smart=VALUE | |
417 | Enables or disables SMART on device. The valid arguments to | |
418 | this option are \fIon\fP and \fIoff\fP. Note that the command \'\-s on\' | |
419 | (perhaps used with with the \'\-o on\' and \'\-S on\' options) should be placed | |
420 | in a start\-up script for your machine, for example in rc.local or rc.sysinit. | |
421 | In principle the SMART feature settings are preserved over | |
422 | power\-cycling, but it doesn\'t hurt to be sure. It is not necessary (or | |
423 | useful) to enable SMART to see the TapeAlert messages. | |
424 | .TP | |
425 | .B \-o VALUE, \-\-offlineauto=VALUE | |
426 | Enables or disables SMART automatic offline test, which scans the drive | |
427 | every four hours for disk defects. This command can be given during normal | |
428 | system operation. The valid arguments to this option are \fIon\fP | |
429 | and \fIoff\fP. | |
430 | ||
431 | Note that the SMART automatic offline test command is listed as | |
432 | "Obsolete" in every version of the ATA and ATA/ATAPI Specifications. | |
433 | It was originally part of the SFF\-8035i Revision 2.0 specification, | |
434 | but was never part of any ATA specification. However it is | |
435 | implemented and used by many vendors. [Good documentation can be found | |
436 | in IBM\'s Official Published Disk Specifications. For example the IBM | |
437 | Travelstar 40GNX Hard Disk Drive Specifications (Revision 1.1, 22 | |
438 | April 2002, Publication # 1541, Document S07N\-7715\-02) page 164. You | |
439 | can also read the SFF\-8035i Specification \-\- see REFERENCES below.] | |
440 | You can tell if automatic offline testing is supported by seeing if | |
441 | this command enables and disables it, as indicated by the \'Auto | |
442 | Offline Data Collection\' part of the SMART capabilities report | |
443 | (displayed with \'\-c\'). | |
444 | ||
445 | SMART provides \fBthree\fP basic categories of testing. The | |
446 | \fBfirst\fP category, called "online" testing, has no effect on the | |
447 | performance of the device. It is turned on by the \'\-s on\' option. | |
448 | ||
449 | The \fBsecond\fP category of testing is called "offline" testing. This | |
450 | type of test can, in principle, degrade the device performance. The | |
451 | \'\-o on\' option causes this offline testing to be carried out, | |
452 | automatically, on a regular scheduled basis. Normally, the disk will | |
453 | suspend offline testing while disk accesses are taking place, and then | |
454 | automatically resume it when the disk would otherwise be idle, so in | |
455 | practice it has little effect. Note that a one\-time offline test can | |
456 | also be carried out immediately upon receipt of a user command. See | |
457 | the \'\-t offline\' option below, which causes a one\-time offline test | |
458 | to be carried out immediately. | |
459 | ||
460 | The choice (made by the SFF\-8035i and ATA specification authors) of | |
461 | the word \fItesting\fP for these first two categories is unfortunate, | |
462 | and often leads to confusion. In fact these first two categories of | |
463 | online and offline testing could have been more accurately described | |
464 | as online and offline \fBdata collection\fP. | |
465 | ||
466 | The results of this automatic or immediate offline testing (data | |
467 | collection) are reflected in the values of the SMART Attributes. | |
468 | Thus, if problems or errors are detected, the values of these | |
469 | Attributes will go below their failure thresholds; some types of | |
470 | errors may also appear in the SMART error log. These are visible with | |
471 | the \'\-A\' and \'\-l error\' options respectively. | |
472 | ||
473 | Some SMART attribute values are updated only during off\-line data | |
474 | collection activities; the rest are updated during normal operation of | |
475 | the device or during both normal operation and off\-line testing. The | |
476 | Attribute value table produced by the \'\-A\' option indicates this in | |
477 | the UPDATED column. Attributes of the first type are labeled | |
478 | "Offline" and Attributes of the second type are labeled "Always". | |
479 | ||
480 | The \fBthird\fP category of testing (and the \fIonly\fP category for | |
481 | which the word \'testing\' is really an appropriate choice) is "self" | |
482 | testing. This third type of test is only performed (immediately) when | |
483 | a command to run it is issued. The \'\-t\' and \'\-X\' options can be | |
484 | used to carry out and abort such self\-tests; please see below for | |
485 | further details. | |
486 | ||
487 | Any errors detected in the self testing will be shown in the | |
488 | SMART self\-test log, which can be examined using the \'\-l selftest\' | |
489 | option. | |
490 | ||
491 | \fBNote:\fP in this manual page, the word \fB"Test"\fP is used in | |
492 | connection with the second category just described, e.g. for the | |
493 | "offline" testing. The words \fB"Self\-test"\fP are used in | |
494 | connection with the third category. | |
495 | .TP | |
496 | .B \-S VALUE, \-\-saveauto=VALUE | |
497 | Enables or disables SMART autosave of device vendor\-specific | |
498 | Attributes. The valid arguments to this option are \fIon\fP | |
499 | and \fIoff\fP. Note that this feature is preserved across disk power | |
500 | cycles, so you should only need to issue it once. | |
501 | ||
502 | For SCSI devices this toggles the value of the Global Logging Target | |
503 | Save Disabled (GLTSD) bit in the Control Mode Page. Some disk | |
504 | manufacturers set this bit by default. This prevents error counters, | |
505 | power\-up hours and other useful data from being placed in non\-volatile | |
506 | storage, so these values may be reset to zero the next time the device | |
507 | is power\-cycled. If the GLTSD bit is set then \'smartctl \-a\' will | |
508 | issue a warning. Use \fIon\fP to clear the GLTSD bit and thus enable | |
509 | saving counters to non\-volatile storage. For extreme streaming\-video | |
510 | type applications you might consider using \fIoff\fP to set the GLTSD | |
511 | bit. | |
512 | ||
513 | .TP | |
514 | .B SMART READ AND DISPLAY DATA OPTIONS: | |
515 | .TP | |
516 | .B \-H, \-\-health | |
517 | Check: Ask the device to report its SMART health status or pending | |
518 | TapeAlert messages. SMART status is based on | |
519 | information that it has gathered from online and offline | |
520 | tests, which were used to determine/update its | |
521 | SMART vendor\-specific Attribute values. TapeAlert status is obtained | |
522 | by reading the TapeAlert log page. | |
523 | ||
524 | If the device reports failing health status, this means | |
525 | .B either | |
526 | that the device has already failed, | |
527 | .B or | |
528 | that it is predicting its own failure within the next 24 hours. If | |
529 | this happens, use the \'\-a\' option to get more information, and | |
530 | .B get your data off the disk and someplace safe as soon as you can. | |
531 | .TP | |
532 | .B \-c, \-\-capabilities | |
533 | Prints only the generic SMART capabilities. These show | |
534 | what SMART features are implemented and how the device will | |
535 | respond to some of the different SMART commands. For example it | |
536 | shows if the device logs errors, if it supports offline surface | |
537 | scanning, and so on. If the device can carry out self\-tests, this | |
538 | option also shows the estimated time required to run those tests. | |
539 | ||
540 | Note that the time required to run the Self\-tests (listed in minutes) | |
541 | are fixed. However the time required to run the Immediate Offline | |
542 | Test (listed in seconds) is variable. This means that if you issue a | |
543 | command to perform an Immediate Offline test with the \'\-t offline\' option, | |
544 | then the time may jump to a larger value and then count down as the | |
545 | Immediate Offline Test is carried out. Please see REFERENCES below | |
546 | for further information about the the flags and capabilities described | |
547 | by this option. | |
548 | .TP | |
549 | .B \-A, \-\-attributes | |
550 | Prints only the vendor specific SMART Attributes. The Attributes are | |
551 | numbered from 1 to 253 and have specific names and ID numbers. For | |
552 | example Attribute 12 is "power cycle count": how many times has the | |
553 | disk been powered up. | |
554 | ||
555 | Each Attribute has a "Raw" value, printed under the heading | |
556 | "RAW_VALUE", and a "Normalized" value printed under the heading | |
557 | "VALUE". [Note: \fBsmartctl\fP prints these values in base\-10.] In | |
558 | the example just given, the "Raw Value" for Attribute 12 would be the | |
559 | actual number of times that the disk has been power\-cycled, for | |
560 | example 365 if the disk has been turned on once per day for exactly | |
561 | one year. Each vendor uses their own algorithm to convert this "Raw" | |
562 | value to a "Normalized" value in the range from 1 to 254. Please keep | |
563 | in mind that \fBsmartctl\fP only reports the different Attribute | |
564 | types, values, and thresholds as read from the device. It does | |
565 | \fBnot\fP carry out the conversion between "Raw" and "Normalized" | |
566 | values: this is done by the disk\'s firmware. | |
567 | ||
568 | The conversion from Raw value to a quantity with physical units is | |
569 | not specified by the SMART standard. In most cases, the values printed | |
570 | by \fBsmartctl\fP are sensible. For example the temperature Attribute | |
571 | generally has its raw value equal to the temperature in Celsius. | |
572 | However in some cases vendors use unusual conventions. For example | |
573 | the Hitachi disk on my laptop reports its power\-on hours in minutes, | |
574 | not hours. Some IBM disks track three temperatures rather than one, in | |
575 | their raw values. And so on. | |
576 | ||
577 | Each Attribute also has a Threshold value (whose range is 0 to 255) | |
578 | which is printed under the heading "THRESH". If the Normalized value | |
579 | is \fBless than or equal to\fP the Threshold value, then the Attribute | |
580 | is said to have failed. If the Attribute is a pre\-failure Attribute, | |
581 | then disk failure is imminent. | |
582 | ||
583 | Each Attribute also has a "Worst" value shown under the heading | |
584 | "WORST". This is the smallest (closest to failure) value that the | |
585 | disk has recorded at any time during its lifetime when SMART was | |
586 | enabled. [Note however that some vendors firmware may actually | |
587 | \fBincrease\fP the "Worst" value for some "rate\-type" Attributes.] | |
588 | ||
589 | The Attribute table printed out by \fBsmartctl\fP also shows the | |
590 | "TYPE" of the Attribute. Attributes are one of two possible types: | |
591 | Pre\-failure or Old age. Pre\-failure Attributes are ones which, if | |
592 | less than or equal to their threshold values, indicate pending disk | |
593 | failure. Old age, or usage Attributes, are ones which indicate | |
594 | end\-of\-product life from old\-age or normal aging and wearout, if | |
595 | the Attribute value is less than or equal to the threshold. \fBPlease | |
596 | note\fP: the fact that an Attribute is of type 'Pre\-fail' does | |
597 | \fBnot\fP mean that your disk is about to fail! It only has this | |
598 | meaning if the Attribute\'s current Normalized value is less than or | |
599 | equal to the threshold value. | |
600 | ||
601 | If the Attribute\'s current Normalized value is less than or equal to | |
602 | the threshold value, then the "WHEN_FAILED" column will display | |
603 | "FAILING_NOW". If not, but the worst recorded value is less than or | |
604 | equal to the threshold value, then this column will display | |
605 | "In_the_past". If the "WHEN_FAILED" column has no entry (indicated by | |
606 | a dash: \'\-\') then this Attribute is OK now (not failing) and has | |
607 | also never failed in the past. | |
608 | ||
609 | The table column labeled "UPDATED" shows if the SMART Attribute values | |
610 | are updated during both normal operation and off\-line testing, or | |
611 | only during offline testing. The former are labeled "Always" and the | |
612 | latter are labeled "Offline". | |
613 | ||
614 | So to summarize: the Raw Attribute values are the ones that might have | |
615 | a real physical interpretation, such as "Temperature Celsius", | |
616 | "Hours", or "Start\-Stop Cycles". Each manufacturer converts these, | |
617 | using their detailed knowledge of the disk\'s operations and failure | |
618 | modes, to Normalized Attribute values in the range 1\-254. The | |
619 | current and worst (lowest measured) of these Normalized Attribute | |
620 | values are stored on the disk, along with a Threshold value that the | |
621 | manufacturer has determined will indicate that the disk is going to | |
622 | fail, or that it has exceeded its design age or aging limit. | |
623 | \fBsmartctl\fP does \fBnot\fP calculate any of the Attribute values, | |
624 | thresholds, or types, it merely reports them from the SMART data on | |
625 | the device. | |
626 | ||
627 | Note that starting with ATA/ATAPI\-4, revision 4, the meaning of these | |
628 | Attribute fields has been made entirely vendor\-specific. However most | |
629 | ATA/ATAPI\-5 disks seem to respect their meaning, so we have retained | |
630 | the option of printing the Attribute values. | |
631 | ||
632 | For SCSI devices the "attributes" are obtained from the temperature | |
633 | and start-stop cycle counter log pages. Certain vendor specific | |
634 | attributes are listed if recognised. The attributes are output in a | |
635 | relatively free format (compared with ATA disk attributes). | |
636 | .TP | |
637 | .B \-l TYPE, \-\-log=TYPE | |
638 | Prints either the SMART Error Log, the SMART Self\-Test Log, the SMART | |
639 | Selective Self\-Test Log [ATA only], or the Log Directory [ATA only]. | |
640 | The valid arguments to this option are: | |
641 | ||
642 | .I error | |
643 | \- prints only the SMART error log. SMART disks maintain a log of the | |
644 | most recent five non\-trivial errors. For each of these errors, the | |
645 | disk power\-on lifetime at which the error occurred is recorded, as is | |
646 | the device status (idle, standby, etc) at the time of the error. For | |
647 | some common types of errors, the Error Register (ER) and Status | |
648 | Register (SR) values are decoded and printed as text. The meanings of these | |
649 | are: | |
650 | .nf | |
651 | \fBABRT\fP: Command \fBAB\fPo\fBRT\fPed | |
652 | \fBAMNF\fP: \fBA\fPddress \fBM\fPark \fBN\fPot \fBF\fPound | |
653 | \fBCCTO\fP: \fBC\fPommand \fBC\fPompletion \fBT\fPimed \fBO\fPut | |
654 | \fBEOM\fP: \fBE\fPnd \fBO\fPf \fBM\fPedia | |
655 | \fBICRC\fP: \fBI\fPnterface \fBC\fPyclic \fBR\fPedundancy \fBC\fPode (CRC) error | |
656 | \fBIDNF\fP: \fBID\fPentity \fBN\fPot \fBF\fPound | |
657 | \fBILI\fP: (packet command\-set specific) | |
658 | \fBMC\fP: \fBM\fPedia \fBC\fPhanged | |
659 | \fBMCR\fP: \fBM\fPedia \fBC\fPhange \fBR\fPequest | |
660 | \fBNM\fP: \fBN\fPo \fBM\fPedia | |
661 | \fBobs\fP: \fBobs\fPolete | |
662 | \fBTK0NF\fP: \fBT\fPrac\fBK 0 N\fPot \fBF\fPound | |
663 | \fBUNC\fP: \fBUNC\fPorrectable Error in Data | |
664 | \fBWP\fP: Media is \fBW\fPrite \fBP\fProtected | |
665 | .fi | |
666 | In addition, up to the last five commands that preceded the error are | |
667 | listed, along with a timestamp measured from the start of the | |
668 | corresponding power cycle. This is displayed in the form | |
669 | Dd+HH:MM:SS.msec where D is the number of days, HH is hours, MM is | |
670 | minutes, SS is seconds and msec is milliseconds. [Note: this time | |
671 | stamp wraps after 2^32 milliseconds, or 49 days 17 hours 2 minutes and | |
672 | 47.296 seconds.] The key ATA disk registers are also recorded in the | |
673 | log. The final column of the error log is a text\-string description | |
674 | of the ATA command defined by the Command Register (CR) and Feature | |
675 | Register (FR) values. Commands that are obsolete in the most current | |
676 | (ATA\-7) spec are listed like this: \fBREAD LONG (w/ retry) [OBS\-4]\fP, | |
677 | indicating that the command became obsolete with or in the ATA\-4 | |
678 | specification. Similarly, the notation \fB[RET\-\fP\fIN\fP\fB]\fP is | |
679 | used to indicate that a command was retired in the ATA\-\fIN\fP | |
680 | specification. Some commands are not defined in any version of the | |
681 | ATA specification but are in common use nonetheless; these are marked | |
682 | \fB[NS]\fP, meaning non\-standard. | |
683 | ||
684 | The ATA Specification (ATA\-5 Revision 1c, Section 8.41.6.8.2) says: | |
685 | \fB"Error log structures shall include UNC errors, IDNF errors for | |
686 | which the address requested was valid, servo errors, write fault | |
687 | errors, etc. Error log data structures shall not include errors | |
688 | attributed to the receipt of faulty commands such as command codes not | |
689 | implemented by the device or requests with invalid parameters or | |
690 | invalid addresses."\fP The definitions of these terms are: | |
691 | .br | |
692 | \fBUNC\fP (\fBUNC\fPorrectable): data is uncorrectable. This refers | |
693 | to data which has been read from the disk, but for which the Error | |
694 | Checking and Correction (ECC) codes are inconsistent. In effect, this | |
695 | means that the data can not be read. | |
696 | .br | |
697 | \fBIDNF\fP (\fBID N\fPot \fBF\fPound): user\-accessible address could | |
698 | not be found. For READ LOG type commands, \fBIDNF\fP can also indicate | |
699 | that a device data log structure checksum was incorrect. | |
700 | ||
701 | If the command that caused the error was a READ or WRITE command, then | |
702 | the Logical Block Address (LBA) at which the error occurred will be | |
703 | printed in base 10 and base 16. The LBA is a linear address, which | |
704 | counts 512\-byte sectors on the disk, starting from zero. (Because of | |
705 | the limitations of the SMART error log, if the LBA is greater than | |
706 | 0xfffffff, then either no error log entry will be made, or the error | |
707 | log entry will have an incorrect LBA. This may happen for drives with | |
708 | a capacity greater than 128 GiB or 137 GB.) On Linux systems the | |
709 | smartmontools web page has instructions about how to convert the LBA | |
710 | address to the name of the disk file containing the erroneous disk | |
711 | sector. | |
712 | ||
713 | Please note that some manufacturers \fBignore\fP the ATA | |
714 | specifications, and make entries in the error log if the device | |
715 | receives a command which is not implemented or is not valid. | |
716 | ||
717 | .I error [SCSI] | |
718 | \- prints the error counter log pages for reads, write and verifies. | |
719 | The verify row is only output if it has an element other than zero. | |
720 | ||
721 | .I selftest | |
722 | \- prints the SMART self\-test log. The disk maintains a self\-test log | |
723 | showing the results of the self tests, which can be run using the | |
724 | \'\-t\' option described below. For each of the most recent | |
725 | twenty\-one self\-tests, the log shows the type of test (short or | |
726 | extended, off\-line or captive) and the final status of the test. If | |
727 | the test did not complete successfully, then the percentage of the | |
728 | test remaining is shown. The time at which the test took place, | |
729 | measured in hours of disk lifetime, is also printed. If any errors | |
730 | were detected, the Logical Block Address (LBA) of the first error is | |
731 | printed in decimal notation. On Linux systems the smartmontools | |
732 | web page has instructions about how to convert this LBA address to the | |
733 | name of the disk file containing the erroneous block. | |
734 | ||
735 | .I selftest [SCSI] | |
736 | \- the self\-test log for a SCSI device has a slightly different format | |
737 | than for an ATA device. For each of the most recent twenty | |
738 | self\-tests, it shows the type of test and the status (final or in | |
739 | progress) of the test. SCSI standards use the terms "foreground" and | |
740 | "background" (rather than ATA\'s corresponding "captive" and | |
741 | "off\-line") and "short" and "long" (rather than ATA\'s corresponding | |
742 | "short" and "extended") to describe the type of the test. The printed | |
743 | segment number is only relevant when a test fails in the third or | |
744 | later test segment. It identifies the test that failed and consists | |
745 | of either the number of the segment that failed during the test, or | |
746 | the number of the test that failed and the number of the segment in | |
747 | which the test was run, using a vendor\-specific method of putting both | |
748 | numbers into a single byte. The Logical Block Address (LBA) of the | |
749 | first error is printed in hexadecimal notation. On Linux systems the | |
750 | smartmontools web page has instructions about how to convert this LBA | |
751 | address to the name of the disk file containing the erroneous block. | |
752 | If provided, the SCSI Sense Key (SK), Additional Sense Code (ASC) and | |
753 | Additional Sense Code Qualifier (ASQ) are also printed. The self tests | |
754 | can be run using the \'\-t\' option described below (using the ATA | |
755 | test terminology). | |
756 | ||
757 | .I selective [ATA] | |
758 | \- Some ATA\-7 disks (example: Maxtor) also maintain a selective | |
759 | self\-test log. Please see the \'\-t select\' option below for a | |
760 | description of selective self\-tests. The selective self\-test log | |
761 | shows the start/end Logical Block Addresses (LBA) of each of the five | |
762 | test spans, and their current test status. If the span is being | |
763 | tested or the remainder of the disk is being read\-scanned, the | |
764 | current 65536\-sector block of LBAs being tested is also displayed. | |
765 | The selective self\-test log also shows if a read\-scan of the | |
766 | remainder of the disk will be carried out after the selective | |
767 | self\-test has completed (see \'\-t afterselect\' option) and the time | |
768 | delay before restarting this read\-scan if it is interrupted (see | |
769 | \'\-t pending\' option). This is a new smartmontools feature; please | |
770 | report unusual or incorrect behavior to the smartmontools\-support | |
771 | mailing list. | |
772 | ||
773 | .I directory | |
774 | \- if the device supports the General Purpose Logging feature set | |
775 | (ATA\-6 and ATA\-7 only) then this prints the Log Directory (the log at | |
776 | address 0). The Log Directory shows what logs are available and their | |
777 | length in sectors (512 bytes). The contents of the logs at address 1 | |
778 | [Summary SMART error log] and at address 6 [SMART self\-test log] may | |
779 | be printed using the previously\-described | |
780 | .I error | |
781 | and | |
782 | .I selftest | |
783 | arguments to this option. [Please note: this is a new, experimental | |
784 | feature. We would like to add support for printing the contents of | |
785 | extended and comprehensive SMART self\-test and error logs. If your | |
786 | disk supports these, and you would like to assist, please contact the | |
787 | \fBsmartmontools\fP developers.] | |
788 | ||
789 | .TP | |
790 | .B \-v N,OPTION, \-\-vendorattribute=N,OPTION | |
791 | Sets a vendor\-specific display OPTION for Attribute N. This option | |
792 | may be used multiple times. Valid arguments to this option are: | |
793 | ||
794 | .I help | |
795 | \- Prints (to STDOUT) a list of all valid arguments to this option, | |
796 | then exits. | |
797 | ||
798 | .I 9,minutes | |
799 | \- Raw Attribute number 9 is power\-on time in minutes. Its raw value | |
800 | will be displayed in the form "Xh+Ym". Here X is hours, and Y is | |
801 | minutes in the range 0\-59 inclusive. Y is always printed with two | |
802 | digits, for example "06" or "31" or "00". | |
803 | ||
804 | .I 9,seconds | |
805 | \- Raw Attribute number 9 is power\-on time in seconds. Its raw value | |
806 | will be displayed in the form "Xh+Ym+Zs". Here X is hours, Y is | |
807 | minutes in the range 0\-59 inclusive, and Z is seconds in the range | |
808 | 0\-59 inclusive. Y and Z are always printed with two digits, for | |
809 | example "06" or "31" or "00". | |
810 | ||
811 | .I 9,halfminutes | |
812 | \- Raw Attribute number 9 is power\-on time, measured in units of 30 | |
813 | seconds. This format is used by some Samsung disks. Its raw value | |
814 | will be displayed in the form "Xh+Ym". Here X is hours, and Y is | |
815 | minutes in the range 0\-59 inclusive. Y is always printed with two | |
816 | digits, for example "06" or "31" or "00". | |
817 | ||
818 | .I 9,temp | |
819 | \- Raw Attribute number 9 is the disk temperature in Celsius. | |
820 | ||
821 | .I 192,emergencyretractcyclect | |
822 | \- Raw Attribute number 192 is the Emergency Retract Cycle Count. | |
823 | ||
824 | .I 193,loadunload | |
825 | \- Raw Attribute number 193 contains two values. The first is the | |
826 | number of load cycles. The second is the number of unload cycles. | |
827 | The difference between these two values is the number of times that | |
828 | the drive was unexpectedly powered off (also called an emergency | |
829 | unload). As a rule of thumb, the mechanical stress created by one | |
830 | emergency unload is equivalent to that created by one hundred normal | |
831 | unloads. | |
832 | ||
833 | .I 194,10xCelsius | |
834 | \- Raw Attribute number 194 is ten times the disk temperature in | |
835 | Celsius. This is used by some Samsung disks (example: model SV1204H | |
836 | with RK100\-13 firmware). | |
837 | ||
838 | .I 194,unknown | |
839 | \- Raw Attribute number 194 is NOT the disk temperature, and its | |
840 | interpretation is unknown. This is primarily useful for the \-P | |
841 | (presets) option. | |
842 | ||
843 | .I 198,offlinescanuncsectorct | |
844 | \- Raw Attribute number 198 is the Offline Scan UNC Sector Count. | |
845 | ||
846 | .I 200,writeerrorcount | |
847 | \- Raw Attribute number 200 is the Write Error Count. | |
848 | ||
849 | .I 201,detectedtacount | |
850 | \- Raw Attribute number 201 is the Detected TA Count. | |
851 | ||
852 | .I 220,temp | |
853 | \- Raw Attribute number 220 is the disk temperature in Celsius. | |
854 | ||
855 | Note: a table of hard drive models, listing which Attribute | |
856 | corresponds to temperature, can be found at: | |
857 | \fBhttp://www.guzu.net/linux/hddtemp.db\fP | |
858 | ||
859 | .I N,raw8 | |
860 | \- Print the Raw value of Attribute N as six 8\-bit unsigned base\-10 | |
861 | integers. This may be useful for decoding the meaning of the Raw | |
862 | value. The form \'N,raw8\' prints Raw values for ALL Attributes in this | |
863 | form. The form (for example) \'123,raw8\' only prints the Raw value for | |
864 | Attribute 123 in this form. | |
865 | ||
866 | .I N,raw16 | |
867 | \- Print the Raw value of Attribute N as three 16\-bit unsigned base\-10 | |
868 | integers. This may be useful for decoding the meaning of the Raw | |
869 | value. The form \'N,raw16\' prints Raw values for ALL Attributes in this | |
870 | form. The form (for example) \'123,raw16\' only prints the Raw value for | |
871 | Attribute 123 in this form. | |
872 | ||
873 | .I N,raw48 | |
874 | \- Print the Raw value of Attribute N as a 48\-bit unsigned base\-10 | |
875 | integer. This may be useful for decoding the meaning of the Raw | |
876 | value. The form \'N,raw48\' prints Raw values for ALL Attributes in | |
877 | this form. The form (for example) \'123,raw48\' only prints the Raw | |
878 | value for Attribute 123 in this form. | |
879 | ||
880 | .TP | |
881 | .B \-F TYPE, \-\-firmwarebug=TYPE | |
882 | Modifies the behavior of \fBsmartctl\fP to compensate for some known | |
883 | and understood device firmware bug. The arguments to this option are | |
884 | exclusive, so that only the final option given is used. The valid | |
885 | values are: | |
886 | ||
887 | .I none | |
888 | \- Assume that the device firmware obeys the ATA specifications. This | |
889 | is the default, unless the device has presets for \'\-F\' in the | |
890 | device database (see note below). | |
891 | ||
892 | .I samsung | |
893 | \- In some Samsung disks (example: model SV4012H Firmware Version: | |
894 | RM100\-08) some of the two\- and four\-byte quantities in the SMART data | |
895 | structures are byte\-swapped (relative to the ATA specification). | |
896 | Enabling this option tells \fBsmartctl\fP to evaluate these quantities | |
897 | in byte\-reversed order. Some signs that your disk needs this option | |
898 | are (1) no self\-test log printed, even though you have run self\-tests; | |
899 | (2) very large numbers of ATA errors reported in the ATA error log; | |
900 | (3) strange and impossible values for the ATA error log timestamps. | |
901 | ||
902 | .I samsung2 | |
903 | \- In more recent Samsung disks (firmware revisions ending in "\-23") | |
904 | the number of ATA errors reported is byte swapped. Enabling this | |
905 | option tells \fBsmartctl\fP to evaluate this quantity in | |
906 | byte\-reversed order. An indication that your Samsung disk needs this | |
907 | option is that the self-test log is printed correctly, but there are a | |
908 | very large number of errors in the SMART error log. This is because | |
909 | the error count is byte swapped. Thus a disk with five errors | |
910 | (0x0005) will appear to have 20480 errors (0x5000). | |
911 | ||
912 | Note that an explicit \'\-F\' option on the command line will | |
913 | over\-ride any preset values for \'\-F\' (see the \'\-P\' option | |
914 | below). | |
915 | ||
916 | .TP | |
917 | .B \-P TYPE, \-\-presets=TYPE | |
918 | Specifies whether \fBsmartctl\fP should use any preset options that | |
919 | are available for this drive. By default, if the drive is recognized | |
920 | in the \fBsmartmontools\fP database, then the presets are used. | |
921 | ||
922 | \fBsmartctl\fP can automatically set appropriate options for known | |
923 | drives. For example, the Maxtor 4D080H4 uses Attribute 9 to stores | |
924 | power\-on time in minutes whereas most drives use that Attribute to | |
925 | store the power\-on time in hours. The command\-line option \'\-v | |
926 | 9,minutes\' ensures that \fBsmartctl\fP correctly interprets Attribute | |
927 | 9 in this case, but that option is preset for the Maxtor 4D080H4 and | |
928 | so need not be specified by the user on the \fBsmartctl\fP command | |
929 | line. | |
930 | ||
931 | The argument | |
932 | .I show | |
933 | will show any preset options for your drive and the argument | |
934 | .I showall | |
935 | will show all known drives in the \fBsmartmontools\fP database, along | |
936 | with their preset options. If there are no presets for your drive and | |
937 | you think there should be (for example, a \-v or \-F option is needed | |
938 | to get \fBsmartctl\fP to display correct values) then please contact | |
939 | the \fBsmartmontools\fP developers so that this information can be | |
940 | added to the \fBsmartmontools\fP database. Contact information is at the | |
941 | end of this man page. | |
942 | ||
943 | The valid arguments to this option are: | |
944 | ||
945 | .I use | |
946 | \- if a drive is recognized, then use the stored presets for it. This | |
947 | is the default. Note that presets will NOT over\-ride additional | |
948 | Attribute interpretation (\'\-v N,something\') command\-line options or | |
949 | explicit \'\-F\' command\-line options.. | |
950 | ||
951 | .I ignore | |
952 | \- do not use presets. | |
953 | ||
954 | .I show | |
955 | \- show if the drive is recognized in the database, and if so, its | |
956 | presets, then exit. | |
957 | ||
958 | .I showall | |
959 | \- list all recognized drives, and the presets that are set for them, | |
960 | then exit. | |
961 | ||
962 | The \'\-P showall\' option takes up to two optional arguments to | |
963 | match a specific drive type and firmware version. The command: | |
964 | .nf | |
965 | smartctl \-P showall | |
966 | .fi | |
967 | lists all entries, the command: | |
968 | .nf | |
969 | smartctl \-P showall \'MODEL\' | |
970 | .fi | |
971 | lists all entries matching MODEL, and the command: | |
972 | .nf | |
973 | smartctl \-P showall \'MODEL\' \'FIRMWARE\' | |
974 | .fi | |
975 | lists all entries for this MODEL and a specific FIRMWARE version. | |
976 | ||
977 | .TP | |
978 | .B SMART RUN/ABORT OFFLINE TEST AND SELF\-TEST OPTIONS: | |
979 | .TP | |
980 | .B \-t TEST, \-\-test=TEST | |
981 | Executes TEST immediately. The \'\-C\' option can be used in | |
982 | conjunction with this option to run the short or long (and also for | |
983 | ATA devices, selective or conveyance) self\-tests in captive mode | |
984 | (known as "foreground mode" for SCSI devices). Note that only one | |
985 | test type can be run at a time, so only one test type should be | |
986 | specified per command line. Note also that if a computer is shutdown | |
987 | or power cycled during a self\-test, no harm should result. The | |
988 | self\-test will either be aborted or will resume automatically. | |
989 | ||
990 | The valid arguments to this option are: | |
991 | ||
992 | .I offline | |
993 | \- runs SMART Immediate Offline Test. This immediately | |
994 | starts the test described above. This command can be given during | |
995 | normal system operation. The effects of this test are visible only in | |
996 | that it updates the SMART Attribute values, and if errors are | |
997 | found they will appear in the SMART error log, visible with the \'\-l error\' | |
998 | option. [In the case of SCSI devices runs the default self test in | |
999 | foreground. No entry is placed in the self test log.] | |
1000 | ||
1001 | If the \'\-c\' option to \fBsmartctl\fP shows that the device has the | |
1002 | "Suspend Offline collection upon new command" capability then you can | |
1003 | track the progress of the Immediate Offline test using the \'\-c\' | |
1004 | option to \fBsmartctl\fP. If the \'\-c\' option show that the device | |
1005 | has the "Abort Offline collection upon new command" capability then | |
1006 | most commands will abort the Immediate Offline Test, so you should not | |
1007 | try to track the progress of the test with \'\-c\', as it will abort | |
1008 | the test. | |
1009 | ||
1010 | .I short | |
1011 | \- runs SMART Short Self Test (usually under ten minutes). | |
1012 | [Note: in the case of SCSI devices, | |
1013 | this command option runs the "Background short" self\-test.] | |
1014 | This command can be given during normal system operation (unless run in | |
1015 | captive mode \- see the \'\-C\' option below). This is a | |
1016 | test in a different category than the immediate or automatic offline | |
1017 | tests. The "Self" tests check the electrical and mechanical | |
1018 | performance as well as the read performance of the disk. Their | |
1019 | results are reported in the Self Test Error Log, readable with | |
1020 | the \'\-l selftest\' option. Note that on some disks the progress of the | |
1021 | self\-test can be monitored by watching this log during the self\-test; with other disks | |
1022 | use the \'\-c\' option to monitor progress. | |
1023 | ||
1024 | .I long | |
1025 | \- runs SMART Extended Self Test (tens of minutes). | |
1026 | [Note: in the case of SCSI devices, | |
1027 | this command option runs the "Background long" self\-test.] | |
1028 | This is a | |
1029 | longer and more thorough version of the Short Self Test described | |
1030 | above. Note that this command can be given during normal | |
1031 | system operation (unless run in captive mode \- see the \'\-C\' option below). | |
1032 | ||
1033 | .I conveyance | |
1034 | \- [ATA ONLY] runs a SMART Conveyance Self Test (minutes). This | |
1035 | self\-test routine is intended to identify damage incurred during | |
1036 | transporting of the device. This self\-test routine should take on the | |
1037 | order of minutes to complete. Note that this command can be given | |
1038 | during normal system operation (unless run in captive mode \- see the | |
1039 | \'\-C\' option below). | |
1040 | ||
1041 | .I select,N\-M | |
1042 | \- [ATA ONLY] [NEW EXPERIMENTAL SMARTCTL FEATURE] runs a SMART | |
1043 | Selective Self Test, to test a \fBrange\fP of disk Logical Block | |
1044 | Addresses (LBAs), rather than the entire disk. Each range of LBAs | |
1045 | that is checked is called a "span" and is specified by a starting LBA | |
1046 | (N) and an ending LBA (M) with N less than or equal to M. For example | |
1047 | the command: | |
1048 | .nf | |
1049 | smartctl \-t select,10\-20 /dev/hda | |
1050 | .fi | |
1051 | runs a self test on one span consisting of LBAs ten to twenty | |
1052 | (inclusive). The \'\-t\' option can be given up to five times, to test | |
1053 | up to five spans. For example the command: | |
1054 | .nf | |
1055 | smartctl \-t select,0\-100 \-t select,1000\-2000 /dev/hda | |
1056 | .fi | |
1057 | runs a self test on two spans. The first span consists of 101 LBAs | |
1058 | and the second span consists of 1001 LBAs. Note that the spans can | |
1059 | overlap partially or completely, for example: | |
1060 | .nf | |
1061 | smartctl \-t select,0\-10 \-t select,5\-15 \-t select,10\-20 /dev/hda | |
1062 | .fi | |
1063 | The results of the selective self\-test can be obtained (both during | |
1064 | and after the test) by printing the SMART self\-test log, using the | |
1065 | \'\-l selftest\' option to smartctl. | |
1066 | ||
1067 | Selective self tests are particularly useful as disk capacities | |
1068 | increase: an extended self test (smartctl \-t long) can take several | |
1069 | hours. Selective self\-tests are helpful if (based on SYSLOG error | |
1070 | messages, previous failed self\-tests, or SMART error log entries) you | |
1071 | suspect that a disk is having problems at a particular range of | |
1072 | Logical Block Addresses (LBAs). | |
1073 | ||
1074 | Selective self\-tests can be run during normal system operation (unless | |
1075 | done in captive mode \- see the \'\-C\' option below). | |
1076 | ||
1077 | [Note: this new experimental smartmontools feature is currently only | |
1078 | available under Linux. The Linux kernel must be compiled with the | |
1079 | configuration option CONFIG_IDE_TASKFILE_IO enabled. Please report | |
1080 | unusual or incorrect behavior to the smartmontools\-support mailing | |
1081 | list.] | |
1082 | ||
1083 | .I afterselect,on | |
1084 | \- [ATA ONLY] perform an offline read scan after a Selective Self\-test | |
1085 | has completed. This option must be used together with one or more of | |
1086 | the \fIselect,N\-M\fP options above. If the LBAs that have been | |
1087 | specified in the Selective self\-test pass the test with no errors | |
1088 | found, then read scan the \fBremainder\fP of the disk. If the device | |
1089 | is powered\-cycled while this read scan is in progress, the read scan | |
1090 | will be automatically resumed after a time specified by the pending | |
1091 | timer (see below). The value of this option is preserved between | |
1092 | selective self\-tests. | |
1093 | ||
1094 | .I afterselect,off | |
1095 | \- [ATA ONLY] do not read scan the remainder of the disk after a | |
1096 | Selective self\-test has completed. This option must be use together | |
1097 | with one or more of the \fIselect,N\-M\fP options above. The value of this | |
1098 | option is preserved between selective self\-tests. | |
1099 | ||
1100 | .I pending,N | |
1101 | \- [ATA ONLY] set the pending offline read scan timer to N minutes. | |
1102 | Here N is an integer in the range from 0 to 65535 inclusive. If the | |
1103 | device is powered off during a read scan after a Selective self\-test, | |
1104 | then resume the test automatically N minutes after power\-up. This | |
1105 | option must be use together with one or more of the \fIselect,N\-M\fP | |
1106 | options above. The value of this option is preserved between selective | |
1107 | self\-tests. | |
1108 | ||
1109 | .TP | |
1110 | .B \-C, \-\-captive | |
1111 | Runs self\-tests in captive mode. This has no effect with \'\-t | |
1112 | offline\' or if the \'\-t\' option is not used. [Note: in the case of | |
1113 | SCSI devices, this command option runs the self\-test in "Foreground" | |
1114 | mode.] | |
1115 | ||
1116 | \fBWARNING: Tests run in captive mode may busy out the drive for the | |
1117 | length of the test. Only run captive tests on drives without any | |
1118 | mounted partitions!\fP | |
1119 | ||
1120 | .TP | |
1121 | .B \-X, \-\-abort | |
1122 | Aborts non\-captive SMART Self Tests. Note that this | |
1123 | command will abort the Offline Immediate Test routine only if your | |
1124 | disk has the "Abort Offline collection upon new command" capability. | |
1125 | .PP | |
1126 | .SH EXAMPLES | |
1127 | .nf | |
1128 | .B smartctl \-a /dev/hda | |
1129 | .fi | |
1130 | Print all SMART information for drive /dev/hda (Primary Master). | |
1131 | .PP | |
1132 | .nf | |
1133 | .B smartctl \-s off /dev/hdd | |
1134 | .fi | |
1135 | Disable SMART on drive /dev/hdd (Secondary Slave). | |
1136 | .PP | |
1137 | .nf | |
1138 | .B smartctl \-\-smart=on \-\-offlineauto=on \-\-saveauto=on /dev/hda | |
1139 | .fi | |
1140 | Enable SMART on drive /dev/hda, enable automatic offline | |
1141 | testing every four hours, and enable autosaving of | |
1142 | SMART Attributes. This is a good start\-up line for your system\'s | |
1143 | init files. You can issue this command on a running system. | |
1144 | .PP | |
1145 | .nf | |
1146 | .B smartctl \-t long /dev/hdc | |
1147 | .fi | |
1148 | Begin an extended self\-test of drive /dev/hdc. You can issue this | |
1149 | command on a running system. The results can be seen in the self\-test | |
1150 | log visible with the \'\-l selftest\' option after it has completed. | |
1151 | .PP | |
1152 | .nf | |
1153 | .B smartctl \-s on \-t offline /dev/hda | |
1154 | .fi | |
1155 | Enable SMART on the disk, and begin an immediate offline test of | |
1156 | drive /dev/hda. You can issue this command on a running system. The | |
1157 | results are only used to update the SMART Attributes, visible | |
1158 | with the \'\-A\' option. If any device errors occur, they are logged to | |
1159 | the SMART error log, which can be seen with the \'\-l error\' option. | |
1160 | .PP | |
1161 | .nf | |
1162 | .B smartctl \-A \-v 9,minutes /dev/hda | |
1163 | .fi | |
1164 | Shows the vendor Attributes, when the disk stores its power\-on time | |
1165 | internally in minutes rather than hours. | |
1166 | .PP | |
1167 | .nf | |
1168 | .B smartctl \-q errorsonly \-H \-l selftest /dev/hda | |
1169 | .fi | |
1170 | Produces output only if the device returns failing SMART status, | |
1171 | or if some of the logged self\-tests ended with errors. | |
1172 | .PP | |
1173 | .nf | |
1174 | .B smartctl \-q silent \-a /dev/hda | |
1175 | .fi | |
1176 | Examine all SMART data for device /dev/hda, but produce no | |
1177 | printed output. You must use the exit status (the | |
1178 | .B $? | |
1179 | shell variable) to learn if any Attributes are out of bound, if the | |
1180 | SMART status is failing, if there are errors recorded in the | |
1181 | self\-test log, or if there are errors recorded in the disk error log. | |
1182 | .PP | |
1183 | .nf | |
1184 | .B smartctl \-a \-d 3ware,0 /dev/sda | |
1185 | .fi | |
1186 | Examine all SMART data for the first ATA disk connected to a 3ware | |
1187 | RAID controller card. | |
1188 | .PP | |
1189 | .nf | |
1190 | .B smartctl \-a \-d 3ware,0 /dev/twe0 | |
1191 | .fi | |
1192 | Examine all SMART data for the first ATA disk connected to a 3ware | |
1193 | RAID 6000/7000/8000 controller card. | |
1194 | .PP | |
1195 | .nf | |
1196 | .B smartctl \-a \-d 3ware,0 /dev/twa0 | |
1197 | .fi | |
1198 | Examine all SMART data for the first ATA disk connected to a 3ware | |
1199 | RAID 9000 controller card. | |
1200 | .PP | |
1201 | .nf | |
1202 | .B smartctl \-t short \-d 3ware,3 /dev/sdb | |
1203 | .fi | |
1204 | Start a short self\-test on the fourth ATA disk connected to the 3ware RAID | |
1205 | controller card which is the second SCSI device /dev/sdb. | |
1206 | .PP | |
1207 | .nf | |
1208 | .B smartctl \-a \-d hpt,1/3 /dev/sda | |
1209 | .fi | |
1210 | Examine all SMART data for the (S)ATA disk directly connected to the third channel of the | |
1211 | first HighPoint RocketRAID controller card. | |
1212 | .nf | |
1213 | .PP | |
1214 | .nf | |
1215 | .B smartctl \-t short \-d hpt,1/1/2 /dev/sda | |
1216 | .fi | |
1217 | Start a short self\-test on the (S)ATA disk connected to second pmport on the | |
1218 | first channel of the first HighPoint RocketRAID controller card. | |
1219 | .PP | |
1220 | .nf | |
1221 | .B smartctl \-t select,10\-100 \-t select,30\-300 \-t afterselect,on \-t pending,45 /dev/hda | |
1222 | .fi | |
1223 | Run a selective self\-test on LBAs 10 to 100 and 30 to 300. After the | |
1224 | these LBAs have been tested, read\-scan the remainder of the disk. If the disk is | |
1225 | power\-cycled during the read\-scan, resume the scan 45 minutes after power to the | |
1226 | device is restored. | |
1227 | .PP | |
1228 | .SH RETURN VALUES | |
1229 | The return values of \fBsmartctl\fP are defined by a bitmask. If all | |
1230 | is well with the disk, the return value (exit status) of | |
1231 | \fBsmartctl\fP is 0 (all bits turned off). If a problem occurs, or an | |
1232 | error, potential error, or fault is detected, then a non\-zero status | |
1233 | is returned. In this case, the eight different bits in the return | |
1234 | value have the following meanings for ATA disks; some of these values | |
1235 | may also be returned for SCSI disks. | |
1236 | .TP | |
1237 | .B Bit 0: | |
1238 | Command line did not parse. | |
1239 | .TP | |
1240 | .B Bit 1: | |
1241 | Device open failed, or device did not return an IDENTIFY DEVICE structure. | |
1242 | .TP | |
1243 | .B Bit 2: | |
1244 | Some SMART command to the disk failed, or there was a checksum error | |
1245 | in a SMART data structure (see \'\-b\' option above). | |
1246 | .TP | |
1247 | .B Bit 3: | |
1248 | SMART status check returned "DISK FAILING". | |
1249 | .TP | |
1250 | .B Bit 4: | |
1251 | SMART status check returned "DISK OK" but we found prefail Attributes <= threshold. | |
1252 | .TP | |
1253 | .B Bit 5: | |
1254 | SMART status check returned "DISK OK" but we found that some (usage | |
1255 | or prefail) Attributes have been <= threshold at some time in the | |
1256 | past. | |
1257 | .TP | |
1258 | .B Bit 6: | |
1259 | The device error log contains records of errors. | |
1260 | .TP | |
1261 | .B Bit 7: | |
1262 | The device self\-test log contains records of errors. | |
1263 | ||
1264 | To test within the shell for whether or not the different bits are | |
1265 | turned on or off, you can use the following type of construction (this | |
1266 | is bash syntax): | |
1267 | .nf | |
1268 | .B smartstat=$(($? & 8)) | |
1269 | .fi | |
1270 | This looks at only at bit 3 of the exit status | |
1271 | .B $? | |
1272 | (since 8=2^3). The shell variable | |
1273 | $smartstat will be nonzero if SMART status check returned "disk | |
1274 | failing" and zero otherwise. | |
1275 | ||
1276 | .PP | |
1277 | .SH NOTES | |
1278 | The TapeAlert log page flags are cleared for the initiator when the | |
1279 | page is read. This means that each alert condition is reported only | |
1280 | once by \fBsmartctl\fP for each initiator for each activation of the | |
1281 | condition. | |
1282 | ||
1283 | .PP | |
1284 | .SH AUTHOR | |
1285 | \fBBruce Allen\fP smartmontools\-support@lists.sourceforge.net | |
1286 | .fi | |
1287 | University of Wisconsin \- Milwaukee Physics Department | |
1288 | ||
1289 | .PP | |
1290 | .SH CONTRIBUTORS | |
1291 | The following have made large contributions to smartmontools: | |
1292 | .nf | |
1293 | \fBCasper Dik\fP (Solaris SCSI interface) | |
1294 | \fBChristian Franke\fP (Windows interface and Cygwin package) | |
1295 | \fBDouglas Gilbert\fP (SCSI subsystem) | |
1296 | \fBGuido Guenther\fP (Autoconf/Automake packaging) | |
1297 | \fBGeoffrey Keating\fP (Darwin ATA interface) | |
1298 | \fBEduard Martinescu\fP (FreeBSD interface) | |
1299 | \fBFr\*'ed\*'eric L. W. Meunier\fP (Web site and Mailing list) | |
1300 | \fBKeiji Sawada\fP (Solaris ATA interface) | |
1301 | \fBSergey Svishchev\fP (NetBSD interface) | |
1302 | \fBDavid Snyder and Sergey Svishchev\fP (OpenBSD interface) | |
1303 | \fBPhil Williams\fP (User interface and drive database) | |
1304 | \fBYuri Dario\fP (OS/2, eComStation interface) | |
1305 | .fi | |
1306 | Many other individuals have made smaller contributions and corrections. | |
1307 | ||
1308 | .PP | |
1309 | .SH CREDITS | |
1310 | .fi | |
1311 | This code was derived from the smartsuite package, written by Michael | |
1312 | Cornwell, and from the previous UCSC smartsuite package. It extends | |
1313 | these to cover ATA\-5 disks. This code was originally developed as a | |
1314 | Senior Thesis by Michael Cornwell at the Concurrent Systems Laboratory | |
1315 | (now part of the Storage Systems Research Center), Jack Baskin School | |
1316 | of Engineering, University of California, Santa | |
1317 | Cruz. \fBhttp://ssrc.soe.ucsc.edu/\fP . | |
1318 | .SH | |
1319 | HOME PAGE FOR SMARTMONTOOLS: | |
1320 | .fi | |
1321 | Please see the following web site for updates, further documentation, bug | |
1322 | reports and patches: \fBhttp://smartmontools.sourceforge.net/\fP | |
1323 | ||
1324 | .SH | |
1325 | SEE ALSO: | |
1326 | \fBsmartd\fP(8), \fBbadblocks\fP(8), \fBide\-smart\fP(8). | |
1327 | .SH | |
1328 | REFERENCES FOR SMART | |
1329 | .fi | |
1330 | An introductory article about smartmontools is \fIMonitoring Hard | |
1331 | Disks with SMART\fP, by Bruce Allen, Linux Journal, January 2004, | |
1332 | pages 74-77. This is \fBhttp://www.linuxjournal.com/article.php?sid=6983\fP | |
1333 | online. | |
1334 | ||
1335 | If you would like to understand better how SMART works, and what it | |
1336 | does, a good place to start is with Sections 4.8 and 6.54 of the first | |
1337 | volume of the \'AT Attachment with Packet Interface-7\' (ATA/ATAPI-7) | |
1338 | specification. This documents the SMART functionality which the | |
1339 | \fBsmartmontools\fP utilities provide access to. You can find | |
1340 | Revision 4b of this document at | |
1341 | \fBhttp://www.t13.org/docs2004/d1532v1r4b-ATA-ATAPI-7.pdf\fP . | |
1342 | Earlier and later versions of this Specification are available from | |
1343 | the T13 web site \fBhttp://www.t13.org/\fP . | |
1344 | ||
1345 | .fi | |
1346 | The functioning of SMART was originally defined by the SFF\-8035i | |
1347 | revision 2 and the SFF\-8055i revision 1.4 specifications. These are | |
1348 | publications of the Small Form Factors (SFF) Committee. Links to | |
1349 | these documents may be found in the References section of the | |
1350 | \fBsmartmontools\fP home page at | |
1351 | \fBhttp://smartmontools.sourceforge.net/\fP . | |
1352 | ||
1353 | .SH | |
1354 | CVS ID OF THIS PAGE: | |
1355 | $Id: smartctl.8.in,v 1.83 2006/09/15 08:03:52 sxzzsf Exp $ | |
1356 | .\" Local Variables: | |
1357 | .\" mode: nroff | |
1358 | .\" End: |