Cannot open the disk 'filename.vmdk' or one of the snapshot disks it depends on. 5 (Input/output error)

[superlizard]

Hi!

I've searched everywhere for an answer to this question but failed to find one, so I hope any of you can help me solve it.

Our server suddenly powered down and when we tried to start a virtual machine we got the following error:

Failed to start the virtual machine.

Module DiskEarly power on failed.

Cannot open the disk '/vmfs/volumes/528d35a1-19d8506c-14b3-6c626dd55891/TURNKEY LAMP/TURNKEY LAMP-000005.vmdk' or one of the snapshot disks it depends on.

5 (Input/output error)

I've attached the latest vmware.log and a screenshot of the directory in the zip-file.

Thanks!

More info:

The server is running VMware ESXi 5.5, 1331820

Cat of TURNKEY LAMP-000005.vmdk

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=445b7b1b

parentCID=445b7b1b

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="TURNKEY LAMP-000001.vmdk"

# Extent description

RW 1048576000 VMFSSPARSE "TURNKEY LAMP-000005-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "b23340ed8bb4fa5e7927ea23445b7b1b"

Cat of TURNKEY LAMP-000001.vmdk

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=445b7b1b

parentCID=2c9270ed

isNativeSnapshot="no"

createType="vmfsSparse"

parentFileNameHint="TURNKEY LAMP.vmdk"

# Extent description

RW 1048576000 VMFSSPARSE "TURNKEY LAMP-000001-delta.vmdk"

# The Disk Data Base

#DDB

ddb.longContentID = "b23340ed8bb4fa5e7927ea23445b7b1b"

And cat of TURNKEY LAMP.vmdk

# Disk DescriptorFile

version=1

encoding="UTF-8"

CID=2c9270ed

parentCID=ffffffff

isNativeSnapshot="no"

createType="vmfs"

# Extent description

RW 1048576000 VMFS "TURNKEY LAMP-flat.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "65270"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "63"

ddb.longContentID = "68fc1974bb9fbc0396661f0c2c9270ed"

ddb.thinProvisioned = "1"

ddb.toolsVersion = "2147483647"

ddb.uuid = "60 00 C2 98 98 56 9a 31-3a a2 7a 93 53 0d bf 13"

ddb.virtualHWVersion = "7"

Cat of TURNKEY LAMP.vmx

encoding = "UTF-8"

config.version = "8"

virtualHW.version = "7"

pciBridge0.present = "TRUE"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge4.functions = "8"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge5.functions = "8"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge6.functions = "8"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

pciBridge7.functions = "8"

vmci0.present = "TRUE"

nvram = "TURNKEY LAMP.nvram"

virtualHW.productCompatibility = "hosted"

powerType.powerOff = "soft"

powerType.powerOn = "hard"

powerType.suspend = "hard"

powerType.reset = "soft"

displayName = "TURNKEY LAMP"

extendedConfigFile = "TURNKEY LAMP.vmxf"

scsi0.present = "TRUE"

scsi0.sharedBus = "none"

scsi0.virtualDev = "lsilogic"

memsize = "12288"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "TURNKEY LAMP-000005.vmdk"

scsi0:0.deviceType = "scsi-hardDisk"

ide1:0.present = "TRUE"

ide1:0.fileName = "cdrom1"

ide1:0.deviceType = "atapi-cdrom"

ide1:0.startConnected = "FALSE"

ethernet0.present = "TRUE"

ethernet0.networkName = "NAT NETWORK"

ethernet0.addressType = "generated"

usb.present = "TRUE"

ehci.present = "TRUE"

ehci.pciSlotNumber = "34"

tools.syncTime = "TRUE"

guestOS = "debian5-64"

annotation = "http://www.turnkeylinux.org/lamp"

uuid.location = "56 4d 70 47 44 0e 9a b6-77 fd 1c f2 90 bd c8 aa"

uuid.bios = "56 4d 70 47 44 0e 9a b6-77 fd 1c f2 90 bd c8 aa"

vc.uuid = "52 d5 9b e5 97 46 8e b9-f4 12 1a 25 e6 78 ec d5"

numvcpus = "6"

cpuid.coresPerSocket = "6"

sched.scsi0:0.shares = "normal"

sched.scsi0:0.throughputCap = "off"

svga.vramSize = "58720256"

sched.cpu.units = "mhz"

sched.cpu.shares = "normal"

scsi0.pciSlotNumber = "16"

ethernet0.generatedAddress = "00:0c:29:bd:c8:aa"

ethernet0.pciSlotNumber = "33"

usb.pciSlotNumber = "32"

vmci0.id = "-1866610518"

vmci0.pciSlotNumber = "35"

cleanShutdown = "TRUE"

replay.supported = "FALSE"

sched.swap.derivedName = "/vmfs/volumes/528d35a1-19d8506c-14b3-6c626dd55891/TURNKEY LAMP/TURNKEY LAMP-58c103b1.vswp"

replay.filename = ""

scsi0:0.redo = ""

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

ethernet0.generatedAddressOffset = "0"

hostCPUID.0 = "0000000b756e65476c65746e49656e69"

hostCPUID.1 = "000106a5001008000098e3bdbfebfbff"

hostCPUID.80000001 = "00000000000000000000000128100800"

guestCPUID.0 = "0000000b756e65476c65746e49656e69"

guestCPUID.1 = "000106a500080800809822011fabfbff"

guestCPUID.80000001 = "00000000000000000000000128100800"

userCPUID.0 = "0000000b756e65476c65746e49656e69"

userCPUID.1 = "000106a500100800009822011fabfbff"

userCPUID.80000001 = "00000000000000000000000128100800"

evcCompatibilityMode = "FALSE"

vmotion.checkpointFBSize = "58720256"

softPowerOff = "FALSE"

tools.remindInstall = "FALSE"

ethernet0.virtualDev = "e1000"

floppy0.present = "FALSE"

[bharathl]

Did the issue happened after the backup completed or after the snapshot removal completed. You can check the 000005-delta.vmdk exist or not then if it does not exist you can edit the settings of the VM and change the path to 000001.vmdk and then try powering on.

[FritzBrause]

Could be that your datastore is full. Then VMs will be powered off.

This one is a little bit tricky.

First of all, the snapshot files "TURNKEY LAMP-000005-delta.vmdk" and "TURNKEY LAMP-000005.vmdk" are invalid.

This can because:

a) Delta file is only 1 MB

b) CID and ParentCID are equal:

CID=445b7b1b

parentCID=445b7b1b

-> This means, the snapshot was taken when the VM was powered off.

So you can forget about this snapshot 000005.

Strange to me is that snapshot 000005 points to 000001, but you have 000002 and 000003 in VMs home folder.

The chain here is: 000005 -> 000001 -> Base disk.

What about 000002 and 000003?

Check the descriptor file of both where they point to. Maybe they belong to a different snapshot chain.

Options to do:

1. First of all, make sure you have enough disk space where the VM is located.

If there is not enough disk space, the VM is powered off.

2. Clone the disks to a new vmdk file in another location. You can clone the complete VM by right-click -> Clone.

Or you just clone the individual vmdk file with

Syntax: vmkfstools -i <sourcevmdk_lastsnapshotfile> <destinationdatastore+newvmdkname> (specify -d thin if destination should be thin)

See KB 1028042.

3. You can point the VM to 000001 by removing 000005 and adding 000001.

Afterwards, commit the snapshot.

[admin]

Hi,

Seems that there was a problem during the snapshot consolidation and your CID and PID is mismatched. Kindly verify the snapshot chain.

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

-- Avinash

[continuum]

Looks to me like you modified the vmx-file manually after you noticed that something is wrong.
Please attach all earlier vmware.logs and do not make any further attempts to start the VM

You have a significant amount of data in snapshot 000001 and 000003. Any further attempt to start the VM with a wrong constellation will produce corruption - the longer you use it the more damage will be the result.

Without your old logs we cant guess the correct config.