R/Evolution 2000 Series, Troubleshooting Manual

Page: 81 / 130

Chapter 7 Troubleshooting and Replacing FRUs 81
Table 7-1 lists the faults you might encounter with a controller module or expansion
module.
Table 7-1 Controller Module or Expansion Module Faults
Problem Solution
FRU OK LED is off • Verify that the controller module is properly seated in the slot and
latched.
• Check the RAIDar event log for power-on initialization events and
diagnostic errors.
FRU Fault LED is on • Examine the event log to determine if there is any error event and
take appropriate action.
• Call technical support and send in the log and event files.
• Replace the controller that displayed the fault LED.
Only one controller module
boots In a dual-controller configuration, if a conflict between controllers
exists, only controller module A will boot. For example, if the cache
size is different on the controller modules, controller module B will
not boot.
An SDRAM memory error is
reported • Replace the controller module where the error occurred.
Controller Failure
Event codes 84 and 74 • The controller might need to have its firmware upgraded or be
replaced.
• Check the specific error code to determine the corrective action to
take.
Controller voltage fault • Check the power-and-cooling module and the input voltage.
Controller temperature fault • Check that the enclosure fans are running.
• Check that the ambient temperature is not too warm. See the
site
planning guide
for temperature specifications.
• Check for any obstructions to the airflow.
When the problem is fixed, event 47 is logged.
Memory Error
Event codes 65 and 138 • Contact Technical Support.
• The controller module needs to be replaced.
After the failover to the other controller, Event 72 indicates that
recovery has started or has completed.
Flash write failure
Event code 157 The controller needs to be replaced.
Firmware mismatch
Event code 89 The downlevel controller needs to be upgraded.