Add a node to a Hyper-V Failover Cluster - Disk issues

[delacom]

We have a Hyper-V Failover cluster running. The Virutal machines are
configured on .VHD files, which are mounted on Mountpoints. For this we
followed following article:
http://support.microsoft.com/default...b;EN-US;947021
Now we added a node to the cluster. All fine. But when we move over a
Hyper-V machine to the new node, the disk is there, but ofcourse the mout
point is not correct. When I try to change the mountpoint, i get following
error:
Logical Disk Manager - The parameter is incorrect.
I can mount the disk on a drive letter, but not on a mount point...
We are running on the Windows 2008 RTM version.
Any idea on how to proceed ?

[jaredhattaway]

We ran into the same issue setting up our cluster.

We are delivering attached storage via iSCSI (Not sure what you are using)

We resolved the issue by first initializing each disk in identical mount
points on each node, then taking the mount point offline.

We found that this had to be done before adding the storage to the cluster
otherwise the system fails to initialize the disk during the failover process.

Hope this helps.

[delacom]

Thank you for this answer. We are using a HP SAN over Fiber connection.
But we are talking about an existing cluster here, on which we are adding a
node.
So we are not able to initialise first... The storage is already added to
the cluster...

What you describe is exactly what we did when seting up the cluster, or when
adding a new Virtual server (and disk) to the cluster.

[anjak]

Hi delacom,

I'm having exact the same problem after setting op a new node I can't figure out how to mount the disks as they already is reserved by the cluster on the existing nodes.

Did you find a solution to you problem?

[Connect_Me]

Here is some quick steps which you can try. First ensure that your third node is compatible with the Windows server and Hyper-V. Then connect the same. After first thing update your bios for the the most recent version for more stability. Now configure the settings for bios for the third node. Setup the operating system in the node and ensure that you had install the same edition of Windows server. Change the name of the node and reboot everything. Then configure all desktop, whatever you want. Configure Windows update and install hyper-v.

[anjak]

Okay I finally found a solution that works for me but it requires a lot off manual work :(

This is the steps to go through to bring cluster shared volumes mounted to mount points online on the new cluster node:

Open iSCSI Initiator
-Logon on to all the available Targets
Open Explorer
-Create MountPoint Folders matching those on the old nodes
Open Failover Cluster Management MMC on the new node
-Run Validate a Configuration
-In the Action Menu select Add Node.. and add the new server
Make all the iSCSI Disks “Cluster Aware on the new node”
-In the Failover Cluster Management Storage window bring the disk you want
to a to this server in to Maintenance Mode. The disk then changes from
Reserved to Online on the old cluster nodes.
-Also in the Failover Cluster Management Storage window the present mount
point location is displayed – take a note off this.
-Now to find the disk number to bring online go into the iSCSI Initiator
Properties, find the target for the disk and click details -> Devices ->
Advanced and take a note off the number.
-In the Disk Management window bring the disk online and click
Change Drive Letter and Paths to match the mount point path from
another node.
-Finally turn Maintenance mode off on the disk in the Failover Cluster
Management Storage window and the disk is ready :)