HP StorageWorks P2000 User manual

HP P2000 G3 MSA System
Event Descriptions Reference Guide
Part number: 591224-004
First edition: May 2011

Legal and notice information
© Copyright 2011 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor’s standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgements
Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.
UNIX is a registered trademark of The Open Group.

HP P2000 G3 MSA System Event Descriptions Reference Guide 3
Introduction
This guide is for reference by storage administrators to help troubleshoot storage-system issues. It describes
event messages that may be reported during system operation and specifies any actions recommended in
response to an event.
Events and event messages
When an event occurs in a storage system, an event message is recorded in the system’s event log
and—depending on the system’s event notification settings—may also be sent to users (via email) and
host-based applications (via SNMP or SMI-S).
Each event has a numeric code that identifies the type of event that occurred, and has one of the following
severities:
•Critical. A failure occurred that may cause a controller to shut down. Correct the problem immediately.
•Error. A failure occurred that may affect data integrity or system stability. Correct the problem as soon
as possible.
•Warning. A problem occurred that may affect system stability but not data integrity. Evaluate the
problem and correct it if necessary.
•Informational. A configuration or state change occurred, or a problem occurred that the system
corrected. No immediate action is required. In this guide, this severity is abbreviated as “Info.”
An event message may specify an associated error code or reason code. Error codes and reason codes
are outside the scope of this guide.
Event format in this guide
This guide lists events by event code and severity, where the most severe form of an event is described first.
Events are listed in the following format. Events that do not apply to P2000 G3 MSA System products are
not listed.
Resources for diagnosing and resolving problems
For further information about diagnosing and resolving problems, see:
•The troubleshooting chapter and the LED descriptions appendix in your product’s user guide
•The topic about verifying component failure in the component’s replacement instructions document
These and other HP documents can be found
on the Software Support/Documentation CD shipped with your
product or at http://www.hp.com/support/manuals.
For links to additional information about your product, see
http://www.hp.com/go/p2000 or http://www.hp.com/go/msa. For product support and to download drivers
and software, see
http://www.hp.com/support.
For a summary of storage events and corresponding SMI-S indications, see Events sent as indications to
SMI-S clients on page 45.
Event code
Severity Event description.
Recommended actions
•If the event indicates a problem, actions to take to resolve the problem.

4
Event descriptions
1
Warning Either:
•The indicated non-RAID-6 vdisk is operating with degraded health due to the failure of one disk.
•The indicated RAID-6 vdisk is operating with degraded health due to the failure of two disks.
The vdisk is online but cannot tolerate another disk failure.
If a dedicated spare or global spare of the proper size and type is present, that spare is used to
automatically reconstruct the vdisk. If an assigned spare is not present, but an available disk of the proper
type and size is present and the dynamic spares feature is enabled, that disk is used to automatically
reconstruct the vdisk.
Recommended actions
•If no spare is present and the dynamic spares feature is disabled, replace the failed disk and use SMU
to add the new disk as a dedicated spare for the vdisk. That spare is used to automatically reconstruct
the critical vdisk.
•Replace the failed disk for future use.
•If the replacement disk was previously used in another vdisk and has status LEFTOVR, use SMU to
clear the disk’s metadata so you can assign the disk as a spare for the critical vdisk or for future use.
•See also Table 1 on page 42.
3
Error The indicated vdisk went offline. Either one disk failed for RAID 0 or NRAID; three disks failed for RAID 6;
or two disks failed for other levels. The vdisk cannot be reconstructed.
Recommended actions
•Use the trust command as described in the CLI reference guide.
4
Info. The indicated disk had an uncorrectable error and the controller reassigned the indicated block.
Recommended actions
•Monitor the error trend and whether the number of errors approaches the total number of bad-block
replacements available.
6
Warning Vdisk creation failed during initialization.
Recommended actions
•In SMU’s System Overview panel, compare the vdisk count with the configuration limit for the maximum
number of vdisks.
• If you reached this limit, either purchase additional storage or removed unneeded vdisks.
• If you have not reached the limit, see Resources for diagnosing and resolving problems on page 3.
Info. Vdisk creation either immediately failed, was canceled by the user, or succeeded.
Recommended actions
•No action required.
7
Error In a testing environment, a controller diagnostic failed and reports a product-specific diagnostic code.
Recommended actions
•Perform failure analysis.

HP P2000 G3 MSA System Event Descriptions Reference Guide 5
8
Warning The indicated disk in the indicated vdisk failed and the vdisk changed to a critical or offline state. If a
spare is present the controller automatically uses the spare to reconstruct the vdisk. Subsequent events
indicate the changes which happen to the vdisk.
Recommended actions
•See Table 1 on page 42.
When the problem is resolved, event 9 is logged.
9
Info. The indicated spare disk has been used in the indicated critical vdisk to bring it back to a fault-tolerant
state. Vdisk reconstruction starts automatically.
This event indicates that a problem reported by event 8 is resolved.
Recommended actions
•No action required.
16
Info. The indicated disk has been designated a global spare.
Recommended actions
•No action required.
18
Warning Vdisk reconstruction failed.
Recommended actions
•Determine whether the reconstruction failed due to a disk problem and whether replacing that disk will
enable reconstruction to start and complete without further errors.
Info. Vdisk reconstruction succeeded.
Recommended actions
•No action required.
19
Info. A rescan has completed.
Recommended actions
•No action required.
20
Info. Storage Controller firmware update has completed.
Recommended actions
•No action required.
21
Warning Vdisk verification failed during the verification process.
Recommended actions
•See Resources for diagnosing and resolving problems on page 3.
Info. Vdisk verification failed immediately, was aborted by a user, or succeeded.
Recommended actions
•No action required.

6
23
Info. Vdisk creation has started.
Recommended actions
•No action required.
25
Info. The statistics for the indicated vdisk have been reset.
Recommended actions
•No action required.
27
Info. Cache parameters have been changed for the indicated vdisk.
Recommended actions
•No action required.
28
Info. Controller parameters have been changed. This event is logged when general configuration changes are
made; for example, utility priority, remote notification settings, user interface passwords, and management
port IP values. This event is not logged when changes are made to vdisk or volume configuration.
Recommended actions
•No action required.
31
Info. The indicated disk is no longer a global or dedicated spare.
Recommended actions
•No action required.
32
Info. Vdisk verification has started.
Recommended actions
•No action required.
33
Info. Controller time/date has been changed. This event is logged before the change happens so the event
timestamp shows the “old” time. (May appear often if NTP is enabled.)
Recommended actions
•No action required.
34
Info. Controller has been restored to factory defaults.
Recommended actions
•For an FC controller, restart it to make the default loop ID take effect.
37
Info. Vdisk reconstruction has started.
Recommended actions
•No action required. When complete, event 18 is logged.

HP P2000 G3 MSA System Event Descriptions Reference Guide 7
39
Warning The sensors monitored a temperature or voltage in the warning range.
Recommended actions
•Check that the storage system’s fans are running.
•Check that the ambient temperature is not too warm. The enclosure operating range is 41–104°F
(5–40°C).
•Check for any obstructions to the airflow.
•If none of the above explanations apply, replace the controller FRU that reported the error.
When the problem is fixed, event 47 is logged.
40
Error The sensors monitored a temperature or voltage in the failure range.
Recommended actions
•Check that the storage system’s fans are running.
•Check that the ambient temperature is not too warm. The enclosure operating range is 41–104°F
(5–40°C).
•Check for any obstructions to the airflow.
•If none of the above explanations apply, replace the controller FRU that reported the error.
When the problem is fixed, event 47 is logged.
41
Info. The indicated disk has been designated a spare for the indicated vdisk.
Recommended actions
•No action required.
43
Info. The indicated vdisk has been deleted.
Recommended actions
•No action required.
44
Warning The controller contains cache data for the indicated volume but the corresponding vdisk is not online.
Recommended actions
•Determine the reason that the disks are not online.
•If an enclosure is down, determine corrective action.
•If the vdisk is no longer needed, you can clear the orphan data; this will result in lost data.
•If the volume is missing and was not intentionally removed, see Resources for diagnosing and resolving
problems on page 3.
45
Info. A communication failure has occurred between the controller and an enclosure management processor
(EMP).
Recommended actions
•No action required.

8
47
Info. An error detected by the sensors has been cleared. This event indicates that a problem reported by event
39 or 40 is resolved.
Recommended actions
•No action required.
48
Info. The indicated vdisk has been renamed.
Recommended actions
•No action required.
49
Info. A lengthy SCSI maintenance command has completed. Output indicates whether it completed successfully
or a failure occurred. (Typically appears after disk firmware update.)
Recommended actions
•No action required.
50
Info. A correctable ECC error occurred in buffer memory.
Recommended actions
•No action required.
51
Error An uncorrectable ECC error occurred in buffer memory.
Recommended actions
•If this event occurs only once, no action is required.
•If the event occurs more than once, replace the controller reporting the event.
52
Info. Vdisk expansion has started.
Recommended actions
•This operation can take days to complete. When complete, event 53 is logged.
53
Info. Vdisk expansion either completed, failed, or was aborted by a user.
Recommended actions
•If the expansion failed because of a disk problem: replace the disk; if vdisk reconstruction starts, wait
for it to complete; and then retry the expansion.
55
Warning A SMART event occurred on the indicated disk, indicating impending disk failure.
Recommended actions
•See Table 1 on page 42.
56
Info. A controller has powered up or restarted.
Recommended actions
•No action required.

HP P2000 G3 MSA System Event Descriptions Reference Guide 9
58
Warning A disk drive or enclosure management processor (EMP) detected a serious error, such as a parity error or
disk hardware failure.
Recommended actions
•If the event indicates that a disk or an expansion module is bad, replace the indicated device.
Info. A disk drive or enclosure management processor (EMP) detected a non-serious error.
Recommended actions
•No action required.
59
Warning The controller detected a parity error while communicating with the indicated SCSI device. The error was
detected by the controller, not the disk.
Recommended actions
•If the event indicates that a disk or an expansion module is bad, replace the indicated device.
Info. The controller detected a non-parity error while communicating with the indicated SCSI device. The error
was detected by the controller, not the disk.
Recommended actions
•No action required.
60
Info. A disk channel was reset from another initiator or target.
Recommended actions
•No action required.
61
Error The controller reset the indicated disk channel to recover from a communication error. This event is logged
to identify an error trend over time.
Recommended actions
•If the controller recovers, no action is required.
•View other logged events to determine other action to take.
62
Warning The indicated global or dedicated spare disk has failed.
Recommended actions
•Replace the failed disk.
65
Error An uncorrectable ECC error occurred on the buffer memory on startup. The controller is automatically
restarted and its cache data is restored from the partner controller’s cache.
Recommended actions
•Replace the controller module.
67
Info. The controller has identified a new disk or group of disks that constitute a vdisk and has taken ownership
of the vdisk. This can happen when disks containing data have been inserted from another enclosure. This
event only applies to non-Active-Active controllers.
Recommended actions
•You may need to clear the disks’ metadata if you want to reuse them in one or more new vdisks.

10
68
Info. The controller that logged this event is shut down, or both controllers are shut down.
Recommended actions
•No action required.
71
Info. The controller has started or completed failing over.
Recommended actions
•No action required.
72
Info. After failover, recovery has either started or completed.
Recommended actions
•No action required.
73
Info. The two controllers are communicating with each other and cache redundancy is enabled.
Recommended actions
•No action required.
74
Info. The FC loop ID for the indicated vdisk was changed to be consistent with the IDs of other vdisks. This can
occur when disks containing a vdisk are inserted from an enclosure having a different FC loop ID.
This event is also logged by the new owning controller after vdisk ownership is changed.
Recommended actions
•No action required.
75
Info. The indicated volume’s LUN has been unassigned because it conflicts with LUNs assigned to other
volumes. This can happen when disks containing data for a mapped volume have been inserted from
another enclosure.
Recommended actions
•If you want hosts to access the volume data on the inserted disks, map the volume with a different LUN.
76
Info. The controller is using default configuration settings. This event occurs on the first power up, and might
occur after a firmware update.
Recommended actions
•If you have just performed a firmware update and your system requires special configuration settings,
you must make those configuration changes before your system will operate as before.
77
Info. The cache was initialized as a result of power up or failover.
Recommended actions
•No action required.