Question : Hyper-V Core 2008R2 Cluster Issues with volumes

Hi all,
I am having a problem with an EqualLogic PS6000XV and a Hyper-V core failover cluster with two hosts. I need to add a few pass-through disks to a couple of VM's. The way to add them is:
- configure the LUN on the SAN
- connect the iSCSI initiators to the volume on both physical hosts.
- using disk manager on hosts make sure the volumes are offline
- Failover Cluster manager - add disk to storage then "Move this resource" to the VM
- within the VM go to disk manager, create simple volume, format
Problem: it happened twice that one of the volumes got de-assigned from the VM and appeared as "available storage: in Failover Cluster Mgr. SCVMM complained that VM was not OK, not HA.
For some reason all other volumes/LUNs appear in FCM as "\\?\GLOBALROOT\device" but this specific one appears as \\?\Volume{3dcd6971-e863-11de-90b5-001018588e26}. If I turn  on maintenance for it, it appears as \\?\GLOBALROOT too but when I turn maintenance off it goes back to \\?\Volume{3dcd6971-e863-11de-90b5-... One more difference is that for all the other LUN's, FCM sees File System: Unknown and for this one it see File System: NTFS and the correct size (see pic)

Does anyone know why this is happening and if it's related to my de-attachment problem. How can I change that \\?\Volume ID to consistently show \\?\GLOBALROOT?

Many, many thanks for your help.
iSee (not quite this time..)

Answer : Hyper-V Core 2008R2 Cluster Issues with volumes

I destroyed the cluster again and re-created it and now all drives are OK. The problem is solved but  I dont know why, I did nothing differently compared to last time so a mistery. Pretty sure it's a Microsoft issue, not hardware or SAN issue. I'll consider this closed and update if I discover more but now I need to put those things into production. Cheers!