How to repair the virtual disk using Fedora 13 linux

[AshokVignesh]

Hi

How to repair the virtual disk using Fedora 13 linux - 32 bit? I'm using latest VMware Player version. Any Idea.

Thanks in advance.

Ashok.

[wila]

Hello Ashok,

Welcome to the VMware communities forum.

Your host is fedora 13?

Anyways try to run:

vmware-vdiskmanager -R yourvmdfilehere.vmdk

It is important to:

- find out why the disk got corrupted

- make a backup of your broken disk to another drive before you try to repair it.

Hope this helps,

--
Wil
_____________________________________________________
VI-Toolkit & scripts wiki at http://www.vi-toolkit.com

Contributing author at blog www.planetvm.net

Twitter: @wilva

[continuum]

AFAIK VMplayer does NOT have vmware-vdiskmanager

Do you know someone with Workstation or have another machine with Workstation ? - you can then try the -R command from that machine.

By the way ... in my experience the -R command maybe works in 5 % of the cases only 😞




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

You also find me in the support crew of PHD Virtual Backup

[wila]

AFAIK VMplayer does NOT have vmware-vdiskmanager

Hello Ulli, yes I should have verified that, just expected it to be there. You are right (of course), this feature is not available with VMware Player.

He could still remove his player instance and install the 30 day evaluation of Workstation, which isn't a bad thing to do anyways.

By the way ... in my experience the -R command maybe works in 5 % of the cases only

Ah but he now has drawn your attention ... which drastically increases his chances of getting his virtual disk back into life

--
Wil
_____________________________________________________
VI-Toolkit & scripts wiki at http://www.vi-toolkit.com

Contributing author at blog www.planetvm.net

Twitter: @wilva

[AshokVignesh]

I tried to use the command but it was showing "the virtual disk, 'Ubuntu.vmdk', is corrupted but the repair process has failed".

They are a lot of muttiple file i.e.,

Ubuntu.nvram Ubuntu-s004.vmdk Ubuntu-s008.vmdk Ubuntu-s012.vmdk Ubuntu-s016.vmdk Ubuntu-s020.vmdk Ubuntu-s024.vmdk Ubuntu.vmsd vmware-1.log

Ubuntu-s001.vmdk Ubuntu-s005.vmdk Ubuntu-s009.vmdk Ubuntu-s013.vmdk Ubuntu-s017.vmdk Ubuntu-s021.vmdk Ubuntu-s025.vmdk Ubuntu.vmx vmware-2.log

Ubuntu-s002.vmdk Ubuntu-s006.vmdk Ubuntu-s010.vmdk Ubuntu-s014.vmdk Ubuntu-s018.vmdk Ubuntu-s022.vmdk Ubuntu-s026.vmdk Ubuntu.vmxf vmware.log

Ubuntu-s003.vmdk Ubuntu-s007.vmdk Ubuntu-s011.vmdk Ubuntu-s015.vmdk Ubuntu-s019.vmdk Ubuntu-s023.vmdk Ubuntu.vmdk vmware-0.log

That conatins some important data. How to get the backup? Please help?

[continuum]

please zip all the vmware*.logs you have and attach the zip here




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

You also find me in the support crew of PHD Virtual Backup

[AshokVignesh]

I enclosed the zip file as an attachment.

[continuum]

Hi

sorry - this vmdk is so messed up - it is beyond my skills to repair it.

Ulli




_________________________

VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook

You also find me in the support crew of PHD Virtual Backup