Message identifiers 24578-24599

Message ID: 24578

Severity: Informational

Log message: The Smart Array SAS/SATA event notification service version %1.

Message ID: 24579

Severity: Informational

Log message: An event queue overflow has occurred for the array controller <controller name / slot information>. At least one event has been lost. This controller will only queue up to 100 events.

Message ID: 24580

Severity: Error

Log Message: The Smart Array SAS/SATA Event Notification Service needs to be upgraded and cannot process events at this time. The service is being stopped and processing of Smart Array controller events to the Windows system event log, ProLiant Integrated Management Log (IML) and Integrity System Event Log (SEL) will not occur until the software is updated.

To upgrade your software, please visit http://www.hpe.com/support/drivers

Message ID: 24581

Severity: Informational

Log message: The Smart Array SAS/SATA event notification service <status message>.

<status message> values:

  • “has encountered an error and has stopped”
  • “has stopped due to a message file error”
  • “was not able to update the service control manager with updated status”
  • “cannot open a registry parameter key”
  • “cannot start due to system event logging being disabled”

Message ID: 24582

Severity: Informational

Log message: A <drive type> physical drive located in bay <bay number> was <inserted / removed>. The drive can be found in box <box number> which is attached to port <port number> of array controller <controller name / slot information>.

Message ID: 24583

Severity: Informational

Log message: Array controller <controller name / slot information> has detected more than one cable with active drives attached.

Message ID: 24584

Severity: Warning

Log message: Too many runtime ECC errors have been received from the array controller <controller name / slot information>. The controller has restarted without utilizing its DIMM.

Message ID: 24585

Severity: Warning

Log message: The <drive type> physical drive located in bay <bay number> is offline but operational. This drive can be found in box <box number> which is connected to port <port number> of the array controller <controller name / slot information>. The offline reason received from the Smart Array firmware is: <firmware error code>.

<firmware error code> values:

  • TOO_SMALL_IN_LOAD_CONFIG - Replacement drive is too small for configured volume(s).
  • ERROR_ERASING_RIS - Could not write to reserved configuration sectors after multiple retries.
  • ERROR_SAVING_RIS - Could not write to reserved configuration sectors after multiple retries.
  • FAIL_DRIVE_COMMAND - “Fail Drive” command received from host.
  • MARK_BAD_FAILED - Unable to create media defect after multiple retries.
  • MARK_BAD_FAILED_IN_FINISH_REMAP - Unable to create media defect after multiple retries.
  • TIMEOUT - Too many SCSI command timeouts.
  • AUTOSENSE_FAILED - Drive is failing commands but is not returning SCSI sense data after multiple retries.
  • MEDIUM_ERROR_1 - Caused by a particular set of SCSI sense codes that indicate the drive is in bad shape and its data may be corrupt.
  • MEDIUM_ERROR_2 - Caused by a particular set of SCSI sense codes that indicate the drive is in bad shape; retries did not help.
  • NOT_READY_BAD_SENSE - Drive is returning unrecognized Not Ready sense codes.
  • NOT_READY - Drive is not ready and will not spin up.
  • HARDWARE_ERROR - Drive is returning a Hardware Error sense key; controller unable to get drive back online.
  • ABORTED_COMMAND - Drive is returning an Aborted Command sense key; controller unable to get drive back online.
  • WRITE_PROTECTED - Drive is returning a sense key indicating it is write protected.
  • SPIN_UP_FAILURE_IN_RECOVER - “Start Unit” command failed during error recovery
  • REBUILD_WRITE_ERROR - Drive failed write command after multiple retries during rebuild.
  • TOO_SMALL_IN_HOT_PLUG - Replacement drive is too small for configured volume(s).
  • BUS_RESET_RECOVERY_ABORTED - Unable to communicate with drive after multiple bus resets and retries; may be due to this drive or another drive that is corrupting the parallel SCSI bus.
  • REMOVED_IN_HOT_PLUG - Drive has been hot-removed.
  • INIT_REQUEST_SENSE_FAILED - “Request Sense” command failed during device discovery/initialization.
  • INIT_START_UNIT_FAILED - “Start Unit” command failed during device discovery/initialization.
  • INQUIRY_FAILED - “Inquiry” command failed after multiple retries.
  • NON_DISK_DEVICE - Attached device is not a hard disk per its inquiry data.
  • READ_CAPACITY_FAILED - “Read Capacity” command failed after multiple retries.
  • INVALID_BLOCK_SIZE - Drive indicates it is not formatted for 512 bytes per sector.
  • HOT_PLUG_REQUEST_SENSE_FAILED - “Request Sense” command failed after drive hot-added.
  • HOT_PLUG_START_UNIT_FAILED - “Start Unit” command failed after drive hot-added)
  • WRITE_ERROR_AFTER_REMAP - After reassigning a media error reported during a write command, the write command failed with another media error.
  • INIT_RESET_RECOVERY_ABORTED - Unable to communicate with drive during initialization after multiple bus resets and retries; may be due to this drive or another drive that is corrupting the parallel SCSI bus.
  • DEFERRED_WRITE_ERROR - Drive with write cache enabled reported that it could not complete a write command that it previously indicated was successful [lost data].
  • MISSING_IN_SAVE_RIS - Could not write to reserved configuration sectors after multiple retries.
  • WRONG_REPLACE - A hot-plug tape drive was plugged in as a replacement into a drive bay that a hard disk was removed from.
  • GDP_VPD_INQUIRY_FAILED - Could not read drive serial number after multiple retries.
  • GDP_MODE_SENSE_FAILED - Could not read certain mode pages after multiple retries.
  • DRIVE_NOT_IN_48BIT_MODE - SATA drive is not supported in 48-bit LBA mode.
  • DRIVE_TYPE_MIX_IN_HOT_PLUG - Attempt to hot-add a SATA drive as a replacement in a SAS-only volume, or vice versa.
  • DRIVE_TYPE_MIX_IN_LOAD_CFG - attempt to use a SATA drive as a replacement in a SAS-only volume, or vice versa.
  • PROTOCOL_ADAPTER_FAILED - Protocol layer reports that the protocol hardware has failed; may be a controller failure.
  • FAULTY_ID_BAY_EMPTY - Drive responds to SCSI ID, but the corresponding bay is empty.
  • FAULTY_ID_BAY_OCCUPIED - Bay is occupied by a drive that does not respond to the corresponding SCSI ID.
  • FAULTY_ID_INVALID_BAY - Drive responds to an ID that doesn’t have a valid corresponding bay.
  • WRITE_RETRIES_FAILED - Unable to complete a write operation after several retries.
  • QUEUE_FULL_ON_ZERO - Drive indicates that its queue is full when we have no requests outstanding to the drive.
  • SMART_ERROR_REPORTED - Drive has reported a predictive-failure error when controller is configured to automatically fail [instead of reporting imminent failure of] drives that report this error.
  • PHY_RESET_FAILED - Phy reset request failed.
  • FR_CHKBLK_FAILED_WRITE - Drive failed write command while checking for media errors.
  • FR_ATI_TEST_FAILED_WRITE - Drive failed write command while checking for errors.
  • OFFLINE_ERASE - Drive is offline due to a Secure Erase operation.
  • OFFLINE_TOO_SMALL - Drive is offline because it’s a replacement drive that is too small.
  • OFFLINE_DRIVE_TYPE_MIX - Drive is offline because it is not the correct type for this array [SATA vs SAS].
  • OFFLINE_ERASE_COMPLETE - Drive is offline because a Secure Erase operation has completed on it but it hasn’t been replaced yet.

Message ID: 24586

Severity: Informational

Log message: The <drive type> physical drive located in bay <bay number> is now online. This drive can be found in box <box number> which is connected to port <port number> of the array controller <controller name / slot information>.

Message ID: 24587

Severity: Warning

Log message: The <drive type> physical drive located in bay <bay number> is in a SMART trip state that indicates the drive has reached 0 percent usage left. Indicates that the drive has a SMART wear error and is approaching the maximum usage limit for writes (wear out). The drive should be replaced as soon as possible. This drive can be found in box <box number> which is connected to port <port number> of the array controller <controller name / slot information>.

Message ID: 24588

Severity: Warning

Log message: Sensor number <sensor number> has reported that the internal temperature has exceeded the preset limit. This sensor is located in box <box number> which is connected to port <port number> of array controller <controller name / slot information>. The array controller may attempt to shut down power to the attached box and/or spin down the installed disk drive(s).

Message ID: 24589

Severity: Warning

Log message: Sensor number <sensor number> has reported that the internal temperature is nearing the preset temperature limit. This sensor is located in box <box number> which is connected to port <port number> of array controller <controller name / slot information>. The array controller may enact precautionary measures to prevent data loss should the temperature reach the operating limit.

Message ID: 24590

Severity: Informational

Log message: Sensor number <sensor number> has reported that a previously existing temperature condition has been corrected. This sensor is located in box <box number> which is connected to port <port number> of array controller <controller name / slot information>. All of the temperature sensors in the attached box are now reporting acceptable temperature levels.

Message ID: 24591

Severity: Warning

Log message: Redundant power supply number <power supply number> has reported a fault. This power supply is located in box <box number> which is connected to port <port number> of array controller <controller name / slot information>.

Message ID: 24592

Severity: Informational

Log message: Redundant power supply number <power supply number> is no longer sensed as being in a failed state. Some possible reasons that would cause this state change to occur include:

1. The previously failed power supply has returned to an operational state.

2. The previously failed power supply was removed from the chassis.

The power supply state change occurred in box <box number> which is connected to port <port number> of array controller <controller name / slot information>.

Message ID: 24593

Severity: Informational

Log message: Array controller <controller name / slot information> has reported that more physical devices were detected than the controller is currently capable of supporting. Some physical drives will not be accessible.

Message ID: 24594

Severity: Warning

Log message: Redundant path number <path number> for the <drive type> physical drive located in bay <bay number> has either failed or been removed. The drive can be found in box <box number> which is attached to port <port number> of array controller <controller name / slot information>.

Message ID: 24595

Severity: Error

Log message: A drive failure notification has been received for the <drive type> physical drive located in bay <bay number>. This drive can be found in box <box number> which is connected to port <port number> of the array controller <controller name / slot information>. The failure reason received from the Smart Array firmware is: <firmware error code>.

<firmware error code> values:

  • TOO_SMALL_IN_LOAD_CONFIG - Replacement drive is too small for configured volume(s).
  • ERROR_ERASING_RIS - Could not write to reserved configuration sectors after multiple retries.
  • ERROR_SAVING_RIS - Could not write to reserved configuration sectors after multiple retries.
  • FAIL_DRIVE_COMMAND - “Fail Drive” command received from host.
  • MARK_BAD_FAILED - Unable to create media defect after multiple retries.
  • MARK_BAD_FAILED_IN_FINISH_REMAP - Unable to create media defect after multiple retries.
  • TIMEOUT - Too many SCSI command timeouts.
  • AUTOSENSE_FAILED - Drive is failing commands but is not returning SCSI sense data after multiple retries.
  • MEDIUM_ERROR_1 - Caused by a particular set of SCSI sense codes that indicate the drive is in bad shape and its data may be corrupt.
  • MEDIUM_ERROR_2 - Caused by a particular set of SCSI sense codes that indicate the drive is in bad shape; retries did not help.
  • NOT_READY_BAD_SENSE - Drive is returning unrecognized Not Ready sense codes.
  • NOT_READY - Drive is not ready and will not spin up.
  • HARDWARE_ERROR - Drive is returning a Hardware Error sense key; controller unable to get drive back online.
  • ABORTED_COMMAND - Drive is returning an Aborted Command sense key; controller unable to get drive back online.
  • WRITE_PROTECTED - Drive is returning a sense key indicating it is write protected.
  • SPIN_UP_FAILURE_IN_RECOVER - “Start Unit” command failed during error recovery
  • REBUILD_WRITE_ERROR - Drive failed write command after multiple retries during rebuild.
  • TOO_SMALL_IN_HOT_PLUG - Replacement drive is too small for configured volume(s).
  • BUS_RESET_RECOVERY_ABORTED - Unable to communicate with drive after multiple bus resets and retries; may be due to this drive or another drive that is corrupting the parallel SCSI bus.
  • REMOVED_IN_HOT_PLUG - Drive has been hot-removed.
  • INIT_REQUEST_SENSE_FAILED - “Request Sense” command failed during device discovery/initialization.
  • INIT_START_UNIT_FAILED - “Start Unit” command failed during device discovery/initialization.
  • INQUIRY_FAILED - “Inquiry” command failed after multiple retries.
  • NON_DISK_DEVICE - Attached device is not a hard disk per its inquiry data.
  • READ_CAPACITY_FAILED - “Read Capacity” command failed after multiple retries.
  • INVALID_BLOCK_SIZE - Drive indicates it is not formatted for 512 bytes per sector.
  • HOT_PLUG_REQUEST_SENSE_FAILED - “Request Sense” command failed after drive hot-added.
  • HOT_PLUG_START_UNIT_FAILED - “Start Unit” command failed after drive hot-added)
  • WRITE_ERROR_AFTER_REMAP - After reassigning a media error reported during a write command, the write command failed with another media error.
  • INIT_RESET_RECOVERY_ABORTED - Unable to communicate with drive during initialization after multiple bus resets and retries; may be due to this drive or another drive that is corrupting the parallel SCSI bus.
  • DEFERRED_WRITE_ERROR - Drive with write cache enabled reported that it could not complete a write command that it previously indicated was successful [lost data].
  • MISSING_IN_SAVE_RIS - Could not write to reserved configuration sectors after multiple retries.
  • WRONG_REPLACE - A hot-plug tape drive was plugged in as a replacement into a drive bay that a hard disk was removed from.
  • GDP_VPD_INQUIRY_FAILED - Could not read drive serial number after multiple retries.
  • GDP_MODE_SENSE_FAILED - Could not read certain mode pages after multiple retries.
  • DRIVE_NOT_IN_48BIT_MODE - SATA drive is not supported in 48-bit LBA mode.
  • DRIVE_TYPE_MIX_IN_HOT_PLUG - Attempt to hot-add a SATA drive as a replacement in a SAS-only volume, or vice versa.
  • DRIVE_TYPE_MIX_IN_LOAD_CFG - attempt to use a SATA drive as a replacement in a SAS-only volume, or vice versa.
  • PROTOCOL_ADAPTER_FAILED - Protocol layer reports that the protocol hardware has failed; may be a controller failure.
  • FAULTY_ID_BAY_EMPTY - Drive responds to SCSI ID, but the corresponding bay is empty.
  • FAULTY_ID_BAY_OCCUPIED - Bay is occupied by a drive that does not respond to the corresponding SCSI ID.
  • FAULTY_ID_INVALID_BAY - Drive responds to an ID that doesn’t have a valid corresponding bay.
  • WRITE_RETRIES_FAILED - Unable to complete a write operation after several retries.
  • QUEUE_FULL_ON_ZERO - Drive indicates that its queue is full when we have no requests outstanding to the drive.
  • SMART_ERROR_REPORTED - Drive has reported a predictive-failure error when controller is configured to automatically fail [instead of reporting imminent failure of] drives that report this error.
  • PHY_RESET_FAILED - Phy reset request failed.
  • FR_CHKBLK_FAILED_WRITE - Drive failed write command while checking for media errors.
  • FR_ATI_TEST_FAILED_WRITE - Drive failed write command while checking for errors.
  • OFFLINE_ERASE - Drive is offline due to a Secure Erase operation.
  • OFFLINE_TOO_SMALL - Drive is offline because it’s a replacement drive that is too small.
  • OFFLINE_DRIVE_TYPE_MIX - Drive is offline because it is not the correct type for this array [SATA vs SAS].
  • OFFLINE_ERASE_COMPLETE - Drive is offline because a Secure Erase operation has completed on it but it hasn’t been replaced yet.

Message ID: 24596

Severity: Error

Log message: The <drive type> physical drive located in bay <bay number> is in a SMART predictive failure state. This drive can be found in box <box number> which is connected to port <port number> of the array controller <controller name / slot information>.

Message ID: 24597

Severity: Warning

Log message: The <drive type> physical hard drive located in bay <bay number> is not supported <not supported reason>. This drive can be found in box <box number> which is connected to port <port number> of the array controller <controller name / slot information>.

<not supported reason> values:

  • “because it is a singled ported drive”
  • “because it is a SATA drive”
  • “because it is smaller than the drive it is replacing”
  • “because it is of an unrecognized type”
  • “because it contains an unsupported RIS configuration”

Message ID: 24598

Severity: Informational

Log message: Logical drive <logical drive number> of array controller <controller name / slot information> has encountered a status change from:

Status: <previous status>

to

Status: <current status>

<previous status> and <current status> values:

  • “OK”
  • “FAILED”
  • “NOT CONFIGURED”
  • “INTERIM RECOVERY MODE”
  • “READY FOR RECOVERY”
  • “RECOVERING”
  • “WRONG PHYSICAL DRIVE REPLACED”
  • “PHYSICAL DRIVE NOT PROPERLY CONNECTED”
  • “HARDWARE IS OVERHEATING”
  • “HARDWARE HAS OVERHEATED”
  • “EXPANDING”
  • “NOT YET AVAILABLE”
  • “QUEUED FOR EXPANSION”
  • “DISABLED DUE TO SCSI ID CONFLICT”
  • “EJECTED”
  • “ERASING”
  • “UNKNOWN”

Message ID: 24599

Severity: Warning

Log message: Logical drive <logical drive number> of array controller <controller name / slot information> has encountered a status change from:

Status: <previous status>

to

Status: <current status>

<previous status> and <current status> values:

  • “OK”
  • “FAILED”
  • “NOT CONFIGURED”
  • “INTERIM RECOVERY MODE”
  • “READY FOR RECOVERY”
  • “RECOVERING”
  • “WRONG PHYSICAL DRIVE REPLACED”
  • “PHYSICAL DRIVE NOT PROPERLY CONNECTED”
  • “HARDWARE IS OVERHEATING”
  • “HARDWARE HAS OVERHEATED”
  • “EXPANDING”
  • “NOT YET AVAILABLE”
  • “QUEUED FOR EXPANSION”
  • “DISABLED DUE TO SCSI ID CONFLICT”
  • “EJECTED”
  • “ERASING”
  • “UNKNOWN”