I'm building a SQL Server 2000 cluster on Server 2003 R2 Ent.
I'm pretty far into this build and I would hate to start from scratch if I don't need to. The cluster works well with the basic cluster services and the cluster disk (Q:). Everything fails over fine and all event logs and the cluster logs are clear of errors. I start having problems when I add physical disk resources and new groups into the cluster service. I've added three physical disks for SQL Server use to node 1. I also added the same disks to node 2...just with node 1 disconnected from the SAN. So both servers have access to all three volumes. With node 2 disconnected ...I've opened cluster admin on node 1 and added the disks to the cluster in a new group called SQL Server. I've also configured MSDTC on node 1 with an additional physical disk (M:). Once created I brought all new disk resources on line. So...from node 1 I have access to all disks required. This includes the Q: drive, M: drive, and three for SQL server use. The cluster groups are setup with the appropriate resources in each group.
The problem comes in when I turn on Node 2. This node cannot access the Q: or M: drives...storage manager shows unreadable volumes but no drive letters in either storage manager or windows explorer. This is expected since the cluster service is reserving the drives. The three volumes created for SQL though do show up with drive letters on node 2...and they are labeled as online. Even though Node 1 has these volumes mounted and the cluster server shows them as online. I have 2 of the 5 drives working great. Any ideas? EqualLogic support suggests starting from scratch and ensuring the persistent drives registry key is added prior to setting up the cluster. I really don't want to start from scratch...I'm close but can't seem to figure out why these three drives are not behaving.