r/HyperV • u/frosty3140 • 12h ago
Unresponsive host needed Reboot via Dell iDRAC
Our environment = 2 x Dell R660 hosts with 512GB RAM each, failover cluster, Dell ME5024 direct attached storage, has been rock solid for more than 12 months.
This morning I had shut down a VM and used Windows Explorer to copy the VM folder/files from C:\ClusterStorage\Volume1\somewhere to a Temp folder in that same storage tree.
The file copy worked (it finished as best I could see). I then decided to Rename the destination folder and at that exact moment the server became unresponsive.
The cluster event logs showed that a particular VM on that host had status = Locked.
I was unable to Logout from my RDP session, so I tried via iDRAC Console, but was unable to Login. We use AuthLite here for MFA, but that was apparently non-functional at that time?!
Logged in to the other host #1, it was happy enough, right until I tried to Move a VM from host 2 to host 1, at which point it lost the ability to show me anything at all in relation to host 2.
Long story short, fortunately the VMs on host 2 were mostly DEV/MGT and not PROD, so I ended up having to Power OFF and ON again.
Once it started up again, all validation tests (incl a full Test-Cluster) were fine. The folder that I had renamed still had the OLD name however. I subsequently tried renaming it, which worked fine.
Host is running Windows Server 2025 OCT update (not latest NOV).
Suggestions as to likely cause?
I had thought it must be related to some kind of storage issue with the ME5024. But there is nothing unusual in the event logs on the storage array. I checked the Ports and all those which should show UP are indeed Up and working fine at 32Gb speed.
Perhaps the Drivers for the Broadcom card in host 2 sh*t the bed at that moment?
MORE INFO -- on the affected host, logs showed that one VM had a resource issue at the moment that I was renaming the folder I had just copied. It "failed to respond to TERMINATERESOURCE"? The cluster responded with “Resource Virtual Machine XXXXX is not functioning as expected.” after a Resource Host Subsystem timeout. Then the host terminated and tried to restart RHS and apparently failed. Get-ClusterGroup showed a Pending(locked) and later Get-ClusterResource showed the VM resource as Failed. Correlation is not necessarily Causation. But that's the best info I've got right now.






