Failover Cluster "Failed to get the disk information." from all nodes

Question

Hello all,

Suddenly we started to experience strange behaviour on our Hyper-V Failover cluster.

When I want to do anything with vhdx (from failover console) I get error.
This is when I click "inspect"

Event log from hyper-v host.

All VMs are on SOFS share and I can edit CPU, RAM,Integration services etc. But not disk, cant get info or resize it. And I cannot create new Virtual machine from this host.
We have multiple SOFS roles and problem is identical.

Even more interesting, I can create and delete VM checkpoints in Hyper-V manager but If I click on edit disk in Failover console for same VM I get :

And finally if I connect to host that holds some VM that I want to modify and do powershell:
Get-VHD -Path "\sofs01\Vm.vhdx" <----I can get disk info and resize it but if VM is on another cluster node this will return error "The operation cannot be performed while the object is in use."

Can Anybody help me with this ?

Answer 1

Which type of SOFS did you use?
Scale-Out File Server for application data This clustered file server feature was introduced in Windows Server 2012, and it lets you store server application data, such as Hyper-V virtual machine files, on file shares, and obtain a similar level of reliability, availability, manageability, and high performance that you would expect from a storage area network. All file shares are simultaneously online on all nodes. File shares associated with this type of clustered file server are called scale-out file shares. This is sometimes referred to as active-active. This is the recommended file server type when deploying either Hyper-V over Server Message Block (SMB) or Microsoft SQL Server over SMB.
File Server for general use This is the continuation of the clustered file server that has been supported in Windows Server since the introduction of Failover Clustering. This type of clustered file server, and therefore all the shares associated with the clustered file server, is online on one node at a time. This is sometimes referred to as active-passive or dual-active. File shares associated with this type of clustered file server are called clustered file shares. This is the recommended file server type when deploying information worker scenarios.

At first you could manualy failover before changing sizes. (All (active) servers must be present. One of the active servers should get the "leading" role.

SMB 3.x protocol is load balanced on it's own.
SMB connections always goes into pair's. If one of two goes down SMB itself will try to recreate a twin connection. (MultiChannel)

That said I remember that there 2 ways of management.
Maybe what you try to do cannot be done from VM Cluster manager but From Failover Cluster Manager.

Answer 2

Hello Pero,

Thank you for your question and reaching out.

I can understand you are facing some issue while edit or accessing .vhdx file from Failover cluster manager or from Windows Admin center in SOFS environment.

Please follows below steps towards to resolve this issue.

1. Please disable any Antivirus , Security application or Firewall, as SOFS works on SMB protocol which may blocks or prevents to connections to Hyper-V Nodes.
2. Please run Cluster Validation Wizard and check if there is any warning or errors related to Networking, Disks, Updates , quorum …etc and overall cluster health and in good state.
3. Please try to Power Cycle SOFS where the File shares are hosted and if you are able to edit .vhdx .
4. Please try to disable any Backup Jobs or Task scheduler configured.
5. Please Turn OFF the VM on which the .vhdx is attached and update Integration services then Turn back ON.

Hope this helps your question:)

---

--If the reply is helpful, please Upvote and Accept as answer--

Answer 3

I copied one vhdx from sofs share to C:\ClusterStorage\Volume\test.vhdx and when I try to add it to VM it works normaly and I see permission of VMid is added.

If I try same vhdx from "\SOFS\share" i get error:
Failed to add device 'Virtual Hard Disk'.

The Machine Account 'domain\S2Dhost$' or the user initiating the VM management operation or both do not have the required access to the file share '\Sofs\Cluster\VMs\Test\Virtual Hard Disks\Test.vhdx'. Please ensure that the computer machine account and the user initiating the VM management operation have full access to the file share as well as the file system folder backing the file share. Error: 'General access denied error'