pkirklewski
Enthusiast
Enthusiast

vmware disk file corrupted

Jump to solution

Hi

I turned off my VM (which was working perfectly fine for ages) and it won't start again.

It complained "File ".

I remember (few months ago) having problems with snapshot's and free space in datastore1. I removed some snapshots manualy since it was impossible to do that the standard way ou to lack of space.

Now I'm sure that this problem has something to do with the snapshot's removal several moths ago.

Here is my vmx file and attached what I can see in the datastore - please help.

.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 = "hermes.nvram"

deploymentPlatform = "windows"

virtualHW.productCompatibility = "hosted"

unity.customColor = "|23C0C0C0"

tools.upgrade.policy = "useGlobal"

powerType.powerOff = "soft"

powerType.powerOn = "default"

powerType.suspend = "hard"

powerType.reset = "soft"

displayName = "hermes"

extendedConfigFile = "hermes.vmxf"

floppy0.present = "TRUE"

scsi0.present = "TRUE"

scsi0.sharedBus = "none"

scsi0.virtualDev = "lsilogic"

memsize = "384"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "hermes-000001.vmdk"

scsi0:0.deviceType = "scsi-hardDisk"

ide1:0.present = "TRUE"

ide1:0.clientDevice = "FALSE"

ide1:0.deviceType = "atapi-cdrom"

ide1:0.startConnected = "FALSE"

floppy0.startConnected = "FALSE"

floppy0.clientDevice = "TRUE"

ethernet0.present = "TRUE"

ethernet0.virtualDev = "e1000"

ethernet0.networkName = "VM Network"

ethernet0.addressType = "generated"

guestOSAltName = "Red Hat Enterprise Linux 5 (64-bit)"

guestOS = "rhel5-64"

uuid.location = "56 4d 4d 39 b5 6b 9c 0b-5d 83 b2 f1 12 af 0a a4"

uuid.bios = "56 4d 4d 39 b5 6b 9c 0b-5d 83 b2 f1 12 af 0a a4"

vc.uuid = "52 a3 db 73 d6 e9 c9 34-56 c6 a5 5c 4f 95 1a 06"

floppy0.fileName = "/dev/fd0"

ethernet0.generatedAddress = "00:0c:29:af:0a:a4"

tools.syncTime = "FALSE"

cleanShutdown = "FALSE"

replay.supported = "TRUE"

#sched.swap.derivedName = "/vmfs/volumes/4a703db6-9dfc91ee-8b40-0024e8671406/hermes/hermes-83d6a231.vswp"

scsi0:0.redo = ""

vmotion.checkpointFBSize = "4194304"

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "16"

ethernet0.pciSlotNumber = "32"

vmci0.pciSlotNumber = "33"

ethernet0.generatedAddressOffset = "0"

vmci0.id = "313461412"

hostCPUID.0 = "0000000d756e65476c65746e49656e69"

guestCPUID.0 = "0000000d756e65476c65746e49656e69"

userCPUID.0 = "0000000d756e65476c65746e49656e69"

hostCPUID.1 = "0001067a00040800040ce3bdbfebfbff"

guestCPUID.1 = "0001067a00010800800822010febfbff"

userCPUID.1 = "0001067a00040800000822010febfbff"

hostCPUID.80000001 = "00000000000000000000000120100800"

guestCPUID.80000001 = "00000000000000000000000120100800"

userCPUID.80000001 = "00000000000000000000000120100800"

evcCompatibilityMode = "FALSE"

ide1:0.fileName = "/vmfs/devices/genscsi/mpx.vmhba0:C0:T1:L0"

checkpoint.vmState.readOnly = "FALSE"

checkpoint.vmState = ""

0 Kudos
1 Solution

Accepted Solutions
continuum
Immortal
Immortal

without seeing all small vmdks there is not much we can do right now - please read

and provide the infos as described there.

From the screenshot it seems hermes-000001.vmdk descriptor is

out of sync but I can't say without seeing the rest

Ulli

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"

View solution in original post

0 Kudos
42 Replies
pkirklewski
Enthusiast
Enthusiast

I should add that from command line I can also see delta files which are not visible form the datastore view.:

-rw------- 1 root root 15217141760 Oct 11 02:23 hermes-000001-delta.vmdk

-rw------- 1 root root 301 Oct 12 06:06 hermes-000001.vmdk

-rw------- 1 root root 33761280 Aug 6 05:26 hermes-000002-delta.vmdk

-rw------- 1 root root 294 Aug 6 05:23 hermes-000002.vmdk

-rw------- 1 root root 436414464 Aug 6 05:33 hermes-000003-delta.vmdk

-rw------- 1 root root 301 Aug 6 05:26 hermes-000003.vmdk

-rw------- 1 root root 8674027520 Sep 1 14:16 hermes-000004-delta.vmdk

-rw------- 1 root root 301 Aug 8 05:42 hermes-000004.vmdk

-rw------- 1 root root 36507428864 Sep 1 14:08 hermes-000008-delta.vmdk

-rw------- 1 root root 301 Aug 8 06:05 hermes-000008.vmdk

-rw-rr 1 root root 13 Sep 1 14:08 hermes-aux.xml

-rw------- 1 root root 107374182400 Oct 12 09:21 hermes-flat.vmdk

-rw------- 1 root root 8684 Oct 9 11:02 hermes.nvram

-rw------- 1 root root 470 Oct 12 09:23 hermes.vmdk

-rw------- 1 root root 2996 Sep 1 14:08 hermes.vmsd

-rwxr-xr-x 1 root root 2869 Oct 12 05:46 hermes.vmx

-rw------- 1 root root 2945 Oct 12 06:06 hermes.vmxf

-rw-rr 1 root root 28936 Oct 12 06:13 vmware-47.log

-rw-rr 1 root root 28936 Oct 12 06:14 vmware-48.log

-rw-rr 1 root root 28955 Oct 12 06:27 vmware-49.log

-rw-rr 1 root root 28956 Oct 12 07:12 vmware-50.log

-rw-rr 1 root root 28956 Oct 12 07:13 vmware-51.log

-rw-rr 1 root root 28956 Oct 12 07:57 vmware-52.log

-rw-rr 1 root root 28954 Oct 12 11:12 vmware.log

0 Kudos
DSTAVERT
Immortal
Immortal

You need to do an ls -la to see all the files. The VMX refers to a snapshot disk hermes-000001.vmdk

-- David -- VMware Communities Moderator
DSTAVERT
Immortal
Immortal

Didn't realize I hit enter. Edit the hermes-000001.vmdk and see where it points.

-- David -- VMware Communities Moderator
pkirklewski
Enthusiast
Enthusiast

hermes-000008.vmdk

Which is there so where is the problem ?

Or how can I recover data from this file ?

Thanks

cat hermes-000001.vmdk

  1. Disk DescriptorFile

version=1

encoding="UTF-8"

CID=905ee9be

parentCID=a5a6c076

createType="vmfsSparse"

parentFileNameHint="hermes-000008.vmdk"

  1. Extent description

RW 209715200 VMFSSPARSE "hermes-000008-delta.vmdk"

  1. The Disk Data Base

#DDB

ddb.longContentID = "6eb674fda618d4668223b05d905ee9be"

Also I noticed that all those files are interconected 08 points to 04 -> 03 -> 02 and 02 points to hermes.vmdk

I don't understand that Smiley Sad

cat hermes-000001.vmdk

parentFileNameHint="hermes-000008.vmdk"

  1. Extent description

RW 209715200 VMFSSPARSE "hermes-000008-delta.vmdk"

cat hermes-000008.vmdk

parentFileNameHint="hermes-000004.vmdk"

  1. Extent description

RW 209715200 VMFSSPARSE "hermes-000008-delta.vmdk"

cat hermes-000004.vmdk

parentFileNameHint="hermes-000003.vmdk"

  1. Extent description

RW 209715200 VMFSSPARSE "hermes-000004-delta.vmdk"

cat hermes-000003.vmdk

parentFileNameHint="hermes-000002.vmdk"

  1. Extent description

RW 209715200 VMFSSPARSE "hermes-000003-delta.vmdk"

cat hermes-000002.vmdk

parentFileNameHint="hermes.vmdk"

  1. Extent description

RW 209715200 VMFSSPARSE "hermes-000002-delta.vmdk"

0 Kudos
continuum
Immortal
Immortal

without seeing all small vmdks there is not much we can do right now - please read

and provide the infos as described there.

From the screenshot it seems hermes-000001.vmdk descriptor is

out of sync but I can't say without seeing the rest

Ulli

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"

View solution in original post

0 Kudos
pkirklewski
Enthusiast
Enthusiast

Hi

So I was able to use hermes-000008.vmdk.

I changed entry in hermes.vmx from hermes-000001.vmdk to hermes-000008.vmdk.

Also in hermes.vmdk i changed CID to point to hermes.vmdk.

The machine started but when I mounted the partition I have found out that the files are old (september).

When I try the same trick with hermes-000001.vmdk I again get the same error: The file is locked.

I also tried hermes-000004.vmdk and it worked - but each time I'm trying the same thing for hermes-000001.vmdk - I get "the file is locked" error.

Any ideas ?

0 Kudos
continuum
Immortal
Immortal

Ideas ? - yes of course.

At once stop what you are doing - you are making things worse by this "tests"

Read my sickbay site and really follow the advice.

You can probably recover from the problem but not if you go on like this !

Shut down the VM immediatly and stop playing with the vmx-file !!!

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
pkirklewski
Enthusiast
Enthusiast

I was thinking I am following your site: http://sanbarrow.com/sickbay.html#planb

It was really helpful for understanding how the files are connected together.

So I turned the machine off.

What's next ?

0 Kudos
continuum
Immortal
Immortal

plan B is last resort - we are not so desparate yet Smiley Wink

post all small vmdk-files + vmx + all vmware*.logs together in one zip-file with a reasonable name - I already have hundreds of vmware.zip - don't send me another one Smiley Wink

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
pkirklewski
Enthusiast
Enthusiast

I took me a while to revert the files to the state that they ware in soon after the crash.

I should mension that I messed with this VM a bit - all the snapshots were removed manualy due to lack of space on the drive.

Tanks for your help mate Smiley Happy

Here is the listing.

-rw------- 1 root root 15217141760 Oct 11 02:23 hermes-000001-delta.vmdk

-rw------- 1 root root 294 Oct 13 01:55 hermes-000001.vmdk

-rw------- 1 root root 33761280 Aug 6 05:26 hermes-000002-delta.vmdk

-rw------- 1 root root 294 Oct 12 16:48 hermes-000002.vmdk

-rw------- 1 root root 436414464 Aug 6 05:33 hermes-000003-delta.vmdk

-rw------- 1 root root 301 Oct 12 16:48 hermes-000003.vmdk

-rw------- 1 root root 8690804736 Oct 12 19:32 hermes-000004-delta.vmdk

-rw------- 1 root root 301 Oct 13 01:58 hermes-000004.vmdk

-rw------- 1 root root 36507428864 Oct 13 00:44 hermes-000008-delta.vmdk

-rw------- 1 root root 301 Oct 13 01:57 hermes-000008.vmdk

-rw-rr 1 root root 13 Sep 1 14:08 hermes-aux.xml

-rw------- 1 root root 107374182400 Oct 12 09:21 hermes-flat.vmdk

-rw------- 1 root root 8684 Oct 13 00:44 hermes.nvram

-rw------- 1 root root 470 Oct 12 09:23 hermes.vmdk

-rw------- 1 root root 2996 Sep 1 14:08 hermes.vmsd

-rwxr-xr-x 1 root root 3003 Oct 13 01:17 hermes.vmx

-rw------- 1 root root 261 Oct 12 19:50 hermes.vmxf

drwxr-xr-x 1 root root 280 Oct 12 13:01 stats

-rw-rr 1 root root 27617 Oct 12 18:58 vmware-70.log

-rw-rr 1 root root 60099 Oct 12 19:25 vmware-71.log

-rw-rr 1 root root 58279 Oct 12 19:30 vmware-72.log

-rw-rr 1 root root 73696 Oct 12 19:32 vmware-73.log

-rw-rr 1 root root 26639 Oct 12 19:33 vmware-74.log

-rw-rr 1 root root 27683 Oct 12 19:39 vmware-75.log

-rw-rr 1 root root 59086 Oct 13 00:44 vmware.log

Can you see the zip file ?

I'm having difficulties to add it.

0 Kudos
continuum
Immortal
Immortal

no attachements there - you can use my email as well - you should be able to find it by searching my site in a minute

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
pkirklewski
Enthusiast
Enthusiast

Sent.

Attachment worked as well.

I also added a snpashot manager view.

0 Kudos
continuum
Immortal
Immortal

oh dear - you have seriously messed up some of those files - next time follow the sickbay rule Do Not Panic

anyway - I guess it can be fixed - give me some time

quick question: do you edited parentfilenamehints in any of the small vmdks ?

do you remeber what the view in snapshotmanager looked like ? - it can either be a single row of snapshots or it can also be a tree of two branches in your case ?

the vmware.logs do not help a lot - they only show failed attempts.

Another important tip for next time: whenever you face issues like this - do immediatly backup all old vmware.logs - they are required to guess the original state

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
pkirklewski
Enthusiast
Enthusiast

Thanks

I've just uploaded the right snaphot view.

Regards

Peter

0 Kudos
continuum
Immortal
Immortal

thanks - for screenshot but I am pretty sure this already shows nonsense ...

please also answer the question about parentfilenamehints

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos
pkirklewski
Enthusiast
Enthusiast

Yes I did.

Also I wasn't the only one who tried to fix it.

I reverted everything I could to a state I have found the files in - but I'm not sure what was their state before I started as my clolege didn't make any bakup of those files.

I think he was tring to make a snapshot which didn't suceed - I'm absoulutely sure that I removed all the snapshots several months ago - manualy.

I think it was a tree.

Regards

0 Kudos
pkirklewski
Enthusiast
Enthusiast

Also the current setup gives me different error.

Attached

0 Kudos
pkirklewski
Enthusiast
Enthusiast

I should probably also mention that I don't need this machine working.

Files from those drives are the only thing that I'm concerned about.

Regards

Peter

0 Kudos
continuum
Immortal
Immortal

you are still trying to start the VM ?

why - this means all my time here is wasted ...

either you NOW stop all your actions or I am out of it

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

Do you need support with a recovery problem ? - send a message via skype "sanbarrow"
0 Kudos