vMotion Failure

[johanswa]

Hi,

Experiencing a strange issue today, DRS vMotioned a VM to another host and failed. Error was that it was unable to located the VM.vmdk file. It failed the VM back to the original host. VM is still running.

When browsing the datastore via vCenter, VMDK file is missing and it displays the -flat.vmdk file (you dont normally see the -flat.vmdk file via the datastore browser).

When listing the files via command line you do see all the vmdk and -flat.vmdk files.

So why would the files not display via the datastore browser? Is there a way to fix this without recreating the descriptor files, as the descriptor files does actually exist when viewing via command line and you can actually cat the files as well.

[a_p_]

Please create a list of file in the VM's folder (ls -lisa > filelist.txt) and attach the filelist.txt as well as the .vmdk descriptor file to a reply post.

André

[johanswa]

Here you, will this do, didnt want to display my server name in the post.

/vmfs/volumes/4d541799-5572ecda-c163-e61f13e80c03/SERVERNAME # ls -l

-rw-r--r--    1 root     root                 76 Jul 19 08:46 SERVERNAME-89f43530.hlog

-rw-------    1 root     root         2147483648 Jul 11 18:30 SERVERNAME-89f43530.vswp

-rw-------    1 root     root       214748364800 Jul 19 11:39 SERVERNAME-flat.vmdk

-rw-------    1 root     root               8684 Jul 19 08:47 SERVERNAME.nvram

-rw-------    1 root     root                618 Jul 19 08:46 SERVERNAME.vmdk

-rw-r--r--    1 root     root                  0 Jul 11 18:30 SERVERNAME.vmsd

-rwxr-xr-x    1 root     root               3626 Jul 19 08:47 SERVERNAME.vmx

-rw-r--r--    1 root     root               2832 Jul 11 18:43 SERVERNAME.vmxf

-rw-------    1 root     root        32226647040 Jul 19 11:40 SERVERNAME_1-flat.vmdk

-rw-------    1 root     root                618 Jul 19 08:46 SERVERNAME_1.vmdk

-rw-------    1 root     root             130882 Jul 11 18:30 vmware-34.log

-rw-------    1 root     root             158574 Jul 11 18:30 vmware-35.log

-rw-------    1 root     root             122092 Jul 11 18:30 vmware-36.log

-rw-------    1 root     root             103601 Jul 11 18:30 vmware-37.log

-rw-------    1 root     root              96082 Jul 11 18:30 vmware-38.log

-rw-r--r--    1 root     root             227969 Jul 19 11:32 vmware-39.log

-rw-r--r--    1 root     root              48926 Jul 19 08:46 vmware.log

-rw-------    1 root     root           60817408 Jul 11 18:30 vmx-SERVERNAME-2314482992-1.vswp

Descriptor File:

/vmfs/volumes/4d541799-5572ecda-c163-e61f13e80c03/SERVERNAME # cat SERVERNAME.vmdk

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=0b38dd0f

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 419430400 VMFS "SERVERNAME-flat.vmdk"

# The Disk Data Base

#DDB

ddb.deletable = "true"

ddb.virtualHWVersion = "8"

ddb.geometry.biosCylinders = "7834"

ddb.geometry.biosHeads = "255"

ddb.geometry.biosSectors = "63"

ddb.toolsVersion = "8395"

ddb.longContentID = "de1485fae7e08489e604eba50b38dd0f"

ddb.uuid = "60 00 C2 99 61 10 5a 1e-96 f4 6d 12 69 3e 54 d9"

ddb.geometry.cylinders = "26108"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.adapterType = "lsilogic"

[a_p_]

I cannot see anything obvious, except for the sizes of the two .vmdk files being exactly the same!? Please confirm the second .vmdk file doesn't contain any incorrect entries. If it looks ok, the check the .log files to see whether they contain more detailed hints. You may post (please attach using the Advanced Editor) the part of the log file which contains information about the error. No problem with replacing production names and addresses..

André

[johanswa]

Well thats roughly the size of any normal VMDK file is it not, its just a text file at the end of the day?

Logs displayed in vCenter, this is the only logs I can find relating to this issue:

The VM Failed to resume on the destination during early power on.

Reason: The system cannot find the file specified

Cannt open SERVERNAME_1.vmdk or one of the snapshots disks it depends on.

VMware ESX cannot dinf the virtual disk SERVERNAME_1.vmdk. Veryfy the path is valid.

[a_p_]

Basically yes, the sizes are similar, but differ slightly depending on some settings, like the virtual disk size. Does SERVERNAME_1.vmdk pint to SERVERNAME_1-flat.vmdk and contain the disk correct size/geometry information?

André