Technical information

HGST Ultrastar C15K600 Hard Disk Drive Specification
329
20.15.4.12
Self Initiated Reset
The Drive will initiate a self reset when the condition of the Drive cannot be determined. The internal reset will
terminate any outstanding commands, release any reserved initiators, and stop the spindle motor. The initiator can
recover by
1. Logging the error
2. Retrying the failing command. If the failing command completes with:
- Good Status, return to normal processing
- Self initiated reset sense, service the drive according the guidelines recommended in Section 20.15.1 "Drive
Service Strategy".
- Other, follow the recommendations for the error reported.
20.15.4.13
Defect List Recovery
This is not an error condition.
The initiator either requested a defect list in a format (block or vendor specific) that the Drive does not support or the
requested defect list(s) exceed the maximum list length that can be returned. If the Sense Key/Code/Qualifier are:
1/1F/00, the requested list(s) exceed the maximum length that can be supported. The initiator should request one list
at a time. If a single list exceeds the maximum returnable length, this may be an indication of a marginally
operational drive. Service the drive following the service guidelines in Section 20.15.1 "Drive Service Strategy".
1/1C/01 or 1/1C/02, the requested defect list is not in the format that the Drive supports. The requested defect list is
returned in the physical (cylinder, sector, head) format. This is the default format. There is no initiator action required
for this condition.
20.15.4.14
Miscompare Recovery
A Miscompare can occur on a Verify (2F) command or a Write and Verify (2E) with the byte check (BytChk) bit active.
Recovery for a Miscompare error is different for the two commands.
Verify Command
The initiator should do the following:
1. Verify that the data sent to the drive is the correct data for the byte-by-byte compare.
2. Read the data from the media with a Read (08) or Read (28) command and verify that the data from the media
is the expected data for the byte-by-byte compare.
- If all data are correct, this is an indication that the data may have been read from the media incorrectly
without an error detected. Service the drive using the procedure specified in Section 20.15.1 "Drive Service
Strategy".
- If all data are not correct, this is an indication that the data on the media is not the data the initiator expected.
Rewrite the correct data to the media.
Write and Verify Command
The drive uses the same data in the data buffer to write then read and compare. A Miscompare error on the Write
and Verify (2E) command is an indication that the drive cannot reliably write or read the media. Service the drive
using the procedures specified in Section 20.15.1 "Drive Service Strategy".