System information

Troubleshooting
6-6
5. Hard disk shows Conflict state
The Conflict state indicates that the hard disk contains valid RAID configurations but the controller cannot work with such
configurations.
If the conflict is because the cache unit size of the controller is bigger than the stripe size of the logical disk on the hard
disks, you can change the cache unit size (see 2.7.16 Miscellaneous on page 2-37) and restart the system to
accommodate the logical disk. The cache management algorithm requires that the cache unit size has to be equal to or
smaller than the stripe size of any logical disks managed by the RAID controller.
The conflict might also be because there has been a disk group with the same disk group ID of the hard disks. You can
use Array Roaming Utilities (see 2.7.12 Array roaming on page 2-35) to import the hard disks to form a disk group with
a new disk group ID.
Other configuration conflicts might be caused incompatible firmware version. You’re required to erase the configuration
information on the hard disks for your RAID system to use the hard disks. Or, contact your system supplier for solutions.
6. Disk group enters degraded mode.
Make sure that there are member disks available. Use the Array Recovery Utility to restore the disks to the degraded disk
group (see 2.7.13 Array recovery on page 2-35).
7. Faulty logical disks or volumes cannot be recovered
You are required to recover a disk group before recovering its logical disks. And similarly, to recover a volume, you’re
required to recover its logical disks.
6.7 Redundant Controller and MPIO
1. The replacement controller stops boot-up with LCD messages
When a replacement controller is online installed to the RAID system, the two controllers will synchronize with each other.
If there is configuration conflict discovered (see Section 5.2), the replacement controller will stop boot-up. The beeper
alerts, and the LCD shows the following messages:
(A) CONTR MOD UNEQ: the two controllers are of different model
(B) DB UNEQ: the two controllers have different daughter board
(C) PLD VERS UNEQ: the two controllers have different PLD version
(D) MEM SZ UNEQ: the two controllers install memory of different size
(E) BBM INSTL UNEQ: one controller has BBM, while the other has no BBM
(F) DISK NR UNEQ: The detected disk numbers are not same of both controller.
(G) EXPAN NR UNEQ WILL BE RE-TEST: The detected expansion numbers are not same of both controller.
Below list the resolutions for the configuration conflict.
(A/B/C/F) Contact your RAID system supplier to get the correct controller
(D/E) Install proper memory module and BBM
(G) Check connection is properly between expansions and controllers. Wait boot agent to re-test.
If the conflict configuration can be resolved by overwriting the configuration of the replacement controller, the following
LCD messages will be displayed and waiting for your confirmation by LCD ENT button:
(H) CHK BC VERS: the two controllers have different boot code version
(I) CHK FW VERS: the two controllers have different firmware code version
(J) CHK BBM OPT: the two controllers have different BBM option
(K) CHK ENC SN: the two controllers belong to different enclosures
(L) CHK EXPAN NR: The two controller have different expansion numbers.
(M) CHK DISK NR: The detected disk numbers are not same of both controller.
For (H) and (I), press the ENT button on the LCD to update the boot code and firmware code, respectively, and the
replacement controller will reboot. For (J) and (K), press the ENT button to overwrite the BBM and enclosure serial
number, and the replacement controller will continue boot-up.
For(L), if disply EXPAN NR UNEQ WILL BE RETEST, please check connection is properly between expansions and
controllers. Wait boot agent to re-test. For(M), Please first plug-out and return back controller try again. If still have any
problem please contact supplier get an help.
2. During dual-controller boot-up, the controllers hang with LCD messages
When the two controllers boot up at the same time, negotiation will be performed between the two controllers to choose
one controller as the master controller, and the other controller will follow the configurations of the master controller. The
negotiation cannot be done if there is configuration conflict between the two controllers (see 5.3 Redundant Controller