Quantcast
Viewing all articles
Browse latest Browse all 12061

The file specified is not a virtual disk

Hi, I'd appreciate urgent help. Here's a description of the problem. I'm also attaching info collected through "collect support info", also. (Fusion 6.0.4. 1887983 running on IMac w/ OSX 10.9.4. BTW, I'm not an expert by any means.

 

 

 

1. When trying to open Win 7 vm I get the message: The file specified is not a virtual disk

 

 

2. Other vm's (Win XP) work fine

 

 

3. Problem occurred when Mac HD failed (IMac running OSX 10.9.4). Not sure if at that point the vm closed normally. Don't know yet what the problem with the HD was (in service now). All files and apps were transported to a new machine (Imac running OSX 10.9.4. also).

 

 

4. Do not have a backup for the vm except for all files (work docs) created with the Win 7 vm

 

 

5. Tried different possible solutions as per online documentation (KB). None worked. I keep getting error messages when trying to repair the vm, like:

 

 

CHECKING FOR DISK CHAIN CONSISTENCY

QUOTE

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -e /Users/mbarrenechea/Documents/Virtual\ Machines.localized/Windows\ 7\ x64.vmwarevm/Windows\ 7\ x64-000002.vmdk

Password:

VixDiskLib: Invalid configuration file parameter.  Failed to read configuration file.

Failed to open the disk '/Users/mbarrenechea/Documents/Virtual Machines.localized/Windows 7 x64.vmwarevm/Windows 7 x64-000002.vmdk' : The parent of this virtual disk could not be opened (0x1700003e8c).

Disk link /Users/mbarrenechea/Documents/Virtual Machines.localized/Windows 7 x64.vmwarevm/Windows 7 x64-000002.vmdk successfully opened.

Failed to open the disk '/Users/mbarrenechea/Documents/Virtual Machines.localized/Windows 7 x64.vmwarevm/Windows 7 x64.vmdk' : The file specified is not a virtual disk (0xf00003ebf).

Disk chain is not consistent: The parent of this virtual disk could not be opened (0x1700003e8c).

 

 

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -e /Users/mbarrenechea/Documents/Virtual\ Machines.localized/Windows\ 7\ x64.vmwarevm/Windows\ 7\ x64.vmdk

VixDiskLib: Invalid configuration file parameter.  Failed to read configuration file.

Failed to open the disk '/Users/mbarrenechea/Documents/Virtual Machines.localized/Windows 7 x64.vmwarevm/Windows 7 x64.vmdk' : The file specified is not a virtual disk (0xf00003ebf).

Failed to open the disk '/Users/mbarrenechea/Documents/Virtual Machines.localized/Windows 7 x64.vmwarevm/Windows 7 x64.vmdk' : The file specified is not a virtual disk (0xf00003ebf).

Disk chain is not consistent: The file specified is not a virtual disk (0xf00003ebf).

UNQUOTE

 

 

Or, like:

 

 

MESSAGE WHEN TRYING TO DEFRAG WITH vmware-vdiskmanager -d

 

 

QUOTE

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -d /Users/mbarrenechea/Documents/Virtual\ Machines.localized/Windows\ 7\ x64.vmwarevm/Windows\ 7\ x64-000002.vmdk

VixDiskLib: Invalid configuration file parameter.  Failed to read configuration file.

Failed to open the disk '/Users/mbarrenechea/Documents/Virtual Machines.localized/Windows 7 x64.vmwarevm/Windows 7 x64-000002.vmdk' : The parent of this virtual disk could not be opened (0x1700003e8c).

Failed to defragment: The parent of this virtual disk could not be opened (0x1700003e8c).

UNQUOTE

 

 

6. The vm bundle shows a snapshot not shown in the snapshot manager. The ID chain seems ok, though (checked through CID. txt).

 

 

7. Also tried to create a new vm using the damaged vm. Did not work.

 

 

8. I've also deleted (per KB instructions) the snapshot and tried to open the vm using the parent vmdm. Did not work either.

 

 

9. I do have a back up for the entire originally damaged vm (as well as a support info obtained through the "Collect support information" command) before trying different solutions.

 

 

 

I would really appreciate anybody helping with this issue,

Mario


Viewing all articles
Browse latest Browse all 12061

Trending Articles