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.

HP P2000 G3 MSA System Event Descriptions Reference Guide 11
78
Warning The controller could not use an assigned spare for a vdisk because the spare’s capacity is too small. This
occurs when a vdisk’s status becomes critical and all global spares are too small or (if the dynamic spares
feature is enabled) all disks are too small.
Recommended actions
•Replace existing spares or add spares with enough capacity to replace the smallest disk in the vdisk.
The vdisk size is limited by its disk with the least capacity.
79
Info. A trust operation has completed for the indicated vdisk. Be sure to complete the trust procedure as
documented for the trust command in the CLI reference guide.
Recommended actions
•No action required.
80
Info. The controller enabled or disabled the indicated parameters for one or more disks.
Recommended actions
•No action required.
81
Info. The current controller has unkilled the partner controller. The other controller will restart.
Recommended actions
•No action required.
83
Info. The partner controller is changing state (shutting down or restarting).
Recommended actions
•No action required.
84
Warning The current controller has forced the partner controller to fail over.
Recommended actions
•See Resources for diagnosing and resolving problems on page 3.
86
Info. Host-port or disk-channel parameters have been changed.
Recommended actions
•No action required.
87
Warning The mirrored configuration retrieved by this controller from the partner controller has a bad cyclic
redundancy check (CRC). The local flash configuration will be used instead.
Recommended actions
•Restore the default configuration by using the restore defaults command, as described in the CLI
reference guide.

12
88
Warning The mirrored configuration retrieved by this controller from the partner controller is corrupt. The local flash
configuration will be used instead.
Recommended actions
•Restore the default configuration by using the restore defaults command, as described in the CLI
reference guide.
89
Warning The mirrored configuration retrieved by this controller from the partner controller has a configuration level
that is too high for the firmware in this controller to process. The local flash configuration will be used
instead.
Recommended actions
•The current controller probably has down-level firmware. Update the firmware on the down-level
controller. Both controllers should have the same firmware versions.
When the problem is fixed, event 20 is logged.
90
Info. The partner controller does not have a mirrored configuration image for the current controller, so the current
controller’s local flash configuration is being used. This event is expected if the other controller is new or its
configuration has been changed.
Recommended actions
•No action required.
91
Error In a testing environment, the diagnostic that checks hardware reset signals between controllers in
Active-Active mode failed.
Recommended actions
•Perform failure analysis.
95
Error Both controllers in an Active-Active configuration have the same serial number. Non-unique serial numbers
can cause system problems; for example, vdisk ownership and WWNs are determined by serial number.
Recommended actions
•Replace one of the controller modules.
96
Info. Pending configuration changes that take effect at startup were ignored because customer data might be
present in cache.
Recommended actions
•If the requested configuration changes did not occur, make the changes again and then use a
user-interface command to shut down or restart the controller.
100
Info. During Active-Active operation, an event (potential error) occurred while communicating with the enclosure
management processor (EMP).
Recommended actions
•No action required.

HP P2000 G3 MSA System Event Descriptions Reference Guide 13
101
Info. An update of enclosure management processor (EMP) data has been triggered.
Recommended actions
•No action required.
103
Info. The name has been changed for the indicated volume.
Recommended actions
•No action required.
104
Info. The size has been changed for the indicated volume.
Recommended actions
•No action required.
105
Info. The LUN (logical unit number) has been changed for the indicated volume.
Recommended actions
•No action required.
106
Info. The indicated volume has been added to the indicated vdisk.
Recommended actions
•No action required.
107
Error The controller experienced the indicated error. In a single-controller configuration, the controller will restart
automatically. In an Active-Active configuration, the surviving controller will kill the controller that
experienced the error.
Recommended actions
•See Resources for diagnosing and resolving problems on page 3.
108
Info. The indicated volume has been deleted from the indicated vdisk.
Recommended actions
•No action required.
109
Info. The statistics for the indicated volume have been reset.
Recommended actions
•No action required.
11 0
Info. Ownership of the indicated vdisk has been given to the other controller.
Recommended actions
•No action required.

14
111
Info. The link for the indicated host port is up. This event indicates that a problem reported by event 112 is
resolved. For a system with FC ports, this event also appears after loop initialization.
Recommended actions
•No action required.
112
Warning The link for the indicated host port has unexpectedly gone down.
Recommended actions
•Look for corresponding event 111 and monitor excessive transitions indicating a host-connectivity or
switch problem. If more than 8 transitions occur per hour, see Resources for diagnosing and resolving
problems on page 3.
112
Info. The link for the indicated host port has gone down because the controller is starting up.
Recommended actions
•No action required.
114
Info. The link for the indicated disk channel port is down. Note that events 114 and 211 are logged whenever a
user-requested rescan occurs and do not indicate an error.
Recommended actions
•Look for corresponding event 211 and monitor excessive transitions indicating disk problems. If more
than 8 transitions occur per hour, see Resources for diagnosing and resolving problems on page 3.
116
Error After a recovery, the partner controller was killed while mirroring write-back data to the current controller.
The current controller restarted to avoid losing the data in the partner controller’s cache, but if the other
controller does not restart successfully, the data will be lost.
Recommended actions
•To determine if data might have been lost, check whether this event was immediately followed by restart
event 56, closely followed by failover event 71 (specifying p1=1).
118
Info. Cache parameters have been changed for the indicated volume.
Recommended actions
•No action required.
127
Warning The controller has detected an invalid disk dual-port connection. This event indicates that a controller host
port is connected to an expansion port, instead of to a port on a host or a switch.
Recommended actions
•Disconnect the host port and expansion port from each other and connect them to the proper devices.
136
Warning Errors detected on the indicated disk channel have caused the controller to mark the channel as degraded.
Recommended actions
•Determine the source of the errors on the indicated disk channel and replace the faulty hardware.
When the problem is fixed, event 189 is logged.

HP P2000 G3 MSA System Event Descriptions Reference Guide 15
139
Info. The Management Controller (MC) has powered up or restarted.
Recommended actions
•No action required.
140
Info. The Management Controller (MC) is about to restart.
Recommended actions
•No action required.
141
Info. The IP address has been changed in the Management Controller (MC), which normally occurs during
power up or failover recovery.
Recommended actions
•No action required.
152
Warning The Management Controller (MC) has not sent a command to the Storage Controller (SC) for 15 minutes
and may have failed.
This event is initially logged as Informational, as described below. If the problem persists, this event is
logged a second time as Warning and the MC is automatically restarted in an attempt to recover from the
problem. Event 156 is then logged.
Recommended actions
•If the controller that is logging this event can communicate with the MC, monitor the error trend. If the
error occurs more than twice per hour, see Resources for diagnosing and resolving problems on
page 3.
•If the controller that is logging this event cannot communicate with the MC within 25 minutes, replace
the controller module.
Info. The Management Controller (MC) has not sent a command to the Storage Controller (SC) for 160 seconds.
If communication is restored in less than 15 minutes, event 153 is logged. If the problem persists, this event
is logged a second time as Warning, as described above.
Recommended actions
•If the controller that is logging this event can communicate with the MC, monitor the error trend. If the
error occurs more than twice per hour, see Resources for diagnosing and resolving problems on
page 3.
•If the controller that is logging this event cannot communicate with the MC within 25 minutes, replace
the controller module.
153
Info. The Management Controller (MC) has re-established communication with the Storage Controller (SC).
Recommended actions
•No action required.
154
Info. New firmware has been loaded on the Management Controller (MC).
Recommended actions
•No action required.

16
155
Info. New loader firmware has been loaded on the Management Controller (MC).
Recommended actions
•No action required.
156
Warning The Management Controller (MC) has been restarted from the Storage Controller (SC) for the purpose of
error recovery.
Recommended actions
•If this event occurs more than twice per hour, see Resources for diagnosing and resolving problems on
page 3.
Info. The Management Controller (MC) has been restarted from the Storage Controller (SC) in a normal case,
such as when initiated by a user.
Recommended actions
•No action required.
157
Error A failure occurred when trying to write to the Storage Controller (SC) flash chip.
Recommended actions
•Replace the controller module.
158
Info. A correctable ECC error occurred in the CPU memory.
Recommended actions
•No action required.
161
Info. One or more enclosures do not have a valid path to an enclosure management processor (EMP). All
enclosure EMPs are disabled.
Recommended actions
•See Resources for diagnosing and resolving problems on page 3.
162
Warning The host WWNs (node and port) previously presented by this controller module are unknown. In a
dual-controller system this event has two possible causes:
•One or both controller modules have been replaced or moved while the system was powered off.
•One or both controller modules have had their flash configuration cleared (this is where the previously
used WWNs are stored).
The controller module recovers from this situation by generating a WWN based on its own serial number.
Recommended actions
•If the controller was replaced or someone reprogrammed its FRU ID data, verify the WWN information
for this controller module on all hosts that access it.

HP P2000 G3 MSA System Event Descriptions Reference Guide 17
163
Warning The host WWNs (node and port) previously presented by the partner controller module, which is currently
offline, are unknown.
This event has two possible causes:
•The online controller module reporting the event was replaced or moved while the system was powered
off.
•The online controller module had its flash configuration (where previously used WWNs are stored)
cleared.
The online controller module recovers from this situation by generating a WWN based on its own serial
number for the other controller module.
Recommended actions
•If the controller was replaced or someone reprogrammed its FRU ID data, verify the WWN information
for the other controller module on all hosts that access it.
166
Warning The RAID metadata level of the two controllers does not match. Usually, the controller at the higher
firmware level can read metadata written by a controller at a lower firmware level. The reverse is typically
not true. Therefore, if the controller at the higher firmware level failed, the surviving controller at the lower
firmware level cannot read the metadata on disks that have failed over.
Recommended actions
•If this occurs after a firmware update, it indicates that the metadata format changed, which is rare.
Update the controller with the lower firmware level to match the firmware level on the other controller.
167
Warning A diagnostic test at controller bootup detected an abnormal operation, which might require a power cycle
to correct.
Recommended actions
•See Resources for diagnosing and resolving problems on page 3.
168
Error The indicated SES alert condition was detected in the indicated enclosure. This event is logged as Error
when one of the power supplies in an enclosure has no power supplied to it or when a hardware failure is
detected.
Recommended actions
•Most voltage and temperature errors and warnings relate to the power supply module; see Table 2 on
page 44. If there is no problem with the power source, the indicated FRU has probably failed and
should be replaced.
When the problem is fixed, event 169 is logged.
Warning The indicated SES alert condition was detected in the indicated enclosure.
Recommended actions
•Most voltage and temperature errors and warnings relate to the power supply module; see Table 2 on
page 44.
When the problem is resolved, event 169 is logged.
Info. The indicated SES alert condition was detected in the indicated enclosure.
Recommended actions
•Most voltage and temperature errors and warnings relate to the power supply module; see Table 2 on
page 44.

18
169
Info. The indicated SES alert condition has been cleared in the indicated enclosure. This event is generated
when the problem that caused event 168 is cleared.
Recommended actions
•No action required.
170
Info. The last rescan indicates that the indicated enclosure was added to the system.
Recommended actions
•No action required.
171
Info. The last rescan indicates that the indicated enclosure was removed from the system.
Recommended actions
•No action required.
172
Warning The indicated vdisk has been quarantined because not all of its disks are available. There are not enough
disks to be fault tolerant. The partial vdisk will be held in quarantine until it becomes fault tolerant.
Recommended actions
•Ensure that all disks are latched into their slots and have power.
•During quarantine, the vdisk is not visible to the host. If after latching disks into their slots and powering
up the vdisk, the vdisk is still quarantined, you can manually remove the vdisk from quarantine so that
the host can see the vdisk. The vdisk is still critical.
•If disks have failed, replace them.
When the vdisk has been removed from quarantine, event 173 is logged.
173
Info. The indicated vdisk has been removed from quarantine.
Recommended actions
•No action required.
174
Info. Enclosure or disk firmware update has succeeded, been aborted by a user, or failed.
Recommended actions
•No action required.
175
Info. An Ethernet link has changed status (up/down).
Recommended actions
•Monitor the error trend. If this event occurs more than 8 times per hour, see Resources for diagnosing
and resolving problems on page 3.
•If the controller that is logging this event cannot communicate with the MC within 25 minutes, replace
the controller module.
176
Info. The error statistics for the indicated disk have been reset.
Recommended actions
•No action required.

HP P2000 G3 MSA System Event Descriptions Reference Guide 19
177
Info. Cache data was purged for the indicated missing volume.
Recommended actions
•No action required.
181
Info. Controller network port parameters have been changed.
Recommended actions
•No action required.
182
Info. All disk channels have been paused. I/O will not be performed on the disks until all channels are
unpaused.
Recommended actions
•If this event occurs in relation to disk firmware update, no action is required. When the condition is
cleared, event 183 is logged.
•If this event occurs and you are not performing disk firmware update, see Resources for diagnosing and
resolving problems on page 3.
183
Info. All disk channels have been unpaused, meaning that I/O can resume. An unpause initiates a rescan,
which when complete is logged as event 19.
This event indicates that a problem reported by event 182 is resolved.
Recommended actions
•No action required.
185
Info. An enclosure management processor (EMP) write command has completed.
Recommended actions
•No action required.
186
Info. Enclosure parameters have been changed by a user.
Recommended actions
•No action required.
187
Info. The write-back cache has been enabled.
Recommended actions
•Look for event 188.
188
Info. Write-back cache has been disabled.
Recommended actions
•If event 187 is not logged within a reasonable amount of time, see Resources for diagnosing and
resolving problems on page 3.

20
189
Info. A disk channel that was previously degraded or failed is now healthy.
Recommended actions
•No action required.
190–201
Info. Includes component-specific environmental indicator events generated by the auto-write-through feature
when an environmental change occurs. If an auto-write-through trigger condition has been met, write-back
cache is disabled and event 188 is also logged. Once the fault is resolved, event 187 is logged to indicate
that write-back mode has been restored.
Recommended actions
•If a positive event is not logged within a reasonable period after a negative event, see Resources for
diagnosing and resolving problems on page 3. For example, if event 198 is not soon followed by event
199, the PSU might require service.
202
Info. An auto-write-through trigger condition has been cleared, causing write-back cache to be re-enabled. The
environmental change is also logged. (See events 191, 193, 195, 199, 201, and 241.)
Recommended actions
•No action required.
203
Warning An environmental change occurred that allows write-back cache to be enabled, but the auto-write-back
preference is not set.
The environmental change is also logged. (See events 190–200.)
Recommended actions
•Manually enable write-back cache.
204
Error This event is generated by the hardware flush firmware whenever the boot processing firmware needs to
inform the user about something.
Recommended actions
•See Resources for diagnosing and resolving problems on page 3.
Warning This event is generated by the hardware flush firmware whenever the boot processing firmware needs to
inform the user about something.
Recommended actions
•See Resources for diagnosing and resolving problems on page 3.
Info. This event is generated by the hardware flush firmware whenever the boot processing firmware needs to
inform the user about something.
Recommended actions
•No action required.
205
Info. The indicated volume has been mapped or unmapped.
Recommended actions
•No action required.