I have a 6 node Server 2012 Hyper-V cluster. Each node was a fresh install with all local drives formatted and repartitioned during OS install.
The first 5 nodes went great, but the 6th node is causing me some problems.
On the 6th node, Im able to connect to the iSCSI LUNs with no issues. Everything looks great until I add this node to the cluster.
When I add it, the add succeeds, but none of the LUNs are mounted to the c:\ClusterStorage folder correctly.
Instead of showing up in ClusterStorage as a mountpoint for each LUN (6 LUNs in total) they show as folders, and are not accessible. In the Windows Event Logs, for FailoverCluster, Diagnostic it shows the following:
Log Name: Microsoft-Windows-FailoverClustering/Diagnostic
Source: Microsoft-Windows-FailoverClustering
Event ID: 2051
[DCM] failed to set volume mount point, source
\\?\C:\ClusterStorage\Volume4\ target
\\?\Volume{89454e8c-4832-4ad8-a43e-75c4ecab253c}\ error 87
It does this for each of the 6 Luns.
I've tried removing this node from the cluster and reinserting it. Reboots while a member of the cluster, and not the cluster. All Windows updates are applied. Full format and wipe of the server, reinstall of OS and try again, etc. I tried looking on Technet and found some references to this error code but they appeared to be related to driver builds using windows API to use mount points. I haven't written any special drivers or anything unique at all for this cluster. Everything is out of the box Microsoft native drivers.
The server is a Dell PowerEdge R710, same as one of the other nodes in the cluster which is working fine. The other 4 are Dell PE 1950s. The first 5 are working great, its just this sixth one. All 6 servers were reloaded over the course of about a week, using the same checklist, same media, etc. I currently have 72 VMs running on this cluster with 5 nodes, and really looking forward to joining #6.
Anyone have any ideas before I call Microsoft support?
Thanks
Sean Greenbaum