This trap is generated whenever the RAID configuration is updated, either by saving the configuration in NetRAID configuration/management utilities, or by a reconstruction operation that results in a RAID configuration change.
This is an informational message. No action is needed.
This trap results from any change in the state of a physical drive, either initiated manually from NetRAID configuration/management utilities or by natural disk failures. The different possible states are:
|
Ready |
The drive is functioning normally but is not part of any logical drive. |
|
Online |
The drive is functioning normally and is part of a configured logical drive. |
|
Hot Spare |
The drive is functioning normally and is designated as a spare drive. |
|
Rebuild |
The drive is being rebuilt with data from a failed drive. |
|
Fail |
A failure has occurred with the drive. |
The change in physical drive state may cause logical drive state changes, which are reported by a logical drive state change trap. The change in physical drive state may cause critical errors, in which data availability is hampered.
For fault-tolerant logical drives, a Fail drive loss should be addressed immediately as the array no longer has redundancy and is subject to data loss should another drive fail. Replace drive and rebuild the array. Contact system administrator immediately.
For non-fault tolerant logical drive (i.e. RAID 0), a Fail drive means all data lost. Only option is replace the failed drive with a new drive (equal or larger capacity). Restore the original RAID configuration from a file or reconfigure the logical drive(s). Re-partition the drive. Reinstall the operating system if necessary. Restore data from backup tape.
This trap is a secondary effect of a physical drive state change. The logical drive states are:
|
Optimal |
The logical drive is functioning properly and all its physical drives in the array are online. |
|
Degraded |
The logical drive is functioning in a degraded mode. One of physical drives in the array has failed. |
|
Fail |
The logical drive is not functioning properly. One or more physical drives in the array have failed. |
If the state of the logical drive is Degraded, the data is still available. However, the logical drive performance will be degraded. Replace the failed physical drive and rebuild.
If the state of the logical drive is Fail. Replace all the failed physical drive(s). Restore the original RAID configuration from a file or reconfigure the logical drive(s). Re-partition the drive. Reinstall the operating system if necessary. Restore data from backup tape
This trap is generated whenever a logical drive is being initialized. For RAID 3 and RAID 5 logical drives this operation must be performed before the logical drive can be used. This ensures that all the stripes of the logical drive are consistent.
This is an informational message. No action is needed.
This trap is generated whenever a logical drive initialization operation completes successfully. This implies that the relevant parts of all the component physical drives of the logical drives have been initialized with zeros and that all the stripes of the logical drives are consistent.
This is an informational message. No action is needed.
This trap is generated whenever the logical drive initialization operation is aborted by the user.
Though the logical drive would be available for use even if the initialization had not completed successfully, using a partially initialized drive is not recommended. Logical drives which are not fully initialized may contain bad blocks which will be mapped out during the intialization. The initialization process should be restarted and allowed to complete before using the array.
This trap is generated if an initialize operation is in progress on a logical drive and the state of one or more component physical drives changes to FAILED. Physical drive state may change due to natural disk failure, excessive media/other errors, a drive being removed by the user, or a drive being FAILED by the user via a NetRAID configuration/management utility.
Determine cause of the failure. For example, did a physical drive fail? Did a drive or a storage cabinet get disconnected from the DAC? Check for other messages relating to a physical drive failure. If a physical drive failed, it should be replaced and the initialization process restarted.
If a physical drive is suspected to have failed due to excessive media errors, it may be corrected by performing a low-level format on the drive first; then reconfigure the drive in the array and begin the initialization process again. A repeat failure of the same drive would indicate a replacement is in order.
This trap is generated whenever a logical drive check consistency operation is started using the NetRAID configuration/management utility. This operation can be performed only on fault-tolerant OPTIMAL logical drives to check if all the stripes are consistent. This operation also cures the consistency by writing proper data in the PARITY block for RAID 5 or RAID 3 and in the MIRROR block for RAID 1. If any such corrective operation takes place, the check consistency operation completes with a status indicating this fact.
Be sure to verify that the consistency check finishes.
This is an informational message. No action is needed.
Note that it is recommended to run a complete consistency check on a regular basis (2-4 weeks) to ensure that any new bad blocks on the hard disks are reallocated. This will ensure the array can always be rebuild should a drive failure occur.
This trap results from the successful completion of a check consistency operation on a logical drive. It indicates that the logical drive was consistent.
This is an informational message. No action is needed.
This trap is generated whenever the logical drive check consistency operation is aborted by the user. Use NetRAID configuration/management utilities to abort a consistency check.
Note that it is recommended to run a complete consistency check on a regular basis (2-4 weeks) to ensure that any new bad blocks on the hard disks are reallocated. This will ensure the array can always be rebuild should a drive failure occur.
This trap results from the successful completion of a check consistency operation on a logical drive. It indicates that inconsistencies were found and fixed.
Inconsistencies are blocks of data on drives which do not contain the correct data based on redundant information from other drives. The inconsistencies were corrected by the controller. It is recommended to run a complete consistency check on a regular basis (2-4 weeks) to ensure that any new bad blocks on the hard disks are reallocated. This will ensure the array can always be rebuild should a drive failure occur.
If regular consistency checks are run, bad blocks will be mapped out and no other action is required.
This trap is generated if a check consistency operation is in progress on a logical drive and one or more component physical drives change state to FAILED. Physical drive state may change due to natural disk failure, excessive media/other errors, a drive being removed by the user, or a drive being FAILED by the user via a NetRAID configuration/management utility.
Determine the cause of failure. For example, did a physical drive fail? Did a drive or a storage cabinet get disconnected from the DAC? Look for other traps indicating a physical drive failure. If a physical drive failed, it should be replaced and rebuilt. The consistency check should be restarted.
A failed consistency check with no failed physical drives indicated would be due to the data in one or more stripes being unrecoverable. This would be due to two or more bad blocks within the same stripe. The bad blocks can be reallocated with a consistency check and this should be done on a regular basis (2-4 weeks) to ensure new bad blocks do not accumulate. A failed consistency check could indicate some data loss, all files on the array would need to be checked for integrity.
This trap is generated when the user initiates a logical drive reconstruct operation to increase the capacity or change the RAID level.
This is an informational message. No action is needed.
This trap indicates that reconstruction of a logical drive has been successfully completed and that the characteristics of the logical drive have been changed to the desired settings.
This is an informational message. No action is needed.
This trap is generated if a reconstruction operation is in progress on a logical drive and one or more component physical drives changes state to FAILED. Physical drive state may change due to natural disk failure, excessive media/other errors, a drive being removed by the user, or a drive being FAILED by the user via a NetRAID configuration/management utility.
The reconstruction will fail only in a data loss condition.
Determine the cause of the failure. If the drive(s), or a storage cabinet, become disconnected from the Disk Array Controller, reconnect them and then restart the reconstruction. Look for traps indicating a physical disk failure.
If the physical drive(s) failed, this means loss of data. Data will not be lost if the drive failure does not cause a loss of data in the source and destination of the reconstruction; e.g., if a drive failed in a RAID5 to RAID5 reconstruction (adding a drive), both source and destination would be degraded without data loss. However, if the source was RMD0, then a drive loss would cause loss of data at the source and the reconstsruction could not continue. The only option is to replace the failed drive(s). Restore the original RAID configuration from a file or reconfigure the logical drive(s). Re-partition the drive. Reinstall the operating system if necessary. Restore your data from your backup tape.
This trap normally is not generated. It is for diagnostics purposes only. This trap is generated only when the informational exception control page is set to turn on the TEST bit.
This is an informational message. No action is needed.
This trap is generated by HP S.M.A.R.T.-enabled physical drives when they detect performance degradation that could result in critical failures in the future.
This is a warning that the drive is not functioning well. It may fail in the future. Backup immediately. Run diagnostic on the drive. If the drive fails the diagnostic test then replace it. If the drive was part of the fault-tolerant logical drive, then replace and rebuild it. If the drive was part of the non fault-tolerant drive then restore the original RAID configuration from a file or reconfigure the logical drive(s). Re-partition the drive. Reinstall the operating system if necessary. Restore data from backup tape.
Whenever any I/O operation on a physical drive results in a CHECK CONDITION status, the REQUEST SENSE operation is performed, and this trap notifies the Sense Key, Additional Sense Code and Additional Sense Code Qualifier are notified using this trap. One should refer to SCSI Specification/Drive User Manual to interpret the cause of the failure.
The check condition indicates an abnormal end to an operation on the SCSI channel. It could be due to the drive or controller, or possibly due to a problem with the physical connection (e.g., cables or storage cabinet).
This trap is supported only for SAF-TE compliant enclosures. Any physical insertion of a hard disk will generate this trap. If the auto rebuild feature is enabled, then a rebuild automatically start if applicable.
This is an informational message. No action is needed.
This trap is generated if the battery backup module (the small daughter board on top of the NetRAID adapter) is missing, not seated properly, or the battery cable is improperly connected. A 3-wire pigtail with a connector comes out of the battery pack for connection to the battery module board. Be sure that the battery is plugged into the card.
If this message persists, there may be risk of losing the cache memory contents in the event of a power failure.
This trap is generated if the voltage of the battery backup module is below operational limit. The battery is automatically charged in such a situation.
Allow sufficient time for the battery to fully charge. Refer to the NetRAID User Guide for charging times.
If this battery condition persists after a long charging period, the battery pack may be faulty and should be replaced.
This trap is generated if the temperature of the battery pack is outside its operating range. The battery cannot be fast charged until the temperature problem has been corrected.
The warning occurs when the temperature inside the system exceeds the upper limit of 50 degree C (122F). Check the system fans to see if they are working. Replace the battery module if the problem persists.
This trap occurs when the controller software detects a Drive Letter Change event on a container.
The controller generates this event and issues the associated trap when a drive letter is assigned to or removed from a container. A system administrator performs these tasks using a controller management application such as the HP Flexible Array Storage Tool (FAST) or the operating system's storage management utility.
This is an informational message. No action is needed.
This trap occurs when the controller software detects a Spare Disk Change event.
The controller generates this event and issues the associated trap when one or more spare disks are assigned to or removed from a container. A system administrator performs these tasks using a controller management application such as the HP Flexible Array Storage Tool (FAST).
This is an informational message. No action is needed.
This trap occurs when the controller software detects a Container Change event.
The controller generates this event and issues the associated trap when the layout of a container has changed. The following list identifies some typical container change events:
Investigate this event using a controller management application such as the HP Flexible Array Storage Tool (FAST).
This trap occurs when the controller software detects a File System Change event.
The controller generates this event and issues the associated trap when a file system is created on or deleted from a container. A system administrator performs these tasks using a controller management application such as the HP Flexible Array Storage Tool (FAST) or the operating system's storage management utility.
This is an informational message. No action is needed.
This trap occurs when the controller software detects a Container General Error event.
The controller generates this event and issues the associated trap usually when an I/O error occurs on a container.
Verify that the container is still functional. If the container is not functional, check for loose SCSI cables and ensure that the disk device is in good working condition.
This trap occurs when the controller software detects a Container Not Mirroring event.
The controller generates this event and issues the associated trap when a container error occurs because the container is no longer functioning as a mirror set.
Ensure that the mirror set has one or more spare disks assigned to it.
This trap occurs when the controller software detects a Mirror Spare Too Small event.
The controller generates this event and issues the associated trap when a rebuild operation could not start on the container because there was not enough space on any of the spare disks.
Use a controller management application such as the HP Flexible Array Storage Tool (FAST) to assign a new spare disk to the container. Ensure that the spare disk is large enough to be used as rebuild space by the container.
Note: Although all container types accept a spare disk assignment, only mirror set and RAID-5 (redundant) container types use the spare disk assignment if a disk fails.
This trap occurs when the controller software detects an Unmirror Failure event.
The controller generates this event and issues the associated trap when an unmirror operation failed. A system administrator initiates the Unmirror task using a controller management application such as the HP Flexible Array Storage Tool (FAST).
This trap is currently not generated.
This trap occurs when the controller software detects a Mirror Rebuild Start event.
The controller generates this event and issues the associated trap when a rebuild operation is started on a mirror set. This trap is preceded by a Mirror Drive Failure event.
Replace the failed disk as instructed in the preceding Mirror Failure advisory. Optionally, assign a new spare disk to the container. Ensure that the spare disk is large enough to be used as rebuild space by the container.
This trap occurs when the controller software detects a Rebuild Failure event.
The controller generates this event and issues the associated trap when a rebuild operation has failed. Possible causes of this condition include failure of the spare disk, inadequate size of the spare disk, and SCSI connection problems.
Investigate this event using a controller management application such as the HP Flexible Array Storage Tool (FAST).
This trap occurs when the controller software detects a Mirror No Spare Assigned event.
The controller generates this event and issues the associated trap when a mirror rebuild operation failed because there is no spare disk assigned to the container.
Either replace the failed disk or assign a spare disk to the container. Ensure that the new disk or spare disk is large enough to be used as rebuild space by the container.
This trap occurs when the controller software detects a Mirror Drive Failure event.
The controller generates this event and issues the associated trap when a disk in a mirror set fails.
Replace the failed disk immediately. The container is no longer redundant and data loss will occur if the remaining disk fails. Use a controller management application such as the HP Flexible Array Storage Tool (FAST) to determine which disk failed. Replace the failed disk with a new disk of equal or larger capacity and verify that the rebuild process restores the container to a redundant state.
This trap occurs when the controller software detects a RAID-5 Rebuild Start event.
The controller generates this event and issues the associated trap when a rebuild operation is started on a RAID-5 container. This trap is preceded by a RAID-5 Failure event.
Replace the failed disk as instructed in the preceding RAID-5 Drive Failure advisory. Optionally, assign a new spare disk to the container. Ensure that the spare disk is large enough to be used as rebuild space by the container.
This trap occurs when the controller software detects a RAID-5 Rebuild Restart event.
The controller generates this event and issues the associated trap when a previously interrupted rebuild operation is restarted on a RAID-5 container.
This is an informational message. No action is needed.
This trap occurs when the controller software detects a RAID-5 Drive Failure event.
The controller generates this event and issues the associated trap when a disk in a RAID-5 set fails.
Replace the failed disk immediately. The container is no longer redundant and data loss will occur if another disk in the RAID-5 container should fail. Use a controller management application such as the HP Flexible Array Storage Tool (FAST) to determine which disk failed. Replace the failed disk with a new disk of equal or larger capacity and verify that the rebuild process restores the container to a redundant state.
This trap occurs when the controller software detects a RAID-5 No Spare Assigned event.
The controller generates this event and issues the associated trap when a RAID-5 rebuild operation fails because there is no spare disk assigned to the container.
Either replace the failed disk or assign a spare disk to the container. Ensure that the new disk or spare disk is large enough to be used as rebuild space by the container.
This trap occurs when the controller software detects a RAID-5 Spare Too Small event.
The controller generates this event and issues the associated trap when a rebuild operation could not start on the container because there wasn't enough available space on any of the spare disks.
Assign a new spare disk to the container. Ensure that the spare disk is large enough to be used as rebuild space by the container.
Note: Although all container types accept a spare disk assignment, only mirror set and RAID-5 (redundant) container types use the spare disk assignment if a disk fails.
This trap occurs when the controller software detects a Snapshot Almost Full event.
The controller generates this event and issues the associated trap when the backing container of a compact mode snapshot backup is 80% full.
Remove the snapshot container as soon as possible.
This trap occurs when the controller software detects a Snapshot Full event.
The controller generates this event and issues the associated trap when the backing container of a compact mode snapshot backup is 100% full.
Remove the snapshot container as soon as possible. The backing container will no longer be available.
This trap occurs when the controller software detects a RAID-5 Rebuild Done event.
The controller generates this event and issues the associated trap when a rebuild operation has completed on a RAID-5 set.
This is an informational message. No action is needed.
This trap occurs when the controller software detects a Device Failure event.
The controller generates this event and issues the associated trap when a disk fails. Container-related traps are also generated when a disk failure occurs. For example: Mirror Drive Failure. A Container General Error trap will be generated for non-redundant containers that experience a device failure.
Replace the failed disk. If the disk was part of a redundant set, see the accompanying container-related trap. If the disk was part of a non-redundant (example: RAID 0) set, a failed disk means that all data has been lost. Use a controller management application such as the HP Flexible Array Storage Tool (FAST) to:
This trap occurs when the controller software detects a Resume I/O event.
The controller generates this event and issues the associated trap when normal I/O operations have resumed on the controller. A system administrator can pause and resume I/O operations using a controller management application such as the HP Flexible Array Storage Tool (FAST).
This is an informational message. No action is needed.
This trap occurs when the NetRAID controller SNMP interface starts.
Network management applications can use this trap to synchronize with the server that generated the trap.
This is an informational message. No action is needed.
This trap occurs when the controller software detects a Battery Recondition Required event.
The controller generates this event and issues the associated trap when its battery requires reconditioning.
Use a controller management application such as the HP Flexible Array Storage Tool (FAST) to start the battery reconditioning operation on the specified controller.
This trap occurs when the controller software detects an Enclosure Failure event.
The controller generates this event and issues the associated trap when a storage enclosure reports a general failure.
Use a controller management application such as the HP Flexible Array Storage Tool (FAST) to determine which enclosure management device failed.
This trap occurs when the controller software detects an Enclosure Fan Failure event.
The controller generates this event and issues the associated trap when a storage enclosure reports a fan failure.
Use a controller management application such as the HP Flexible Array Storage Tool (FAST) to determine which fan failed. Ensure that nothing is blocking the fan. Replace the fan if it is no longer functional.
This trap occurs when the controller software detects an Enclosure Power Supply Failure event.
The controller generates this event and issues the associated trap when a storage enclosure reports a power supply failure.
Use a controller management application such as the HP Flexible Array Storage Tool (FAST) to determine which power supply failed. Replace the failed power supply if it is no longer functional.
This trap occurs when the controller software detects an Enclosure Bad Temperature event.
The controller generates this event and issues the associated trap when a storage enclosure reports a temperature reading above the manufacturer-defined threshold.
Check the ventilation and cooling requirements in the storage enclosure's manual and ensure that these requirements are met.
This trap occurs when the controller software detects an Enclosure Temperature Over Threshold event.
The controller generates this event and issues the associated trap when a storage enclosure reports a temperature reading above the user-defined threshold. A system administrator can set this threshold using a controller management application such as the HP Flexible Array Storage Tool (FAST).
Check the ventilation and cooling requirements in the storage enclosure's manual and ensure that these requirements are met. You may want to raise the user settable threshold or increase the cooling of the enclosure.
This trap occurs when the controller software detects a Battery Dead event.
The controller generates this event and issues the associated trap when a previously good battery loses all charge, is missing, or is broken.
Contact technical support. The controller's battery is not functioning properly.
This trap occurs when the controller software detects a Battery Improving event.
The controller generates this event and issues the associated trap when a previously dead battery changes to the low improving state.
Use a controller management application such as the HP Flexible Array Storage Tool (FAST) to monitor the state of the controller's battery. Contact technical support if the battery does not return to the Good state within 24 hours.
This trap occurs when the controller software detects a Battery Degrading event.
The controller generates this event and issues the associated trap when a previously good battery changes to the low degrading state.
Use a controller management application such as the HP Flexible Array Storage Tool (FAST) to monitor the state of the controller's battery. Although the battery is still usable, it has degraded. Contact technical support if the battery does not return to the Good state within 24 hours.
This trap occurs when the controller software detects a Battery Good event.
The controller generates this event and issues the associated trap when a previously dead or low battery is charged enough for normal operations.
This is an informational message. No action is needed.
This trap occurs when the controller software detects a Pause I/O event.
The controller generates this event and issues the associated trap when normal I/O operations have been paused on the controller. A system administrator can pause and resume I/O operations using a controller management application such as the HP Flexible Array Storage Tool (FAST).
This is an informational message. No action is needed.
This trap occurs when the controller software detects a Container Created event.
The controller generates this event and issues the associated trap when a container is created. A system administrator performs this task using a controller management application such as the HP Flexible Array Storage Tool (FAST).
This is an informational message. No action is needed.
This trap occurs when the controller software detects a Container Deleted event.
The controller generates this event and issues the associated trap when a container is deleted. A system administrator performs this task using a container management application such as the HP Flexible Array Storage Tool (FAST).
This is an informational message. No action is needed.
This trap occurs when the controller software detects a Failure Predicted event.
The controller generates this event and issues the associated trap when a device reports that a failure prediction threshold was exceeded. This is an indication that the device may soon fail.
Replace the device as soon as possible.
This trap occurs when the controller software detects a Device Test Done event.
The controller generates this event and issues the associated trap when a device reports that its failure prediction threshold reporting mechanism was tested. This event is usually operator initiated.
This is an informational message. No action is needed.
This trap occurs when the controller software detects a Device Warning event.
The controller generates this event and issues the associated trap when a device reports a warning. This is an indication that the device may soon fail.
Replace the device as soon as possible.
This trap occurs when the controller software detects a Device Temperature Warning event.
The controller generates this event and issues the associated trap when a device reports a temperature reading above the manufacturer-defined threshold. This is an indication that the device may soon fail or that it is too hot.
Check the ventilation and cooling requirements in the storage enclosure's manual and ensure that these requirements are met. If no problems are found with the ventilation and cooling, then replace the device.
This trap occurs when the controller software detects a Device Degraded event.
The controller generates this event and issues the associated trap when a device reports that its status has degraded. This is an indication that the device may soon fail.
Replace the device as soon as possible.
This trap occurs when the controller software detects a Failure Prediction Change event.
The controller generates this event and issues the associated trap when a device reports that its failure prediction method has been reconfigured. A system administrator performs these tasks using a controller management application such as the HP Flexible Array Storage Tool (FAST).
This is an informational message. No action is needed.