Hi,
I've got a really simple setup: a two node healthy cluster constisting of SRV1 and SRV2. Current Vote is 1 for SRV1 and 0 for SRV2. To simulate a lost node (and in this case cluster losing quorum) I remove SRV1 from the network. Failover Cluster Manager (FCM) on SRV1 pretty instantly reports the status of the nodes as:
SRV1 - UP
SRV2 - DOWN
Fine. On SRV2 however, nothing happens in FCM for some time. After about a minute, FCM loses contact with the cluster. When I try to reconnect FCM to the local node (SRV2), I get the following error:
Node 'SRV2' is in the process of being started. The remote server has been paused or is in the process of being started.
Waiting does not help - the problem persists. I then resort to PowerShell and "Start-ClusterNode -ForceQuorum". It responds with State=Joining. But the node is never started. Cannot connect to it in FCM. And any other PowerShell command (e.g. Get-ClusterNode) returns "The remote server has been paused or is in the process of being started".
What am I doing wrong? How can I manually force a node to start in a cluster that's lost quorum?
Kindly,
Fredrik