Self-Monitoring, Analysis and Reporting Technology#Visibility to host systems

Hard disk and other storage drives are subject to failures (see hard disk drive failure) which can be classified into two basic classes:

• Predictable failures which result from slow processes such as mechanical wear and gradual degradation of storage surfaces. Monitoring can determine when such failures are becoming more likely.
• Unpredictable failures which occur without warning due to anything from electronic components becoming defective to a sudden mechanical failure, including failures related to improper handling.

Mechanical failures account for about 60% of all drive failures.{{cite web |url=http://www.seagate.com/docs/pdf/whitepaper/enhanced_smart.pdf |publisher=Seagate |title=Enhanced Smart attributes |url-status=dead |archive-url=https://web.archive.org/web/20060328023033/http://seagate.com/docs/pdf/whitepaper/enhanced_smart.pdf |archive-date=2006-03-28 }}

While the eventual failure may be catastrophic, most mechanical failures result from gradual wear and there are usually certain indications that failure is imminent. These may include increased heat output, increased noise level, problems with reading and writing of data, or an increase in the number of damaged disk sectors.

PCTechGuide's page on S.M.A.R.T. (2003) comments that the technology has gone through three phases:{{cite web |title=SMART|url=https://www.pctechguide.com/hard-disks/hard-disk-smart-drives|year=2003|publisher=PCTechGuide}}

{{Blockquote |In its original incarnation S.M.A.R.T. provided failure prediction by monitoring certain online hard drive activities. A subsequent version of the standard improved failure prediction by adding an automatic off-line read scan to monitor additional operations. Online attributes are always updated while the offline attributes get updated when the HDD is not under working condition. If there is an immediate need to update the offline attributes, the HDD slows down and the offline attributes get updated. The latest "S.M.A.R.T." technology not only monitors hard drive activities but adds failure prevention by attempting to detect and repair sector errors.

Also, while earlier versions of the technology only monitored hard drive activity for data that was retrieved by the operating system, this latest S.M.A.R.T. tests all data and all sectors of a drive by using "off-line data collection" to confirm the drive's health during periods of inactivity.}}

A field study at Google{{Cite conference |year=2007 |title=Failure Trends in a Large Disk Drive Population |url=http://research.google.com/archive/disk_failures.pdf |pages=8-9|first1=Eduardo |last1=Pinheiro |first2=Wolf-Dietrich |last2=Weber |first3=Luís André |last3=Barroso |location=Mountain View, Calif.|conference=5th USENIX Conference on File and Storage Technologies (FAST 2007)}} covering over 100,000 consumer-grade drives from December 2005 to August 2006 found correlations between certain S.M.A.R.T. information and annualized failure rates:

• In the 60 days following the first uncorrectable error on a drive (S.M.A.R.T. attribute 0xC6 or 198) detected as a result of an offline scan, the drive was, on average, 39 times more likely to fail than a similar drive for which no such error occurred.
• First errors in reallocations, offline reallocations (S.M.A.R.T. attributes 0xC4 and 0x05 or 196 and 5) and probational counts (S.M.A.R.T. attribute 0xC5 or 197) were also strongly correlated to higher probabilities of failure.
• Conversely, little correlation was found for increased temperature and no correlation for usage level. However, the research showed that a large proportion (56%) of the failed drives failed without recording any count in the "four strong S.M.A.R.T. warnings" identified as scan errors, reallocation count, offline reallocation, and probational count.
• Further, 36% of failed drives did so without recording any S.M.A.R.T. error at all, except the temperature, meaning that S.M.A.R.T. data alone was of limited usefulness in anticipating failures.{{cite conference |url=http://research.google.com/archive/disk_failures.pdf |title=Failure Trends in a Large Disk Drive Population: Conclusion |first1=Eduardo |last1=Pinheiro |first2=Wolf-Dietrich |last2=Weber |first3=Luís André |last3=Barroso |location=Mountain View, Calif.|conference=5th USENIX Conference on File and Storage Technologies (FAST 2007)}}

An early hard disk monitoring technology was introduced by IBM in 1992 in its IBM 9337 Disk Arrays for AS/400 servers using IBM 0662 SCSI-2 disk drives.{{cite web |url=http://www-306.ibm.com/common/ssi/OIX.wss?DocURL=http://d03xhttpcl001g.boulder.ibm.com/common/ssi/rep_ca/9/877/ENUSZG92-0289/index.html&InfoType=AN |publisher=IBM |type=announcement letter |title=No. ZG92-0289 |date=September 1, 1992}} Later it was named Predictive Failure Analysis (PFA) technology. It was measuring several key device health parameters and evaluating them within the drive firmware. Communications between the physical unit and the monitoring software were limited to a binary result: namely, either "device is OK" or "drive is likely to fail soon".

Later, another variant, which was named IntelliSafe, was created by computer manufacturer Compaq and disk drive manufacturers Seagate, Quantum, and Conner.{{cite report |title=Playing it S.M.A.R.T.: The emergence of reliability prediction technology. |publisher=Seagate Technology Paper |first1=Eric |last1=Ottem |first2=Judy |last2=Plummer |date=1995}} The disk drives would measure the disk's "health parameters", and the values would be transferred to the operating system and user-space monitoring software. Each disk drive vendor was free to decide which parameters were to be included for monitoring, and what their thresholds should be. The unification was at the protocol level with the host.

Compaq submitted IntelliSafe to the Small Form Factor (SFF) committee for standardization in early 1995.{{cite report |title=Compaq. IntelliSafe. Technical Report SSF-8035 |publisher=Small Form Committee |date=January 1995}} It was supported by IBM, by Compaq's development partners Seagate, Quantum, and Conner, and by Western Digital, which did not have a failure prediction system at the time. The Committee chose IntelliSafe's approach, as it provided more flexibility. Compaq placed IntelliSafe into the public domain on 12 May 1995.{{cite report|author1=Seagate Product Marketing|title=Get S.M.A.R.T. for Reliability|date=July 1999|archive-date=12 June 2001|archive-url=https://web.archive.org/web/20010612122823/http://www.seagate.com/newsinfo/docs/disc/enhanced_smart.pdf|url=http://www.seagate.com/newsinfo/docs/disc/enhanced_smart.pdf|series=Technology Paper|publisher=Seagate Technology|location=Scotts Valley, California|language=en|id=TP-67D|quote=Compaq placed IntelliSafe in the public domain by presenting its specification for the ATA environment, SFF-8035, to the Small Form Factor Committee on May 12, 1995.}} The resulting jointly developed standard was named S.M.A.R.T..

That SFF standard described a communication protocol for an ATA host to use and control monitoring and analysis in a hard disk drive, but did not specify any particular metrics or analysis methods. Later, "S.M.A.R.T." came to be understood (though without any formal specification) to refer to a variety of specific metrics and methods and to apply to protocols unrelated to ATA for communicating the same kinds of things.

The technical documentation for S.M.A.R.T. is in the AT Attachment (ATA) standard. First introduced in 1994,{{Cite book |last=Mueller |first=Scott |url=https://www.worldcat.org/oclc/816159579 |title=Upgrading and repairing PCs |year=2013 |publisher=Que Pub. |isbn=978-0-7897-5000-6 |edition=21st |location=Indianapolis, Ind. |chapter=The ATA/IDE Interface |oclc=816159579 |chapter-url=https://www.informit.com/articles/article.aspx?p=2028834&seqNum=2}} the ATA standard has gone through multiple revisions. Some parts of the original S.M.A.R.T. specification by the Small Form Factor (SFF) Committee were added to ATA-3,{{Cite web |last=Allen |first=Bruce |date=2004-01-01 |title=Monitoring Hard Disks with SMART {{!}} Linux Journal |url=https://www.linuxjournal.com/article/6983 |access-date=2021-04-13 |website=www.linuxjournal.com}} published in 1997. In 1998 ATA-4 dropped the requirement for drives to maintain an internal attribute table and instead required only for an "OK" or "NOT OK" value to be returned. Albeit, manufacturers have kept the capability to retrieve the attributes' value. The most recent ATA standard, ATA-8, was published in 2004.{{cite web |title=AT Attachment 8 – ATA/ATAPI Command Set (ATA8-ACS): SMART (Self-monitoring, analysis, and reporting technology) feature set |publisher=ANSI INCITS |date=September 6, 2008 |url=http://www.t13.org/documents/uploadeddocuments/docs2008/d1699r6a-ata8-acs.pdf |access-date=March 23, 2020 |archive-date=October 10, 2014 |archive-url=https://web.archive.org/web/20141010045105/http://www.t13.org/documents/UploadedDocuments/docs2008/D1699r6a-ATA8-ACS.pdf |url-status=dead }} It has undergone regular revisions,{{Harvnb |Stephens |2006 |pp=44–126, 198–213, 327–44 |loc=Sections 4.19: "SMART (Self-monitoring, analysis, and reporting technology) feature set", 7.52: "SMART", Annex A: "Log Page Definitions"}} the latest being in 2011.{{cite web |work=ATA Command Set 2 |title=ATA/ATAPI Command Set - 2 (ACS-2) |type=working draft |edition=7 |publisher=ANSI INCITS |date=June 22, 2011 |url=http://www.t13.org/documents/UploadedDocuments/docs2011/d2015r7-ATAATAPI_Command_Set_-_2_ACS-2.pdf |access-date=June 8, 2017 |archive-date=July 1, 2016 |archive-url=https://web.archive.org/web/20160701095638/http://www.t13.org/documents/UploadedDocuments/docs2011/d2015r7-ATAATAPI_Command_Set_-_2_ACS-2.pdf |url-status=dead }} Standardization of similar features on SCSI is more scarce and is not named as such on standards, although vendors and consumers alike do refer to these similar features as S.M.A.R.T. too.{{cite web |last1=Gilbert |first1=Douglas |title=Smartmontools for SCSI devices |url=https://www.smartmontools.org/browser/trunk/www/smartmontools_scsi.xml}}

The most basic information that S.M.A.R.T. provides is the S.M.A.R.T. status. It provides only two values: "threshold not exceeded" and "threshold exceeded". Often, these are represented as "drive OK" or "drive fail" respectively. A "threshold exceeded" value is intended to indicate that there is a relatively high probability that the drive will not be able to honor its specification in the future: that is, the drive is "about to fail". The predicted failure may be catastrophic or may be something as subtle as the inability to write to certain sectors, or perhaps slower performance than the manufacturer's declared minimum.

The S.M.A.R.T. status does not necessarily indicate the drive's past or present reliability. If a drive has already failed catastrophically, the S.M.A.R.T. status may be inaccessible. Alternatively, if a drive has experienced problems in the past, but the sensors no longer detect such problems, the S.M.A.R.T. status may, depending on the manufacturer's programming, suggest that the drive is now healthy.

The inability to read some sectors is not always an indication that a drive is about to fail. One way that unreadable sectors may be created, even when the drive is functioning within specification, is through a sudden power failure while the drive is writing. Also, even if the physical disk is damaged at one location, such that a certain sector is unreadable, the disk may be able to use spare space to replace the bad area, so that the sector can be overwritten.{{cite web |publisher=Hitachi Data Systems |date=19 September 2003 |title=Hitachi Travelstar 80GN |edition=2.0 |id=Hitachi Document Part Number S13K-1055-20 |url=http://www.hitachigst.com/tech/techlib.nsf/techdocs/85CC1FF9F3F11FE187256C4F0052E6B6/$file/80GNSpec2.0.pdf |url-status=dead |archive-url=https://web.archive.org/web/20110718181944/http://www.hitachigst.com/tech/techlib.nsf/techdocs/85CC1FF9F3F11FE187256C4F0052E6B6/$file/80GNSpec2.0.pdf |archive-date=18 July 2011 }}

More detail on the health of the drive may be obtained by examining the S.M.A.R.T. Attributes. S.M.A.R.T. Attributes were included in some drafts of the ATA standard, but were removed before the standard became final. The meaning and interpretation of the attributes varies between manufacturers, and are sometimes considered a trade secret for one manufacturer or another. Attributes are further discussed below.

Drives with S.M.A.R.T. may optionally maintain a number of 'logs'. The error log records information about the most recent errors that the drive has reported back to the host computer. Examining this log may help one to determine whether computer problems are disk-related or caused by something else (error log timestamps may "wrap" after 2³² ms=49.71 days{{cite web |url=http://smartmontools.sourceforge.net/examples/MAXTOR-1.txt |publisher=Source forge |title=Smartmontools }})

A drive that implements S.M.A.R.T. may optionally implement a number of self-test or maintenance routines, and the results of the tests are kept in the self-test log. The self-test routines may be used to detect any unreadable sectors on the disk, so that they may be restored from back-up sources (for example, from other disks in a RAID). This helps to reduce the risk of incurring permanent loss of data.

Many motherboards display a warning message upon boot when a disk drive is approaching failure. Although an industry standard exists among most major hard drive manufacturers, issues remain due to attributes intentionally left undocumented to the public in order to differentiate models between manufacturers.{{cite web |author1=Bruno Sonnino |title=What is S.M.A.R.T.? |url=https://www.pcmag.com/article2/0,2817,1879485,00.asp |website=PC Mag |publisher=Ziff Davis |access-date=12 July 2016 |pages=1 |language=en |date=31 October 2005}}{{cite web |last=Hatfield |first=Jim |title=SMART Attribute Annex |url=http://www.t13.org/documents/uploadeddocuments/docs2005/e05148r0-acs-smartattributesannex.pdf |archive-url=https://web.archive.org/web/20070203040514/http://www.t13.org/documents/uploadeddocuments/docs2005/e05148r0-acs-smartattributesannex.pdf |archive-date=2007-02-03 |website=Technical Committee T13 |publisher=Seagate Technology |access-date=12 July 2016 |pages=1–5 |language=en |date=30 September 2005}} Note: this source usefully lists a set of attributes in use. However, its description of "worst value" deviates from SFF-8035, which is closer to reality.

From a legal perspective, the term "S.M.A.R.T." refers only to a signaling method between internal disk drive electromechanical sensors and the host computer. Because of this the specifications of S.M.A.R.T. are entirely vendor specific and, while many of these attributes have been standardized between drive vendors, others remain vendor-specific. S.M.A.R.T. implementations still differ and in some cases may lack "common" or expected features such as a temperature sensor or only include a few select attributes while still allowing the manufacturer to advertise the product as "S.M.A.R.T. compatible."

Depending on the type of interface being used, some S.M.A.R.T.-enabled motherboards and related software may not communicate with certain S.M.A.R.T.-capable drives. For example, few external drives connected via USB and FireWire correctly send S.M.A.R.T. data over those interfaces. With so many ways to connect a hard drive (SCSI, Fibre Channel, ATA, SATA, SAS, SSA, NVMe and so on), it is difficult to predict whether S.M.A.R.T. reports will function correctly in a given system.

Even with a hard drive and interface that implements the specification, the computer's operating system may not see the S.M.A.R.T. information because the drive and interface are encapsulated in a lower layer. For example, they may be part of a RAID subsystem in which the RAID controller sees the S.M.A.R.T.-capable drive, but the host computer sees only a logical volume generated by the RAID controller.

On the Windows platform, many programs designed to monitor and report S.M.A.R.T. information will function only under an administrator account.

BIOS and Windows (Windows Vista and later) may detect S.M.A.R.T. status of hard disk drives and solid state drives, and give a prompt if the S.M.A.R.T. status is bad.{{Cite web |date=2019-08-27 |title=Hard drive acting up? It could be hardware issues — here's how to find out |url=https://www.windowscentral.com/how-check-if-hard-drive-failing-smart-windows-10 |access-date=2021-03-04 |website=Windows Central}}

Each drive manufacturer defines a set of attributes,{{Sfn |Stephens |2006 |p=207 |ps=Of the 512 octets listed in table 42 on page 207: "Device SMART data structure" a total of 489 are marked as "Vendor specific".}}{{cite report |title=Playing it S.M.A.R.T.: The emergence of reliability prediction technology. |publisher=Seagate |first1=Eric |last1=Ottem |first2=Judy |last2=Plummer |date=1995 |quote=Though attributes are drive-specific, a variety of typical characteristics can be identified: [...] The attributes listed above illustrate typical kinds of reliability indicators. Ultimately, the disc drive design determines which attributes the manufacturer will choose. Attributes are therefore considered proprietary, since they depend on drive design.}} and sets threshold values beyond which attributes should not pass under normal operation. Each attribute has:{{cite web |author1=SFF Committee |title=Specification for Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) SFF-8035i Revision 2.0 |url=https://www.linux-mips.org/pub/linux/mips/people/macro/S.M.A.R.T./8035R2_0.PDF |date=April 1, 1996|archive-url=https://web.archive.org/web/20140423014210/https://www.linux-mips.org/pub/linux/mips/people/macro/S.M.A.R.T./8035R2_0.PDF |archive-date=2014-04-23 }}

• 1 byte for the ID (1 through 254).
• 1 byte for status flags.
• 1 byte of threshold value, which ranges from 0 to 254.
• 1 byte of normalized value aka current value, which ranges from 0 to 254 (higher is usually better, but vendors are allowed to vary; the threshold entry stored elsewhere describes which direction is better). The initial normalized value of attributes is 100 but can vary between manufacturer.
• 8 bytes "vendor-specific".

In practice, however, the full "vendor-specific" field is not used as-is. Instead, one of the following occurs:{{cite web |title=smartmontools/smartmontools: atacmds.cpp, ata_get_attr_raw_value() |url=https://github.com/smartmontools/smartmontools/blob/8686712ff3e0efebd38311a784f369e7e4260271/smartmontools/atacmds.cpp#L1846 |publisher=Smartmontools.org |date=30 May 2023}}

• In the 7-byte setup, the first byte of "vendor-specific" is used to store a "worst" normalized value, leaving 7 bytes for vendor data.
• In the 6-byte setup, the first byte of "vendor-specific" is used to store a "worst" normalized value and the last byte "reserved", leaving 6 bytes.
• In the 8-byte setup, the normalized byte is added to the field while the last byte is reserved.

In any case, the vendor field, also commonly called a "raw value", may be displayed as a decimal or hexadecimal number; its meaning is entirely up to the drive manufacturer (but often corresponds to counts or a physical unit, such as degrees Celsius or seconds).{{cite web |title=smartmontools/smartmontools: atacmds.h: struct ata_smart_attribute, enum ata_attr_raw_format |url=https://github.com/smartmontools/smartmontools/blob/8686712ff3e0efebd38311a784f369e7e4260271/smartmontools/atacmds.h#LL135C50-L135C59 |publisher=Smartmontools.org |date=30 May 2023}}

If one or more attribute have the "prefailure" flag, and the "current value" of such prefailure attribute is smaller than or equal to its "threshold value" (unless the "threshold value" is 0), that will be reported as a "drive failure". In addition, a utility software can send SMART RETURN STATUS command to the ATA drive, it may report three status: "drive OK", "drive warning" or "drive failure".

Manufacturers that have implemented at least one S.M.A.R.T. attribute in various products include Samsung, Seagate, IBM (Hitachi), Fujitsu, Maxtor, Toshiba, Intel, sTec, Inc., Western Digital and ExcelStor Technology.

The following chart lists some S.M.A.R.T. attributes and the typical meaning of their raw values. Normalized values are usually mapped so that higher values are better (exceptions include drive temperature, number of head load/unload cycles{{cite web |publisher=Source forge |url=https://www.smartmontools.org/wiki/FAQ#Attribute194TemperatureCelsiusbehavesstrangelyonmySeagatedisk |title=Smartmontools |quote=Attribute 194 (Temperature Celsius) behaves strangely on my Seagate disk}}), but higher raw attribute values may be better or worse depending on the attribute and manufacturer. For example, the "Reallocated Sectors Count" attribute's normalized value decreases as the count of reallocated sectors increases. In this case, the attribute's raw value will often indicate the actual count of sectors that were reallocated, although vendors are in no way required to adhere to this convention.

As manufacturers do not necessarily agree on precise attribute definitions and measurement units, the following list of attributes is a general guide only.

Drives do not support all attribute codes (sometimes abbreviated as "ID", for "identifier", in tables). Some codes are specific to particular drive types (magnetic platter, flash, SSD). Drives may use different codes for the same parameter, e.g., see codes 193 and 225.

{{Missing information|section|description of this more organized interface; pseudo-logs E0 E1 for SCT commands|date=June 2023}}

Threshold Exceeds Condition (TEC) is an estimated date when a critical drive statistic attribute will reach its threshold value. When Drive Health software reports a "Nearest T.E.C.", it should be regarded as a "Failure date". Sometimes, no date is given and the drive can be expected to work without errors.{{cite web |url=http://www.drivehealth.com/faq.html |website=Drive health |title=FAQ |access-date=October 4, 2011 |archive-date=September 26, 2011 |archive-url=https://web.archive.org/web/20110926184700/http://www.drivehealth.com/faq.html |url-status=dead }}

To predict the date, the drive tracks the rate at which the attribute changes. Note that TEC dates are only estimates; hard drives can and do fail much sooner or much later than the TEC date.{{cite web |url=http://www.altrixsoft.com/en/support/help/hddinsp/tec%20and%20smart.php |title=The interpretation of the TEC and the SMART |publisher=Altrix soft |access-date=October 4, 2011 |archive-date=January 13, 2012 |archive-url=https://web.archive.org/web/20120113084606/http://www.altrixsoft.com/en/support/help/hddinsp/tec%20and%20smart.php |url-status=dead }}

NVMe specification has defined unified S.M.A.R.T. attributes for different drive manufacturers. The data is present in a log page of 512 bytes long.{{Cite book |url=https://nvmexpress.org/wp-content/uploads/NVMe-NVM-Express-2.0a-2021.07.26-Ratified.pdf |title=NVM Express Base Specification Revision 2.0a |date=July 23, 2021 |pages=181–3}}

The SCSI standard does not mention the term "S.M.A.R.T." except in one place, but the equivalent logging/failure-prediction functionality is available in standard log pages prescribed by SPC-4. There is also space for vendor-specific log pages. Log pages are variable-length.{{cite web |author1=Seagate |title=SCSI Commands Reference Manual (100293068 Rev. D) |url=https://enos.itcollege.ee/~edmund/storage/loengud/varasem/SAN_IPSAN_NAS_CAS/SCSI-command-reference-manual.pdf |date=December 2010}}

SCSI has a specialized set of S.M.A.R.T. features for tape drives known as TapeAlert defined in SMC-2. SCSI offers self-testing, similar to ATA.

Information related to the reallocation of bad sectors is provided not via a log page, but via the READ DEFECT DATA command. In addition to a grand total, this command provides information about which specific sectors were allocated and why.

S.M.A.R.T. drives may offer a number of self-tests:{{cite web |url=https://manned.org/smartctl.8 |title=smartctl - Control and Monitor Utility for SMART Disks}}{{cite web |url=http://hddscan.com/ |title=HDDScan}} – free HDD test utility with USB flash and RAID support.{{cite web |publisher=T10 |url=http://www.t10.org/ftp/t10/document.99/99-179r0.pdf |title=Hard Drive Self-tests |first=Mark |last=Evans |location=Milpitas, Calif., US |date=26 April 1999}}

;Short

: Checks the electrical and mechanical performance as well as the read performance of the disk. Electrical tests might include a test of buffer RAM, a read/write circuitry test, or a test of the read/write head elements. Mechanical test includes seeking and servo on data tracks. Scans small parts of the drive's surface (area is vendor-specific and there is a time limit on the test). Checks the list of pending sectors that may have read errors, and it usually takes under two minutes.

;Long/extended

: A longer and more thorough version of the short self-test, scanning the entire disk surface with no time limit. This test usually takes several hours, depending on the read/write speed of the drive and its size. It is possible for the long test to pass even if the short test fails.{{cite web |title=HDD fails S.M.A.R.T. short test, but passes long test? |url=http://www.hardwarecanucks.com/forum/storage/23040-hdd-fails-s-m-r-t-short-test-but-passes-long-test.html |url-status=dead |archive-url=https://web.archive.org/web/20130729110522/http://www.hardwarecanucks.com/forum/storage/23040-hdd-fails-s-m-r-t-short-test-but-passes-long-test.html |archive-date=2013-07-29 |access-date=2013-01-15 |publisher=Hardware Canucks}}

;Conveyance

: Intended as a quick test to identify damage incurred during transporting of the device from the drive manufacturer to the computer manufacturer.{{cite web |publisher=T10 |url=http://www.t10.org/t13/technical/e01137r0.pdf |title=Proposal for Extensions To Drive Self Test |first=Darrin |last=Bulik |location=Lake Forest, Calif. |date=Sep 24, 2001 |url-status=dead |archive-url=https://web.archive.org/web/20110928091120/http://www.t10.org/t13/technical/e01137r0.pdf |archive-date=2011-09-28 }} Only available on ATA drives, and it usually takes several minutes.

;Selective

: Some ATA drives allow selective self-tests of just a part of the surface.{{cite web |publisher=T10 |url=http://www.t10.org/t13/technical/e01139r0.pdf |title=Proposal for a Selective Self-test |first=Pete |last=McLean |location=Longmont, Colo. |date=23 October 2001 |url-status=dead |archive-url=https://web.archive.org/web/20110928091148/http://www.t10.org/t13/technical/e01139r0.pdf |archive-date=28 September 2011 }} There is a dedicated log for selective test results, separate from the main self-test log.

; Background scan

: SCSI drives have the ability to schedule periodic full-surface self-tests known as a background media scan (BMS). The {{code|sdparm}} program may be used to adjust whether to run the scans ({{tt|EN_BMS}}) and various parameters for the scan (e.g. period, idle time before run). The drive remains operable during the test.{{cite web |title=PSA: If you have SAS drives, check the Background Media Scan function. It's very useful and not necessarily on by default. |url=https://www.reddit.com/r/DataHoarder/comments/e677p1/psa_if_you_have_sas_drives_check_the_background/ |website=r/DataHoarder |date=4 December 2019}} There is a dedicated log for background scan results, separate from the self-test log.

; Offline data collection

: ATA drives may support a periodic short operation called "offline data collection". Although this feature is marked "obsolete", many modern hard drives retain this feature. The drive remains operable during collection and any result is reflected only in SMART attributes (some attributes only update when "offline").{{cite web |title=test_offline – smartmontools |url=https://www.smartmontools.org/wiki/test_offline |website=www.smartmontools.org}}

Drives remain operable during self-test, unless a "captive" option (ATA only) is requested.

The self-test logs for SCSI and ATA drives are slightly different.

The ATA drive's self-test log can contain up to 21 read-only entries. When the log is filled, old entries are removed.[https://sourceforge.net/p/smartmontools/mailman/message/10781945/], Smartmontools mailing lists

• Comparison of S.M.A.R.T. tools
• Data scrubbing
• Disk utility
• List of disk partitioning software
• {{section link|Optical disc#Surface error scanning}}
• Predictive failure analysis
• System monitor

{{Reflist|30em}}

• {{cite web |editor-last=Stephens |editor-first=Curtis E |work=ATA Command Set 2 |title=ATA/ATAPI Command Set - 2 (ACS-2) |type=working draft |edition=g=7 |publisher=ANSI INCITS |date=June 22, 2011 |url=http://www.t13.org/documents/UploadedDocuments/docs2011/d2015r7-ATAATAPI_Command_Set_-_2_ACS-2.pdf |page=73 |access-date=June 8, 2017 |archive-date=July 1, 2016 |archive-url=https://web.archive.org/web/20160701095638/http://www.t13.org/documents/UploadedDocuments/docs2011/d2015r7-ATAATAPI_Command_Set_-_2_ACS-2.pdf |url-status=dead }}.
• {{cite web |url=http://www.siguardian.com/products/siguardian/on_line_help/s_m_a_r_t_attribute_meaning.html |archive-url=https://web.archive.org/web/20110226194620/http://www.siguardian.com/products/siguardian/on_line_help/s_m_a_r_t_attribute_meaning.html |title=S.M.A.R.T. attribute meaning |website=siguardian.com |access-date=February 3, 2006 |archive-date=February 26, 2011}}
• {{cite web |first=Zbigniew |last=Chlondowski |url=http://smartlinux.sourceforge.net/smart/attributes.php |title=S.M.A.R.T. Site: attributes reference table |publisher=S.M.A.R.T. Linux |access-date=January 17, 2007}}
• {{cite web |publisher=Ariolic |year=2007 |url=http://www.ariolic.com/activesmart/smart-attributes/ |title=S.M.A.R.T. attributes meaning |access-date=October 26, 2007}}
• {{cite web |work=H.D.S. Hungary |year=2007 |url=http://www.hdsentinel.com/smart |title=Can we believe SMART? |access-date=June 4, 2008}}
• {{cite magazine |first=Bruce |last=Allen |year=2004 |url=http://www.linuxjournal.com/article/6983 |title=Monitoring Hard Disks with SMART |magazine=Linux Journal| access-date=August 8, 2010}}

{{Wikibooks |Minimizing Hard Disk Drive Failure and Data Loss}}

;Projects

• {{cite web |url=https://www.smartmontools.org/wiki |title=smartmontools & smartsuite |publisher=smartmontools.org}}
• {{cite web |url=https://sourceforge.net/projects/smartsuite/ |title=UC Santa Cruz SMART suite |date=20 March 2013 |publisher=SourceForge}} by: [http://sourceforge.net/users/cornwell cornwell].
• [https://sourceforge.net/projects/gsmartcontrol/ GSmartControl] {{--}} A GUI for smartctl (part of smartmontools) by Alexander Shaduri
• [https://github.com/linuxhw/SMART GitHub: linuxhw/SMART] {{--}} A project to estimate reliability of desktop-class HDD/SSD drives by the analysis of SMART data collected by Linux users at https://linux-hardware.org.

;Articles

• [https://www.backblaze.com/blog/hard-drive-smart-stats/ Hard Drive SMART Stats (2014)] {{--}} A large-scale field report from BackBlaze
• [https://web.archive.org/web/20190114164625/http://wdc.custhelp.com/app/answers/detail/a_id/251/ KB251: Understanding S.M.A.R.T. and S.M.A.R.T. failure and errors (archived 2019)] from Western Digital, published in 2002, last updated in 2017.
• [http://www.hdsentinel.com/smart/index.php How does S.M.A.R.T. function of hard disks Work?] from HDSentinel.com
• [https://web.archive.org/web/20030802131842/http://www.pc-king.co.uk/tips3.htm How S.M.A.R.T. is your hard drive? (archived 2003)] {{--}} A short "Tip" written by Brian K. Lewis, Ph.D., Member of the Sarasota Personal Computer Users Group, Inc.

;Specifications

• [http://t1.daumcdn.net/brunch/service/user/axm/file/zRYOdwPu3OMoKYmBOby1fEEQEbU.pdf Seagate SMART Attribute Specification] from Seagate Technology, 2011
• [http://t1.daumcdn.net/brunch/service/user/axm/file/Vw3RJSZllYbDc86ssL6bofiL4r0.pdf Normal SATA SMART Attribute Behavior] from Seagate {{--}} A document that reviews the current behavior of SATA SMART attributes for Seagate drives and will identify normal changes that occur in the SMART Normalized value with drive usage.

Category:Computer storage technologies

Category:AT Attachment

Category:SCSI