In this case.
delete the VM from host and re-register to host again. if it is successful, check for the snapshots and delete it.
. if the above case not resolving the problem, please follow below steps
- Checked for locks using vmkfstools –D on the parent vmdk and showed the mac address of the local host.
- Ran lsof command to see if we could kill the process with the current file lock
- Kill -9 of the process could not be ended as there was a lock that couldn’t be removed.
- Rebooted the host that contained the VM.
- Once the host was rebooted, the VM was still not starting stating it couldn’t open the parent disk vmdk.
- Reviewed the descriptor file for the snapshot disk and parent disk vmdk file and found that the CID in the parent vmdk was not matching what the snapshot vmdk was calling.
- Changed the CID on the parent vmdk to match what was in the snapshot descriptor file and VM powered on.
- VM would not connect to the network as the IP information of the nic were gone.
- Once we were able to login directly to the VM, we were able to set the IP address
- Rebooted the VM and validated all services were started and user could log in with domain credentials
Thanks for share.
It looks like the original storage drive is offline, but still shows up. I'm investigating further and will update this post with the solution once found.
The storage drive is connected to the host via Fibre Channel and the storage is online, but the vSphere can't see the storage itself.