IBM ServeRAID-4 Ultra160 Series, User Reference

Page: 175 / 208

Problem Action
RAID level-5 logical drives cannot be
accessed by the operating system after a
failover. Use the ServeRAID Manager program to check the state of the
logical drive to ensure that it is not blocked. Using this program,
select the logical drive and look for Blocked state Yes. If the logical
drive is blocked, make sure all physical drives that are part of the
logical drive are in the online state. If all physical drives are not in the
online state, a drive might have failed during one of the following
situations:
v
A failover
v
A resynchronization process after a failover
Data integrity cannot be guaranteed in this case and the logical drive
has been blocked to prevent the possibility of incorrect data being
read from the logical drive.
Unblock, reinitialize, and synchronize the logical drive and restore the
data from a backup source. Depending on the type of data contained
on the logical drive and the availability of a recent backup copy, you
can do one of the following:
v
Unblock the drive and continue normal operation.
v
Replace and rebuild one or more defunct drives.
However, if you do not reinitialize, synchronize, and restore the drive,
be aware that some data could be lost or damaged.
If one of the cluster servers fails and the
surviving server takes over the cluster
resources, occasionally one or more of the IP
address resources will stay in the online
pending state for several minutes after moving
over to the surviving server. After this, the
resource will go to the Failed state and the
following error message will be displayed in
the surviving server system log (as viewed
with the Event Viewer).
For example, the Windows NT Event Log
Message:
Date: ??? Event ID: 1069
Time: ??? Source: ClusSvc
User: N/A Type: Error
Computer: ??? Category: (4)
Description:
Cluster resource 'ip address resource
name' failed
Do the following:
1. Using the right mouse button, click the IP resource in the Cluster
Administrator.
2. From the General tab, select Properties.
3. Check the box labeled Run this resource in a separate
Resource Monitor. A message appears stating that the resource
must be restarted for the change to take effect.
Note: Placing IPSHA disk resources into their own Resource Monitor
can decrease failover time.
Chapter 18. Solving ServeRAID problems
157