Viking Technology Technology Computer Drive PSF1XXXXGXXXX Manuel D’Utilisation
Manual
1/2/2014
PSFS1XXXXGXXXX
Viking Technology
Revision B7
Page 38 of 60
www.vikingtechnology.com
Table 5-4: Supported S.M.A.R.T. EXECUTE OFF-LINE IMMEDIATE
Subcommands
Subcommands
Value
Description
00h
Execute S.M.A.R.T. off-line routine immediately in off-line mode
01h
Execute S.M.A.R.T. Short self-test routine immediately in off-line
mode
mode
02h
Execute S.M.A.R.T. Extended self-test routine immediately in off-line
mode
mode
04h
Execute S.M.A.R.T. Selective self-test routine immediately in off-line
mode
mode
7Fh
Abort off-line mode self-test routine
81h
Execute S.M.A.R.T. Short self-test routine immediately in captive
mode
mode
82h
Execute S.M.A.R.T. Extended self-test routine immediately in captive
mode
mode
84h
Execute S.M.A.R.T. Selective self-test routine immediately in captive
mode
mode
5.1.8.3
Captive Mode
When executing a self-test in captive mode, the Element SSD executes the self-
test routine after receipt of the command. At the end of the routine the Element
SSD places the results of this routine in the self-test execution status byte and
reports command completion. If an error occurs while the Element SSD is
performing the routine it discontinues its testing, place the results of this routine
in the self-test execution status byte and the DST log page, and complete the
command.
test routine after receipt of the command. At the end of the routine the Element
SSD places the results of this routine in the self-test execution status byte and
reports command completion. If an error occurs while the Element SSD is
performing the routine it discontinues its testing, place the results of this routine
in the self-test execution status byte and the DST log page, and complete the
command.
5.1.8.4
S.M.A.R.T. Logs
S.M.A.R.T. logs are intended to enhance S.M.A.R.T. Attribute information by
capturing additional drive details at appropriate times. This information may lead
to improved error detection and reporting capability. The controller supports
S.M.A.R.T. logs, and relevant tests, events, and conditions each have an
associated log. S.M.A.R.T. logs conform to industry-standard structures.
The reported size of each log is reported by the Log Directory (Log 0). Note that
the information returned via S.M.A.R.T. Read Log access to Log 0 is more limited
than that via GP Read Log. Log size is only reported the LSB (max 255 blocks)
when access via S.M.A.R.T. Read Log command; and full 2 bytes (max 65535
blocks) when access via Read Log EXT command.
The frequency at which S.M.A.R.T. logs are updated is the frequency at which
checkpoint information is saved. That frequency is related to data volume, and
can range between approximately 2 seconds and 2 minutes, depending on how
capturing additional drive details at appropriate times. This information may lead
to improved error detection and reporting capability. The controller supports
S.M.A.R.T. logs, and relevant tests, events, and conditions each have an
associated log. S.M.A.R.T. logs conform to industry-standard structures.
The reported size of each log is reported by the Log Directory (Log 0). Note that
the information returned via S.M.A.R.T. Read Log access to Log 0 is more limited
than that via GP Read Log. Log size is only reported the LSB (max 255 blocks)
when access via S.M.A.R.T. Read Log command; and full 2 bytes (max 65535
blocks) when access via Read Log EXT command.
The frequency at which S.M.A.R.T. logs are updated is the frequency at which
checkpoint information is saved. That frequency is related to data volume, and
can range between approximately 2 seconds and 2 minutes, depending on how