Drive Slot Sensor For Storage Drive Fault Was Asserted
The storage drive was removed. Backplane Drive: Drive Slot sensor for Backplane, drive fault was asserted: The storage drive failed. System Board PFault Fail Safe: Voltage sensor for System Board, state asserted was asserted: This event is generated when the system board voltages are not at normal levels. Storage Drive 5 Drive Slot Sensor For Storage Drive Fault Was Asserted, red rock casino resort & spa pool, aspers casino funding, casino festsaal uni frankfurt.
- I am trying to install SATA hard drives. All drives i try actually work but i get a fault on the LCD and in iDRAC saying: BP Drive 0: Drive Slot sensor for BP, drive fault was asserted. This fault moves with the hard drives through all drive bays and also on the 2nd server the same. I have tried these drives: Hitachi HTS54322 232GiB.
- Drive Slot Sensor For Storage Drive Fault Was Asserted, cannery casino craig road, najlepsie online poker herne, medidas de mesa de blackjack New customer offer. Place 5 x £10 or more bets to receive £20 in free bets.
Drive Slot Sensor For Storage Drive Fault Was Asserted Dell
[ Bottom of Page Previous Page Next Page Contents ]
This section contains code descriptions for possible I/O error messages from the Tivoli Storage Manager server for the AIX, HP-UX, Solaris, Linux, and Windows(R) operating systems.
- READ
- WRITE
- FSR (forward space record)
- FSF (forward space file)
- WEOF (write end of file mark)
- A string of hex digits
See Operation Code Values for Tape Library Devices for a list of operation codes.
0 = no additional sense bytes available
1 = recovered error
2 = not ready
3 = medium error
4 = hardware error
5 = illegal request
6 = unit attention (for example, a SCSI bus reset)
7 = data protect
8 = blank check
9 = vendor specific
A = copy aborted
B = aborted command
C = equal compare on SEARCH DATA command
D = volume overflow
E = miscompare
F = reserved
Completion Code and Operation Code Values
This section lists the completion code values for the following:
- All device classes
- Media changers
- Tape and optical drives
This section lists the operation code values for tape library devices. See Operation Code Values for Tape Library Devices for a description of the operation codes.
Completion Code Values Common to All Device Classes
The following table shows the completion code values, in decimal and hexadecimal numbers, common to all device classes. It provides a description for the I/O error message and the recommended action. After performing the recommended action, retry the failing operation. If the failing operation is not successful, contact Tivoli Storage Manager support.
Dell R710 Drive Slot Sensor For Storage Drive Fault Was Asserted
| Decimal | Hexadecimal | Description | Recommended Action |
|---|---|---|---|
| 200 | X'C8' | The device indicated a failure condition, but sense data was unavailable. | Retry the failing operation. |
| 201 | X'C9' | Device driver failure | Contact Tivoli Storage Manager support. |
| 202 | X'CA' | The device EEPROM failed. | The device should be tested or serviced. |
| 203 | X'CB' | Manual intervention required | Correct the problem on the device. This may be a stuck tape, dirty heads or a jammed library arm. |
| 204 | X'CC' | Recovered from an I/O error; for your information only | No action necessary |
| 205 | X'CD' | SCSI adapter failure | Check for loose cables, bent pins, bad cables, bad SCSI adaptors, improper termination or bad terminators. |
| 206 | X'CE' | General SCSI failure | Check for loose cables, bent pins, bad cables, bad SCSI adaptors, improper termination or bad terminators. |
| 207 | X'CF' | Device is not in a state capable of performing request | Ensure the device is on and ready. Ensure the DEFINE DRIVE and DEFINE DEVCLASS have been issued properly. |
| 208 | X'D0' | Command aborted | Contact Tivoli Storage Manager support. |
| 209 | X'D1' | Device microcode failure detected | Check the microcode level of the drive. Call the drives manufacturer and request latest level. |
| 210 | X'D2' | The device was reset due to device power-up, SCSI bus reset, or manual tape load/eject. | Retry the failing operation. |
| 211 | X'D3' | The SCSI bus was busy. | Ensure the SCSI ids are correctly assigned to the correct device, and the device is not being accessed by another process. |
Completion Code Values for Media Changers
The following table shows the completion code values, in decimal and hexadecimal numbers, for the media changers. It provides a description for the I/O error message and the recommended action. After performing the recommended action, retry the failing operation. If the failing operation is not successful, contact Tivoli Storage Manager support.
| Decimal | Hexadecimal | Description | Recommended Action |
|---|---|---|---|
| 300 | X'12C' | Cartridge entry/exit error | Check the entry/exit ports for a jammed volume. |
| 301 | X'12D' | Cartridge load failure | Check the drive for jammed volumes. On AIX, display the errpt to check for hardware errors. |
| 302 | X'12E' | Cartridge in failed drive | Check the drive for jammed volumes. On AIX, display the errpt to check for hardware errors. |
| 303 | X'12F' | Carousel not loaded | Ensure the carousel is correctly in place and the door is shut. |
| 304 | X'130' | Changer failure | On AIX, display the errpt to check for hardware errors. |
| 305 | X'131' | Drive failure | Ensure the heads have been cleaned. On AIX, display the errpt to check for hardware errors. |
| 306 | X'132' | Drive or media failure | Ensure the heads have been cleaned. On AIX, display the errpt to check for hardware errors. |
| 307 | X'133' | Entry/exit failure | Contact Tivoli Storage Manager support. |
| 308 | X'134' | Entry/exit port not present | Contact Tivoli Storage Manager support. |
| 309 | X'135' | Library audit error | Ensure that there are no jammed volumes. It is possible that the library audit is failing due to hardware errors. On AIX, display the errpt to check for hardware errors. |
| 310 | X'136' | Library full | Check for jammed volumes. Ensure the volumes have not been rearranged. If the library is not actually full, perform an AUDIT LIBRARY. |
| 311 | X'137' | Media export | Contact Tivoli Storage Manager support. |
| 312 | X'138' | Slot failure | Ensure that nothing is jammed in the slot. |
| 313 | X'139' | Slot or media failure | Ensure the volume is not jammed in the slot and that the volumes have not been rearranged. If problem persists, perform an AUDIT LIBRARY. |
| 314 | X'13A' | The source slot or drive was empty in an attempt to move a volume. | Ensure the volumes have not been rearranged. If problem persists, perform an AUDIT LIBRARY. |
| 315 | X'13B' | The destination slot or drive was full in an attempt to move a volume. | Ensure the volumes have not been rearranged, or that a volume is not stuck in the drive. If problem persists, perform AUDIT LIBRARY. |
| 316 | X'13C' | Cleaner cartridge installed | Contact Tivoli Storage Manager support. |
| 317 | X'13D' | Media not ejected | Ensure the volumes have not been rearranged, or that a volume is not stuck in the drive. If problem persists, perform AUDIT LIBRARY. |
| 318 | X'13E' | I/O port not configured | Contact Tivoli Storage Manager support. |
| 319 | X'13F' | First destination empty | Ensure the volumes have not been rearranged. If problem persists, perform AUDIT LIBRARY. |
| 320 | X'140' | No inventory information | Perform AUDIT LIBRARY. |
| 321 | X'141' | Read element status mismatch | Contact Tivoli Storage Manager support. |
| 322 | X'142' | Initialize range failed | Contact Tivoli Storage Manager support. |
Completion Code Values for Tape and Optical Drives
The following table shows the completion code values, in decimal and hexadecimal numbers, for tape and optical drives. It provides a description for the I/O error message and the recommended action. After performing the recommended action, retry the failing operation. If the failing operation is not successful, contact Tivoli Storage Manager support.
| Decimal | Hexadecimal | Description | Recommended Action |
|---|---|---|---|
| 400 | X'190' | Physical end of media encountered | Ensure the heads are clean on the drive. |
| 402 | X'192' | Media corrupted | Ensure the heads are clean and the media is not physically damaged or too old. |
| 403 | X'193' | Media failure | Ensure the heads are clean and the media is not physically damaged or too old. |
| 404 | X'194' | Media incompatibility | Ensure the correct length and type of media is being used. |
| 406 | X'196' | Sector requested is invalid. | Internal server error. Contact Tivoli Storage Manager support. |
| 407 | X'197' | Write protect | Ensure the volume is not write protected. |
| 408 | X'198' | Clean the media and the drive. | Clean the drive heads with a cleaning cartridge that is not too old. |
| 409 | X'199' | Media fault | Clean the heads and ensure the media is not physically damaged or too old. |
| 410 | X'19A' | Cleaning complete | Retry the failing operation. |
| 412 | X'19C' | Media not present in drive | Ensure the media is correctly positioned in the drive. If problem persists, perform an AUDIT LIBRARY. |
| 414 | X'19E' | Erase failure | Clean the drive heads. |
| 415 | X'19F' | Attempted to overwrite written WORM media | Internal server error. Contact Tivoli Storage Manager support. |
| 416 | X'1A0' | An incorrect length block was read. | Ensure the heads are clean. On AIX, display the errpt to check for hardware errors. |
| 417 | X'1A1' | Open read only | Contact Tivoli Storage Manager support. |
| 418 | X'1A2' | Open write only | Contact Tivoli Storage Manager support. |
| 419 | X'1A2' | Media scan failed | Clean the drive and media. |
| 420 | X'1A4' | Logical write protect | Ensure the heads have been cleaned. Check operating system error logs for hardware errors. |
| 422 | X'1A6' | Cleaning required | Clean the tape drive. |
| 423 | X'1A7' | Optical media error | Check operating system error logs for hardware errors. Possible bad media. |
Operation Code Values for Tape Library Devices
The following table shows the operation code values for tape library devices. The table provides the two least significant bytes of the operation code. Refer to the Tape Library System Calls chapter in the IBM TotalStorage Tape Device Drivers Installation and User's Guide for detailed information on operation codes.
| Hexadecimal | Name | Description |
|---|---|---|
| X'6D31' | MTIOCLM | Mount a volume on a specified drive. |
| X'6D32' | MTIOCLDM | Demount a volume on a specified drive. |
| X'6D34' | MTIOCLSVC | Change the category of a specified volume. |
| X'6D37' | MTIOCLQ | Return information about the tape library and its contents. |
| X'6D38' | MTIOCLQMID | Query the status of the operation for a given message ID. |
| X'6D38' | MTIOCLQMID | Query the status of the operation for a given message ID. |
| X'6D39' | MTIOCLSDC | Assign a category to the automatic cartridge loader for a specified device. |
Common Values for ASC and ASCQ Codes
This section provides descriptions for common values of the ASC and ASCQ codes, which are bytes 12 and 13 for SCSI-2 devices. For Windows , these codes also appear in the Event Log. See Windows Event Log Entries.
See server message ANR8300E or ANR8302E for the recommended action.
The following table provides descriptions for common values of the ASC and ASCQ codes. Each value has a prefix of 0x, which indicates that it is a hexadecimal constant.
| ASC | ASCQ | Description |
|---|---|---|
| 0x00 | 0x00 | No additional sense |
| 0x00 | 0x01 | Filemark detected |
| 0x00 | 0x02 | End-of-medium detected |
| 0x00 | 0x03 | Setmark detected |
| 0x00 | 0x04 | Beginning of medium |
| 0x00 | 0x05 | End of data |
| 0x00 | 0x06 | I/O process terminated |
| 0x02 | 0x00 | No seek complete |
| 0x03 | 0x00 | Device write fault |
| 0x03 | 0x01 | No write current |
| 0x03 | 0x02 | Excessive write errors |
| 0x04 | 0x00 | Logical unit not ready |
| 0x04 | 0x01 | Becoming ready |
| 0x04 | 0x02 | Not ready, initializing command required |
| 0x04 | 0x03 | Not ready, manual intervention required |
| 0x04 | 0x04 | Not ready, formatting |
| 0x05 | 0x00 | No response to select |
| 0x06 | 0x00 | No reference position found |
| 0x07 | 0x00 | Multiple devices selected |
| 0x08 | 0x00 | Communication failure |
| 0x08 | 0x01 | Communication timeout |
| 0x08 | 0x02 | Communication parity error |
| 0x09 | 0x00 | Track following error |
| 0x0A | 0x00 | Error log overflow |
| 0x0C | 0x00 | Write error |
| 0x11 | 0x00 | Unrecovered read error |
| 0x11 | 0x01 | Read retries exhausted |
| 0x11 | 0x02 | Error too long to correct |
| 0x11 | 0x03 | Multiple read errors |
| 0x11 | 0x08 | Incomplete block read |
| 0x11 | 0x09 | No gap found |
| 0x11 | 0x0A | Miscorrected error |
| 0x14 | 0x00 | Recorded entity not found |
| 0x14 | 0x01 | Record not found |
| 0x14 | 0x02 | Filemark/setmark not found |
| 0x14 | 0x03 | End-of-data not found |
| 0x14 | 0x04 | Block sequence error |
| 0x15 | 0x00 | Random positioning error |
| 0x15 | 0x01 | Mechanical positioning error |
| 0x15 | 0x02 | Read positioning error |
| 0x17 | 0x00 | No error correction applied |
| 0x17 | 0x01 | Recovered with retries |
| 0x17 | 0x02 | Recovered with positive head offset |
| 0x17 | 0x03 | Recovered with negative head offset |
| 0x18 | 0x00 | ECC applied |
| 0x1A | 0x00 | Parameter list length error |
| 0x1B | 0x00 | Synchronous data transfer error |
| 0x20 | 0x00 | Invalid operation code |
| 0x21 | 0x00 | Block out of range |
| 0x21 | 0x01 | Invalid element address |
| 0x24 | 0x00 | Invalid field in CDB |
| 0x25 | 0x00 | LUN not supported |
| 0x26 | 00 | Invalid field in parameter list |
| 0x26 | 0x01 | Parameter not supported |
| 0x26 | 0x02 | Parameter value invalid |
| 0x26 | 0x03 | Threshold parameters not supported |
| 0x27 | 0x00 | Write protected |
| 0x28 | 0x00 | Not-ready to ready |
| 0x28 | 0x01 | Import/export element accessed |
| 0x29 | 0x00 | Power-on, reset, bus reset |
| 0x2A | 0x00 | Parameters changed |
| 0x2A | 0x01 | Mode parameters changed |
| 0x2A | 0x02 | Log parameters changed |
| 0x2B | 0x00 | Copy cannot execute |
| 0x2C | 0x00 | Command sequence error |
| 0x2D | 0x00 | Overwrite error on update |
| 0x2F | 0x00 | Command cleared by initiator |
| 0x30 | 0x00 | Incompatible media |
| 0x30 | 0x01 | Media unknown format |
| 0x30 | 0x02 | Media incompatible format |
| 0x30 | 0x03 | Cleaning cartridge installed |
| 0x31 | 0x00 | Media format corrupted |
| 0x33 | 0x00 | Tape length error |
| 0x37 | 0x00 | Rounded parameter |
| 0x39 | 0x00 | Saving parameters not supported |
| 0x3A | 0x00 | Medium not present |
| 0x3B | 0x00 | Sequential positioning error |
| 0x3B | 0x01 | Positioning error at BOT |
| 0x3B | 0x02 | Positioning error at EOT |
| 0x3B | 0x08 | Reposition error |
| 0x3B | 0x0D | Medium destination element full |
| 0x3B | 0x0E | Medium source element empty |
| 0x3D | 0x00 | Invalid bits in message |
| 0x3E | 0x00 | LUN not self-configured |
| 0x3F | 0x00 | Operating conditions changed |
| 0x3F | 0x01 | Microcode has been changed |
| 0x3F | 0x02 | Changed operating definition |
| 0x3F | 0x03 | Inquiry data has changed |
| 0x43 | 0x00 | Message error |
| 0x44 | 0x00 | Internal target failure |
| 0x45 | 0x00 | Select/reselect failure |
| 0x46 | 0x00 | Unsuccessful soft reset |
| 0x47 | 0x00 | SCSI parity error |
| 0x48 | 0x00 | Initiator detected message received |
| 0x49 | 0x00 | Invalid message error |
| 0x4A | 0x00 | Command phase error |
| 0x4B | 0x00 | Data phase error |
| 0x4C | 0x00 | LUN failed self-configuration |
| 0x4E | 0x00 | Overlapped commands attempt |
| 0x50 | 0x00 | Write append error |
| 0x50 | 0x01 | Write append position error |
| 0x50 | 0x02 | Position error (timing) |
| 0x51 | 0x00 | Erase failure |
| 0x52 | 0x00 | Cartridge fault |
| 0x53 | 0x00 | Load/media eject failed |
| 0x53 | 0x01 | Unload tape failure |
| 0x53 | 0x02 | Media removal prevented |
| 0x5A | 0x00 | Operator state changed |
| 0x5A | 0x01 | Operator media removal |
| 0x5A | 0x02 | Operator write protect |
| 0x5A | 0x03 | Operator write permit |
| 0x5B | 0x00 | Log exception |
| 0x5B | 0x01 | Threshold condition met |
| 0x5B | 0x02 | Log counter at maximum |
| 0x5B | 0x03 | Log list codes exhausted |
Windows Event Log Entries
The code values will appear as hexadecimal values in the Data area of the Windows Event Log. The Event Log omits the 0x prefix for the displayed information.
In the Windows Event Log, the entries with source AdsmScsi are produced by the AdsmScsi device driver. In these entries, byte 3E is the sense key, byte 3D is the ASC, and byte 3C is the ASCQ. (This is also true of entries logged by any of the Windows tape device drivers.) If byte 44 is 'ef', the error logged is not a check condition error. Examples of such errors are command timeouts or device selection errors.
[ Top of Page Previous Page Next Page Contents ]