Recreate vmdk descriptor file for VMWare Fusion 3.1?

[darfield]

Is it possible to re-create the vmdk descriptor file in VMWare Fusion 3.1?

I have accidentally deleted the 'Windows XP Professional.vmdk' file from my virtual machine (called 'Windows XP Professional.vmdk').

I have read about recovery of this file in the ESX environment where there is also a flat.vmdk file.

My impression is that the process is similar except that there is no flat file in VMWare Fusion.  Instead there are a series of files tagged numerically.

Can anyone point me in the right direction for recovery of the vmdk file in Fusion?

Thanks in advance,

Chris

[a_p_]

Welcome to the Community,

It is not as easy as with a single flat vmdk file, however it is possible. Do you remember the size of the virtual disk? Has it been resized at any time?

To help figure out what is what the best way to provide comprehensive  diagnostic information is to use the "Collect Support Information"  command from the VMware Fusion (menu bar) > Help > Collect Support  Information and then attach the .tgz file it created on your Desktop to  a reply post. (description copied from WoodyZ)

André

[darfield]

Hi Andre,

Thanks for replying!

I have attached the .tgz file generated from 'Collect Support Information' as you suggested in your reply.

Right off the top of my head I think it is a 40GB hard drive ... but I can confirm that tomorrow when I am back in at work. I do not believe I ever resized this disk.

Let me know what you think the next step is.

Chris

P.S. - The virtual machines are stored under Volumes.

[WoodyZ]

The attached "Server02.192.168.2.241.vmdk.zip" file contains the "Server02.192.168.2.241.vmdk" file and was created from information in the "vmware.log" file and "Server02.192.168.2.241-000001.vmdk" file found in the "Windows XP Professional.vmwarevm" Virtual Machine Paclage within the "vm-10-03-11.38327.tgz" file.

[darfield]

Hi WoodyZ,

I am not exactly sure what I should do with the file Server02.192.168.2.241.vmdk that you included in your response.

I am assuming that I should rename it to 'Windows XP Professional.vmdk' and attempt to run my 'Windows XP Professional' virtual machine using this vmdk file?

Thanks for the help,

Chris

[WoodyZ]

According to information in the "vmware.log" file and "Server02.192.168.2.241-000001.vmdk" file found in the "Windows XP Professional.vmwarevm" Virtual Machine Package within the "vm-10-03-11.38327.tgz" file the "Server02.192.168.2.241.vmdk" belongs in the "/Volumes/Storage 1TB/VMWare/Server02.192.168.2.241/S" folder, named just as it is.

The "Server02.192.168.2.241.vmdk" virtual disk is the Parent Disk of the Child Disk (Snapshot Disk) "Server02.192.168.2.241-000001.vmdk" that is in the "/Volumes/Storage 1TB/Windows XP Professional.vmwarevm" Virtual Machine Package that also contains additional Snapshots.  This first Snapshot "Server02.192.168.2.241-000001.vmdk" file which in this case is the "Disk DescriptorFile" file shows the "parentFileNameHint" as "/Volumes/Storage 1TB/VMWare/Server02.192.168.2.241/Server02.192.168.2.241.vmdk" and this is confirmed by information in the vmware.log file.

So I used vmware-vdiskmanager to create an new virtual disk base on the name and other information in the vmware.log file and first Snapshot Disk and then edited several parameters in the "Server02.192.168.2.241.vmdk" file which in this case is also a "Disk DescriptorFile" to match what the first Snapshot Disk is expecting to see.

If the "/Volumes/Storage 1TB/VMWare/Server02.192.168.2.241/" folder does not exist any longer along with files "Server02.192.168.2.241-s001.vmdk" through "Server02.192.168.2.241-s056.vmdk"  then you're in real trouble!

[darfield]

Prior to copying the VMDK file that you provided above I got the following message when launching the virtual machine I would get the message:

File not found: /Volumes/Storage 1TB/VMWare/Server02.192.168.2.241/Server02.192.168.2.241.vmdk

This file is required to power on this virtual machine.  If this file was moved, please provide its new location.

The message popup then gave me the options Cancel and Browse.

I placed the file that you provided in "/Volumes/Storage 1TB/Windows XP Professional.vmwarevm/", browsed to that location by clicking on the Browse button mentioned above and then got the following message:

Unable to open file "/Volumes/Storage 1TB/Windows XP Professional.vmwarevm/Server02-2.192.168.2.241.vmdk": The system cannot find the file specified.

The only option provided on this popup is 'OK'.

After copying the file into the above location do I have to do something to tell the virtual machine that the file is there now?

You said ...

"If the "/Volumes/Storage 1TB/VMWare/Server02.192.168.2.241/" folder does not exist any longer along with files "Server02.192.168.2.241-s001.vmdk" through "Server02.192.168.2.241-s056.vmdk"  then you're in real trouble!"

These files exist but are actually in "/Volumes/Storage 1TB/Windows XP Professional.vmwarevm/".

Is this the problem?

Chris

[a_p_]

The folder in which you need to copy the vmdk file WoodyZ provided, is "/Volumes/Storage 1TB/VMWare/Server02.192.168.2.241". This should contain the base virtual disk files "Server02.192.168.2.241-s001.vmdk" through "Server02.192.168.2.241-s056.vmdk".

Does this folder exist or has it been deleted?

André

[darfield]

The folder /Volumes/Storage 1TB/VMWare/Server02.192.168.2.241 has been deleted.

These files do exist in /Volumes/Storage 1TB/VMWare/Windows XP Professional.vmwarevm.

Can the virtual disk files "Server02.192.168.2.241-s001.vmdk" through "Server02.192.168.2.241-s001.vmdk" from the .vmwarevm file be used here?

If not, what are these files?

Thanks,

Chris

[a_p_]

These files do exist in /Volumes/Storage 1TB/VMWare/Windows XP Professional.vmwarevm.

That's strange. According to the support package you provided the files are not in this folder. Can you please double check.

The mentioned files are the base virtual disk files. The other files - which are also important - "<vmname>-00000x-s0x.vmdk" are snapshot files which only contain delta data blocks. Without the base vmdk files the snapshots are close to useless.

see http://kb.vmware.com/kb/1015180

André

[darfield]

Uh oh ... looks like you were right. The files in the .vmwarevm folder were the -00000x-s0x.vmdk files .... not the -s001 through -s056 files are not here.

I take it this means I am out of luck?

Chris

[a_p_]

I take it this means I am out of luck?

Unless you have a backup of these files, I'm afraid there's not much you can do. Sorry.

Are you sure the folder has been deleted? Did you already double check the folder has not accidentally been moved to another place?

André

[darfield]

No ... I am afraid these files have been deleted.

I have a backup but it is about a month out of date ... I will lose some database information.

This is not the best news, but is also not the end of the world.

Thanks for all of your help.

One thing that does have me confused is that this seems to be the only virtual machine that I have running where the vdmk files are stored outside of the .vmwarevm file.

That is why those files got deleted ... I did realize they were part of an active virtual machine.

I have definitely learned something!

Chris

[mosschops80]

Hi Woody

Please would you be able to tell us the steps you followed to do this using the vdiskmanager?  Perhaps some examples as I'm finding it quite hard to get my head around.  Just really don't want to mess it up.

Your help would be greatly appreciated.

Regards

M

[WoodyZ]

mosschops80 wrote: Please would you be able to tell us the steps you followed to do this using the vdiskmanager?  Perhaps some examples as I'm finding it quite hard to get my head around.  Just really don't want to mess it up.

I'm sorry that at the present time I just do not have the time to write a tutorial on the subject and it's just easier for me if I have an actual real world scenario to try and resolve and just create the file(s) for someone then to teach them how to do it.

If you're having an issue such as this, nonetheless start you're own discussion thread and attach the support .tgz file and we can go from there.

[mosschops80]

Not a tutorial, just what you done, which commands

[WoodyZ]

Executing vmware-vdiskmanager without any arguments provides the syntax with examples.