Chapter 87 Open SCSI Messages

Cause  Recovery from a media error occurred after a retry.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The Open SCSI device is not ready or loaded.

Effect  None.

Recovery  Make sure that the Open SCSI device is ready.

Cause  An unrecoverable media error occurred.

Effect  Read and write errors occur.

Recovery  Replace the tape or format media.

Cause  The Open SCSI device is damaged.

Effect  The Open SCSI device is unusable.

Recovery  Repair or replace the Open SCSI device.

Cause  The command is not supported for this Open SCSI device.

Effect  The request fails.

Recovery  Specify a correct command for this Open SCSI device.

Cause  The Open SCSI device has been reset.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The media is write protected.

Effect  The media cannot be written to.

Recovery  Write-enable the media.

Cause  The tape is not initialized. This error message applies only to Open SCSI devices that contain tapes.

Effect  The tape is not mounted.

Recovery  ACCEPT the tape using MEDIACOM to initialize it.

Cause   The cause of this error is vendor-specific.

Effect  See the vendor documentation.

Recovery  See the vendor documentation.

Cause  This function is currently not supported.

Effect  None.

Recovery  None.

Cause  This function is currently not supported.

Effect  None

Recovery  None

Cause  This function is currently not supported.

Effect  None.

Recovery  None.

Cause  The end-of-tape indicator is missing. This message applies only to Open SCSI devices that contain tapes.

Effect  For Open SCSI devices related to tape, a write operation has failed.

Recovery  Replace the tape.

Cause  This function is currently not supported.

Effect  None.

Recovery  None.

Cause  A processor switch (backup takes over as primary) occurred.

Effect  None.

Recovery  If the processor switch occurred as a result of a command, then no corrective action is needed.

If the processor switch occurred because of a hardware problem, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A path state (for example, UP or DOWN) has changed.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  A Open SCSI device reported an internally- or externally-initiated path switch.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  This function is currently not supported.

Effect  None.

Recovery  None.

Cause  An error was injected by an external program.

Effect  The Module Driver has injected an error to comply with the request.

Recovery  Informational message only; no corrective action is needed.

Cause  A power on (PON) interrupt (indicating a power failure) occurred. The state of the hardware might have changed because of a power failure and a subsequent power on.

Effect  Microcode is reloaded for all downloadable ServerNet addressable primary controllers in the processor where the power failed.

Recovery  Informational message only; no corrective action is needed.

Cause  An execute I/O (EIO) was issued, but no interrupt was received for the EIO; a timeout on the EIO did not occur. The interrupt from the controller never occurred, or the interrogate I/O (IIO) processing the interrupt failed. A problem exists with the path or the controller.

Effect  The Open SCSI device operation aborts.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An unexpected interrupt for a device occurred. The ServerNet addressable controller should not be randomly interrupting.

Effect  A problem might exist with the controller because it should not be randomly interrupting.

Recovery  If this error occurs repeatedly, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  This function is currently not supported.

Effect  None.

Recovery  None.

Cause  This function is currently not supported.

Effect  None.

Recovery  None.

Cause  The loadable control store (LCS) of a downloadable ServerNet addressable controller is loaded. (A series of LOAD LOCS execute I/Os [EIOs] was executed.)

Effect  This EIO changes the microcode in the LCS of the controller.

Recovery  During normal operations, the controller should not become unloaded. Frequent use of this EIO may indicate a problem. Note the occurrence of this EIO to track the state of the subsystem.

Cause  An Open SCSI device problem occurred.

Effect  The Open SCSI device cannot be selected.

Recovery  Power off and then power on the Open SCSI device again. If the error continues to occur, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A timeout value is too short or there is a Open SCSI device problem.

Effect  The command fails.

Recovery  Reset the Open SCSI device. If the error continues to occur, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An incomplete command was received by an Open SCSI device.

Effect  The command fails.

Recovery  Reset the Open SCSI device. If the error continues to occur, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A command was not completed by the Open SCSI device.

Effect  The command fails.

Recovery  Reset the Open SCSI device and reissue the command. If the error continues to occur, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  This function is not currently supported.

Effect  None.

Recovery  None.

Cause  A controller or SCSI bus error occurred when a command was sent from the controller to the Open SCSI device.

Effect  The command fails.

Recovery  Power off and then power on the Open SCSI device again. If the error continues to occur, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The Open SCSI device was reset by a controller because a command from the controller to the Open SCSI device aborted.

Effect  The command fails.

Recovery  The reset causes the command to be retried. If the error continues to occur, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The path to a device changed.

Effect  Requests for the device are sent through the new path.

Recovery  If the path change occurred as a result of a command, then no corrective action is needed.

If the path change occurred because of a hardware problem, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A path state (for example, Started or Stopped) changed.

Effect  If the states of both the primary and the backup path are STOPPED, the device is no longer accessible. Otherwise, the device is accessible through the path that is STARTED.

Recovery  From the TACL prompt, issue the SCF STATUS $dev-name command. If the device is STOPPED, issue the START command. If the state of the device is Taa, the I/O process is in a terminating loop and it must be stopped, deleted, added, and restarted using the Subsystem Control Facility (SCF).

Cause  A power on (PON) interrupt (indicating a power failure) occurred and power to the device was restored.

Effect  The device is powered on.

Recovery  Informational message only; no corrective action is needed.

Cause  A processor switch (backup takes over as primary) occurred. If a processor failure caused the switch, this message reports that the change was initiated by an I/O process.

Effect  None.

Recovery  If the processor switch occurred as a result of a command (for example, the SCF SWITCH command), then no corrective action is needed.

If the processor switch occurred because of a hardware problem, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  During the processing of a request, one or more items of interest was gathered.

Effect  None.

Recovery  In general, this is an informational message only; no corrective action is usually needed. However, if this event precedes a serious problem, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An unexpected interrupt for a device occurred. A problem might exist with the controller.

Effect  The I/O process recovers.

Recovery  If this error occurs repeatedly, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The state of the device controller does not match the state expected by the I/O process at the time the execute I/O (EIO) was attempted. A controller or channel failure might have occurred.

Effect  The operation aborts.

Recovery  Retry the operation. If the operation continues to fail, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An illegal or unknown interrogate I/O (IIO) or high-priority interrogate I/O (HIIO) instruction did not finish.

Effect  The state of the I/O operation is unknown.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The I/O was invoked, but no interrupt was received.

Effect  The operation aborts.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  An I/O was invoked and the returned value indicates that an illegal command was sent.

Effect  The operation aborts.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The channel microcode detected an abnormal operating condition, but the exact cause of the error is unknown.

Effect  The I/O operation in progress aborts.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A problem exists in the controller. An EIO instruction was issued, and the termination status (TERMSTAT) value returned indicates that a soft controller error occurred.

Effect  The operation aborts.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A problem exists in the controller. An EIO instruction was issued, and the termination status (TERMSTAT) value returned indicates that a hard controller error occurred.

Effect  The operation aborts.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  A hard controller error has cleared.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  There is a problem with the controller, or with a device, or a device on the SCSI bus is not compliant with the SCSI-2 specification.

Effect  The command is not executed.

Recovery  Check any recently added SCSI devices: these devices might not be fully compliant with the SCSI-2 specification. Remove recently added devices and see if this error recurs. If this error occurs repeatedly, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  This error might indicate a problem with the device, the controller, or the cable. This error indicates that one of the following conditions exist:

Effect  The command is not executed.

Recovery  Make sure that all of the cables between the devices on the bus and the controller are connected. Make sure that the SCSI bus is terminated properly at both ends of the bus. If a device is busy, turn off the power to the device, then turn the power to the device back on. If none of these recovery actions are successful and if this error occurs frequently, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The IOP sent too many concurrent commands to the same device.

Effect  The command is not executed.

Recovery  Retry the command. If this error occurs repeatedly, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause   The returned value indicates a problem that cannot be identified.

Effect  The operation aborts.

Recovery  Contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause   A problem has occurred with the microcode of the Open SCSI device.

Effect  The Open SCSI device might be unusable.

Recovery  If the Open SCSI device goes down, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause   A hardware error occurred.

Effect  The Open SCSI device might be unusable.

Recovery  If the Open SCSI device goes down, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause  The syndrome indicates error returned by the SCSI module driver.

Effect  The IOP performs recovery.

Recovery  If the drive goes down, contact your service provider and provide all relevant information as follows:

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

Cause   A TMDS SCSI FIRMUP command has been issued.

Effect  A firmware update is initiated.

Recovery  Informational message only; no corrective action is needed.

Cause   A TMDS SCSI FIRMUP has completed.

Effect  FIRMUP loads the firmware code from the PROM code file into the EEPROM of the controller. The existing firmware of the EEPROM is replaced by the newly loaded code.

Recovery  Informational message only; no corrective action is needed.

Cause   A TMDS SCSI FIRMUP has failed.

Effect  The existing firmware of the EEPROM is not replaced.

Recovery  See the 3223 SCSI-2 Controller System Note for Himalaya K-Series Servers.

Cause   The cause of this error is vendor-specific.

Effect  See the vendor documentation.

Recovery  See the vendor documentation.