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

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 ?

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.

-Jared

"delacom" wrote:

> 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 ?
>

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.

"jaredhattaway" wrote:

> 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.
>
> -Jared
>
> "delacom" wrote:
>
> > 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 ?
> >