LKBEN11090: VMware ESX: virtual machine does not start after failed failover and there seems to be no leftover process on any server with HA


This article has not been checked!

LKB | Created: 02/04/2020 | Version: 1 | Language: EN | Rating: 0 | Outdated: False | Marked for deletion: False

Author: Wim Peeters - Keskon GmbH & Co. KG

Latest update: 19/09/2020 | Comment:


Symptom

Error message: "Faild to power on on in : Could not power on VM : No swap file."

Cause

The swap file does still exist and is locked from a process trying to start the VM

Solution

In addition to article ID 151:

The machine that wont start left many entries like "faild failover..." - this could be the reason you won't be able to trace down the process, which locks the swap file:
Since HA is enabled, after a failed failover the next host tries to start the VM and so on. You must have a good deal of luck to be on the right server, find and kill the process...

Cause:
After a crash the virtual machine (VM) was left with too many logfiles for ESX (3.5) to handle. Since HA was enabled the trying to failover this machine went on and on...

Solution:
Switch off HA for this VM on all ESX hosts but one. Now you should be able to identify the locking process like detailed in Lubby - Linux Entry ID 151. After this, delete the logfiles off the affected VMs dirctory. Look for additional repair to be done (snapshots etc.).

Now you should be able to power on your VM again.

About the Author

Wim Peeters is electronics engineer with an additional master in IT and over 30 years of experience including time spent in support, development, consulting, training and database administration. Wim has worked with SQL Server since version 6.5. He has developed in C/C++, Java and C# on Windows and Linux in different European countries and different European languages. He writes knowledge base articles to solve IT problems and publishes them on the Lubby Knowledge Platform where he is one of the most important contributors and the main developer.

Disclaimer:

The information provided in this document is intended for your information only. Lubby makes no claims to the validity of this information. Use of this information is at own risk!