Doing some investigate why the Windows 2008 R2 Server was not responding I discovered the vmdk file had disappeared. This happened while I was at work. The file was located in a directory on a FREENAS iSCSI volume which I am able to browse to using the Datastore Browser. All the other files seem to be there. I've attached the last log file.
Any help would be greatly appreciated.
Please check this KB:
You need to browse Datastore from Command line into the Host, should be able to see the flat vmdk, please let me know if you can see it.
Can you explain me with more details what happened? how did you found the incident? some previous task? please, if you can, share your .vmx file
on the other hand, this was a test with another disk?
OPEN scsi0:1 '/vmfs/volumes/50a47359-c3e7d514-3f5d-001e68c5c1d8/New Virtual Machine/New Virtual Machine_1.vmdk' persistent
The missing flat.vmdk was stored on a VMFS formatted iSCSI LUN ?
Can you create a new VM that can attach that LUN - either via RDM or with a iSCSI-client running in a guest ?
If yes - I have several procedures for that scenarion but no time to explain details here.
If the vmdk is important give me teamviewer access and I can check myself.
Does anyone else other than you have access to delete files on a datastore?
I believe you cannot delete a VMDK file that's in use. We experimented with this a while back when looking at detecting and removing orphaned VMDK files and couldn't delete a VMDK if it was registered to a VM and powered on.
So if the VMDK file was deleted, to me suggests the VM was powered down, the file deleted, and the VM powered back on. Events in vCenter may not reflect this if someone logged in directly to an ESX/ESXi host and performed these operations via the command line.
But I believe the events should show up on the ESX/ESXi host itself if you login directly to it with a vSphere Client and check its local set of events/tasks?
> I believe you cannot delete a VMDK file that's in use.
ESXi itself can loose vmdks all by itself - even when ESXi can not see the files they may still be visible to vmfs-fuse
Create a new VM with same OS (you need not install the os here, just create) as the vm for which the vmdk is missing with exactly same hard disk size. Now a new vmdk will be created. Copy this vmdk to the missing place (datastore). power on now.