VMware Cloud Community
pkirklewski
Enthusiast
Enthusiast
Jump to solution

vmware disk file corrupted

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 = ""

Reply
0 Kudos
42 Replies
pkirklewski
Enthusiast
Enthusiast
Jump to solution

I created a new VM called hermes on a different ESXi server.

What would I have to do to "attach" the hermes-000001-delta.vmdk to it.

I created a snapshot so the new hermes has hermes-000001-delta.vmdk.

Do you thing I can cheat this way ?

I only need the VM to start - then I will mount the drive from Live CD.

Regards

Peter

Reply
0 Kudos
DSTAVERT
Immortal
Immortal
Jump to solution

Isn't the moral of a story supposed to be given on the last line ? Smiley Wink

I keep thinking this is the last line.

Personally I don't see a reason to give up at this stage - if the data is really so important

Obviously this story has another chapter at least. Play on.

-- David -- VMware Communities Moderator
Reply
0 Kudos
continuum
Immortal
Immortal
Jump to solution

Peter - I do not have much time now - did you read my notes about the "fake basedisk" procedure at my site ?

I'll be back tomorrow with more time

Ulli

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos