HP XP RAID Manager Software User Manual
Page 53
Causes and solutions
Problem
Solutions:
•
Add pool-VOLs to another pool.
•
Initialize the V-VOL management area.
•
Check pool-VOLs requirements. For more information, see
.
Causes:
You cannot create the SS pairs.
•
There are not enough differential tables to create the pairs.
•
The conditions to create the pair are not fulfilled.
•
The volumes that are specified to create the pair are in “SMPL (PD)” status and are in
the process of being deleted.
Solutions:
•
Secure enough differential tables to create the pairs.
•
Fulfill the conditions to create the pair and try the pair creation again.
•
In the BC/SS Pair Operation window, verify that the status of the volume changes to
SMPL, and then try the pair creation again.
•
Using the RAID Manager, do the following:
1. Run the inqraid command.
2. Verify that SS is not using the volume.
3. Create the pair.
Causes:
SS pairs are not shown in the volume
list.
•
The pairs are not created.
•
The filtering function is prohibiting you from showing the pairs.
Solutions:
•
Create the pairs.
•
Open the Display Filter dialog box and change the settings.
Cause: A volume is blocked because a failure occurred in the hard disk drive.
An error occurred while restoring
the pair.
Solution: Delete the pair that is blocked, and contact HP Technical Support.
Causes:
A volume is blocked.
•
A failure occurred in two or more hard disk drives.
•
The breaker was turned off and then the power was restored.
Solution: Contact the HP Technical Support for assistance.
Cause: Access to the volume is rejected.
A problem occurred with the
software application on the host
Solution:
server that is monitoring the volumes
of SS pairs.
1.
On the host server, stop the monitoring software application.
2.
Change all pair statuses to “PSUS”.
3.
On the host server, start the monitoring software application.
To check whether the host has access to pair volumes, view the P-VOL/S-VOL access columns.
For more information about the pair status definitions, see
“Pair status definitions” (page 44)
.
Cause: Access to the volume is rejected.
A V-VOL cannot be recognized
correctly after you boot or reboot the Solution:
host server or after you run the
1.
On the host server, stop the monitoring software application.
command for recognizing the device
or V-VOL on the host server.
2.
Change all pair statuses to “PSUS”.
3.
Do one of the following:
• Reboot the host server.
• Run the command for recognizing the device or V-VOL on the hose server.
4.
On the host server, start the monitoring software application.
General troubleshooting
53