I make a new directory named 172.31.18.143 in /vmfs/volumes/5bcf481f-70bab5a4-9131-c4b8b42ec002/,
[root@lscyy-server1:/vmfs/volumes/5bcf481f-70bab5a4-9131-c4b8b42ec002/172.31.18.143-Centos6.8-HDFS_HBASE(S)_zk] mv * ../172.31.18.143/
mv: can't rename '172.31.18.143-Centos6.8-HDFS_HBASE(S)_zk.vmx~': No such file or directory
mv: can't rename 'vmware.log': No such file or directory
The output means all the normal files are moved successfully, except the unnormal files like '172.31.18.143-Centos6.8-HDFS_HBASE(S)_zk.vmx~'
In in other words, the new directory '172.31.18.143' can be used to register VM.
Then I unregister the stopped unnormal VM, and register it from the vmx file in new directory '172.31.18.143', the new VM starts successfuly.
This problem occur due to the the power failed, when I try to start the VM, got this error:
And I check the VM directory, there's no someting like "xxxx.vmk~"
Then I ssh to the ESXi server, run find / -name "*~", I do get this:
I don't konw why there's no such file, but the server says "The file already exists"?
How can I fix this?
i will be appreciated if anyone could give me some help!
the find command you are using will not show you "~" files, e.g.temporary files. You need to use this: find / -name "*~" -ls
after you've found the file, delete it.
You should be able to start VM after that.
Let's go to a debug mode then.
Create a new VM with the same configuration as your CentOS 6.8 and try to power on. Let's see if it can get up and running. No need to install any OS there.
Run this command to check which host is holding a lock on the .vmx file
vmkfstools -D filename.vmx
You will get something like this as output
Lock [type 10c00001 offset 216614912 v 16442, hb offset 3883008
gen 127, mode 2, owner 00000000-00000000-0000-000000000000 mtime 31256807
num 2 gblnum 0 gblgen 0 gblbrk 0]
RO Owner HB Offset 3883008 5c65b98b-f3e2a3ec-8d91-0894ef010738 <== This is the mac of the owner
Addr <4, 486, 89>, gen 14270, links 1, type reg, flags 0, uid 0, gid 0, mode 600
len 483183820800, nb 460800 tbz 0, cow 0, newSinceEpoch 460800, zla 4304, bs 1048576
Once found the above you can either reboot the ESXi host or check any other which might also be a culprit.