ANSI X3.131-1994
`
`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 O 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 reler 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 logical block address.
`It 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. it the active notch is zero. the ending of the
`logical unit.
`lithe LPN bit is one. then the four bytes represent logical block address.
`It 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
`ig nored.
`
`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 00h.
`It a bit is one. then the corresponding mode page contains
`parameters that may be different for difierent notches.
`it a bit is zero. then the corresponding mode page contains
`parameters that are constant tor all notches. This field shall be reported as unchangeable.
`
`9.3.3.6 Heed-write error recovery page
`
`The read-write error recovery page (see table 138) specifies the error recovery parameters the target shall use during
`any command that performs a read or write operation to the medium {e.g.FiEAD(B). HEADHD),WRITElS}.WHITE(1D],
`COPY, COMPARE. WRITE & VERIFY. etc.).
`
`Table 158 - Rea d-wrlte error recovery page
`
`use
`
`an
`
`_n
`
`-"m-mm
`
`l____
`__
`
`'
`
`
`
`{M83}-10
`
`Recovery time limit
`
`207
`
`(cid:50)(cid:47)(cid:60)(cid:48)(cid:51)(cid:56)(cid:54)(cid:3)(cid:40)(cid:59)(cid:17)(cid:3)(cid:20)(cid:19)(cid:20)(cid:23)(cid:3)(cid:16)(cid:3)(cid:21)(cid:22)(cid:24)(cid:18)(cid:23)(cid:25)(cid:27)
`
`OLYMPUS EX. 1014 - 235/468
`
`

`

`ANSI X3.131-1994
`
`The parameters savable (PS) bit is only used with the MODE SENSE command. This bit is reserved with the MODS
`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 (AWFlE) bit of one indicates that the target shall enable automatic reallocatioi
`to be perforrned during write operations. The automatic reallocation shall be performed only tithe target has the veil:
`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 (EEFl. PER. UTE. and OOH) shall be performed only atte
`completion of the reallocation. The reallocation operation shall report any failures that occur. See the HEASSlGl‘
`BLOCKS command (9.2.10) for error procedures.
`
`An AWFIE bit of zero indicates that the target shall not perform automatic reallocation of defective data blocks during
`write operations.
`
`An automatic read reallocation enabled (ARHE) bit of one indicates that the target shall enable automatic reallocation
`of defective data blocks during read operations. All error recovery actions required by the error recovery bits (TE
`EER. F'ER. DTE, and OCR) shall be executed. The automatic reallocation shall then be performed only if the targe
`successtully 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 reallocatioi
`process shall present any failures that occur. See the FIEASSIGN BLOCKS command (9.2.10) for error procedures.
`
`An AHBE 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 TE bit of zero indicates that cool
`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 (FIG) bit of one indicates the target shall transfer the entire requested length of data without add in;
`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, DCFl. DTE. and PEFI) within this byte.
`
`NOTE 129 Fabricated data may be data already In the buffer or any 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 transfa
`Data shall not be fabricated.
`
`The individual bit definitions for EEFI. PEH. DTE and DOE are contained in table 169. The combinations of these bit-
`are explained in table 170.
`
`208
`
`(cid:50)(cid:47)(cid:60)(cid:48)(cid:51)(cid:56)(cid:54)(cid:3)(cid:40)(cid:59)(cid:17)(cid:3)(cid:20)(cid:19)(cid:20)(cid:23)(cid:3)(cid:16)(cid:3)(cid:21)(cid:22)(cid:25)(cid:18)(cid:23)(cid:25)(cid:27)
`
`OLYMPUS EX. 1014 - 236/468
`
`

`

`T—ahle169 - Error recovery bit definitions
`
`ANSJX3J314QQA
`
`' A
`
`n 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.
`
`
`
`An EEH 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
`EPPOI".
`
`A disable correction {OCR} bit of one indicates that
`error correction codes shall not he used for data error
`recovery.
`
`A non bit of zero allows the use of error correction
`
`codes for data error recovery
`
`NOTE 130 An EEFi bit of one may imply an Increase in the probability oi mis-detection or mic-correction. An EEH bit of
`zero typically means that the specified retry limit is exhausted prior to using error correction codes.
`
`209
`
`(cid:50)(cid:47)(cid:60)(cid:48)(cid:51)(cid:56)(cid:54)(cid:3)(cid:40)(cid:59)(cid:17)(cid:3)(cid:20)(cid:19)(cid:20)(cid:23)(cid:3)(cid:16)(cid:3)(cid:21)(cid:22)(cid:26)(cid:18)(cid:23)(cid:25)(cid:27)
`
`OLYMPUS EX. 1014 - 237/468
`
`

`

`ANSlXana14994
`
`
`Table 170 - Combined error recovery parameter desorlptlons
`
`Description
`
` sen PEH o'reocn
`
`
`
`
`
`
`
`The full number of retries (specified in the read. write
`or verify retry count field} and error correction are
`A
`attempted to recover the data (EEH and OCR set to O).
`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
`occurredI
`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 OCR set to one} so only the
`
`full number of retries
`speci led in the read, write or
`
`verify retry count fiel } are attem ted to recover the
`
`data [EER set to O}.
`A CHECK CONDI
`ION is not reported
`at the completion of the command for recoverable errors
`(PEH 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}
`
`Invalid mode {PER must be set to one if DTE is set to
`one}.
`1}
`
`
`
`0
`
`o
`
`1
`
`1
`
`O
`
`1
`
`O
`
`O
`
`
`
`
`
`
`
`
`
`
`
`
`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 DCH set to O}.
`The command terminates with CH CK 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 EHHOH is regorted at the completion of
`
`
`the command for any recovers 1e 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
`
`(cid:50)(cid:47)(cid:60)(cid:48)(cid:51)(cid:56)(cid:54)(cid:3)(cid:40)(cid:59)(cid:17)(cid:3)(cid:20)(cid:19)(cid:20)(cid:23)(cid:3)(cid:16)(cid:3)(cid:21)(cid:22)(cid:27)(cid:18)(cid:23)(cid:25)(cid:27)
`
`OLYMPUS EX. 1014 - 238/468
`
`

`

`
`Table 170 - (contlnued)
`
`ANSIX3J314994
`
`
`
`
`
`; o
`
`o
`
`1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`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 {EEH 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 settin of
`the transfer block {TB} bit {read operation only).
`CHECK CONDITION with a sense he
`of RECOVERED E ROH is
`reported at the com leticn of t a command for an
`recoverable error t at occurs [PER set to 1}.
`T e
`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 do a
`EEH and OCH set to O .
`The command terminates with CH CK CONDITION status
`efore
`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 me
`not be transferred to the
`initiator depending on t e 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
`speci ied in the read. write or
`verify retry count fiel ) are attempted to recover the
`data (EER set to 0).
`The command terminates with CHECK
`CONDITION status before the transfer count is exhausted
`if any error (recoverable or unrecoverable) is detected
`[OTE set to 1).
`The information field in the sense date
`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 [EEH set to one and OCR set
`to Di.
`A CHECK CONDITION is not reported at the
`comp etion 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}.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`211
`
`(cid:50)(cid:47)(cid:60)(cid:48)(cid:51)(cid:56)(cid:54)(cid:3)(cid:40)(cid:59)(cid:17)(cid:3)(cid:20)(cid:19)(cid:20)(cid:23)(cid:3)(cid:16)(cid:3)(cid:21)(cid:22)(cid:28)(cid:18)(cid:23)(cid:25)(cid:27)
`
`OLYMPUS EX. 1014 - 239/468
`
`

`

`ANSI X3.131-1994
`
`Table 170- (concluded)
`
`one]
`
`
`
`Invalid1Tode [OCR must be set to zero if EER is set to
`Invalid mode
`[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 settin of the transfer block
`
`
`{TB} bit (read operation only}.
`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 recovared error which occurred during the transfer.
`
`
`1
`
`
`
`
`
`
`Invalid Tode (OCR must be set to zero if EEH is set to
`one .
`The fewest possible retries and error correction are
`attempted to recover the data [EER set to one and OCR set
`to O}.
`The command terminates with CHECK CONDITION
`status before the transfer count is exhausted if an
`error (recoverable or unrecoverable] is detected (D E set
`to 1} The information field in the sense data shall
`contain the log icel 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).
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Invalid mode (OCR must be set to zero if EER is set to
`one}.
`1}
`
` status with the sense key set to ILLEGAL REQUEST and the
`
`'
`If an invalid mode for the error recovery combination is
`sent by the initiator the target shall return CHECK CONDITION
`
`additional sense code set to INVALID FIELD IN PARAMETER LIST.
`
`The read and write retry count fields specify the number of times that the target shall attempt its recovery
`algorithm during read and write operations. respectively.
`If the retry count field and the recovery time limit field
`are both specified in a MODE SELECT command. the field that requires the least time for data error recovery
`actions shall have priority.
`
`The correction span field specifies the size. in bits. of the largest data error burst for which data error correction
`may be attempted. A correction span of zero specifies that the target shail use its default value or that this field is
`not supported.
`
`The head offset count field specifies in Mo's-complement notation an incremental offset position from the track
`center to which the heads shall be moved. The ellect of this field on Write operations is unspecified. A head
`oliset count of Zero indicates that no offset is specified. A positive value indicates moving In the direction of
`increasing logical block addresses. A negative value indicates moving in the direction of decreasing logical block
`addresses. Any value specified in this field does not preclude the target irorn using positive or negative head
`
`212
`
`(cid:50)(cid:47)(cid:60)(cid:48)(cid:51)(cid:56)(cid:54)(cid:3)(cid:40)(cid:59)(cid:17)(cid:3)(cid:20)(cid:19)(cid:20)(cid:23)(cid:3)(cid:16)(cid:3)(cid:21)(cid:23)(cid:19)(cid:18)(cid:23)(cid:25)(cid:27)
`
`OLYMPUS EX. 1014 - 240/468
`
`

`

`ANSI X3131-1994
`
`offset during error recovery. However. after any error recovery is completed the target shall return the head offset
`to the valua specified in this field.
`
`NOTE 131 The degree of offset for each incremental value and the number of valid values are device specific.
`recommended that the number of valid values be equal for the positive and negative head offset counts.
`
`It is
`
`The target shall retum CHECK CONDITION stems and shall set the sense key to ILLEGAL REQUEST if an
`unsupported head offset valua is specified. The Valid bit shall be set to one and the information field shall be set
`to the positive value of the maximum head offset count that is supported. The target shall set the valid bit to zero
`if it cannot determine the maximum head offset count supported.
`
`NOTE 132 If the target does not support this field. it returns a zero value in the MODE SENSE command.)
`
`The data strobe offset count field specifies in two‘s-complement notation an incremental position to which the
`recovered data strobe shall be adjusted from its nominal setting. The effect of this field on write operations is
`unspecified. A value of zero indicates that no data strobe offset is specified. A positive value indicates
`movement in a positive direction as defined by the target. A negative value indicates movement in the negative
`direction as defined by the target. Any valua specified in this field does not preclude the target from Using
`positiVe or negative data strobe offset during error recovery. However, after any error recovery is completed the
`target shall return the data strobe effect to the value specified in this field.
`
`NOTE 13:3 The degree of offset for each incremental value and the number of valid values are device specific.
`recommended that the number of valid values be equal for the positive and negative data strobe offset counts.
`
`it is
`
`The target shall return CHECK CONDITION status and shall set the sense key to ILLEGAL REQUEST if an
`unsupported data strobe offset count value is specified. The valid bit shall be set to one and the information field
`shall be set to the positive value of the maximum data strobe offset count that is supported. The target shall set
`the valid bit to zero if it cannot determine the maximum data strobe offset supported.
`
`NOTE 134 If the target does not support the data strobe offset count field, it returns a zero value in the MODE SENSE
`command.
`
`The recovery time limit field specifies in increments of one ms the maximum time duration that the target shall use
`for data error recovery procedures. The target may round this Value as described in 7.5.4. The limits in this field
`specifies the maximum error recovery time allowed for any individual logical block. A recovery time limit of zero
`specifies that the target shall use its default value.
`
`If both retry count and recover time limit are specified. the field that specifies the recovery action of least
`duration shall have priority.
`
`213
`
`(cid:50)(cid:47)(cid:60)(cid:48)(cid:51)(cid:56)(cid:54)(cid:3)(cid:40)(cid:59)(cid:17)(cid:3)(cid:20)(cid:19)(cid:20)(cid:23)(cid:3)(cid:16)(cid:3)(cid:21)(cid:23)(cid:20)(cid:18)(cid:23)(cid:25)(cid:27)
`
`OLYMPUS EX. 1014 - 241/468
`
`

`

`ANSI X3.131-1994
`
`9.3.3.7 Rigid disk drive geometry page
`
`The rigid disk drive geometry page (see table 171) specifies parameters for direct-access devices employing a
`rigid disk drive.
`
`Table 171 - Rigid disk drive geometry page
`
`Eli
`Byte
`
`'7
`
`
`
`mn— m...
`Page length (ten)
`
`(MSB)
`
`(MSB)
`
`{
`
`MSB
`
`z0'!m
`
`1
`
`[use]
`
`(use)
`
`_I.—k—A‘_A
`
`(oer-«rails
`
`Number of cylinders
`
`Number of heads
`
`_
`_
`starting cylinder-write precompensatlon
`
`Starting cylinder-reduced write current
`
`Drive step rate
`
`Landing zone cylinder
`
`Reserved
`
`Rotational offset
`
`Reserved
`
`Medium rotation rate
`
`(LSB)
`
`iLSB}
`
`(L58)
`
`{LSB}
`
`{LSB}
`
`In TI |—
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`(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-specific location.
`
`NOTE 135 This page is intended to define drive geometry parameters or rigid disk drives.
`devices if applicable.
`
`It may be used for other
`
`The number of cylinders field defines the number of physical cylinders used for data storage.
`
`The number of heads field defines the physical number of heads used for data storage. Heads used exclusively
`for servo information are excluded.
`
`The starting cylinder for write precompensetion field is the physical cylinder at which write precompensation is to
`begin. The first cylinder is number 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.
`
`214
`
`(cid:50)(cid:47)(cid:60)(cid:48)(cid:51)(cid:56)(cid:54)(cid:3)(cid:40)(cid:59)(cid:17)(cid:3)(cid:20)(cid:19)(cid:20)(cid:23)(cid:3)(cid:16)(cid:3)(cid:21)(cid:23)(cid:21)(cid:18)(cid:23)(cid:25)(cid:27)
`
`OLYMPUS EX. 1014 - 242/468
`
`

`

`ANSIXSJSTJQQQ
`
`The starting cylinder for reduced write current field is the physical cylinder at which write current is reduced. The
`first cylinder is number Zero.
`It 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 indicates the step rate in 100 ns increments. The target shall use the drive step rate.
`greater than or equal to the driVe step rate specified.
`If the target rounds this field it shall terminate the command
`as described in 7.5.4. A value of zero requests the target to set its default value.
`
`The landing zone cylinder field Indicates two's complement location where the target shall position the disk
`heads. A negative value indicates that the heads are positioned below cylinder zero by that number of cylinders.
`A positive value greater than the number of cylinders indicates that the heads are positioned beyond the cylinders
`used tor data storage at the cylinder location specified. A zero indicates that the default should be used.
`
`The rotational position locking (RPL) field is used for spindle synchronization as defined in table 172. See K of
`the ANSI X3.17OA-1991 for further information on synchronized spindles.
`
`
`Table 172 - Rotational position locking
`
`—l
`
`—__
`
`Descriptzon
`
`
`
`Indicates that spindle synchronization is disabled or not supported
`The target operates as a synchronized-spindle slave
`
`The target operates as e synchronized-spindle master
`
`The target operates as a synchronized-spindle master control
`
`
`
`
`
`
`
`
`NOTE 136 The signals and connectors used for rotational position locking are external to the SCSI bus and are not
`part oi this standard.
`
`If a target fails to achieve synchronization it shall create a unit attention condition to all initiators. The sense key
`shall be set to UNIT ATTENTION and the additional sense code set to RPL STATUS CHANGE.
`
`if subsequent to achieving synchronization the target detects a change of synchronization:
`a) and. if the logical unit is not presently executing an IIO process for the initiator. the target shall create a unit
`attention condition. The sense key shall be set to UNIT ATTENTION and the additional sense code set to
`RPL STATUS CHANGE.
`b) and. if the logical unit is presently executing an IIO process and no other error occurs. then the target shall
`return CHECK CONDITION status. The sense key shall be set to RECOVERED ERROR if the target is able
`to complete the liO process or HARDWARE ERROR if the target is unable to complete the ifO process.
`The additional sense code is set to RPL STATUS CHANGE.
`
`The rotational ofiset indicates the amount of rotational skew that the target shall use when synchronized. The
`rotational skew is applied in the retarded direction (lagging the synchronized spindle master control). The value
`in the field is the numerator of a fractional multiplier that has 256 as its denominator {e.g. a value at 128 indicates
`a one-half revolution skew]. A value of zero indicates that rotational offset shall not be used. This value may be
`rounded as defined in 7.5.4. The rotational offset is not used when a target is configured as synchronized-spindle
`master.
`
`The medium rotation rate indicates the speed at which the medium rotates. The unit of measure is rotations per
`minute (e.g. 3 600 rpm).
`
`9.3.3.3 Verify error recovery page
`
`The verily error recovery page (see table 173) specifies the error recovery parameters the target shall use during
`the VERIFY command. the verify operation of the WRITE AND VERIFY command and the verify operation of the
`COPY AND VERIFY command.
`
`215
`
`(cid:50)(cid:47)(cid:60)(cid:48)(cid:51)(cid:56)(cid:54)(cid:3)(cid:40)(cid:59)(cid:17)(cid:3)(cid:20)(cid:19)(cid:20)(cid:23)(cid:3)(cid:16)(cid:3)(cid:21)(cid:23)(cid:22)(cid:18)(cid:23)(cid:25)(cid:27)
`
`OLYMPUS EX. 1014 - 243/468
`
`

`

`ANSI X3.131-1994
`
`
`fl
`m'5
`
`
`
`
`
`-«q ._.
`
`{use}
`
`
`Verify recovery time limit
`. i
`(LSB)
`
`
`Table 113 - Verity error recovery page
`
`.____._____ _
`
`4 __ __ __-_ __
`
`
`
`—““
`
`
`
`
`The parameters savabie (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.
`
`The AWRE bit as defined in the read-Mite error recoVery page (see 9.3.3.6) applies to the WHITE AND VERIFY
`command. The VERIFY and COMPARE commands shall not perform automatic reallocation. The COPY and
`COPY AND VERIFY commands might or might not perform automatic reallocation depending on the settings of
`the mode parameters.
`
`The EEFI. PER. DTE and DCFI bits are defined in 9.3.3.6. The combinations cfthese bits is defined in 93.3.6.
`
`The verify retry count field specifies the number of times that the target shell attempt its recovery algorithm during
`a verily operation.
`if the verify retry count and the verify recovery time limit are both specified. the one that
`requires the least time for data error recovery actions shall have priority.
`
`The verify correction span field specifies the size. in bits. of the largest burst data error for which data error
`correction may be attempted.
`it the target does not implement this field. a value oi zero Is returned in MODE
`SENSE data.
`
`The verify recovery time limit field specifies in increments of one millisecond the maximum time duration that the
`target shall use error recovery procedures to recover data for an individual logical block. The target may round
`this value as described in 7.5.4.
`If the verily retry count and the verify recovery time limit are both specified. the
`one that requires the least time for data error recovery actions shall have priority.
`
`NOTE 137 To disable all types of correction and retries the initiator should set the EER bit to zero. the PER. DTE and
`DCFl bits to one and the number of retries and recovery time limit to zero.
`
`216
`
`(cid:50)(cid:47)(cid:60)(cid:48)(cid:51)(cid:56)(cid:54)(cid:3)(cid:40)(cid:59)(cid:17)(cid:3)(cid:20)(cid:19)(cid:20)(cid:23)(cid:3)(cid:16)(cid:3)(cid:21)(cid:23)(cid:23)(cid:18)(cid:23)(cid:25)(cid:27)
`
`OLYMPUS EX. 1014 - 244/468
`
`

`

`ANSIXS131-1994
`
`9.4 Definitions specific to direct-access devices
`
`9.4.1 cache memory: A temporary (and often volatile) data storage area outside the useraaccessible area. A
`cache memory Is usually faster to access than the medium and thus has the effect of increasing data throughput
`by reducing the number of accesses to the medium.
`
`9.4.2 non-volatile medium: Physical storage medium that retains data written to it for a subsequent read
`operation through a power-on condition. An example of this is a disk device that stores data as magnetic fields
`that do not require device power to exist.
`
`9.4.3 notch: A notch refers to all or part of the medium having a consistent set at geometry parameters.
`Notches are Used to increase storage capacity by optimizing the number of sectors per track between the inner
`and outer tracks.
`
`9.4.4 user-accessible: The area of the medium that can be read from or written to by HEAD and WHITE
`commands.
`
`9.4.5 volatile medium: Medium that may not retain data written to it for a subsequent read operation through a
`power-on condition. An example of this Is a silicon memory device that loses data written to it if device power is
`lost.
`
`217
`
`(cid:50)(cid:47)(cid:60)(cid:48)(cid:51)(cid:56)(cid:54)(cid:3)(cid:40)(cid:59)(cid:17)(cid:3)(cid:20)(cid:19)(cid:20)(cid:23)(cid:3)(cid:16)(cid:3)(cid:21)(cid:23)(cid:24)(cid:18)(cid:23)(cid:25)(cid:27)
`
`OLYMPUS EX. 1014 - 245/468
`
`

`

`ANSI X3.131-1994
`
`10 Sequential-access devices
`
`10.1 Sequential-access device model
`
`10.1.1 Physical elements
`
`Sequential~access devices (called devices beloW) optimize their use in storing or retrieving user data in a
`seqUential manner. Since access is sequential. position changes typically take a long time. when compared to
`direct-access devices.
`
`Sequential-access devices are usually tape devices. The remainder of this description is from the point of view oi
`a tape device: howavar. other implementations are not precluded.
`
`The recording medium tor tape devices consists of various widths and lengths of a flexible substrate coated with
`a semi-permanent magnetic material. The recording medium may be wound onto single reels or encapsulated
`into cartridges containing both a supply reel and a take-up reel. Several American National Standards exist
`covering the construction of reels and cartridges for Interchange as well as recording techniques for many of the
`format or density combinations.
`
`A complete unit composed of the recording medium and its physical carrier (e.g. reel. cartridge. cassette) is
`called a volume. Volumes have an attribute of being mounted or de—mcunted on a suitable transport mechanism
`
`Mounted is the state of a volume when the device is physically capable of executing commands that cause the
`medium to be moved. A volume is de-rncunted when it is being loaded. threaded. unloaded. unthreadecl. or
`when not attached to the device.
`
`Fieady is the state ofthe device when medium access and non-medium access commands can be executed.
`The device is not ready when no volume is mounted or. from the initiator's perspective. whenever all medium
`access commands report CHECK CONDITION status and a NOT READY sense key. Some devices may have a
`separate switch function which places the device in a not ready state even when a volume is mounted.
`
`The write enabled or write protected state determines when an initiator may write information on a volume. This
`attribute is usually controlled by the user of the volume through manual intervention fag. thumbwheel switch).
`
`The recording medium has two physical attributes called beginning-ot—medium (BOM) and end-of—medium (EDM).
`Beginning-oi-medium is at the end of the medium that is attached to the takeup reel. End-cf-medium is at the
`end of the medium that is attached to the supply reel.
`In some cases. the medium is permanently affixed to one
`or both of the reel hubs.
`
`As shown in figure 18. the entire physical length of medium is not usable for recording data. For most volumes. a
`length of the medium is reserved betore the beginning-of-medium and after the end-ot-rnedium position. This is
`done to provide sufficient tape wraps onto the reel hubis) and to ensure that recording starts in an undamaged
`section of the medium.
`
`218
`
`(cid:50)(cid:47)(cid:60)(