| Sense Key (Hex) |
ASC (Hex) | ASCQ (Hex) |
Description of Error (see Note) |
|---|---|---|---|
| 00 | 00 | 01 | Unexpected FM encountered |
| 00 | 00 | 02 | EOM encountered Unit off-line |
| 00 | 00 | 03 | EOM encountered |
| 01 | 0A | 00 | Error log overflow |
| 01 | 37 | 00 | Rounded parameter |
| 01 | 3B | 08 | Repositioning error |
| 01 | 44 | C1 | Internal target failure EEROM copy 1 area bad |
| 01 | 44 | C2 | Internal target failure EEROM copy 2 area bad |
| 01 | 44 | C3 | Internal target failure EEROM copy 3 area bad |
| 01 | 47 | 00 | SCSI parity error |
| 01 | 48 | 00 | IDE message received |
| 01 | 51 | 00 | Erasefailure |
| 01 | 53 | 01 | Unload tape failure |
| 01 | 5B | 02 | Log counter at maximum |
| 01 | 80 | 02 | Cleaning requested |
| 02 | 04 | 00 | Unit not ready, cause nonreportable |
| 02 | 04 | 01 | Unit not ready, calibration in progress |
| 02 | 04 | 02 | Unit not ready, load command needed |
| 02 | 04 | 03 | Unit not ready, manual intervention needed |
| 02 | 3A | 00 | Medium not present |
| 02 | 3A | 80 | Medium not present, cartridge missing |
| 02 | 5A | 01 | Operator media removal request |
| 03 | 04 | 02 | Unit not ready, load command needed |
| 03 | 0C | 00 | Write error |
| 03 | 11 | 00 | Unrecovered read error |
| 03 | 11 | 08 | Unrecovered read error, incomplete block read |
| 03 | 14 | 00 | Recorded entity not found |
| 03 | 15 | 02 | Position error detected by read of medium |
| 03 | 30 | 00 | Can't read medium |
| 03 | 3B | 00 | Sequential positioning error |
| 03 | 51 | 00 | Erase failure |
| 03 | 80 | 00 | Calibration error |
| 03 | 80 | 01 | Cleaning required |
| 03 | 81 | 00 | Directory read error |
| 04 | 08 | 00 | LUN communication failure |
| 04 | 08 | 01 | LUN communication time out failure |
| 04 | 15 | 01 | Random mechanical positioning error |
| 04 | 21 | 01 | Invalid element address |
| 04 | 3B | 08 | Repositioning error |
| 04 | 3B | 0D | Media destination element full |
| 04 | 3B | 0E | Media source element empty |
| 04 | 40 | 80 | Diagnostic/POST failure, ROM EDC failure |
| 04 | 40 | 81 | Diagnostic/POST failure, RAM failure |
| 04 | 40 | 82 | Diagnostic/POST failure, bad drive status |
| 04 | 40 | 83 | Diagnostic/POST failure, loader diagnostic failure |
| 04 | 40 | 84 | Diagnostic/POST failure, POST soft failure |
| 04 | 44 | 00 | Internal target failure |
| 04 | 44 | 80 | Unexpected selection interrupt |
| 04 | 44 | 83 | SCSI chip gross error |
| 04 | 44 | 84 | Unexplained residue in TC registers |
| 04 | 44 | 85 | Immediate data transfer time out |
| 04 | 44 | 86 | Insufficient CDB bytes |
| 04 | 44 | 87 | Disconnected/SDP sequence failed |
| 04 | 44 | 88 | Bus DMA transfer time out |
| 04 | 47 | 00 | SCSI parity error |
| 04 | 48 | 00 | IDE message received |
| 04 | 51 | 00 | Erasefailure |
| 04 | 53 | 00 | Media load/eject failure |
| 04 | 53 | 01 | Unload tape failure |
| 05 | 1A | 00 | Parameter list length error |
| 05 | 20 | 00 | Illegal firmware |
| 05 | 21 | 01 | Invalid element adciress |
| 05 | 24 | 00 | Invalid CDB field |
| 05 | 24 | 81 | Invalid mode on write buffer |
| 05 | 24 | 82 | Media in drive |
| 05 | 24 | 84 | Insufficient resources |
| 05 | 24 | 86 | Invalid offset |
| 05 | 24 | 87 | Invalid size |
| 05 | 24 | 89 | Image data over limit |
| 05 | 24 | 8B | Image/personality is bad |
| 05 | 24 | 8C | Not immediate command |
| 05 | 24 | 8D | Bad drive/server image EDC |
| 05 | 24 | 8E | Invalid personality for firmware update |
| 05 | 24 | 8F | Bad controller image EDC |
| 05 | 25 | 00 | Illegal LUN |
| 05 | 26 | 00 | Parameter list error, invalid field |
| 05 | 26 | 01 | Parameter list error, parameter not supported |
| 05 | 26 | 02 | Parameter list error, parameter value invalid |
| 05 | 39 | 00 | Saving parameters not supported |
| 05 | 3B | 0D | Media destination element full |
| 05 | 3B | 0E | Media source element empty |
| 05 | 3D | 00 | Invalid bits in ID message |
| 05 | 53 | 02 | Media removal prevented |
| 05 | 82 | 00 | Not allowed if not at BOT |
| 06 | 28 | 00 | Not ready to ready transition |
| 06 | 29 | 00 | Reset occurred |
| 06 | 2A | 01 | Mode parameters changed |
| 06 | 2A | 02 | Log parameters changed |
| 06 | 3F | 01 | Firmware has been changed |
| 06 | 5B | 01 | Log threshold condition met |
| 07 | 27 | 80 | Hardware write protected |
| 07 | 27 | 82 | Data safety write protected |
| 08 | 00 | 05 | EOD encountered |
| 0B | 43 | 00 | Message error |
| 0B | 44 | 82 | Command complete sequence failure |
| 0B | 45 | 00 | Select/reselect failure |
| 0B | 47 | 00 | SCSI parity error |
| 0B | 48 | 00 | IDE message received |
| 0B | 49 | 00 | Invalid message error |
| 0B | 4E | 00 | Overlapped commands attempted |
| 0D | No additional sense firmware | ||
| 0E | No additional sense firmware |
Note: The filemark/EOM/ILI bits may be set, even though ASC/ASCQ = 00 00.
The following are ways in which the filemark/EOM/ILI bits can be set:
- FM, EOM, ILI bit may be set with no sense key (0) and ASC/ASQ = 00 00.
- FM, EOM, ILI bit may be set with recovered error (1) and ASC/ASQ = 00 00.
- FM, EOM, ILI bit may be set with medium error (3) and ASC/ASQ = 00 00.
- EOM bit is set at Volume Overflow (Dh) ASC/ASQ = 00 00.
- FM (byte 2, bit 7), EOM (byte 2, bit 6), and ILI (byte 2, bit 5) are fields in request data.
The internal status code (ISC) is unique to the DLT7000 drive and gives a more complete definition of the drive's error condition.
The ISC is located at byte 18 of the request sense data.
Depending on the hex value of the ISC code that appears in byte 18 of the errpt report (see (above) Figure 64),
there are two ways of determining a description of the error:
- If the ISC hex value is 7Fh or lower, refer to below Figure 66.
- If the ISC hex value is 80h or higher, refer to the bit numbers and descriptions in (below) Figure 67.
Figure 66. Internal Status Codes. Use this table for ISC hex values of 7Fh or lower.
Example: Byte 18 = 82h
Please see the LEGAL - Trademark notice.
Hex Value
Description of Error
0
No meaning
1
Reed-Solomon error correction code recovery
2
Read or write block retry (soft error)
3
Reposition command aborted
4
Controller has stopped reading
5
No control or data buffers available
6
Target delivered in read ahead
7
Logical EOT encountered, two file marks
8
Ccmmand connection dropped
9
Cleared from queue
0A
Missing data block - read only
0B
Gap within object (missing blocks in record)
0C
Record on tape larger than requested
0D
Compare error
0E
Successive blocks missing across objects
0F
Drive state not valid for command
10
Drive error
11
Drive communication time-out error
12
Drive unloaded
13
Unable to write - no CRC
14
Block to append to not found
15
Data synchronization error (read after write not
happening)
16
Missing block(s) in current entity
17
Drive hardware write protected
18
Reposition target not found
19
Long gap encountered (blank tape or no data
encountered)
1A
End of data or filler block encountered
1B
File mark encountered
1C
EDC error found by GPSP3 - FECC RAM bad
1D
Beginning of medium encountered
1E
EDC error
1F
Hard write error - GPSP3 Underrun
20
Hard write error - Read Sync Time-out
21
Hard write error - Overshoot Append
22
Hard write error - CRC error
23
EDC error found by GPSP3 - FECC RAM OK
24
Time-out on command to medium changer
25
Medium changer UART error (overrun)
26
Medium changer response length error
27
Medium changer detected error
28
Invalid source slot
29
Invalid destination slot
2A
Source slot empty
2B
Destination slot full
2C
Medium changer motion error
2D
Medium changer/drive interface error
2E
Medium changer/slot interface error
2F
Medium changer mechanical error
30
Medium changer hardware error
31
Medium changer controller error
32
Unrecognized medium changer subcommand
33
Medium changer fatal error
34
Medium changer is in manual mode
35
68020 detected communication error with servo area
36
68020 detected drive command time-out
37
Calibration failure
38
Bad tape format
Byte 18 has two formats: a byte code and a bit flags format.
The bit flags format is used when there is no internal status code to report, and can be distinguished by
bit 7 being set.
The bit flag numbers are shown in Figure 67, and provide a description of the error.
To interpret the bit flags, follow the example below using the SC value that you extract from the errpt report (see above Figure 64).
As shown in the following example, the error for internal status code 82 that appears in byte 18 of
the errpt report can be defined as a flag bit 7 on, with the cleaning light off and the status unknown.
Bit order 7 6 5 4 | 3 2 1 0
Binary value 1 0 0 0 0 0 1 0
Hex value 8 2
Bit 7 on: Flag bit status code
Bit 1, 2 (01): Unknown status
Bit 0 off: Cleaning light off
Figure 67. Internal Status Codes. Use this table for ISC hex values of 80h or higher.
Number of Bit
FlagDescription of Error
0 (least significant
bit - LSB)If set, cleaning light is on; otherwise it is off
1 - 2
Tape directory status:
0 Good status
1 Unknown status
2 Directory partially bad
3 Directory bad
3 - 6
Reserved
7 (most significant
bit - MSB)If set, the internal status byte 18 is in a bit flags format;
otherwise it is an internal status code
Back to 
Feel free - send a 
for any BUG on this page found - Thank you.