User guide

LSI Corporation
- 47 -
Syncro CS 9286-8e Solution User Guide
March 2013
Chapter 5: Troubleshooting
Error Situations and Solutions
5.4 Error Situations and Solutions
The following table lists some problems that you might encounter in a Syncro CS configuration, along with possible
causes and solutions.
5.5 Event Messages and Error Messages
Each message that appears in the MegaRAID Storage Manager event log has an error level that indicates the severity
of the event, as listed in the following table.
Error Level Meaning
Table 2 Error Situations and Solutions
Problem Possible Cause Solution
A drive is reported as Unsupported, and
the drive cannot be used in a drive
group.
The drive is not a SAS drive, or it does
not support SCSI-3 PR.
Be sure you are using SAS drives that are included on the list
of compatible SAS drives on the LSI web site, or ask your
drive vendor.
One or more of the following error
messages appear after you run the
Microsoft Cluster Validation tool:
 Disk bus type does not support
clustering. Disk partition style is
MBR. Disk partition type is BASIC.
 No disks were found on which to
perform cluster validation tests.
 Two I/O paths are not established
between the controller and drive.
 This build of the Windows
operating system does not natively
support RAID controllers for
clustering.
 Confirm that device ports and all cabling connections
between the controller and drive are correct and are
functioning properly. See Section 5.2, Confirming SAS
Connections.
 Confirm that the version (or the current settings) of the
operating system supports clustered RAID controllers.
When booting a controller node, the
controller reports that it is entering Safe
Mode. After entering Safe Mode, the
controller does not report the presence
of any drives or devices.
 An incompatible peer controller
parameter is detected. The peer
controller is prevented from
entering the HA domain.
 A peer controller is not compatible
with the controller in the HA
domain. Entering Safe Mode
protects the VDs by blocking
access to the controller to allow for
correction of the incompatibility.
 The peer controller might have settings that do not
match the controller. To correct this situation, update
the firmware for the peer controller and the other
controller, or both, to ensure that they are at the same
firmware version.
 The peer controller hardware does not exactly match
the controller. To correct this situation, replace the peer
controller with a unit that matches the controller
hardware.
The LSI management applications do not
present or report the HA options and
properties.
The version of the management
applications might not be HA-
compatible.
Obtain an HA-compatible version of the management
application from the LSI web site, or contact an LSI support
representative.
Drives are not reported in a consistent
manner.
Improper connections might impact the
order in which the drives are discovered.
Make sure you are following the cabling configuration
guidelines listed in Section 2.2, Cabling Configurations.
The management application does not
report a VD or disk group, but the VD or
disk group is visible to the OS.
The shared VD is managed by the peer
controller.
The VD or drive group can be seen and managed on the
other controller node. Log in or to open a terminal on the
other controller node.
Table 3 Event Error Levels
Error Level Meaning
Information Informational message. No user action is necessary.
Warning Some component might be close to a failure point.
Critical A component has failed, but the system has not lost data.
Fatal A component has failed, and data loss has occurred or will occur.