4 error situations and solutions – Avago Technologies Syncro CS 9286-8e User Manual
Page 75
Avago Technologies
- 75 -
Syncro CS 9286-8e Solution User Guide
November 2014
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.
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
.
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
.
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.
In Windows clustered environments, I/O
stops on the remote client when both
SAS cable connections from one
controller node are severed. The
clustered shared volumes appear in
offline state even when both cables have
been reconnected.
Behavior outlined in Microsoft
Knowledge Base article 2842111 might
be encountered.
1.
Reconnect the severed SAS cables.
2. Open
Failover Cluster Manager > Storage > Disk >
Cluster Disk to check the status of the cluster.
3.
If the disks are online, you can restart your client
application.
If the disks are not online, right click on Disks > Refresh
and bring them online manually. If the disks do not go
online through manual methods, reboot the server
node.
4.
Restart the Server Role associated with the disks.
5.
Apply hotfix for Microsoft Knowledge Base article
2842111 to both server nodes.