A physical device came on-line

This event is generated when an array physical device (such as a drive) is detected to have come online. Possible causes are:

A rebuild completed.
A device was configured.
A physical device was manually set to on-line.

This is an informational message. No action is needed.

A physical device became a hot spare

This event is generated when an array physical device (such as a drive) is detected to have become a hot spare. Possible causes are:

A device was configured as a hot spare.
A manual hot spare was done.
An automatic hot spare was done.

Raidbld made it a hot spare. (Not applicable to array systems with external controllers, such as the HP Rack Storage/12FC.)

This is an informational message. No action is needed.

A physical device reports a hard error

This event is generated when an array physical device (such as a drive) is detected to have an error. Possible causes are:

A bad sector was found on the physical media.
Mechanical failure on the device.
The host SCSI device detected an illegal instruction.
The target device generated an unknown phase sequence. You may need to review other events in the event log to determine the cause.

If problem happens frequently, note the problem device listed in the event message and replace it or contact your service representative.

A physical device predicted potential failure (PFA/SMART)

This event is generated when an array physical device (such as a drive) alerts the system that it is about to fail. HP hard disk drives include predictive failure code in their firmware. This code monitors the drive for errors, when it crosses the factory set threshold for the maximum allowable number of errors, it generates this message. Possible causes are:

A physical device predicts future failure.
An external RAID logical device may have become critical.

When you encounter this problem, contact or your service representative.

Automatic rebuild started

This event is generated when an array begins the rebuild process. Possible causes are:

A physical device failed and a spare was available.
A physical device failed and no spare was available.
A spare device was added.

This is an informational message. No action is needed.

Manual rebuild started

This event is generated when a user manually begins the rebuild process on a array. Possible causes are:

An FC Array client started the rebuild on user’s request.

This is an informational message. No action is needed.

Rebuild completed

This event is generated when an array rebuild completed successfully.

This is an informational message. No action is needed.

Rebuild canceled

This event is generated when an array rebuild is canceled due to one of the following causes:

A user cancels a rebuild.

Restart the rebuild, if required.

Rebuild error

Due to some unknown error on the array controller, the rebuild failed. Retry the rebuild.

If the problem continues without additional information contact your service representative.

Rebuild failed due to new physical device

This event is generated when the rebuild of the array failed due to a new physical device. Possible causes are:

A new physical device failed.
A new physical device may not be compatible with the array controller hardware/firmware.

Replace the physical device and retry the rebuild.

Rebuild failed due to logical device failure

This event is generated when the rebuild of the array failed due to logical device failure. Possible causes are:

At least one more physical device failed in array.
Bad data table overflow.

Check individual drive status. If possible replace or change the state of the drive and restart the rebuild.

A physical device failed

This event is generated when a physical device in the array has failed. Possible causes are:

A user action caused the physical device to fail.

Replace the failed device.

A physical device was found

This event is generated when a physical device in the array was found. Possible causes are:

A physical device has been powered on.
A new physical device has been added.
Controller was powered on.
Controller was added.
System has rebooted.

This is an informational message. No action is needed.

A physical device is gone

This event is generated when a physical device in the array is gone. Possible causes are:

User removed an unconfigured physical device.
An unconfigured physical device failed.
A controller was removed.
A controller powered off.

Replace the device, if needed

A physical device is unconfigured

This event is generated when a user sets a physical device in the array to unconfigured.

To keep this event from being generated make sure all devices are configured.

Expand capacity started

This event is generated when an array's capacity is being expanded. Possible causes are:

User started an Expand Array operation.
A suspended Expand Array operation was restarted.

This is an informational message. No action is needed.

Expand capacity finished

This event is generated when an array's capacity has been expanded using the Expand Array function. The expansion operation has finished.

This is an informational message. No action is needed.

Expand capacity failed

This event is generated when the expand capacity function for an array has failed. Multiple physical devices failed during the operation.

It may not be possible to recover from this error. Contact your service representative.

Command to physical device timed out

This event is generated when a command to one of the array's physical devices timed out. Possible causes are:

The physical device has been removed.
The physical device failed.
The Command Time Out value is not correct.

If the physical device has failed then replace the device. Otherwise, this may indicate that there is a problem with the host SCSI HBA (Host Bus Adapter). Check that the SCSI cable to the host HBA is properly connected and the correct length. Also, check to be sure the host SCSI HBA has the latest driver installed.

Physical device command aborted

This event is generated when a command to one of the array's physical devices is aborted. Possible causes are:

The user may have requested to abort the command.
The firmware may have aborted the command to recover from error.
The device may have aborted the command.

There is no action to be taken for the physical device. This may indicate that there is a problem with the host SCSI HBA (Host Bus Adapter). Check that the SCSI cable to the host HBA is properly connected and the correct length. Also, check to be sure the host SCSI HBA has the latest driver installed.

Command was retried

This event is generated when a command to one of the array's physical devices was retried. Possible causes are:

The original command may have timed out.
Bus reset may have occurred.
Device reset may have occurred.

Parity Error

This event is generated when a parity error was detected on one of the array's physical devices. Possible causes are:

A physical device did not generate proper parity
The controller failed, did not check parity properly.
A cable failed.
Improper cable length.
Another physical device interfered.
Some outside environmental affected the data on the cable (e.g., radio frequency signal).
A terminator is not connected.
Improper termination.

If problem happens frequently, note the problem device listed in the event message and replace it or contact your service representative.

Soft Error

This event is generated when an error in the array was detected by physical device and data was recovered. You should run a consistency check on the device using the FCArray Assistant software.

If the problem happens frequently, note the problem device listed in the event message and replace it.

Miscellaneous error

This event is generated when a miscellaneous error was detected on one of the array's physical devices. Possible causes are:

A physical device reported some error which does not fit in any category.
Read/Write command time out.
Data over run.
Physical device was busy when host attempted to send command.

If problem happens frequently, note the problem device listed in the event message and replace it.

Physical device reset

This event is generated when a reset of a physical device in an array is detected. Possible causes are:

The firmware has done reset to recover from error.
The user has done a reset.

This is an informational message. No action is needed.

A physical device became an active spare

This event is generated when a physical device in an array becomes an active spare. Possible causes are:

Device was configured.
Manual active spare was done.
Automatic active spare was done.

This is an informational message. No action is needed.

A physical device became a warm spare

This event is generated when a physical device in an array becomes an active spare. Possible causes are:

Device was configured.
Manual warm spare was done.
Automatic warm spare was done.

This is an informational message. No action is needed.

Request Sense data present

This event is generated when a Request Sense Data error occurs on a physical device in an array. Possible causes are:

A physical device reported an error.
Firmware reported an operational error.

Using the FCArray Assistant software, read the request sense data to understand the root cause. Refer to the HP NetServer FCArray Assistant Installation and User Guide for details.

Consistency check started

This event is generated when a Consistency Check is started on an array. Possible causes are:

The user started a consistency check.

This is an informational message. No action is needed.

Consistency check completed without error

This event is generated when a Consistency Check on an array completed successfully without detecting any errors.

This is an informational message. No action is needed.

Consistency check canceled

This event is generated when a Consistency Check on an array was canceled by the user before completion.

Restart consistency check, if required

Consistency check completed with an error

This event is generated when a Consistency Check on an array completes with an error. Possible causes are:

In consistent data was found.
Bad sectors were found.
A physical device reliability problem.

Using the FCArray Assistant software, read the bad block and request sense table for more information. Refer to the HP NetServer FCArray Assistant Installation and User Guide for details.

Consistency check failed due to logical device

This event is generated when a Consistency Check failed due to the failure of a logical device in the array. Possible causes are:

A logical device became critical.
A logical device failed.

Using the FCArray Assistant software, read request sense data for more information. Refer to the HP NetServer FCArray Assistant Installation and User Guide for details.

Consistency check failed due to physical device failure

This event is generated when a Consistency Check failed due to a failure of a physical device in the array.

Using the FCArray Assistant software, read request sense data for more information. Refer to the HP NetServer FCArray Assistant Installation and User Guide for details.

Logical device became off-line

This event is generated because one or more physical devices in the array failed.

It may not be possible to recover from this error. Check individual drive status. If possible replace or change the state of the drive and restart the rebuild. If this fails contact your service representative.

Logical device became critical

This event indicates that a physical device in the array has failed. Replace the physical device. Start the rebuild, if required.

Logical device became on-line

This event is generated when a logical device in the array comes on-line. Possible causes are:

The rebuild completed.
The user set the physical device online.
A new configuration was added.

This is an informational message. No action is needed.

Automatic rebuild started on logical device

This event is generated when the array begins the rebuild process using a spare device. Possible causes are:

A physical device failed and a spare device was available.
A spare physical device was found and replaced the failed device.

This is an informational message. No action is needed.

Manual rebuild started on logical device

This event is generated when a user manually begins the rebuild process on the array. Possible causes are:

FCArray Assistant client started the rebuild on user’s request.

This is an informational message. No action is needed.

Rebuild completed on logical device

This event is generated when an array rebuild completed successfully only for this logical device.

This is an informational message. No action is needed.

Rebuild canceled on logical device

This event is generated when an rebuild is canceled.

The canceled rebuild may be due to one of the following causes:

The user canceled the rebuild.
A higher priority rebuild started.

Restart the rebuild, if required.

Rebuild error on logical device

Due to some unknown error on the controller, the array rebuild failed. Retry the rebuild.

If the problem continues without additional information contact your service representative.

Rebuild of logical device failed due to new physical device

This event is generated when the rebuild of the array failed due to a new physical device. Possible causes are:

A new physical device failed.
A new physical device may not be compatible with FCArray controller hardware/firmware.

Replace the physical device and retry the rebuild.

Rebuild of logical device failed due to logical device failure

This event is generated when the rebuild of the array failed due to logical device failure. At least one more physical device failed in array. Possible causes are:

It may not be possible to recover from this error. Check individual drive status. If possible replace or change the state of the drive and restart the rebuild. If it still fails, contact your service representative.

A logical device initialization started

This event is generated when a user starts an initialization of a logical device in the array. Note that any previous data stored on the logical device is lost during initialization.

A logical device initialization completed

This event is generated when an initialization operation on a logical device in the array completed successfully.

This is an informational message. No action is needed.

A logical device initialization was canceled

This event is generated when an initialization operation on a logical device in the array is canceled by the user.

Restart the initialization, if required

A logical device initialization failed

This event is generated when an initialization operation on a logical device in the array fails. Possible causes are:

One or more physical device(s) failed.
The controller has been removed.
The controller has been powered off.

Refer to the device failure event message for more information.

A logical device was found

This event is generated when a logical device in the array is found. Possible causes are:

A new configuration has been added.
An Expand Array operation completed.
A new controller has been plugged in.
A controller has been powered on.
The system has rebooted.

This is an informational message. No action is needed.

A logical device is gone

This event is generated when a logical device in the array is no longer available. Possible causes are:

A new configuration has been added.
The user deleted a logical device.
The controller has been removed.
The controller has been powered off.

This is an informational message.

Expand capacity started on logical device

This event is generated when a user starts an Expand Array operation to expand the capacity of a logical device in the array.

This is an informational message. No action is needed.

Expand capacity finished on logical device

This event is generated when an Expand Array operation to expand the capacity of a logical device in the array has completed.

This is an informational message. No action is needed.

Expand capacity on logical device failed

This event is generated when multiple physical devices fail during an Expand Array operation to expand the capacity of a logical device in the array.

It may not be possible to recover from this error. Check individual drive status. If possible replace or change the state of the drive and restart the rebuild. If problem persists contact your service representative.

Bad Block was found

This event is generated when a bad sector was found on a physical device in the array during:

A consistency check.
A rebuild.
An Expand Array operation.

This is an informational message.

System device size changed

This event is generated when the size of a system device in the array has changed. Possible causes are:

A new configuration has been added.
An Expand Array operation has added extra capacity.

This is an informational message. No action is needed.

System device type changed

This event is generated when the type of a system device in the array has changed. Possible causes are:

A new configuration has been added.
RAID migration completed.
An Expand Array operation completed on RAID 1

This is an informational message. No action is needed.

A bad data block was found on a logical device

This event is generated when a bad data blocks were found on multiple physical devices in the same zone in the array. Restore data from a backup.

System or array controller started

This event is generated when the server system (though may be only the FCArray controller) started. If you did not expect a system reboot, you need to investigate the source of this problem to prevent it from happening again.

Write Back error

This event is generated when a data cache write operation failed on the array.

Data may have been lost. Restore the data from a backup.

State Table is full

This event is generated when too many configuration changes occurred since the last boot of the array.

Reboot the system by power cycling when convenient.

Controller is dead

This event is generated when the system detects that the array controller is unavailable. Possible causes are:

The controller failed.
The controller was removed from the system.
The controller has been powered off.

If the controller has failed, contact your service representative.

Controller has reset

This event is generated when the system detects that the array controller has reset. Possible causes are:

The controller driver has reset the controller to recover from an error.
The controller driver has reset the controller to activate new firmware or functionality or configuration.

This is an informational message.

A Controller was found

This event is generated when the system finds an array controller. Possible causes are:

A new controller has been installed.
A controller has been powered on.
The system has rebooted.

This is an informational message. No action is needed.

A Controller is gone

This event is generated when an array controller is no longer available to the system. Possible causes are:

The controller has failed.
The controller has been removed.
The controller has been powered off.

This is an informational message.

Battery Backup Unit found

This event is generated when a Battery Backup Unit is found on the array controller.

This is an informational message. No action is needed.

BBU power is low

This event is generated when a Battery Backup Unit does not have enough power to enable the write data cache of the array controller.

If this message happens without a power failure, replace the Battery Backup Unit.

BBU power is OK

This event is generated when a Battery Backup Unit has enough power to enable the write data cache of the array controller.

This is an informational message. No action is needed.

Controller has been powered off

This event is generated when an array controller is powered off.

This is an informational message. No action is needed.

Controller has been powered on

This event is generated when an array controller is powered on.

This is an informational message. No action is needed.

Controller is Online

This event is generated when an array controller comes online.

This is an informational message. No action is needed.

Controller is Offline

This event is generated when an array controller is offline.

Possible causes are:

The controller has failed.
The controller has been removed.
The controller has been powered off.

This is an informational message. If the controller has failed, contact your service representative.

Controller's Partner is gone

This event is generated when the partner controller of a dual-active array controller pair is gone. System is now running in fail-over mode.

The secondary controller has taken over operation of the array. Replace the failed controller as soon as possible to maintain redundant fault tolerance.

BBU Recondition Start

This event is generated when the BBU (Battery Backup Unit) recondition operation has started.

This is an informational message. No action is needed.

BBU Recondition Finished

This event is generated when the BBU (Battery Backup Unit) recondition operation has finished.

This is an informational message. No action is needed.

BBU Recondition Cancelled

This event is generated when the BBU (Battery Backup Unit) recondition operation has been cancelled.

This is an informational message. No action is needed.

System started

Physical device size table is full

This event is generated when too much physical device size information is defined in the array.

Remove unused device information for this system

User logged in

This event is generated when a user logged in using FCArray Assistant on the server system.

This is an informational message. No action is needed.

User logged out

This event is generated when a user using FCArray Assistant logged out from the server system.

This is an informational message. No action is needed.

Storage cabinet fan Failed

This event is generated when the system detects a failed fan in the array storage cabinet. Possible causes are:

A cable connection is broken.
A bad fan.

Check fan status LEDs. Replace the failed fan.

Storage cabinet fan is OK

This event is generated when the system detects that a previously failed fan in the array storage cabinet is now operational. Possible causes are:

Faulty fan has been replaced.
Cable is connected properly.

This is an informational message. No action is needed.

Drive enclosure fan failed

This event is generated when the system detects a failed fan in the HP Rack Storage/12FC. Possible causes are:

A cable connection is broken.
A bad fan.

Check fan status LEDs. Replace the failed fan.

Storage cabinet fan is not present

This event is generated when the system detects that a fan in the array storage cabinet is no longer available. Possible causes are:

The enclosure management connection is broken.
The management hardware is bad.
The fan is not present.

Refer to your array storage cabinet documentation for diagnostic and repair procedures.

Storage cabinet power supply failed

This event is generated when the system detects a failed power supply in the array storage cabinet. Possible causes are:

A cable connection is broken.
A bad power supply.

Check power supply status LEDs. Replace the power supply.

Storage cabinet power supply is OK

This event is generated when the system detects that a previously failed power supply in the array storage cabinet is now operational.

This is an informational message. No action is needed.

Drive enclosure power supply failed

This event is generated when the system detects a failed power supply in the HP Rack Storage/12FC. Possible causes are:

A cable connection broken.
A bad power supply.

Check power supply status LEDs. Replace power supply.

Storage cabinet power supply is not present

This event is generated when the system detects that a power supply in the array storage cabinet is no longer available. Possible causes are:

The management connection is broken.
The management hardware is bad.
The power supply is not present.

Refer to your array storage cabinet documentation for diagnostic and repair procedures.

Storage cabinet too hot

This event is generated when the system detects that the array storage cabinet is too hot. Possible causes are:

The room temperature is too high.
A bad fan.
A bad sensor.

Turn off the system and storage cabinet now and allow it to cool down before components are damaged. Check the system to determine the source of the temperature problem. Reduce the room temperature where the storage cabinet resides.

Storage cabinet is hot

This event is generated when the system detects that the array storage cabinet is hot. Possible causes are:

The room temperature is high.
A bad fan.
A bad sensor.

Check the system to determine the source of the temperature problem. Reduce the room temperature where the storage cabinet resides.

Storage cabinet temperature is OK

This event is generated when the system detects that the temperature of the array storage cabinet has returned to normal. Possible causes are:

A faulty fan has been replaced.
The room temperature was reduced.

This is an informational message. No action is needed.

Drive enclosure is too hot

This event is generated when the system detects that the HP Rack Storage/12FC is too hot. Possible causes are:

Room temperature is too high.
Bad fan.

Turn off the system and array now and allow it to cool down before components are damaged. Check the system to determine the source of the temperature problem. Reduce the room temperature where the storage cabinet resides.

Storage cabinet temperature sensor is not present

This event is generated when the system detects that the temperature sensor of the array storage cabinet is no longer available. Possible causes are:

Enclosure management connection is broken.
The management hardware is bad.
The sensor is not present.

Refer to your array storage cabinet documentation for diagnostic and repair procedures.