Accusys ExaRAID GUI - Manual (Page 253)

Troubleshooting
6-10
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-56) 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-52) 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-53).
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