Owners Manual
Table Of Contents
- Dell EMC PowerVault ME4 Series Storage System Owner’s Manual
- Contents
- Storage system hardware
- Troubleshooting and problem solving
- Module removal and replacement
- ESD precautions
- Dealing with hardware faults
- Firmware updates
- Continuous operation during replacement
- Shutting down attached hosts
- Shutting down a controller module
- Verifying component failure
- Customer-replaceable units (CRUs)
- Attach or remove the front bezel of a 2U enclosure
- Replacing a drive carrier module in a 2U enclosure
- Replacing a DDIC in a 5U enclosure
- Replacing a controller module or IOM in a 2U or 5U enclosure
- Replacing a power supply unit (PSU) in a 5U enclosure
- Replacing a fan cooling module (FCM) in a 5U enclosure
- Replacing a power cooling module (PCM) in a 2U enclosure
- Completing the component installation process
- Verifying component operation
- Performing updates in PowerVault Manager after replacing an FC or SAS HBA
- Events and event messages
- Connecting to the CLI port using a serial cable
- Technical specifications
- Standards and regulations
Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
● No action is required.
190 Info. The controller module's supercapacitor pack has started charging.
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
191 is logged to indicate that write-back mode has been restored.
Recommended actions:
● If event 191 is not logged within 5 minutes after this event, the supercapacitor has probably
failed and the controller module should be replaced.
191 Info. The auto-write-through trigger event that caused event 190 to be logged has been resolved.
Recommended actions:
● No action is required.
192 Info. The controller module's temperature has exceeded the normal operating range.
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
193 is logged to indicate that write-back mode has been restored.
Recommended actions:
● If event 193 has not been logged since this event was logged, the over-temperature
condition probably still exists and should be investigated. Another over-temperature event
was probably logged at approximately the same time as this event (such as event 39, 40,
168, 307, 469, 476, or 477). See the recommended actions for that event.
193 Info. The auto-write-through trigger event that caused event 192 to be logged has been resolved.
Recommended actions:
● No action is required.
194 Info. The Storage Controller in the partner controller module is not up.
This indicates that a trigger condition has occurred that has caused the auto-write-through
feature to disable write-back cache and put the system in write-through mode. When the fault is
resolved, event 195 is logged to indicate that write-back mode has been restored.
Recommended actions:
● If event 195 has not been logged since this event was logged, the other Storage Controller
is probably still down and the cause should be investigated. Other events were probably
logged at approximately the same time as this event. See the recommended actions for
those events.
195 Info. The auto-write-through trigger event that caused event 194 to be logged has been resolved.
Recommended actions:
● No action is required.
198 Info. A power supply has failed.
This indicates that a trigger condition has occurred that has caused the auto-write-through
feature to disable write-back cache and put the system in write-through mode. When the fault is
resolved, event 199 is logged to indicate that write-back mode has been restored.
Recommended actions:
● If event 199 has not been logged since this event was logged, the power supply probably
does not have a health of OK and the cause should be investigated. Another power-supply
event was probably logged at approximately the same time as this event (such as event 168).
See the recommended actions for that event.
199 Info. The auto-write-through trigger event that caused event 198 to be logged has been resolved.
Recommended actions:
● No action is required.
Events and event messages 91