Specifications

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . .
3-44 Diagnostic Tools
Identify controller data did not match with CMOS
The identify controller data from the array controller did not match with the information
stored in nonvolatile RAM. This could occur if new, previously configured drives have
been placed in a system that has also been previously configured. This situation could also
occur if the firmware on the controller has been upgraded and the System Configuration
Utility was not run.
Check the identify controller data under the Inspect Utility. If the firmware version field is
the only thing different between the controller and nonvolatile RAM data, this is not a
problem. Otherwise run the System Configuration Utility.
Identify logical drive data did not match with CMOS
The identify unit data from the array controller did not match with the information stored in
nonvolatile RAM. This could occur if new, previously configured drives have been placed
in a system that has also been previously configured.
Run the System Configuration Utility to configure the controller and
nonvolatile RAM.
Insufficient adapter resources
The adapter does not have sufficient resources to perform operations to the array
accelerator board. Drive rebuild may be occurring.
Operate the system without the array accelerator board until the drive rebuild completes.
Less than 75% batteries at sufficient voltage
The operation of the array accelerator board has been disabled due to less than 75% of the
battery packs being at the sufficient voltage level.
Allow sufficient time for the batteries to recharge (36 hours). If the batteries have not
recharged after 36 hours, replace the array accelerator board.
Logical drive X failed due to cache error
This logical drive failed due to a catastrophic cache error.
Replace the array accelerator board and re-configure using the System
Configuration Utility.