Decarn
asked on
Clustering: Unable to failover to another node.
Hi,
I have a Exchange serer on Windows 2003 and I'm not able to failover to another node.
The Event ID is: 1034.
The disk associated with cluster disk resource 'Disk Q:' could not be found. The expected signature of the disk was "". If the disk was removed from the server cluster, the resource should be deleted. If the disk was replaced, the resource must be deleted and created again in order to bring the disk online. If the disk has not been removed or replaced, it may be inaccessible at this time because it is reserved by another server cluster node.
It is not only Disk Q but all other data disks as well. Also, it's strange that there is no disk signature in the log.
In addition to finding the solution, I'm trying to replicate the problem using VMWare workstation. I have successfully set up clustering between two nodes and need advice on the next step.
Thanks.
I have a Exchange serer on Windows 2003 and I'm not able to failover to another node.
The Event ID is: 1034.
The disk associated with cluster disk resource 'Disk Q:' could not be found. The expected signature of the disk was "". If the disk was removed from the server cluster, the resource should be deleted. If the disk was replaced, the resource must be deleted and created again in order to bring the disk online. If the disk has not been removed or replaced, it may be inaccessible at this time because it is reserved by another server cluster node.
It is not only Disk Q but all other data disks as well. Also, it's strange that there is no disk signature in the log.
In addition to finding the solution, I'm trying to replicate the problem using VMWare workstation. I have successfully set up clustering between two nodes and need advice on the next step.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
You were right. The affected node is not able to see any disk drives. The HBA logs did not show any lost connection and the storage seem to be working fine. Any ideas how it could have happen or where else to check?