If your environment recently had an outage (or shutdown unexpectedly or ungracefully), or had snapshots for whatever reason (eg. testing, and making alot of changes), then there’s a small chance that your vmdk file could corrupt or go missing after shutdown. This is a rare occasion, however it could happen.
Your VM might be running fine after the outage, but you havent had to shutdown or restart the VM for months, until you really need to. This is where you find that your VM will not turn on. In this case your descriptor file is missing or corrupted.
The solution to this problem is:
Review the above article and you will be alright.
NOTE: Ensure that you don’t overwrite the -flat.vmdk file otherwise you will lose all your data and you will need to perform a full restore.
Hope this helps!
Image may be NSFW.
Clik here to view.
Image may be NSFW.Clik here to view.
