Seagate ST19171WC Product Manual - Page 43

Defect and error management

Page 43 highlights

Barracuda 9 Product Manual, Rev. C 33 7.0 Defect and error management The drive, as delivered, complies with this product manual. The read error rate and specified storage capacities are not dependent on using defect management routines by the host (initiator). Defect and error management in the SCSI system involves the drive internal defect/error management and SCSI systems error considerations (errors in communications between Initiator and the drive). Tools for use in designing a defect/error management plan are briefly outlined in this section, with references to other sections where further details are given. 7.1 Drive internal defects During the initial drive format operation at the factory, media defects are identified, tagged as being unusable, and their locations recorded on the drive primary defects list (referred to as the "P" list and also as the EFT defect list). At factory format time, these known defects are also reallocated, that is, reassigned to a new place on the medium and the location listed in the defects reallocation table. The "P" list is not altered after factory formatting. Locations of defects found and reallocated during error recovery procedures after drive shipment are listed in the "G" list (defects growth list). The "P" and "G" lists may be referenced by the initiator using the Read Defect Data command (see Section 5.2.1.2 in the SCSI Interface Product Manual, part number 77738479). 7.2 Drive error recovery procedures Whenever an error occurs during drive operation, the drive, if programmed to do so, performs error recovery procedures to attempt to recover the data. The error recovery procedures used depend on the options previously set up in the error recovery parameters mode page. Error recovery and defect management may involve the use of several SCSI commands, the details of which are described in the SCSI Interface Product Manual. The drive implements selectable error recovery time limits such as are required in video applications. For additional information on this, refer to Table 5.2.1-22 in the SCSI Interface Product Manual which describes the Mode Select/Mode Sense Error Recovery parameters. The error recovery scheme supported by the drive provides a means to control the total error recovery time for the entire command in addition to controlling the recovery level for a single LBA. The total amount of time spent in error recovery for a command can be limited via the Recovery Time Limit bytes in the Error Recovery Mode Page. The total amount of time spent in error recovery for a single LBA can be limited via the Read Retry Count or Write Retry Count bytes in the Error Recovery Mode Page. The drive firmware error recovery algorithms consist of 16 levels for read recoveries and 12 levels for writes. Each level may consist of multiple steps, where a step is defined as a recovery function involving a single reread or re-write attempt. The maximum level used by the drive in LBA recovery is determined by the Read and Write Retry Counts. Table 4 equates the Read and Write Retry Count with the maximum possible recovery time for read and write recovery of individual LBAs. The times given do not include time taken to perform reallocations, if reallocations are performed. Reallocations are performed when the ARRE bit (for reads) or AWRE bit (for writes) is one, the RC bit is zero, and the Recovery Time Limit for the command has not yet been met. Time needed to perform reallocation is not counted against the Recovery Time Limit. 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
  • 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

Barracuda 9 Product Manual, Rev. C
33
7.0
Defect and error management
The drive, as delivered, complies with this product manual. The read error rate and specified storage capaci-
ties are not dependent on using defect management routines by the host (initiator).
Defect and error management in the SCSI system involves the drive internal defect/error management and
SCSI systems error considerations (errors in communications between Initiator and the drive). Tools for use in
designing a defect/error management plan are briefly outlined in this section, with references to other sections
where further details are given.
7.1
Drive internal defects
During the initial drive format operation at the factory, media defects are identified, tagged as being unusable,
and their locations recorded on the drive primary defects list (referred to as the “P” list and also as the EFT
defect list). At factory format time, these known defects are also reallocated, that is, reassigned to a new place
on the medium and the location listed in the defects reallocation table. The “P” list is not altered after factory
formatting. Locations of defects found and reallocated during error recovery procedures after drive shipment
are listed in the “G” list (defects growth list). The “P” and “G” lists may be referenced by the initiator using the
Read Defect Data command (see Section 5.2.1.2 in the
SCSI Interface Product Manual,
part number
77738479).
7.2
Drive error recovery procedures
Whenever an error occurs during drive operation, the drive, if programmed to do so, performs error recovery
procedures to attempt to recover the data. The error recovery procedures used depend on the options previ-
ously set up in the error recovery parameters mode page. Error recovery and defect management may involve
the use of several SCSI commands, the details of which are described in the
SCSI Interface Product Manual.
The drive implements selectable error recovery time limits such as are required in video applications. For addi-
tional information on this, refer to Table 5.2.1-22 in the
SCSI Interface Product Manual
which describes the
Mode Select/Mode Sense Error Recovery parameters.
The error recovery scheme supported by the drive provides a means to control the total error recovery time for
the entire command in addition to controlling the recovery level for a single LBA. The total amount of time spent
in error recovery for a command can be limited via the Recovery Time Limit bytes in the Error Recovery Mode
Page. The total amount of time spent in error recovery for a single LBA can be limited via the Read Retry
Count or Write Retry Count bytes in the Error Recovery Mode Page.
The drive firmware error recovery algorithms consist of 16 levels for read recoveries and 12 levels for writes.
Each level may consist of multiple steps, where a step is defined as a recovery function involving a single re-
read or re-write attempt. The maximum level used by the drive in LBA recovery is determined by the Read and
Write Retry Counts.
Table 4 equates the Read and Write Retry Count with the maximum possible recovery time for read and write
recovery of individual LBAs. The times given do not include time taken to perform reallocations, if reallocations
are performed. Reallocations are performed when the ARRE bit (for reads) or AWRE bit (for writes) is one, the
RC bit is zero, and the Recovery Time Limit for the command has not yet been met. Time needed to perform
reallocation is not counted against the Recovery Time Limit.
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.