HP MSA Events Description Reference Guide (762785-001, March 2014)

Event descriptions 35
236
Error A special shutdown operation has started. These special shutdown types indicate an incompatible feature.
Recommended actions
Replace the indicated controller module with one that supports the indicated feature.
Info. A special shutdown operation has started. These special shutdown types are used as part of the
firmware-update process.
Recommended actions
No action is required.
237
Info. A firmware update has started and is in progress. This event provides details of the steps in a
firmware-update operation that may be of interest if you have problems updating firmware.
Recommended actions
No action is required.
238
Warning An attempt to install a licensed feature failed due to an invalid license.
Recommended actions
Check the license for what is allowed for the platform, make corrections as appropriate, and reinstall.
239
Warning A timeout occurred while flushing the CompactFlash.
Recommended actions
Restart the Storage Controller that logged this event.
If this event is logged again, shut down the Storage Controller and replace the controller module.
240
Warning A failure occurred while flushing the CompactFlash.
Recommended actions
Restart the Storage Controller that logged this event.
If this event is logged again, shut down the Storage Controller and replace the controller module.
241
Info. The auto-write-through trigger event that caused event 242 to be logged has been resolved.
Recommended actions
No action is required.
242
Error The controller module's CompactFlash card has failed.
This change met a condition to trigger the auto-write-through feature, which has disabled write-back
cache and put the system in write-through mode. When the fault is resolved, event 241 is logged to
indicate that write-back mode has been restored.
Recommended actions
If event 241 has not been logged since this event was logged, the CompactFlash probably does not
have health of OK and the cause should be investigated. Another CompactFlash event was probably
logged at approximately the same time as this event (such as event 239, 240, or 481); see the
recommended actions for that event.