Setup a Windows Server 2012 Failover Cluster with two hosts and a backend SAS SAN (Dell MD3200 with Dell Dual Port 6Gbps HBAs).
Did a number of tests and failover of VMs from one host to the other worked great in restarting one host or the other. Livemigration and moving storage ownership between the two was working. I was missing a few windows updates on one to have it completely up to date so I did those. Now after restart (and I’ve tried several restarts) the cluster doesn’t come up immediately and it takes about 5 minutes of thinking and trying before it comes up when logged into windows.
Here were the updates done:
Should I just try removing one at a time and seeing which culprit caused the issue? Or is there a better way at handling this so that I can still have the windows updates?
The Critical error in the system log is:
Task Category: Resource Control Manager
The cluster Resource Hosting Subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually associated with recovery of a crashed or deadlocked resource. Please determine which resource and resource DLL is causing the issue and verify it is functioning properly.