I am experiencing issues joining a 2003 Enterprise R2 cluster node to our production cluster. I have 2 nodes with HBA cards directly attached directly to a Nexsan Sataboy unit with 1 storage controller and two fiber ports. It is an Active/Passive File cluster. Node 1 connects to fiber port 1 on Nexsan. Node 2 connects to fiber port 2. Both existing production nodes are running Server 2003 Enterprise SP2. My goal is to replace/ upgrade each node with a new server (2003 ENT R2 SP2) one at a time:
1 - Evict old node running 2003 Enterprise SP2
2- Join new Node running 2003 Enterprise R2 SP2
I can successfully join new 2003 Enterprise R2 SP2 node to cluster. However, when attempting to move group or fail over to new cluster node, It reverts right back to original cluster node. The system event log displays Error ID 1034:
The disk associated with cluster disk resource 'SATABOY Q:F:' could not be found. The expected signature of the disk was E611A4A1. 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.
I am using exact model of HBA card on new server with updated Driver, FW, and card management utility on new node. I also tried the same scenario with card taken from production node using same firmware, driver and card management version used in production. I still get the same error.
I can revert back to original cluster node and everything works perfectly.
I have tried joining new node to cluster (node 2, 2003 Ent R2 SP2), rebooting node 1 and attempting failover again with same results. As soon as I revert back to original node 2 with 2003 Ent SP2, everything starts working fine.
Nexsan is set to map ports to proper LUN with R/W access.
I did notice a difference in HBA card software between old and new node. Old node sees Nexsan storage device as SCSI3 device. New node with 2003 R2 sees Nexsan as SCSI2 device. HBA drivers and software act as transport only and OS Device negotiation (SCSI2/SCSI3) is between OS and Nexsan.
I have Nexsan looking into issue currently.
No drives have been removed or replaced.
Are there any known issues with joining 2003 Ent R2 to cluster with other nodes running 2003 ENT SP2?
Is there a difference in the ENT 2003 SP2 vs ENT 2003 R2 SP2 OS in how they view SCSI devices?