Chapter 90 SMD (SCSI Module Driver) Messages

Cause  Either the SCSI Module Driver (for J-series RVUs) or the Storage Mid Layer (SML) (for L-series RVUs) version does not match the I/O process (IOP) version, or an IOP programming error has occurred.

Effect  The command cannot be completed.

Recovery  Verify that the versions of the SCSI Module Driver (for J-series RVUs) or the SML (for L-series RVUs) and the IOP are compatible.

Cause  Either the SCSI Module Driver (for J-series RVUs) or the Storage Mid Layer (SML) (for L-series RVUs) version does not match the I/O process (IOP) version, or an IOP programming error has occurred.

Effect  The command cannot be completed.

Recovery  Verify that the versions of the SCSI Module Driver (for J-series RVUs) or the SML (for L-series RVUs) and the IOP are compatible.

Cause  The controller lock has not been acquired for an operation or entry point call that requires the controller lock.

Effect  The mailbox command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process acquires the controller lock and retries the operation or entry point call.

Cause  A SCSI Module Driver programming error has occurred. When present, the event detail provides more information for development.

Effect  The command cannot be completed.

Recovery   Contact the Global Customer Service Center to file a Genesis case against the SCSI Module Driver subsystem.

Cause  The most probable cause is that, during startup operations, the SCSI Module Driver version did not match the SCSI Interface Monitor (IFM) version. When present, the event detail provides more information for development.

Effect  The command cannot be completed.

Recovery  Verify that the versions of the SCSI Module Driver and the IOP are compatible.

Cause  A SCSI Module Driver programming error has occurred. When present, the event detail provides more information for development.

Effect  The mailbox command cannot be completed.

Recovery  Contact the Global Customer Service Center to file a Genesis case against the SCSI Module Driver subsystem.

Cause  The SCSI Module Driver (SMF) has detected an unknown or mismatched controller or device type.

Effect  The command cannot be completed.

Recovery  Check the SCF configuration of the device. Also verify that the versions of the SCSI interface manager (IFM) and SMD are compatible.

Cause  The Storage Mid Layer (SML) has temporarily run out of resources.

Effect  The command cannot be completed.

Recovery  Contact the Global Customer Service Center to file a Genesis case against the SML product.

Cause  The SCSI Module Driver is unknown by the I/O process (IOP).

Effect  The event name is not reported correctly in the event log.

Recovery  Verify that the versions of the SCSI Module Driver (for J-series RVUs) or the SML (for L-series RVUs) and the IOP are compatible and check the version of the template file. Contact the Global Customer Service Center to determine the underlying error.

Cause  A SCSI Module Driver programming error has occurred. When present, the event detail provides more information for development.

Effect  The command cannot be completed.

Recovery  Contact the Global Customer Service Center to file a Genesis case against the SCSI Module Driver subsystem.

Cause  The ServerNet hardware in the processor detected a ServerNet transfer timeout. This timeout was caused by the controller hardware, ServerNet congested traffic, or a ServerNet interconnect hardware problem.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command. If the error persists, check the ServerNet hardware.

Cause  ServerNet Services has reported that no access validation table (AVT) is available. The most probable cause is a programming error or a ServerNet configuration error.

Effect  The command cannot be completed.

Recovery  Check the ServerNet configuration.

Cause  The processor ServerNet hardware has received an error ServerNet packet. The error can be an address, direction, or source ID error. The packet can be a data or interrupt packet. Possible causes are an I/O process (IOP) error, SCSI Module Driver software error, a controller firmware or hardware error, or a ServerNet hardware error.

Effect  None. It might be an indication of some other problem.

Recovery  Informational message only; no corrective action is needed. The device IOP retries the command. If the error persists, check the controller hardware first, then ServerNet hardware, and then verify the compatibility of the IOP, SCSI Module Driver, and firmware versions.

Cause  A controller hardware error has occurred that is related to the ServerNet.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The host access disable (HAD) error has been detected by a processor that accesses the controller. The most probable cause is a ServerNet error.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The SCSI Module Driver clears the HAD error, and the device I/O process retries the command.

Cause  A ServerNet hardware error has caused the ServerNet path from the processor to the controller to go down.

Effect  The path from the processor to the devices attached to the controller is lost.

Recovery  The device I/O process retries the command with other paths. Check the ServerNet hardware.

Cause  ServerNet transfers have been aborted by ServerNet Services because of a processor power fail.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  An invalid memory access has led to an invalid ServerNet inbound transfer.

Effect  The command result is invalid.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  A controller access validation and translation (AVT) error has occurred.

Effect  The command cannot be completed because ServerNet transfers have been aborted by ServerNet Services.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  For a period of time, the SCSI Module Driver is holding off direct-bulk I/O (DBIO) requests for the path to the requesting processor due to a previous ServerNet error.

Effect  The command cannot be completed, but the file system and the device I/O process retries the command as a non-DBIO transfer.

Recovery  Informational message only; no corrective action is needed. However, if the error persists, check the ServerNet hardware between the adapter and the requesting processor.

Cause  A ServerNet path from the processor to the controller has come up.

Effect  I/O commands can use the available ServerNet path.

Recovery  Informational message only; no corrective action is needed.

Cause  The most likely cause is that the device is not connected to the SCSI bus. If the device is connected to the SCSI bus, the cause is a device, SCSI bus, or controller error.

Effect  The command cannot be completed.

Recovery  Check the device and the device power.

Cause  Either a device problem has occurred or an insufficient timeout has been set by the device I/O process (IOP).

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device IOP reattempts the command.

Cause  A device or controller problem has caused a command to the SCSI device to stop in an abnormal SCSI state.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The device might be busy with a previous outstanding SCSI command.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process reattempts the command.

Cause  Unexpected SCSI status was received. When present, the event detail allows development to identify the specific problem.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process reattempts the command.

Cause  A device, bus, or controller problem has occurred. When present, the event detail allows development to identify the specific problem.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process reattempts the command.

Cause  The device has kept the SCSI bus busy without data transfer. The controller has reset the SCSI device.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  Data transfer between the device and the processor has been interrupted.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command. If the error persists, check the ServerNet hardware.

Cause  A 45xx Modular Disk Subsystem back-end board (BEB) has reported an error to an F‑SAC on a ServerNet/DA.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command. If the error persists, check the BEB.

Cause  The SCSI Module Driver has detected an environment error from the back-end board (BEB) connected to an F‑SAC on a ServerNet/DA.

Effect  The device I/O process retries the command.

Recovery  The details of this event describe the exact failure reported by the BEB. Examine the event to determine the cause of the hardware failure and then remedy the failure.

Cause  The controller has logged out the device.

Effect  The device I/O process attempts a login to the device and reattempts the command.

Recovery  Informational message only; no corrective action is needed. The device I/O process attempts a login to the device and reattempts the command.

Cause  The controller could not locate the specified device.

Effect  The path to the device is lost.

Recovery  Check that the device is physically present. Check that the device is configured correctly. Check the controller to device interfaces.

Cause  The device I/O process has not performed a login to the device on that controller.

Effect  The device I/O process attempts a login to the device and reattempts the command.

Recovery  Informational message only; no corrective action is needed. The device I/O process attempts a login to the device and reattempts the command.

Cause  The device is encrypted but the controller could not locate an encryption key for the device.

Effect  The path to the device is lost.

Recovery  Check the encryption status of the device. Check that the controller (CLIM) can access the Enterprise Secure Key Manager (ESKM).

Cause  The controller has completed re-encrypting the device media with a new key.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The controller has aborted a device rekeying operation due to I/O errors.

Effect  The path to the device is lost.

Recovery  Check the encryption status of the device. If the encryption rekeying was aborted, perform a new key operation on the device followed by a disk revive. If the problem persists, contact the Global Customer Service Center for assistance.

Cause  The controller could not locate the specific partition on the device.

Effect  The path to the device is lost.

Recovery  Check that the device is physically present. Check that the device is configured and partitioned correctly. Check that the LDEV is configured correctly. Add or delete partitions on the device as necessary.

Cause  The IOP is accessing a partitioned device without specifying a partition number.

Effect  The path to the device is lost.

Recovery  Check that the device is physically present. Check that the device is configured and partitioned correctly. Check that the LDEV is configured correctly. Add or delete partitions on the device as necessary.

Cause  The controller CLIM has blocked the SCSI device for a short period due to error recovery.

Effect  The device I/O process reattempts the command after a short delay.

Recovery  Informational message only; no corrective action is needed. The device I/O process delays and reattempts the command.

Cause  The controller CLIM has put the SCSI host or device in an offline or deleted state.

Effect  The path to the device is lost.

Recovery  Check that the device is physically present and configured correctly. Check the controller to device interfaces.

Cause  The controller is not available or it has caused too many interrupts.

Effect  The path from the processor to the devices attached to the controller is lost.

Recovery  Check the controller hardware.

Cause  Access from the processor to the controller has not been established or has been lost because of a controller timeout. Access from the CPU to the controller has not been established.

Effect  None. The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process establishes CPU access to the controller.

Cause  Either the controller has lost power or it has failed to communicate with the module driver. Firmware needs to be downloaded to the SCSI controller.

Effect  None.

Recovery  Informational message only; no corrective action is needed. The device I/O process downloads firmware into the controller. If the error persists, contact your service provider to determine the underlying error.

Cause  An I/O process programming error has occurred.

Effect  An operation or a SCSI Module Driver call cannot be completed while the controller request queue is active.

Recovery  Informational message only; no corrective action is needed.

Cause  For J-series RVUs, either a controller request abort failed or a ServerNet error occurred during a write operation to the controller request queue.For L-series RVUs, the controller is not connected to the CPU.

Effect  None.The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process re-establishes CPU access to the controller.

Cause  A controller problem has occurred; the controller generated too many ServerNet errors.

Effect  The path from the processor to the devices attached to the controller is lost.

Recovery  Informational message only; no corrective action is needed. The device I/O process re-establishes CPU access to the controller.

Cause  The controller was disconnected by the CPU due to a controller failure or because it failed to complete an I/O abort.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process re-establishes CPU access to the controller.

Cause  The controller has detected that the SCSI bus was busy but not transferring data. As a result, the controller has reset the SCSI bus.

Effect  Commands to the devices on the SCSI bus have been aborted.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The other controller has detected that the SCSI bus was busy without data transfer. As a result, the other controller has reset the SCSI bus.

Effect  Commands to the devices on the SCSI bus have been aborted.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The controller has detected a Fibre Channel LIP Reset.

Effect  The device I/O process retries the command.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The controller has detected that a Fibre Channel Link has gone down.

Effect  The path to the devices attached to the controller is lost.

Recovery  Check the controller to device interfaces.

Cause  The controller has detected a Fibre Channel LIP.

Effect  The device I/O process retries the command.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The controller has detected a storm of Fibre Channel LIPS.

Effect  The device I/O process retries the command.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command. If the error persists contact your service provider to determine the underlying error.

Cause  The controller returned an unexpected error. For J-series RVUs, a controller problem has occurred. For L-series RVUs, the controller returned an unexpected error

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process reattempts the command.

Cause  A controller problem has occurred.

Effect  The mailbox command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  A controller problem has occurred.

Effect  The mailbox command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The controller has sent to the SCSI module driver a status message that is not related to any outstanding request, but which indicates the detection of a serious firmware error. When present, the event detail provides more information for development.

Effect  None. This is an indication of some other event.

Recovery  Informational message only; no corrective action is needed. If the error persists, contact the Global Customer Service Center for assistance.

Cause  The controller has not been configured correctly by XIOMON.

Effect  The path from the processor to the devices attached to the controller is lost.

Recovery  Check the configuration.

Cause  A controller problem has occurred.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process reattempts the command.

Cause  A data transfer has been interrupted by a ServerNet (for J-series RVUs) or an IB (InfiniBand) (for L-series RVUs), controller or device hardware error.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process reattempts the command. If the error persists, check the ServerNet (for J-series RVUs) or IB (for L-series RVUs), controller and device hardware.

Cause  The controller has sent to the SCSI module driver a status message that is not related to any outstanding request. When present, the event detail provides more information for development.

Effect  None. This might be an indication of some other problem.

Recovery  Informational message only; no corrective action is needed.

Cause  An excessive number of interrupts was received from the controller, so it has been disabled.

Effect  The path from the processor to the devices attached to the controller is lost.

Recovery  Check the controller hardware.

Cause  A controller problem has occurred.

Effect  The path from the processor to the devices attached to the controller is lost.

Recovery  Check the controller hardware.

Cause  A configuration error has occurred. Either too many processors accessed the controller or a SCSI Module Driver programming error has occurred.

Effect  The paths from the processor to the devices attached to the controller are lost.

Recovery  Check the configuration.

Cause  A firmware file error, controller memory error, or transfer error has occurred.

Effect  The controller download has failed. Repeated failures can cause the paths from the processor to the devices attached to the controller to become lost.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries downloading the controller.

Cause  The SCSI Module Driver has detected an error in the fiber connection between the F‑SAC on a ServerNet/DA and the attached back-end board (BEB).

Effect  The command cannot be completed, but device I/O process retries the command with other paths.

Recovery  Check the fiber connections between the F-SAC and the attached BEB.

Cause  The controller was disconnected by the CPU because it failed to complete an I/O abort.

Effect   The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process reattempts the command.

Cause  The processor has detected that the controller has been recently reset.

Effect  The path from the processor to the devices attached to the controller is temporarily lost.

Recovery  Informational message only; no corrective action is needed. The device I/O process downloads the controller after a short hold-off period. If the error persists contact your service provider to determine the underlying error.

Cause  The controller is busy rescanning its devices or performing device-related tasks.

Effect  The device I/O process cannot successfully complete I/O to the controller for a short period.

Recovery  Informational message only; no corrective action is needed. The device I/O process will delay for a short period and retry the command.

Cause  The controller does not support the SCSI command sent by the CPU.

Effect  The command cannot be completed.

Recovery  Contact the Global Customer Service Center to determine the underlying error.

Cause  The controller has detected an invalid LSA in the SCSI command sent by the CPU.

Effect  The command cannot be completed.

Recovery  Contact the Global Customer Service Center to determine the underlying error.

Cause  A SCSI command has timed out and been aborted. Possible causes are a SCSI bus reset, a device reset, a controller error, or a ServerNet error. Possible causes are a SCSI device, bus, controller or interface error.

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device I/O process reattempts the command.

Cause  The command has been aborted on request from the input/output process (IOP).

Effect  The command cannot be completed.

Recovery  Informational message only; no corrective action is needed. The device IOP reattempts the command.

Cause  The SCSI LLDD logged an event. The event text describes the cause.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  An NCSL or RDMA Services API returned an error to the SRP LLDD.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  An NCSL or RDMA Services API returned an error to the SRP LLDD.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  An IB path to the CLIM went down.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  An IB path to the CLIM came up.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The CLIM has disconnected from the CPU.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The CPU has connected to the CLIM.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The SRP LLDD received an unexpected event from NCSL.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The SRP LLDD obtained an unexpected work completion from NCSL or RDMA Services.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The SRP LLDD obtained an unexpected response packet from the CLIM.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The SRP LLDD could not obtain resources to perform the I/O to the CLIM.

Effect  None.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The SRP LLDD failed an I/O abort to the CLIM.

Effect  None.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The SRP LLDD timed out an I/O abort to the CLIM.

Effect  None.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The SRP LLDD successfully completed an I/O abort to the CLIM.

Effect  None.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The SRP LLDD failed to reset the connection to the CLIM.

Effect  None.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The SRP LLDD timed out on the connection reset to the CLIM.

Effect  None.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.

Cause  The SRP LLDD successfully reset the connection to the CLIM.

Effect  None.

Recovery  Informational message only; no corrective action is needed. The device I/O process retries the command.