Skip to main content
NetApp Knowledge Base

Description of SCSI check condition

  1. Last updated
  2. Save as PDF
Views:
5,360
Visibility:
Public
Votes:
1
Category:
data-ontap-8
Specialty:
hw
Last Updated:

​ ​ ​  

Applies to

  • CORE
  • Administration

Answer

  • SCSI check condition indicates that the attached device wants to report some condition that it has detected.
  • Sense Key is the primary classification of the condition. Additional information may also be reported in numerous Additional Sense Codes (ASC) and Additional Sense Code Qualifiers (ASCQ).
Meaning of SCSI Sense Keys
0h
  • No Sense: No specific sense key information being reported.
  • This can occur if device needs to report Filemark, EOM, or ILI information from a tape drive, or for a successful command.
1h Recovered Error: The last command completed successfully, but the device needed to apply some recovery actions.
2h
  • Not Ready: The device is not ready to complete the requested action.
  • This can be caused by a missing tape, or a disk needs to spin up, or otherwise requires additional time to be ready to execute the command.
3h The device reports that the storage medium (tape cartridge or disk platter) contains a flaw that caused the command to not complete successfully. It may also be reported if the device cannot distinguish between this error and error 4h.
4h Hardware Error: The device reports an unrecoverable device-internal error.
5h 
  • Illegal Request: The command sent by the host system cannot be executed because the device does not understand the request.
  • Indicates an invalid command code or command parameters.
6h
  • Unit Attention: Removable medium has been changed.
  • The device signals this so the host system can take necessary action to quit using the previous medium and begin using the new one.
7h
  • Data Protect: The device cannot read or write the medium.
  • This can be caused by switches on the device or on a tape cartridge.
8h
  • Blank Check: A tape read has been requested when no data exists on the tape at or beyond the point of the request.
  • Can also occur in write-once devices if data already exists at a requested write location.
9h Vendor Specific: Vendor documentation for the SCSI device must be consulted to determine the meaning.
Ah
  • Copy Aborted: SCSI COPY, COMPARE or COPY AND COMPARE command has failed because of errors on either the source device or destination device.
  • These operations move data directly from one SCSI device to another.
Bh
  • Aborted Command: The device stopped execution of the command because of a serious error condition such as a SCSI bus parity error.
  • The host system may retry the operation.
Ch  Obsolete: SCSI no longer reports this Sense Key.
Dh Volume Overflow: A buffered SCSI device has reached the end-of-partion, but data remains in the buffer.
 
Eh Miscompare: The SCSI device reports that the data it read from the medium does not match the source data.
Fh Reserved: SCSI does not report this Sense Key.
Action for SCSI Sense Keys
0h
  • Most often, this is a report from a tape drive. It can indicate that unexpected end of tape has been encountered.
  • Verify that the tape is the correct one, or that you are not attempting to write or read beyond tape capacity.
1h
  • Occasional recovered errors will occur. They are generally not a cause for concern.
  • If a particular device exhibits excessive errors, a call to your NetApp representative may be in order.
2h
  • For tape device, install the required tape cartridge.
  • For a disk, wait for the disk to spin up or become ready.
  • It will almost always do so on its own, under control of Data ONTAP.
3h
  • For tape device, the medium should be replaced.
  • Data ONTAP deals with disks that report this error generally by telling the disk to assign an alternate sector for the failed one.
  • Grown defects are expected in the medium, and are dealt with automatically by Data ONTAP or by the disk itself.
4h
  • The device has failed.
  • Contact the vendor or NetApp for further information.
5h
  • Data ONTAP and the device do not agree on some portion of the device's capabilities.
  • Contact NetApp.
6h Unit Attention is normal when tape medium is replaced.
 
7h
  • Change the device switch/jumper and/or tape cartridge write-protect settings to allow the desired operation.
  • Verify that the correct tape is being used before writing.
8h
  • The data being requested does not exist.
  • Verify that the correct tape is in the device, or that the tape has been positioned to the correct location for the requested operation.
Bh
  • This error is often caused by unstable SCSI bus (or fibre channel) connections.
  • Verify that termination and cabling are correct for the application, and that they are securely fastened. The host bus adapter or the SCSI device may also be at fault.
  • All other codes: Contact the device vendor or NetApp.

Additional Information

Add your text here.

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.