+ Reply to Thread
Results 1 to 2 of 2

Thread: Explanation of sense key asc and ascq for ST9146802

  1. #1
    joseph's Avatar
    joseph is offline Website Master Achievements:
    500 Experience Points1000 Experience Points5000 Experience Points10000 Experience PointsRecommendation Second Class
    joseph has disabled reputation
    Join Date
    2008-09-08
    Posts
    412

    Default Explanation of sense key asc and ascq for ST9146802

    Sense key Description

    0H No Sense. In the case of a successful command, no specific sense key information needs to be reported for the drive.

    1H Recovered error. The drive completed the last command successfully with some recovery action. When many recovered errors occur during one command, the drive determines which error it will report.

    2H Not ready. The addressed logical unit cannot be accessed. Operator intervention may be required to correct this condition.

    3H Medium error. The command was terminated with a non-recoverable error condition, probably caused by a flaw in the media or an error in the recorded data.

    4H Hardware error. The drive detected a non-recoverable hardware failure while performing the command or during a self-test. This includes, for example, SCSI interface parity errors, controller failures and device failures.

    5H Illegal request. An illegal parameter in the command descriptor block or in the additional parameters supplied as data for some commands (for example, the Format Unit command, the Mode Select command and others). If the drive detects an invalid parameter in the CDB, it terminates the command without altering the media. If the drive detects an invalid parameter in the additional parameters supplied as data, the drive may have already altered the media.

    6H Unit attention. The drive may have been reset. See the Seagate SCSI-2 Interface Manual for more details about the Unit Attention condition. BH Aborted command. The drive aborted the command. The initiator may be able to recover by retrying. EH Miscompare. The source data did not match the data read from the media.

  2. #2
    joseph's Avatar
    joseph is offline Website Master Achievements:
    500 Experience Points1000 Experience Points5000 Experience Points10000 Experience PointsRecommendation Second Class
    joseph has disabled reputation
    Join Date
    2008-09-08
    Posts
    412

    Default

    The Additional Sense Code and Additional Sense Code Qualifiers returned in byte 12 and byte 13, respectively, of the Sense Data Format of the Request Sense command are listed in the following table. Some sense codes and qualifiers are vendor specific and may not be on this table. 
Error code (hex) Description (Bytes 12 and 13):

    00 00 No additional information is supplied.
    01 00 There is no index/sector signal.
    02 00 There is no seek complete signal.
    03 00 A write fault occurred.
    04 00 The drive is not ready and the cause is not reportable.
    04 01 The drive is not ready, but it is in the process of becoming ready.
    04 02 The drive is not ready; it is waiting for the initializing command.
    04 03 The drive is not ready; human intervention is required.
    04 04 The drive is not ready; the format routine is in process.
    05 00 The drive does not respond when it is selected.
    06 00 Track 0 was not found.
    07 00 More than one drive is selected at a time.
    08 00 There was a drive communication failure.
    08 01 A drive communication time-out occurred.
    08 02 A drive communication parity error occurred.
    09 00 A track following error occurred.
    0A 00 An error log overflow occurred.
    0C 01 A write error occurred, but the error was recovered using auto-reallocation.
    0C 02 A write error occurred. Auto-reallocation was attempted, but it failed.
    10 00 An ID CRC or ECC error occurred.
    11 00 An unrecovered read error occurred.
    11 01 The read retries were exhausted.
    11 02 The error was too long to correct.
    11 03 There were multiple read errors.
    11 04 A read error occurred. Auto-reallocation was attempted, but it failed.
    12 00 The address mark was not found in the ID field.
    13 00 The address mark was not found in the data field.
    14 00 No record was found.
    14 01 No record was found.
    15 00 A seek positioning error occurred.
    15 01 A mechanical positioning error occurred.
    15 02 A positioning error was detected by reading the media.
    16 00 A data synchronization mark error occurred.
    17 00 The data was recovered without applying error correction or retrying.
    17 01 The data was recovered with retries.
    17 02 The data was recovered with positive head offset.
    17 03 The data was recovered with negative head offset.
    17 05 The data was recovered using the previous sector ID.
    17 06 The data was recovered without ECC. The drive uses data auto-reallocation.
    18 00 The data was recovered with ECC.
    18 01 The data was recovered with ECC and retries.
    18 02 The data was recovered with ECC, retries, and auto-reallocation.
    19 00 There is an error in the defect list.
    19 01 The defect list is not available.
    19 02 There is an error in the primary defect list.
    19 03 There is an error in the grown defect list.
    1A 00 A parameter overrun occurred.
    1B 00 A synchronous transfer error occurred.
    1C 00 The defect list could not be found.
    1C 01 The primary defect list could not be found.
    1C 02 The grown defect list could not be found.
    1D 00 During a verify operation, a compare error occurred: the source data did not match the data read from the media.
    1E 00 An ID error was recovered.
    20 00 The drive received an invalid command operation code.
    21 00 The logical block address was not within the acceptable range.
    22 00 The drive received a CDB that contains an invalid bit. (This error code applies to direct-access devices.)
    24 00 The drive received a CDB that contains an invalid bit. (This error code applies to all SCSI devices.)
    25 00 The drive received a CDB that contains an invalid LUN.
    26 00 The drive received a CDB that contains an invalid field.
    26 01 The drive received a CDB containing a parameter that is not supported.
    26 02 The drive received a CDB containing an invalid parameter.
    26 03 The drive received a CDB containing a threshold parameter that is not supported.
    29 00 A power-on reset or a bus device reset occurred.
    2A 00 Some parameters were changed by another initiator.
    2A 01 The Mode Select parameters were changed by another initiator.
    2B 00 The microcode was downloaded.
    2F 00 The tagged commands were cleared by another initiator.
    30 01 The media cannot be read because the format is not recognized.
    30 02 The media cannot be read because the format is incompatible with certain parameters.
    31 00 The media format is corrupted.
    31 01 The format command failed.
    32 00 There are no spare defect locations available.
    32 01 An error occurred when the defect list was being updated.
    37 00 A rounded parameter caused an error.
    3D 00 The identify message contains invalid bits.
    3F 00 The target operation command was changed.
    3F 01 The microcode was changed.
    3F 02 The drive was operating as a SCSI drive and is now operating as a SCSI-2 drive, or vice versa.
    3F 03 The inquiry data was changed.
    40 00 The RAM failed.
    40 8x A correctable ECC error occurred; x equals the length of the error.
    40 90 A configuration error occurred.
    40 A0 The self-test routine discovered an error in a ROM.
    40 A1 The self-test routine discovered an error in the processor RAM.
    40 A2 The self-test routine discovered an error in the buffer RAM.
    40 A3 The self-test routine discovered a SCSI protocol error.
    40 A4 The self-test routine discovered a DMA error.
    40 A5 The self-test routine discovered an error in the disc sequencer.
    40 A6 The self-test routine discovered an error in the disc sequencer RAM.
    40 A7 A self-test error occurred.
    40 A8 The flash memory cannot be read or written.
    40 A9 The flash memory directory cannot be read, or it is corrupted.
    40 AA The flash memory contains an incompatible version number.
    40 AB The flash memory contains an incompatible revision number.
    40 AC A flash memory checksum error occurred.
    40 AD The flash memory contains invalid parameters.
    Forwarded from forums.seagate

+ Reply to Thread

Similar Threads

  1. Add. Sense: Internal target failure
    By joseph in forum Hardware Forum
    Replies: 1
    Last Post: 2009-12-20, 09:20 AM
  2. LXer: Suspend to disk - does it still make sense?
    By edenCC in forum Technology News
    Replies: 0
    Last Post: 2009-06-25, 12:55 AM
  3. LXer: Can Oracle make sense of Sun's hardware?
    By edenCC in forum Technology News
    Replies: 0
    Last Post: 2009-04-21, 10:09 AM
  4. Replies: 0
    Last Post: 2009-03-18, 10:53 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts