'The file specified is not a virtual disk' for VMWare Fusion

[larsberger]

Hello together ,

as shown in the similar threads with this subject, i also got the problem after a system crash with the virtual disk, my persoanl problem is thats the ceo's vm.

As i seen in the other threads i asked you to help me with this, please. i have attached the files from the support collection of vmfusion to this message.

thanks a lot for your help in this great forum,

lars

Attachment(s)

vm-01-03-13.2250.tgz   1.10 MB 1 version

[WoodyZ]

The Disk DescriptorFile for the "Windows 7 x64-000007.vmdk" snapshot disk is corrupt and the attached "Windows 7 x64-000007.vmdk.zip" file contains a proper "Windows 7 x64-000007.vmdk" Disk DescriptorFile.  With VMware Fusion closed you should open the Virtual Machine Package and if there are any .lck folders/files delete them and then replace the existing  "Windows 7 x64-000007.vmdk" Disk DescriptorFile with the one attached here.  Have a look at: Work with Virtual Machine Packages

I cannot say whether or not any of the binary extents are also corrupted however without replacing this file you'll not be able to continue.

Also note that if you do not have a known good working proper* backup then at least backup this Virtual Machine Package before doing anything else.

==========

*  It is a known fact that Time Machine is not 100% reliable backing up/restoring Virtual Machines under all circumstances/conditions.  Also backing up Virtual Machines via Time Machine is disk/time intensive and wastes a tremendous amount of space for something that may be corrupt and worthless come time to restore it.  At a minimum I would exclude Virtual Machines from Time Machine and with the Virtual Machines shutdown, not suspended, and VMware Fusion closed then manually copy the Virtual Machines Package(s) to an alternate location, preferably on to a different physical hard disk.  Then keep the User Data that is stored within the Virtual Machine backed up off of the Virtual Machine on a regular basis so as to always have a current User Data Backup.  If you have to restore a properly backed up Virtual Machine that is not as current at least you'll have a working Virtual Machine and current User Data to go forward with when you find out your Time Machine Backup of the Virtual Machine fails.

Message was edited by: WoodyZ - Originally posted, Jan 3, 2013 10:28 AM.

[larsberger]

Dear WoodyZ,

unfortunately i tried it  a whole weekend, the vm is corrupt. we got a backup from begin of december, that seems to work.

thanks for your fast reply,

lars