Seagate ST3300457FC Cheetah 15K.5 SCSI Product Manual - Page 25

SCSI Commands Reference Manual

Get Seagate ST3300457FC PDF manuals and user guides View all Seagate ST3300457FC manuals
Add to My Manuals
Save this manual to your list of manuals

Page 25 highlights

6.2.6.1 DST Failure Definition The drive will present a "diagnostic failed" condition through the self-tests results value of the diagnostic log page if a functional failure is encountered during DST. The channel and servo parameters are not modified to test the drive more stringently, and the number of retries are not reduced. All retries and recovery processes are enabled during the test. If data is recoverable, no failure condition will be reported regardless of the number of retries required to recover the data. The following conditions are considered DST failure conditions: • Seek error after retries are exhausted • Track-follow error after retries are exhausted • Read error after retries are exhausted • Write error after retries are exhausted Recovered errors will not be reported as diagnostic failures. 6.2.6.2 Implementation This section provides all of the information necessary to implement the DST function on this drive. 6.2.6.2.1 State of the drive prior to testing The drive must be in a ready state before issuing the Send Diagnostic command. There are multiple reasons why a drive may not be ready, some of which are valid conditions, and not errors. For example, a drive may be in process of doing a format, or another DST. It is the responsibility of the host application to determine the "not ready" cause. While not technically part of DST, a Not Ready condition also qualifies the drive to be returned to Seagate as a failed drive. A Drive Not Ready condition is reported by the drive under the following conditions: • Motor will not spin • Motor will not lock to speed • Servo will not lock on track • Drive cannot read configuration tables from the disc In these conditions, the drive responds to a Test Unit Ready command with an 02/04/00 or 02/04/03 code. 6.2.6.2.2 Invoking DST To invoke DST, submit the Send Diagnostic command with the appropriate Function Code (001b for the short test or 010b for the extended test) in bytes 1, bits 5, 6, and 7. Refer to the SCSI Commands Reference Manual, part number 100293068, for additional information about invoking DST. 6.2.6.2.3 Short and extended tests DST has two testing options: 1. short 2. extended These testing options are described in the following two subsections. Each test consists of three segments: an electrical test segment, a servo test segment, and a read/verify scan segment. Cheetah 15K.5 SCSI Product Manual, Rev. J 19

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
Cheetah 15K.5 SCSI Product Manual, Rev. J
19
6.2.6.1
DST Failure Definition
The drive will present a “diagnostic failed” condition through the self-tests results value of the diagnostic log
page if a functional failure is encountered during DST. The channel and servo parameters are not modified to
test the drive more stringently, and the number of retries are not reduced. All retries and recovery processes
are enabled during the test. If data is recoverable, no failure condition will be reported regardless of the number
of retries required to recover the data.
The following conditions are considered DST failure conditions:
•
Seek error after retries are exhausted
•
Track-follow error after retries are exhausted
•
Read error after retries are exhausted
•
Write error after retries are exhausted
Recovered errors will not be reported as diagnostic failures.
6.2.6.2
Implementation
This section provides all of the information necessary to implement the DST function on this drive.
6.2.6.2.1
State of the drive prior to testing
The drive must be in a ready state before issuing the Send Diagnostic command. There are multiple reasons
why a drive may not be ready, some of which are valid conditions, and not errors. For example, a drive may be
in process of doing a format, or another DST. It is the responsibility of the host application to determine the “not
ready” cause.
While not technically part of DST, a Not Ready condition also qualifies the drive to be returned to Seagate as a
failed drive.
A Drive Not Ready condition is reported by the drive under the following conditions:
•
Motor will not spin
•
Motor will not lock to speed
•
Servo will not lock on track
•
Drive cannot read configuration tables from the disc
In these conditions, the drive responds to a Test Unit Ready command with an 02/04/00 or 02/04/03 code.
6.2.6.2.2
Invoking DST
To invoke DST, submit the Send Diagnostic command with the appropriate Function Code (001b for the short
test or 010b for the extended test) in bytes 1, bits 5, 6, and 7. Refer to the
SCSI Commands Reference Manual
,
part number 100293068, for additional information about invoking DST.
6.2.6.2.3
Short and extended tests
DST has two testing options:
1.
short
2.
extended
These testing options are described in the following two subsections.
Each test consists of three segments: an electrical test segment, a servo test segment, and a read/verify scan
segment.