VMware Communities
rasmus8888
Contributor
Contributor

"The file specified is not a virtual file"

Hi

I have my virtual environment on workstation 9. I get this error, "The file specified is not a virtual file" when im trying to start my virtual environment.

Also, the Hard drive (SCSI) on the hardware config is blanked.

I really need a solution soon, i have a really imported project that i have been worked in 6 months

Thanks

Reply
0 Kudos
24 Replies
a_p_
Leadership
Leadership

Welcome to the Community,

I assume it's "...not a virtual disk" rather than "...file". Anyway, to start with, please post a complete list of files in the VM's folder which shows all files with their sizes and time stamps (e.g. the output of dir *.* /one from the command line).

André

Reply
0 Kudos
rasmus8888
Contributor
Contributor

pic1.PNG

pic2.PNG

pic3.PNG

Reply
0 Kudos
rasmus8888
Contributor
Contributor

Thats the image of my environment and my error. Thanks


Regards //

Reply
0 Kudos
WoodyZ
Immortal
Immortal

Need to see a copy of the "Triangeln IT Miljo.vmdk" file.  The .vmdk extension is hidden by default so I've attached a cropped picture that you posted and put red arrows pointing to relevant information so you'd attach the correct file.

(Click image to enlarge.)

Triangeln_vmdk.PNG

Note: Use the "Use advanced editor" link in the upper right corner of the normal reply window to bring up the Advanced Editor where you'll be able to attach files via the Choose File button or Browse button (depending on the Browser) above the Post Message button! Smiley Wink

Reply
0 Kudos
rasmus8888
Contributor
Contributor

Thanks!

Here is Triangeln IT Miljö.vmdk

Reply
0 Kudos
a_p_
Leadership
Leadership

From a first look at the screenshot I don't see anything wrong. To see what else could cause the issue, please compress/zip the following files:

  • "Triangeln IT Miljö.vmdk"
  • "Triangeln IT Miljö.vmx"
  • "vmware.log"
  • "vmware-0.log"
  • "vmware-1.log"
  • "vmware-2.log"

and attach the resulting .zip file to a reply post.

André

Reply
0 Kudos
WoodyZ
Immortal
Immortal

To add to what André said, DO NOT take screen shots of the requested files and post them!  We need a copy of the actual physical files as it is easier to analyze the information.  Please just follow the directions when asked so we are not unnecessarily burdened while trying to help you! Smiley Wink

Reply
0 Kudos
rasmus8888
Contributor
Contributor

Here is all files you asked for, not pictures..

Thanks

Reply
0 Kudos
a_p_
Leadership
Leadership

It looks like you made some changes in the VM's configuration!? The virtual disk is currently connected to "scsi0:1" and was connected to "scsi0:0" before. In addition to this the current configuration expects the virtual disk on the C: drive, but it looks like it's located on the E: drive!? Please make sure the VM's configuration contains the proper absolute path to the virtual disk if it's not located in the VM's home folder!

e.g. scsi0:1.fileName = "E:\Triangeln IT Miljö\Triangeln IT Miljö.vmdk"

André

Reply
0 Kudos
rasmus8888
Contributor
Contributor

I tested to change virtual disk with my older virtual environment i have on E, thats why you see that in the config file. But that is not the solution of my problem

Reply
0 Kudos
a_p_
Leadership
Leadership

Just to ensure it's not related, please delete (with VMware Workstation or at least the VM's tab closed) the "Triangeln IT Miljö-7e9d8377.vmss" and "Triangeln IT Miljö-7e9d8377.vmem" files.

André

Reply
0 Kudos
WoodyZ
Immortal
Immortal

I see a discrepancy in naming between what is in the "Triangeln IT Miljö.vmdk" file for the binary extents of the virtual hard disk ("Triangeln IT Miljˆ-s001.vmdk") and whats in the .log files and the screen shots ("Triangeln IT Miljö-s001.vmdk").  I highlighted in bold in the two names show and this is typical of all the extents.

Reply
0 Kudos
WoodyZ
Immortal
Immortal

Use the attached "Triangeln IT Miljö.vmdk.zip" as a replacement for the existing "Triangeln IT Miljö.vmdk" file.  (Unzip it first.)

Reply
0 Kudos
WoodyZ
Immortal
Immortal

Okay this file may not work and having looked further at the various files in the .rar file you attached with a hex editor I see that while what I highlighted in bold as copied and pasted from the documents is different in appearance, probably because of Language settings, are in fact the same the character between the "f" and the "-" in the file name shows as "F6" in the hex editor.

So the only other thing I can think of is one or more of the headers of the binary extents are damaged.  I noticed in two of the .log files it was reporting the disk had error and need repair.  Did you try repairing the disk?

Reply
0 Kudos
rasmus8888
Contributor
Contributor

Thanks for every answear!

I have now tryied everything you have told me, nothing have worked yet. I have not tryied to repair the disk. How do i repair the disk?

Thank you so much //

Reply
0 Kudos
rasmus8888
Contributor
Contributor

How can i retrieve important files from this broken virtual machine?

I dont care if the virtual enviroment not working, its just that i have a visual studio project on it need to have recovered. How can i do that?

Please Thanks for answear

Reply
0 Kudos
a_p_
Leadership
Leadership

What you may try is to see whether mapping the virtual disk (File -> Map virtual disk) as a host drive will work.

André

Reply
0 Kudos
rasmus8888
Contributor
Contributor

yes that wouldnt work either, error reading file information.

How can i repair the disk? I have tryied nothing happens

Reply
0 Kudos
a_p_
Leadership
Leadership

KB article http://kb.vmware.com/kb/1023856 explains how to repair virtual disks.

If this still doesn't help I can offer you to check the virtual disk files. To do this I need the first 320KB of each of the data .vmdk files as well as a list of files which shows the exact sizes of the files. Please follow these steps to gather the required information:

run dir *.* /one > filelist.txt in the VM's folder

Then download dsfo.exe (see http://faq.sanbarrow.com/index.php?action=artikel&cat=47&id=111&artlang=en) and extract the first 320kB from each of the ...-s0xx.vmdk files. You can use the following command to extract the required metadata.

for %i in (*-s???.vmdk) do @dsfo.exe "%i" 0 327680 "x_%~ni.bin"

Once done compress/zip the .bin files along with the filelist.txt and attach the .zip file to a reply post.

André

Reply
0 Kudos