Mount Points in Windows 2012 R2 Cluster not displaying correctly

Question

Hi,
Try
and I might, I can't get Mount Points displayed properly in a Windows 2012 R2 cluster.
In Windows 2008 R2, I added them, and they appear under Storage, as for Example, Cluster Disk 7: Mounted Volume (S:\SYSDB). (I may have had to bring them offline/online).
in Windows 2012 R2, they are showing up as, for example, '\\?\Volume{7c636157-e7e9-11e4-80dc0005056873123}'
In the error log it shows up as :
Cluster disk resource 'Cluster Disk 7' contains an invalid mount point. Both the source and target disks associated with the mount point must be clustered disks, and must be members of the same group.
Mount point 'SYSDB\' for volume '\\?\Volume{7c636106-e7e9-11e4-80dc-005056873123}\' references an invalid target disk. Please ensure that the target disk is also a clustered disk and in the same group as the source disk (hosting the mount point).
Now I've checked the error, and in
https://technet.microsoft.com/en-au/library/dd353925(v=ws.10).aspx it says
"The mounted disk and the disk it is mounted onto must be part of the same clustered service or application. They cannot be in two different clustered services or applications, and they cannot be in the general pool of Available Storage in the cluster."
So I have created a 'Other Server' Role. When I go right click on the Role and go to 'Add Storage', Cluster Disk 6 (the root volume) displays S:\, and Cluster Disk 9 (hosting the mountpoint) says Mount Point(s): (S:\SYSDB). I select both, and add, but
alas, the Mount Point still shows up as '\\?\Volume{7c636106-e7e9-11e4-80dc-005056873123}\ (not S:\SYSDB or Cluster Disk 6: Mounted Volume (S:\SYSDB).) as I would expect.
They are both clustered disks (iSCSI). I would expect when it says in the "same group", both added to the same role would be in the same group.

Answer 1

Hi,
Thankyou for your response. That's (sort of) good to know, but it seems to be a step backwards from Windows 2008 R2, where you would actually have the meaningful Mounted Volume: (S:\SYSDB) displayed, to the meaningless '\\?\Volume{7c636157-e7e9-11e4-80dc0005056873123}'
GUID. Obviously before you do anything, you need to cross reference the disk number to 'Disk Management'; it would be better if is was displayed correctly in Failover Cluster Manager in the first place.
Secondly, the GUID is somewhat misleading. In Windows 2008 R2 for example, it appears as though the same GUID was displayed on each node (e.g. using Mountvol.exe). In Windows 2012 R2, it appears as though different GUID's are displayed on each node, e.g.
Node 1.
\\?\Volume{7c6368a4-e7e9-11e4-80dc-005056873123}\
        S:\SYSDB\
Node 2.
\\?\Volume{97cc0d34-e7e9-11e4-80db-0050568724c4}\
        S:\SYSDB\
But the GUID in Failover cluster manager remains the same (you can't really cross reference with what you see in FCM to Mountvol).
Strangely enough, when I check the registry in 'MountedDevices' on Node 1, both of the GUIDs are displayed (even though only one is displayed in MountVol.exe),  referencing the same Disk ID listed in Diskpart.exe. I can see this mentioned in
https://support.microsoft.com/en-us/kb/959573, where is says :
A volume can be multiple unique volume names (and thus multiple GUIDs) when it is used by multiple running installations of Windows.  This could happen in the following scenarios and in similar scenarios where multiple installations of Windows have
accessed the volume:
Using a volume on a shared disk in a cluster where multiple nodes have accessed the volume.
Oh well, that's progress I guess.