troubleshooting Question
Hyper-V clustering - VMs rebooting after node failure
I have a 2-node Hyper-V R2 cluster.
Today, I had all the VMs running on node1, so I could do maintenance on node2. As I was doing some upgrades on node 2, the server BSOD'd and rebooted.
Right after this happened, all the clusted VMs that were running on node 1 rebooted themselves.
After checking the logs, it appears that they lost their storage momentarily, that I think that's what caused them to reboot.
Afterwards, I noticed that the quorom disk was shown to be failed. It was being hosted on Node2. I had to manually reconnect the iSCSI LUN then I was able to bring it online.
My question is why did a node failure of Node 2 cause all clustered VMs on node 1 to reboot?
Here's one of the event log entries. There was one for each VM:
The Virtual Machines configuration ED2F9165-5316-4856-8C50-F9
Then each machine has an entry like this:
'Virtual Machine Configuration Server1' successfully registered the configuration for the virtual machine.
'Virtual Machine Server1' successfully started the virtual machine.
I also noticed that the quorom disk for the cluster was/is hosted by Node2.
Today, I had all the VMs running on node1, so I could do maintenance on node2. As I was doing some upgrades on node 2, the server BSOD'd and rebooted.
Right after this happened, all the clusted VMs that were running on node 1 rebooted themselves.
After checking the logs, it appears that they lost their storage momentarily, that I think that's what caused them to reboot.
Afterwards, I noticed that the quorom disk was shown to be failed. It was being hosted on Node2. I had to manually reconnect the iSCSI LUN then I was able to bring it online.
My question is why did a node failure of Node 2 cause all clustered VMs on node 1 to reboot?
Here's one of the event log entries. There was one for each VM:
The Virtual Machines configuration ED2F9165-5316-4856-8C50-F9
Then each machine has an entry like this:
'Virtual Machine Configuration Server1' successfully registered the configuration for the virtual machine.
'Virtual Machine Server1' successfully started the virtual machine.
I also noticed that the quorom disk for the cluster was/is hosted by Node2.
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 4 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.