vmdk file showing 0MB on ESXi 5.5U3

[vickyshiv123]

Hi Guys,

I am wondering, could anyone please help on the below issue

Our customer CRMDB VM (windows server 2008r2)has two virtual hard disk (C-80GB, D-100GB), C drive with 80GB vmdk is on one separate datastore, this is working fine VM  and also VM is up & running

The issue now is the D-drive with 100GB on separate data store was suddenly showing 0MB on the Edit settings of the VM, then we removed from the VM and tried to add new virtual hard disk using existing hard disk on the datastore, it wasn't able to read the existing vmdk file but the vmdk file is there on the datastore

Much appreciate your prompt advise on further troubleshooting

Please find the attached file for your reference

Thanks in advance

Vick

[a_p_]

Without digging deeper (e.g. analyzing log files), it's hard to say what could be causing this issue.

With the virtual disk in question being thin provisioned, can you confirm that the datastore didn't run out of disk space?

Did you check the VM's vmware*.log files to see whether they contain any hints?

Anyway, it may be a good idea to open a support case with VMware asap.

André

[JinuV]

Since flat file is exist you can recover the VM. You need to recreate the disk descriptor ,refer the below link

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100251...

[vickyshiv123]

Hi Guys,

Manage to recover the VM, by the changing CBT (ctkenabled=false) on the configuration parameters and also on the VM configuration file(.vmx)

Thanks

Vignesh

[bhanupratapk]

you can even try out the thrid party tools available like test disk from the following link

TestDisk - Partition Recovery and File Undelete

Regards,

Pratap Koonisetty.

[continuum]

Obviously you dont ever used Testdisk in VMware context before - your suggestion will not help at all and is rather misguiding in this case.
Please dont post tips like that !
For the record: Testdisk is a very good tool - in vSphere-context it may be used to fix damaged vmdks in the following case:
- vmdk-descriptor exists
- flat-vmdk exists
- VM config is ok and VM is starting fine
- guestOS does not boot - or one of the data-vmdks is unreadable
Using Testdisk is not useful when:
- used against a VMFS-volume
- a VM does not start at all because of a vmdk-misconfiguration/error

@OP

Please attach the latest vmware.logs
That will help to create a new descriptor and probably also tells us what went wrong.
I would guess that the datastore is filled up.
Can you run
vmkfstools -p 0 flat.vmdk > /tmp/mapping.txt
That cmd may tell us if the flat.vmdk itself is also damaged.