Seagate ST336754SS Cheetah 15K.4 SAS Product Manual - Page 50

SAS system errors

Page 50 highlights

When the RC bit is one, reallocations are disabled even if the ARRE or AWRE bits are one. The drive will still perform data recovery actions within the limits defined by the Read Retry Count, Write Retry Count, and Recovery Time Limit parameters. However, the drive does not report any unrecovered errors. Table 5: Read and write retry count maximum recovery times Maximum recovery time per Read retry count1 LBA (cumulative, msec) 0 51.87 1 59.85 2 203.49 3 235.41 4 271.32 5 283.29 6 315.21 7 395.01 8 454.86 9 486.78 10 522.69 11 (default) 1,264.83 Maximum recovery time per Write retry count1 LBA (cumulative, msec) 0 23.94 1 35.91 2 55.86 3 67.83 4 119.7 5 (default) 147.63 [1] Setting these retry counts to a value below the default setting could result in degradation of the unrecovered error rate which may exceed the value given in this product manual. A setting of zero (0) will result in the drive not performing error recovery. For example, suppose the read/write recovery page has the RC bit set to 0, read retry count set to 4, and the recovery time limit field (Mode Sense page 01, bytes 10 and 11) set to FF FF hex (maximum). A four LBA Read command is allowed to take up to 271.32 msec recovery time for each of the four LBAs in the command. If the recovery time limit is set to 00 C8 hex (200 msec decimal) a four LBA read command is allowed to take up to 200 msec for all error recovery within that command. The use of the Recovery Time Limit field allows finer granularity on control of the time spent in error recovery. The recovery time limit only starts counting when the drive is executing error recovery and it restarts on each command. Therefore, each command's total recovery time is subject to the recovery time limit. Note: A recovery time limit of 0 will use the drive's default value of FF FF. Minimum recovery time limit is achieved by setting the Recovery Time Limit field to 00 01. 7.3 SAS system errors Information on the reporting of operational errors or faults across the interface is given in the SAS Interface Manual. The SSP Response returns information to the host about numerous kinds of errors or faults. The Receive Diagnostic Results reports the results of diagnostic operations performed by the drive. Status returned by the drive to the initiator is described in the SAS Interface Manual. Status reporting plays a role in systems error management and its use in that respect is described in sections where the various commands are discussed. 40 Cheetah 15K.4 SAS Product Manual, Rev. B

  • 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
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94

40
Cheetah 15K.4 SAS Product Manual, Rev. B
When the RC bit is one, reallocations are disabled even if the ARRE or AWRE bits are one. The drive will still
perform data recovery actions within the limits defined by the Read Retry Count, Write Retry Count, and
Recovery Time Limit parameters. However, the drive does not report any unrecovered errors.
[1]
Setting these retry counts to a value below the default setting could result in degradation of the unrecov-
ered error rate which may exceed the value given in this product manual. A setting of zero (0) will result in
the drive not performing error recovery.
For example, suppose the read/write recovery page has the RC bit set to 0, read retry count set to 4, and
the recovery time limit field (Mode Sense page 01, bytes 10 and 11) set to FF FF hex (maximum). A four
LBA Read command is allowed to take up to 271.32 msec recovery time for each of the four LBAs in the
command. If the recovery time limit is set to 00 C8 hex (200 msec decimal) a four LBA read command is
allowed to take up to 200 msec for all error recovery within that command. The use of the Recovery Time
Limit field allows finer granularity on control of the time spent in error recovery. The recovery time limit
only starts counting when the drive is executing error recovery and it restarts on each command. There-
fore, each command’s total recovery time is subject to the recovery time limit. Note: A recovery time limit
of 0 will use the drive’s default value of FF FF. Minimum recovery time limit is achieved by setting the
Recovery Time Limit field to 00 01.
7.3
SAS system errors
Information on the reporting of operational errors or faults across the interface is given in the
SAS Interface
Manual
. The SSP Response returns information to the host about numerous kinds of errors or faults. The
Receive Diagnostic Results reports the results of diagnostic operations performed by the drive.
Status returned by the drive to the initiator is described in the
SAS Interface Manual.
Status reporting plays a
role in systems error management and its use in that respect is described in sections where the various com-
mands are discussed.
Table 5:
Read and write retry count maximum recovery times
Read retry count
1
Maximum recovery time per
LBA (cumulative, msec)
Write retry count
1
Maximum recovery time per
LBA (cumulative, msec)
0
51.87
0
23.94
1
59.85
1
35.91
2
203.49
2
55.86
3
235.41
3
67.83
4
271.32
4
119.7
5
283.29
5 (default)
147.63
6
315.21
7
395.01
8
454.86
9
486.78
10
522.69
11 (default)
1,264.83