9.3.3.2 Flexible disk page
`
`The flexible disk page (see table 158) contains parameters for control and reporting of flexible disk drive parameters.
`
`Table 158 • Flexible disk page
`
`ANSI X3.131-1994
`
`8~Bit
`yte
`0
`
`7
`
`PS
`
`6
`
`5
`
`Reserved
`
`I 4
`
`3
`
`I 2
`
`I 1
`
`I 0
`
`Page code (05h)
`Page length in bytes ( 1 Eh)
`
`Transfer rate
`
`Number of heads
`Sectors per track
`
`Data bytes per sector
`
`Number of cylinders
`
`Starting cylinder-write precompensation
`
`Starting cylinder-reduced write current
`
`Drive step rate
`
`Drive step pulse width
`
`Head settle delay
`
`Motor on delay
`Motor off delay
`l
`Reserved
`
`Write compensation
`Head load delay
`Head unload delay
`
`Medium rotation rate
`
`Reserved
`Reserved
`
`~
`
`SPC
`
`Pin 2
`Pin 1
`
`-
`(LSB)
`
`-
`(LSB)
`
`-
`(LSB)
`
`(LSB)
`
`(LSB)
`-
`(LSB)
`
`-
`(LSB)
`
`-
`{LSB)
`
`(MSB)
`
`(MSB)
`
`(MSB)
`
`(MSB)
`
`(MSB)
`
`(MSB)
`
`(MSB)
`
`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
`
`TROY
`
`SSN
`Reserved
`
`MD
`
`Pin 34
`Pin 4
`
`The parameters savable (PS) bit is only used with the MODE SENSE command. This bit is reserved with the MODE
`SELECT command. A PS bit of one indicates that the target is capable of saving the page in a non-volatile vendor(cid:173)
`specific location.
`
`199
`
`ZTE (USA) 1006, Page 227
`
`

`
`ANSI X3.131-1994
`
`NOTE 125 This page is mainly intended for defining parameters of flexible disk drives, but may be used for other devices,
`if applicable.
`
`The transfer rate indicates the data rate of the peripheral device. See table 159 for examples of common transfer
`rates.
`
`Table 159 ·Examples of transfer rates
`
`Value
`OOFAh
`012Ch
`01F4h
`03E8h
`07DOh
`1388h
`
`Transfer rate
`250 kbit/s transfer rate
`300 kbit/s transfer rate
`500 kbit/s tranfer rate
`1 mbit/s transfer rate
`2 mbit/s transfer rate
`5 mbit/s transfer rate
`
`The number of heads field specifies the number of heads used for reading and writing data on the medium. Heads
`used exclusively for servo information are excluded.
`
`The sectors per track field specifies the number of sectors per revolution per head.
`
`The data bytes per sector field specifies the number of bytes of data per sector that an initiator can read or write.
`
`The number of cylinders field specifies the number of cylinders used for data storage.
`
`The starting cylinder for write precompensation field specifies the cylinder at which write precompensation is to begin.
`Cylinders are numbered starting with zero. If the starting cylinder for write precompensation is equal to the value in
`the number of cylinders field, write precompensation shall be disabled by the target.
`
`The starting cylinder for reduced write current field specifies cylinder at which write current is reduced. Cylinders are
`numbered starting with zero. If the starting cylinder for reduced write current is equal to the value in the number of
`cylinders field, reduced write current shall be disabled by the target.
`
`The drive step rate field specifies the step rate in units of 100 ps. This value may be rounded as defined in 7.5.4.
`A value of zero requests the target to set its default value.
`
`The drive step pulse width field specifies the width of the step pulse in microseconds. This value may be rounded
`as defined in 7.5.4. A value of zero requests the target to set its default value.
`
`The head settle delay field specifies the head settle time in units of 100 ps. This value may be rounded as defined
`in 7.5.4. A value of zero requests the target to set its default value.
`
`If a true ready signal is not available, the motor on delay field specifies in tenths of a second the time that the target
`shall wait before attempting to access the medium after the motor on signal is asserted. If a true ready signal is
`available, the motor on delay field specifies in tenths of a second the time that the target shall wait for drive ready
`status before aborting an attempt to access the medium. This value may be rounded as defined in 7.5.4.
`
`The motor off delay field specifies in tenths of a second the time that the target shall wait before releasing the motor
`on signal after an idle condition exists. A value of FFh indicates that the motor on signal shall not be released. The
`START STOP UNIT command is not affected by this parameter. This value may be rounded as defined in 7.5.4.
`
`A true ready (TROY) bit of one specifies that a signal is provided that indicates the medium is ready to be accessed.
`
`A start sector number (SSN) bit of one specifies that sectors are numbered starting with one. An SSN bit of zero
`specifies that sectors are numbered starting with zero.
`
`200
`
`ZTE (USA) 1006, Page 228
`
`

`
`ANSI X3 131-1994
`
`A motor on (MO) bit of one specifies that pin 16 (motor on) shall remain released. This bit shall be set to one when
`using high capacity (192 tracks per inch) drives and their pre-formatted diskettes. An MO bit of zero indicates that
`pin 16 (motor on) shall be asserted.
`
`The step pulse per cylinder (SPC) field is used to specify the number of additional step pulses required per cylinder.
`Non-zero values allow a drive to read a diskette formatted on a drive with a lower number of tracks per inch. For
`example, a value of one allows a 96 track-per-inch drive to access tracks on a diskette that was formatted for 48
`tracks per inch.
`
`The write compensation field is used to specify the amount of write compensation to be used starting at the cylinder
`specified in the starting cylinder for write precompensation field. The correlation of any values used in this field to
`actual write precompensation time values is vendor-specific. If a zero is specified in this field the target shall use its
`default write precompensation value. This value may be rounded as defined in 7.5.4.
`
`The head load delay field specifies the head loading time in milliseconds. This value may be rounded as defined in
`7.5.4. A value of zero requests the target to set its default value.
`
`The head unload delay field specifies the head unloading time in milliseconds. This value may be rounded as defined
`in 7.5.4. A value of zero requests the target to set its default value.
`
`The Pin 34 field defines the usage of pin 34 of the flexible disk drive interface. This use of this pin varies among
`vendors and drives. The settings allow the initiator to select how pin 34 shall be used by the interface. See table
`160.
`
`Bit 7 6 5 4
`p 0 0 0
`p 0 0 1
`p 0 1 0
`
`Table 160 • Pin 34 field
`
`Description of pin 34 use
`
`Open
`Ready
`Disk changed
`
`NOTES
`1 P is a polarity bit, where 0 is active low and 1 is active high.
`2 All undefined values are reserved.
`
`The pin 4 field defines the usage of pin 4 of the flexible disk drive interface. This use of this pin varies among drive
`vendors and drives. The settings allow the initiator to specify how pin 4 shall be used by the interface. See table
`161.
`
`Table 161 ·Pin 4 field
`
`Description of pin 4 use
`
`Bit 7 6 5 4
`p 0 0 0
`p 0 0 1
`p 0 1 0
`p 0 0 0
`NOTES
`1 P is a polarity bit, where 0 is active low and 1 is active high.
`2 All undefined values are reserved.
`
`Open
`In use
`Eject
`Head load
`
`The pin 1 field defines the usage of pin 1 of the flexible disk drive interface. This use of this pin varies among vendors
`and drives. The settings allow the initiator to specify how pin 1 shall be used by the interface. See table 162.
`
`201
`
`ZTE (USA) 1006, Page 229
`
`

`
`ANSI X3.131-1994
`
`Table 162 ·Pin 34 field
`
`Bit 7 6 5 4
`p 0 0 0
`p 0 0 1
`
`Description of pin 34 use
`Open
`Disk change reset
`
`NOTES
`1 P is a polarity bit, where 0 is active low and 1 is active high.
`2 All undefined values are reserved.
`
`The medium rotation rate field specifies the speed at which the medium rotates. The unit of measure is rotations pe
`minute (e.g. 2 400 rpm). This field cannot be changed by a MODE SELECT command.
`
`9.3.3.3 Format device page
`
`The format device page (see table 163) contains parameters which specify the medium format.
`
`202
`
`ZTE (USA) 1006, Page 230
`
`

`
`Table 163 ·Format device page
`
`6
`
`5
`
`Reserved
`
`I 4
`
`I 3
`
`I 2
`
`Page code (03h)
`Page length ( 16h)
`
`ANSI X3.131-1994
`
`I 1
`
`I 0
`
`gr 7
`
`0
`
`PS
`
`1
`
`2
`3
`4
`
`5
`6
`
`7
`
`8
`
`9
`10
`11
`12
`13
`14
`
`15
`16
`
`17
`
`18
`
`19
`
`(MSB)
`
`(MSB)
`
`{MSB)
`
`(MSB)
`
`(MSB)
`
`(MSB)
`
`(MSB)
`
`(MSB)
`
`(MSB)
`
`Tracks per zone
`
`Alternate sectors per zone
`
`Alternate tracks per zone
`
`Alternate tracks per logical unit
`
`Sectors per track
`
`Data bytes per physical sector
`
`Interleave
`
`Track skew factor
`
`Cylinder skew factor
`
`-
`(LSB)
`
`-
`{LSB)
`
`-
`(LSB)
`
`-
`(LSB)
`
`-
`(LSB)
`
`-
`(LSB)
`
`-
`(LSB)
`
`-
`{LSB)
`
`-
`(LSB)
`
`-
`
`20
`21 ----
`23
`
`SSEC
`
`HSEC
`
`RMB
`
`l SURF l
`
`Reserved
`
`Reserved
`
`The parameters savable (PS) bit is only used with the MODE SENSE command. This bit is reserved with the MODE
`SELECT command. A PS bit of one indicates that the target is capable of saving the page in a non-volatile vendor(cid:173)
`specific location.
`
`NOTE 126 If the initiator changes any of the current physical parameters defined below, the target may not be able to
`access the media until a FORMAT UNIT command has been successfully completed.
`
`If the defect handling format parameters (tracks per zone, alternate sectors per zone, alternate tracks per zone and
`alternate tracks per logical unit) requested by the initiator are not supported by the target the target may round these
`fields to acceptable values as described in 7.5.4.
`
`The tracks per zone field specifies the number of tracks per zone to use in dividing the capacity of the device for the
`purpose of allocating alternate sectors. A value of zero means that one zone is defined for the entire device. The
`last zone on the device might not contain the same number of tracks as the previous zone(s).
`
`203
`
`ZTE (USA) 1006, Page 231
`
`

`
`ANSI X3.131-1994
`
`The alternate sectors per zone field specifies the number of sectors per zone the target shall reserve for defec
`handling. The target shall de-allocate these sectors from the initiator addressable blocks during the FORMAT UNI
`command. If the notch page is implemented and the ND bit of the notch page is one and the active notch field c
`the notch page is zero, then a value of zero indicates that no alternate sectors shall be reserved. Otherwise, a valu
`of zero indicates that the number of alternate sectors is target specific.
`
`The alternate tracks per zone field specifies the number of tracks per zone the target shall reserve for defect handlin~
`The target shall de-allocate these tracks from the initiator addressable blocks during the FORMAT UNIT commanc
`lfthe notch page is implemented and the ND bit of the notch page is one and the active notch field ofthe notch pag
`is zero, then a value of zero indicates that no alternate tracks shall be reserved. Otherwise, a value of zero indicate
`that the number of alternate tracks is target specific.
`
`The alternate tracks per logical unit field specifies the number of tracks per logical unit the target shall reserve fc
`defect handling. The target shall de-allocate these tracks from the initiator addressable blocks during the FORMA
`UNIT command. lfthe notch page is implemented and the ND bit ofthe notch page is one and the active notch fief•
`of the notch page is zero, then a value of zero indicates that no alternate tracks shall be reserved. Otherwise, a valu
`of zero indicates that the number of alternate tracks is target specific.
`
`The sectors per track field specifies the number of physical sectors
`included within each track. This numbe
`includes any alternate sectors the target may allocate. A value of zero during MODE SELECT indicates that the targe
`shall define the number of sectors per track. For devices with a variable number of sectors per track, the value it
`MODE SELECT shall be zero and the value reported in MODE SENSE for the number of sectors per track is vendor
`specific.
`
`The data bytes per physical sector field specifies the number of data bytes per physical sector that the target sha
`use. This value may be different than the logical block size reported in the MODE SELECT data. The target sha
`return CHECK CONDITION status if it determines that the combination of this field and the sectors per track tiel<
`exceed the capability of the medium. A value of zero indicates that the data bytes per physical sector is defined b~
`the target.
`
`For MODE SENSE the interleave field returns the same parameter passed in the FORMAT UNIT command, The targe
`shall report this field as target defined in the corresponding MODE SENSE command. For MODE SELECT this fielc
`is ignored.
`
`NOTE 127 It is recommended that this field be marked non-changeable and that initiators send the value returned in MODE
`SENSE. This allows migration to specifying interleave as a mode parameter instead of in the FORMAT UNIT command.
`
`The track skew factor field specifies the number of physical sectors between the last logical block of one track anc
`the first logical block on the next sequential track of the same cylinder.
`
`The cylinder skew factor field specifies the number of physical sectors between the last logical block of one cylinde
`and the first logical block on the next sequential cylinder.
`
`The SSEC bit set to one indicates that the target shall use soft sector formatting.
`
`The HSEC bit set to one indicates that the target shall use hard sector formatting. The HSEC bit and the SSEC bi
`are mutually exclusive in MODE SELECT commands.
`
`The combinations sector formatting supported that are reported in response to a request for default values arE
`defined in table 164.
`
`204
`
`ZTE (USA) 1006, Page 232
`
`

`
`Table 164 • Reporting of default sector formatting support
`
`SSEC
`
`HSEC
`
`0
`1
`0
`1
`
`0
`0
`1
`1
`
`Description
`Target shall not return this combination
`Target supports soft sector formatting only
`Target supports hard sector formatting only
`Target supports both soft and hard sector formatting
`
`ANSI X3.131-1994
`
`The combinations sector formatting supported that are reported in response to a request for changeable values are
`defined in table 165.
`
`Table 165 • Reporting of changeable sector formatting support
`
`SSEC
`
`0
`1
`0
`1
`
`HSEC
`0
`0
`1
`1
`
`Description
`Sector formatting not changeable
`Target shall not return this combination
`Target shall not return this combination
`Target supports both soft and hard sector formatting
`
`The removable medium (RMB) bit set to one indicates that the logical unit supports removable media. A RMB bit
`set to zero indicates that the logical unit does not support removable media. The status of this bit shall be reflected
`in the INQUIRY command RMB bit.
`
`The surface (SURF) bit set to zero indicates that the target shall allocate progressive addresses to all logical blocks
`within a cylinder prior to allocating addresses on the next cylinder. A SURF bit set to one indicates that the target
`shall allocate progressive addresses to all logical blocks on a surface prior to allocating sector addresses on the next
`surface.
`
`NOTE 128 If the target supports savable parameters, all savable parameters for this initiator, including those in page codes
`3, 4, and 5, are saved to non-volatile memory when the save parameters bit (SP) in the command descriptor block is set
`to one. The savable parameters may also be saved to non-volatile memory during a FORMAT UNIT command (see 9.2.1).
`
`9.3.3.4 Medium types supported page
`
`The medium types supported page (see table 166) contains a list of the medium types implemented by the target
`for logical units.
`
`Table 166 • Medium types supported page
`
`Bit
`Byte
`0
`
`7
`
`PS
`
`6
`
`5
`
`Reserved
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`I 4
`
`I 3
`
`Page code (OBh)
`Page length (06h)
`Reserved
`Reserved
`Medium type one supported
`Medium type two supported
`Medium type three supported
`M~:dium type four supported
`
`I 2
`
`I 1
`
`I 0
`
`205
`
`ZTE (USA) 1006, Page 233
`
`

`
`ANSI X3.131-1994
`
`The parameters savable (PS) bit is only used with the MODE SENSE command. This bit is reserved with the MODE
`SELECT command. A PS bit of one indicates that the target is capable of saving the page in a non-volatile vendor(cid:173)
`specific location.
`
`The code values for each medium type supported by the target (up to four maximum), are reported in ascending
`order. If only the default medium type is supported zero is reported. If less than four medium types are supported
`the unused entries shall be returned as zero.
`
`9.3.3.5 Notch and partHion page
`
`The notch page (see table 167) contains parameters for direct-access devices which implement a variable number
`of blocks per cylinder and support this page. Each clause of the logical unit with a different number of blocks per
`cylinder is referred to as a notch.
`
`fsJ;t
`
`0
`1
`2
`3
`4
`
`5
`6
`
`7
`
`7
`
`PS
`
`NO
`
`(MSB)
`
`(MSB)
`
`(MSB}
`8
`f - - - f - -
`11
`12
`(MSB}
`f - - - 1--
`15
`16
`(MSB}
`f - - - f - -
`23
`
`Table 167 ·Notch page
`
`6
`
`5
`
`Reserved
`
`LPN
`
`I 4
`
`I 3
`
`Page code (OCh}
`Page length ( 16h}
`Reserved
`Reserved
`
`I 2
`
`I 1
`
`I 0
`
`Maximum number of notches
`
`Active notch
`
`Starting boundary
`
`Ending boundary
`
`Pages notched
`
`-
`(LSB}
`
`-
`(LSB)
`
`-
`(LSB}
`
`-
`(LSB}
`
`-
`(LSB}
`
`The parameters savable (PS) bit is only used with the MODE SENSE command. This bit is reserved with the MODE
`SELECT command. A PS bit of one indicates that the target is capable of saving the page in a non-volatile vendor(cid:173)
`specific location.
`
`A notched drive (NO) bit of zero indicates that the device is not notched and that all other parameters in this page
`shall be returned as zero by the target. A ND bit of one indicates that the device is notched. For each supported
`active notch value this page defines the starting and ending boundaries of the notch.
`
`A logical or physical notch (LPN) bit of zero indicates that the boundaries are based on the physical parameters of
`the logical unit. The cylinder is considered most significant, the head least significant. A LPN bit of one indicates
`that the notch boundaries are based on logical blocks of the logical unit.
`
`The maximum number of notches field indicates the maximum number of notches supported by the logical unit. This
`field shall be reported as unchangeable.
`
`206
`
`ZTE (USA) 1006, Page 234
`
`

`
`ANSlX3J314994
`
`The active notch field indicates the notch that this and subsequent MODE SELECT and MODE SENSE commands
`shall refer to, until the active notch is changed by a later MODE SELECT command. The value of the active notch
`shall be greater than or equal to 0 and less than or equal to the maximum number of notches. An active notch value
`of zero indicates that this and subsequent MODE SELECT and MODE SENSE commands refer to the parameters that
`apply across all notches.
`
`The starting boundary field indicates the beginning of the active notch or, if the active notch is zero, the beginning
`boundary of the logical unit.
`if the LPN bit is one, then the four bytes represent a iogical block address.
`if the LPN
`bit is zero, then the three most significant bytes shall represent the cylinder number and the least significant byte shall
`represent the head number. This field shall be reported as unchangeable. When used with the MODE SELECT
`command this field is ignored.
`
`The ending boundary field indicates the ending of the active notch or, ifthe active notch is zero, the ending of the
`logical unit.
`if the LPN bit is one, then the four bytes represent logical block address.
`if the LPN bit is zero, then the
`three most significant bytes shall represent the cylinder number and the least significant byte shall represent the head
`number. This field shall be reported as unchangeable. When used with the MODE SELECT command this field is
`ignored.
`
`Each notch shall span a set of consecutive logical blocks on the logical unit, the notches shall not overlap, and no
`logical block shall be excluded from a notch.
`
`The pages notched field is a bit map of the mode page codes that indicates which pages contain parameters that
`may be different for different notches. The most significant bit of this field corresponds to page code 3Fh and the
`least significant bit corresponds to page code Ooh.
`if a bit is one, then the corresponding mode page contains
`parameters that may be different for different notches.
`if a bit is zero, then the corresponding mode page contains
`parameters that are constant for all notches. This field shall be reported as unchangeable.
`
`9.3.3.6 Read-write error recovery page
`
`The read-write error recovery page (see table 168) specifies the error recovery parameters the target shall use during
`any command that performs a read or write operation to the medium (e.g. READ (6), FtEAD(10), WRlTE(6), WRlTE(10),
`COPY, COMPARE, WRITE & VERIFY, etc.).
`
`Table 168 - Read-wrlte error recovery page
`
`-7M"WWWH“"”‘i"
`code (om)
`l
`Page length (OAh)
`RC
`
`‘ l
`
`PER
`
`DTE
`
`DCR
`
`
`
`
`
`
`
`
`
`
`Reserved
`
`AWRE
`
`ARRE
`
`TB
`
`Read retry count
`
`(MSB)
`
`Recovery time limit
`
`
`
`
`
`
`(LSB)
`
`207
`
`ZTE (USA) 1006, Page 235
`
`ZTE (USA) 1006, Page 235
`
`

`
`ANSI X8181-1 994
`
`The parameters savable (PS) bit is only used with the MODE SENSE command. This bit is reserved with the MODE
`SELECT command. A PS bit of one indicates that the target is capable of saving the page in a non-volatile vendor
`specific location.
`
`An automatic write reallocation enabled (AWRE) bit of one indicates that the target shall enable automatic reallocatioi
`to be performed during write operations. The automatic reallocation shall be performed only ifthe target has the valic
`data (e.g. original data in the buffer or recovered from the medium). The valid data shall be placed in the reallocate<
`block. Error reporting as required by the error recovery bits (EER, PER, DTE, and DCR) shall be performed only afte
`completion of the reallocation. The reallocation operation shall report any failures that occur. See the REASSIGF
`BLOCKS command (92.10) for error procedures.
`
`An AWRE bit of zero indicates that the target shall not perform automatic reallocation of defective data blocks during
`write operations.
`
`An automatic read reallocation enabled (ARRE) bit of one indicates that the target shall enable automatic reallocatioi
`of defective data blocks during read operations. All error recovery actions required by the error recovery bits (TE
`EEFl, PER, DTE, and DCR) shall be executed. The automatic reallocation shall then be performed only if the targe
`successfully recovers the data. The recovered data shall be placed in the reallocated block. Error reporting a:
`required by the error recovery bits shall be performed only after completion of the reallocation. The reallocatio:
`process shall present any failures that occur. See the REASSIGN BLOCKS command (92.10) for error procedures.
`
`An ARRE bit of zero indicates that the target shall not perform automatic reallocation of defective data blocks during
`read operations.
`
`A transfer block (TB) bit of one indicates that a data block that is not recovered within the recovery limits specifier
`shall be transferred to the initiator before CHECK CONDITION status is returned. A TB bit of zero indicates that sue!
`a data block shall not be transferred to the initiator. The TB bit does not affect the action taken for recovered data
`
`A read continuous (RC) bit of one indicates the target shali transfer the entire requested length of data without adding
`delays to perform error recovery procedures. This implies that the target may send data that is erroneous o
`fabricated in order to maintain a continuous flow of data. The target shall assign priority to this bit over conflicting
`error control bits (EER, DCR, DTE, and PER) within this byte.
`
`NOTE 129 Fabricated data may be data already in the buffer orany other target-specific data. This bit is typically used
`in image processing, audio, or video applications.
`
`A RC bit of zero indicates that error recovery operations that cause delays are acceptable during the data transfer
`Data shall not be fabricated.
`
`The individual bit definitions for EER, PER, DTE and DCR are contained in table 169. The combinations of these bit‘
`are explained in table 170.
`
`208
`
`ZTE (USA) 1006, Page 236
`
`ZTE (USA) 1006, Page 236
`
`

`
`Table 169 - Error recovery bit definitions
`
`ANSlX&1314994
`
`
`
`
`
`WH“--V'flwMMM
`EER
`Fen DTE
`
`ocn
`
`
`
`
`
`
`An enable early recovery (EER) bit of one indicates that
`the target shall use of the most expedient form of error
`recovery first. This bit only applies to data error
`recovery and it does not affect positioning retries and
`the message system error recovery procedures.
`
`Descriptionm—%_mm“#“#—mA*_
`
`
`
`
`An EER bit of zero indicates that the target shall use an
`error recovery procedure that minimizes the risk of mis-
`
`detection or mis-correction.
`
`A post error (PER) bit of one indicates that the target
`shall report recovered errors.
`
`
`
`A PER bit of zero indicates that the target shall not
`report recovered errors. Error recovery procedures shall
`
`be performed within the limits established by the error
`recovery parameters.
`
`
`A disable transfer on error (DTE) bit of one indicates
`that the target shall terminate the data phase upon
`
`detection of a recovered error.
`
`A DTE bit of zero indicates that the target shall not
`terminate the data phase upon detection of a recovered
`error.
`
`
`
`A disable correction (DCR) bit of one indicates that
`error correction codes shall not be used for data error
`
`recovery.
`A DCR bit of zero allows the use of error correction
`codes for data error recovery.
`
`
`
`
`
`
`
`
`NOTE 130 An EEFl bit of one may imply an increase in the probability of mis-detection or mis-correction. An EER bit of
`zero typically means that the specified retry limit is exhausted prior to using error correction codes.
`
`209
`
`ZTE (USA) 1006, Page 237
`
`ZTE (USA) 1006, Page 237
`
`

`
`ANSiX3A314994
`
`
`
`
`
`
`
`Table 170 - Combined error recovery parameter descriptions
`
` I’
`Dscp
`
`
` The full number of retries (specified in the read, write
`or verify retry count field) and error correction are
`
`attempted to recover the data (EER and DCR set to 0).
`A
`CHECK CONDITION is not reported at the completion of the
`
`command for recovered errors (PER set to O).
`The command
`terminates with CHECK CONDITION status before the
`
`transfer count is exhausted only if an unrecoverable
`
`error is detected.
`If an unrecoverable data error
`occurred,
`the data in the block with the unrecoverable
`
`error may or may not be transferred to the initiator
`depending on the setting of the transfer block (TB) bit
`(read operation only).
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Error correction is disabled (DCR set to one) so only the
`full number of retries (specified in the read, write or
`verify retry count field) are attempted to recover the
`data (EER set to D).
`A CHECK CONDITION is not reported
`at the completion of the command for recoverable errors
`(PER set to O).
`The command terminates with CHECK
`CONDITION status before the transfer count is exhausted
`only if an unrecoverable error is detected.
`If an
`unrecoverable data error occurred,
`the data in the block
`with the unrecoverable error may or may not be
`transferred to the initiator depending on the setting of
`the transfer block (TB) bit (read operation only).
`
`
`
`Invalid mode (PER must be set to one if DTE is set to
`
`one).
`1)
`
`
`one).
`Invalid1mode (PER must be set to one if DTE is set to
` The full number of retries (specified in the read, write
`
`
`or verify retry count field) and error correction are
`
`
`attempted to recover the data (EER and DCR set to 0).
`The command terminates with CHECK CONDITION status before
`the transfer count is exhausted only if an unrecoverable
`error is detected.
`If an unrecoverable data error
`occurred,
`the data in the block with the unrecoverable
`error may or may not be transferred to the initiator
`depending on the setting of the transfer block (TB) bit
`(read operation only).
`A CHECK CONDITION with a sense
`key of RECOVERED ERROR is reported at the completion of
`the command for any recoverable error that occurs (PER
`
`set to 1).
`The information field in the sense data shall
`
`contain the logical block address of the last recovered
`error which occurred during the transfer.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`210
`
`ZTE (USA) 1006, Page 238
`
`ZTE (USA) 1006, Page 238
`
`

`
`Table 170 - (continued)
`
`ANSIX3J314994
`
`
`
`
`
`
`
`
`EER
`
`PER DTE
`
`DCR
`
`
`
`
`
`
`Description
`
`Error correction is disabled (DCR set to one) so only the
`full number of retries (specified in the read, write or
`verify retry count field) are attempted to recover the
`data (EER set to 0).
`The command terminates with CHECK
`CONDITION status before the transfer count is exhausted
`only if an unrecoverable error is detected.
`If an
`unrficogerable data Error occurred,
`the data fin the block
`wit
`t e unrecovera
`e error may or may not
`e
`transferred to the initiator depending on the setting of
`‘BEc§"é3§S?¥:8%.°°“u€“’ W‘ ‘£”“ $”SE35$§3eB"éK%aa A
`C
`wi
`a sense
`e
`o
`is
`reported at the com letion of the command for any
`recoverable error t at occurs (PER set to 1).
`The
`information field in the sense data shall contain the
`logical block address of the last recovered error which
`occurred during the transfer.
`
`The full number of retries (specified in the read, write
`or verify retry count field) and error correction are
`attempted to recover the data (EEH and DCR set to 0).
`The command terminates with CHECK CONDITION status before
`the transfer count is exhausted if any error (recoverable
`or unrecoverable) is detected (DTE set to 1).
`The
`information field in the sense data shall contain the
`logical block address of the block in error.
`If an
`unrecoverable data error occurs the data in the block
`with the error may or may not be transferred to the
`initiator depending on t a setting of the transfer block
`(TB) bit (reed operation only).
`
`Error correction is disabled (OCR set to one) so only the
`full number of retries (specified in the read, write or
`verify retry count field) are attempted to recover the
`data (EER set to O).
`The command terminates with CHECK
`CONDITION status before the transfer count is exhausted
`if any error (recoverable or unrecoverable) is detected
`(DTE set to 1).
`The information field in the sense data
`shall contain the logical block address of the block in
`error.
`If an unrecoverable data error occurs the data in
`the block with the error may or may not be transferred to
`the initiator depending on the setting of the transfer
`block (TB) bit (read operation only).
`
`
`
`The fewest possible retries and error correction are
`attempted to recover the data (EER set to one and DCR set
`to 0).
`A CHECK CONDITION is not reported at the
`completion of the command for recoverable errors (PER set
`to 0).
`The command terminates with CHECK CONDITION
`status before the transfer count is exhausted only if an
`unrecoverable error is detected.
`If an unrecoverable
`data error occurred,
`the data in the block with the
`unrecoverable error may or may not be transferred to the
`initiator depending on the setting of the transfer block
`(TB) bit (read operation only).
`
`
`
`
`
`
`
`211
`
`ZTE (USA) 1006, Page 239
`
`ZTE (USA) 1006, Page 239
`
`

`
`ANSlX3J314994
`
`Table 170 - (concluded)
`
`ER PER DTE
`
`ocn
`
`
`
`Invalid mode (OCR must be set to zero if EER is set to
`one).
`1)
`
`
`Invalid made
`
`(PER must be set to one if DTE is set to
`one).
`1)
`
`
`
`
`
`
`
`Invalid mode (PER must be set to one if DTE is set to
`one).
`1)
`
`
`
`
`
`
`
`
`
`
`
`
`
`The fewest possible retries and error correction are
`attempted to recover the data (EER set to one and DCR set
`
`to O).
`The command terminates with CHECK CONDITION
`status before the transfer count is exhausted only if an
`unrecoverable error is detected.
`If an unrecoverable
`
`data error occurred,
`the data in the block with the
`unrecoverable error may or may not be transferred to the
`initiator depending on the setting of the transfer block
`
`(TB) bit (read operation only).
`A CHECK CONDITION with a
`sense key of RECOVERED ERROR is reported at the
`completion of the command for any recoverable error that
`occurs (PER set to 1).
`The information field in the
`sense data shall contain the logical block address of the
`last recovered error which occurred during the transfer.
`
`
`
`Invalid mode (DCR must be set to zero if EER is set to
`one).
`1)
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`The fewest possible retries and error correction are
`attempted to recover the data (EER set to one and DCR set
`to O).
`The command terminates with CHECK CONDITION
`status before the transfer count is exhausted if an
`error (recoverable pr unrecoverable) is detected (D E set
`to 1).
`The information field in the sense data shall
`contain the logical block address of the block in error.
`If an unrecovera