Finding and correcting the cause of the problem, Inding, Orrecting – Promise Technology 2-Year Extended Warranty for VessR2000 RAID Head User Manual
Page 654: Ause, Roblem
627
Product Manual
f
inding
And
c
Orrecting
the
c
Ause
Of
the
P
rObleM
External Checks
Make the following external checks to your Vess subsystem. Be sure that:
• Both RAID controllers are present, fully inserted into their slots, and locked into place.
• The RAID controllers match, meaning both are the same model
• All SAS expansion cables from the RAID controllers to external
JBOD units in good condition and are securely connected.
Internal Checks
If all external checks are OK, take the following actions:
1. Shut down the Vess.
See
“Shutting Down the Subsystem” on page 110.
2. Remove one of the RAID controllers.
See
“Replacing a RAID Controller – Dual Controllers” on page 544.
3. Restart the Vess.
4. After the Vess is fully booted, view the controller information.
“Viewing Controller Information” on page 112.
5. Observe and record the following information about the first controller:
• SDRAM memory size
• Hardware version
• Firmware version
6. Shut down the Vess.
7. Remove the first controller and install the second controller.
8. Repeat steps 3 through 6. Then compare your records.
9. Correct any differences between the two controllers. See “Updating Firmware on a RAID Subsystem” on
Important
A disconnected SAS expansion cable causes the two RAID con-trollers to see
a different set of configured drives. This condition is the most common cause
of a controller entering maintenance mode.