Pb with description file .vmdk erase (Workstation Pro V12)

[EIJerome]

Hello,

i need your help for a description file .vmdk erase by mistake

We have the file .vmx and all the ...s001.vdmk ...s002.vdmk ...

Is it possible de rebuild the missing file.

Thanks a lot for response and surely solution

Jérôme from France

Tomorrow is another day !

[a_p_]

Welcome to the Community,

what you can do is to simply create another (dummy) VM with  a virtual disk of the exact same size, and use its descriptor file as a template (rename it, and adjust the names within the file).

André

[EIJerome]

Thanks you André

But what do you mean when you said "and use its descriptor file as a template (rename it, and adjust the names within the file)" what about my ...s001.vmdk ...

My VM will start as before ?

Thank you in advance for your answer

Jérôme

[a_p_]

Let's assume you create a new dummy VM "XRV16-GPAO" (note the "X" instaed of "S") with a virtual disk that has the same size as the original virtual disk.

This will create several files, including a "XRV16-GPAO.vmdk", which is the .vmdk descriptor file (a small text file).

Copy this file to the original VM's folder, rename it to "SRV16-GPAO.vmdk", and edit it, i.e. replace all occurrences of "XRV16-GPAO" to "SRV16-GPAO".

André

PS: Although you shouldn't need it, it may be a good idea to backup the current files before changing things!

[EIJerome]

i do it but when i attach the disk in the vm configuration i have this message

  the system connot find the file specified

my new descriptor file

# Disk DescriptorFile

version=1

encoding="windows-1252"

CID=fffffffe

parentCID=ffffffff

isNativeSnapshot="no"

createType="twoGbMaxExtentSparse"

# Extent description

RW 8323072 SPARSE "SRV16-GPAO-s001.vmdk"

RW 8323072 SPARSE "SRV16-GPAO-s002.vmdk"

RW 8323072 SPARSE "SRV16-GPAO-s003.vmdk"

RW 8323072 SPARSE "SRV16-GPAO-s004.vmdk"

RW 8323072 SPARSE "SRV16-GPAO-s005.vmdk"

RW 8323072 SPARSE "SRV16-GPAO-s006.vmdk"

RW 8323072 SPARSE "SRV16-GPAO-s007.vmdk"

RW 8323072 SPARSE "SRV16-GPAO-s008.vmdk"

RW 8323072 SPARSE "SRV16-GPAO-s009.vmdk"

RW 8323072 SPARSE "SRV16-GPAO-s010.vmdk"

RW 655360 SPARSE "SRV16-GPAO-s011.vmdk"

# The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.cylinders = "5874"

ddb.geometry.heads = "255"

ddb.geometry.sectors = "56"

ddb.longContentID = "8235c42e928462c394e7717bfffffffe"

ddb.uuid = "60 00 C2 91 2a a4 36 09-6d 95 f8 4a e5 80 3e f5"

ddb.virtualHWVersion = "12"

if you have a  new idea

thank you

[a_p_ · Accepted solution]

After taking another look at the screenshot you've posted, I saw that "SRV16-GPAO-s005.vmdk" is missing.

If the VM contains  important data, I'd recommend that you replace the missing file with a copy of e.g. "SRV16-GPAO-s010.vmdk". After this, do NOT boot the VM (unless you have a complete copy of the VM's files), but map the virtual disk to the host OS, and copy/backup data that's needed (and accessible).

André

[EIJerome]

Hello André,

thanks a lot for your help, we have seen that we had missing file.

Our problem was solved.

Our backup will be more efficient in the future.

Thank you for your reactivity and efficiency

Jérôme