Hi there,
@AT10
We can see the temp.vmdk in the datastore browser on two of our three hosts. On the host on which the VM was running we can't see it. But we see the LUN under the device tab of the vSphere client.
The VM had two disk. The temp.vmdk was the second disk. If we try to start the VM with the second disk in the configuration file the VM won't start because of the input/output error. When we delete the second disk from the configuration file the VM starts.
@cjscol
This is the temp.vmdk file:
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=fffffffe
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfs"
# Extent description
RW 3865470568 VMFS "icg4aida-flat.vmdk"
# The Disk Data Base
#DDB
ddb.virtualHWVersion = "7"
ddb.longContentID = "9e796ea9788f3926d0729452fffffffe"
ddb.uuid = "60 00 C2 91 bf 57 74 b4-8d fb be bd e5 ee 49 17"
ddb.geometry.cylinders = "240614"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"
There is no -delta.vmdk file in the directory and no log file. The icg4aida-flat.vmdk has a size of 1.92TB.
I also recreated the temp.vmdk with vmkfstools like it's written in the vmware kb. We wanted to be shure that the original vmdk file had no error. But the recreated file is identical to the original vmdk file.