Error: the specified file is not a virtual disk

Similar Questions

• When I tried to power on VM ends up in the right error: the specified file is not a virtual disk. Cannot open disk ' / vmfs/volumes/4d48ad95-ad5e027a-67f4-e41f1360cc9e/Iso/ser01/ser01.vmdk' or one of the snapshot disks it depends on.

  I stop a virtual machine after a certain time, I tried to power. Its has ended up in the following error message

  Reason: The specified file is not a virtual disk. Cannot open disk ' / vmfs/volumes/4d48ad95-ad5e027a-67f4-e41f1360cc9e/Iso/ser01/ser01.vmdk' or one of the snapshot disks it depends on.

  The machine was working fine before the closure.

  In the data store, the file type of the virtual machine is 'file' instead of 'virtual drive '.

  Help, please

  You are missing the file descriptor hard. The xxxx - flat hard is the file that contains the data effectively. But the xxxx.vmdk is missing, which is a text file that connects to the flat file.

  AWo

• How to resolve the error "the specified file is not a virtual disk?

  Hello - I have a ubuntu/linux host running vmware 1.08 with a SBS2003 VM that recently ran out of physical space in HD. After adding a new drive hard I know to get a specified file is not a virtual disk on one disk error I try to add - the other 3 work. After looking around here, I checked the file descriptor and it seems in good condition.

  My paper does not help because I can not start the virtual machine with the hard drive, I need.

  What are some solutions that I can try?

  Thanks for any help!

  B.

  Unfortunately, you lost the data of zero bytes hard snapshot files. I hope that you don't have a backup of your data, since the snapshot was created in January!

  To be able to feed the virtual machine - even with the disk data corruption - replace zero files hard bytes per who has 327680 bytes, which is essentially an empty file with only the metadata.

  André

  PS: as mentioned earlier, please save the files until you turn on the virtual computer to be able to return to the current status in case you should!

• "The specified file is not a virtual disk" Please someone help, very URGENT

  Dear members,

  Yesterday the electricity of night exploded, so my PC crashed. Today when I tried to open my virtual computer (Workstation 8), it says error: "the specified file is not a virtual disk.

  Tried to do a lot a lot of things that I found online. Nothing has worked yet. My head is about to explode, because I had the very important company data on this machine.

  If someone could provide a working solution, I could pay.

  Please help me!

  Thank you very much, I'm so desperate.

  Attached is some useful info, such as my iii and vmdk, etc files. PNG for the image of the full file in the directory of the virtual machine list.

  On the screen, it seems that you have lost SERVER - s014.vmdk (zero bytes). You can try to replace this file with a hard clean/empty file (for example a copy of the SERVER - s010.vmdk) to see if this allows the access card to the virtual disk again. However, first save all files of the virtual machine to ensure you can return to the current state. At least create a snapshot after you replaced the hard file.

  According to the blocks of data previously stored in this file, you may have lost up to 2 GB of data.

  André

• VM Workstation V9 "the specified file is not a virtual disk.

  I use 9 Workstation and run all my virtual machines from an external hard drive.   When I open two of my most often used VM "hard drive" in the devices section is empty and when I try to start the virtual machine, it gives me the error "the specified file is not a virtual disk.

  It looks like all of my hard are present and represent.

  Any ideas why the 'Hard drive' field is empty?

  

  Thank you for all the ideas.

  The following extensions are of length zero and why you get the error message.

  "Windows XP Professional SP3-cl1-s001.vmdk"
  "Windows XP Professional SP3-cl1-s020.vmdk"
  "Windows XP Professional SP3-cl1-s038.vmdk"
  

  The only thing you can try is to copy an empty measure (binary hard), which has a 320 KB on the behalf of the extent of the lack and then try to ride it to retrieve all user data may need/want to recover.  That said, the probability of it being viable virtual hard drive to function as a VM with the first binary measure missing and now replaced is generally thin at best.  If you have a backup of the virtual machine then copying scopes missing backup is also an option.

• Trying to fix a CID parent access to a file descriptor of delta but VM still does not start. Other error "cannot open the disk...". The specified file is not a virtual disk.

  Starting the virtual machine has been tried several times earlier when I received the error message to tell the parent disk had been changed since the child was created. I looked at the resolution and had a go at fixing.

  I downloaded the vmdk files to find the problematic descriptor file it corrected and then download the a back fixed to the data store. I then removed the VM of the inventory and then re he added before attempting to start it. He says now the specified file is not a virtual disk. Unfortunately, I didn't know that he was still working on a snapshot file and had been for some time. It was a former VM test that I had played a little bit with all learning on VMware, but unfortunately he had a few files on it which is no longer, I have backup ups for and I could really do with recovery of them! The base file and delta file are always on display in the data store and I can re - use the base file in a new virtual machine but I need the data from the snapshot if possible file. Not sure if it can be manually engaged at the base (I have a copy of). I'm new to this depth of troubleshooting and according to research I realize it is a great chance, the data is not recoverable. Having said that if there is no hope at all then I would try or at least have someone who knows what they're doing a go help before you tell me everything is lost! I'm not really bothered to get the virtual machine running again, but must be able to copy some files in the C drive.

  Any help much appreciated.

  Thank you

  Craig

  I can't tell you if the data in the virtual drive itself can be retrieved by the attached hard file. However, it seems that you have used an editor who added a BOM (Byte-Order-Mark) at the beginning of the file, which made her an invalid for ESXi.

  André

• Resumption of the Suspended virtual machine does not work, "the specified file is not a virtual disk.

  Resume a Suspended computer virtual fails with the message "the specified file is not a virtual disk. Tried to go back to the last snapshot fails with the same message "error restoring snapshot: the specified file is not a virtual disk '. '"

  The virtual machine has worked without delivers up to 21/12/2015 while she was snecessary. I often suspend > resume this machine virtual, but for some reason, I am now getting this error. Please help!

  The file unfortunately doesn't look very promising. It seems that the contents were crushed,

  Unless you have a backup, you can try to replace this file with a file 'empty' hard (e.g. copy Windows 7 x 64-000002-s100. ) ( vmdk) that contains only metadata (size = 327 680), to see if this allows you to use the virtual machine again. Note that you will lose all the data stored in the (corrupt) original hard file, and that the virtual machine will probably suffer file system errors. So make sure that you run chkdsk for all partitions in the guest OS.

  In any case, before doing so, I strongly recommend that you back up the existing files of the virtual machine! Once done, it could also be a good idea to run chkdsk for physical training.

  BTW. do you need all the snapshots? With all these clichés and the size of the virtual disk of the virtual machine, the virtual disk consists of files hard ~ 400.

  André

• Windows 7 Vmware the specified file is not a virtual disk.

  When I power on Vmware Windows 7
  The specified file is not a virtual disk.
  I get this error that the specified file is not a virtual disk.
  Please help me solve this question bcz in this virtual machine, my passwrds are save.
  Help me solve this problem.

  To help understand what components are, how best to provide comprehensive diagnostic information is to use the command "Collect information to Support" the Fusion of VMware (menu bar) > help > collect Support information and then attach the .tgz file it created on your desktop for a response post.

• Broken the instant string: the specified file is not a virtual disk.

  Hello

  I have a problem with my VM Workstation 8. After having turned off does not correctly even if that I waited a long time to complete the operation, the vmdk file seems to be broken.

  Error message when you try to start: "the specified file is not a virtual disk.

  Comments & host system: Windows 7 x 64

  Disc type: thin with a size of 2 GB per file, three shots were made

  I checked the CID & parentCID, but found no errors (see attached vmdk).

  VMware - vdiskmanager.exe - R "Customer X64.vmdk model W7"-> no errors

  VMware - vdiskmanager.exe - R "Client model W7 x 64 - 000001.vmdk"-> no output if the operation is successful or not

  VMware - vdiskmanager.exe - R "Client model W7 x 64 - 000002.vmdk"-> no output if the operation is successful or not

  VMware - vdiskmanager.exe - R "Client model W7 x 64 - 000003.vmdk"-> no errors

  VMware - vdiskmanager.exe - e 'model customer W7 x64.vmdk'-> drive chain is consistent

  VMware - vdiskmanager.exe - e ' customer model W7 x 64 - 000001.vmdk ".

  -> could not open *-000001.vmdk: the specified file is not a virtual disk.

  -> could not open *-000001.vmdk: the specified file is not a virtual disk.

  Drive chain is not consistent.

  VMware - vdiskmanager.exe - e ' customer model W7 x 64 - 000002.vmdk.

  -> could not open *-000002.vmdk: the specified file is not a virtual disk.

  -> could not open *-000002.vmdk: the specified file is not a virtual disk.

  Drive chain is not consistent.

  VMware - vdiskmanager.exe - e ' customer model W7 x 64 - 000003.vmdk.

  -> could not open *-000003.vmdk: the parent of this virtual disk could not be opened.

  -> link to disk *-000003.vmdk successfully opened

  -> could not open *-000002.vmdk: the specified file is not a virtual disk.

  Drive chain is not consistent.

  Can someone help me?

  Best regards

  Joe

  That looks really bad. Do you have any AV running application that scans the vmdk files?

  Important: As a first step, back up all files to ensure that nothing can go wrong!

  Then replace all the zero byte vmdk files with one of the files vmdk 327,680 bytes (for example "model client W7 x 64-000001 - s020.vmdk"). If the virtual machine at startup, run a chkdsk on all readers of the virtual machine as there is a chance of corruption/loss of data due to missing data (zero bytes vmdk files).

  André

• Could not start the virtual machine: "the specified file is not a virtual disk.

  Hi, I have a problem from a guest vm-workstation.

  Details below - I've done some reading here for some other "the file specified."

  is

  not a virtual disk' messages and I suspect that I am out of luck

  but I have

  wanted to ask just in case there was something miss me

  Here I tried to gather records / logs that other threads

  mentioned - I

  Welcome to all the tips on the revival of the guest, or a

  pointer to a how-to on recovering the files of a given snapshot.

  Thank you

  John

  Summary:

  VMware workstation: 7.0.1 build 227600

  host of os: Vista sp2, 64-bit

  (16 GB of ram)

  guest operating system: sles10 sp2 64-bit (4 GB ram)

  the virtual machine folder:

  drive eSATA (samsung 320, blacx attachment)

  symptom: guest vm

  does not start: says "the specified file is not a virtual disk.

  history: this particular comments works fine; I've done about 30 shots

  during the last 2 months.  The guest is not a copy - even if she did start life as a full-clone

  another linux-client with or without an operating system installed.  In any case, I've used it to very good

  effect for 2 months now.

  So last night I wanted to power off of the host, while I lived my usual steps:

  (1) stop my os of burst (# shutdown - h now)

  (2) even worksation vmware (file - & gt; exit)

  (3) stop start vista (not "suspend" but the real stop turn off the power).

  (4) visa bluescreened.  Now she is doing this every so often, so I thought that it would be

  a big deal.

  (5) this morning I tried to turn on the virtual machine and I got the 'not a virtual disk' error.

  My best guess at this point is the bluescreen stopped some write cache to be

  flushed to disk.  The funny thing is, after the previous bluescreens 3 or 4, the

  Comments to restart without a hitch.

  shrug In any case, just to be weave, I disabled write Vista for outside cache

  device (set to security policy / deletion in Device Manager).  Seems smarter to

  an external device.

  Spare part

  Attached is a file cant_start.zip (191KO) containing:

  dircontents.txt - directory of the client's file listing
  sles10_sp2. NVRAM
  sles10_sp2.vmsd
  sles10_sp2.vmx
  sles10_sp2.vmxf
  VMware.log - other requests asked for *.log files, so I thought
  VMware - 0.log - I should send him these as well.
  VMware - 1.log
  VMware - 2.log
  \ui-logs - 2 IU-logs from C:\Users\jgreve\AppData\Local\Temp\vmware-jgreve
  \vmdk_files - subdirectory of *.vmdk files, light, & can be useful
  -end-

  I checked the VMDK and newspapers - and the VMDK all look great.

  Last departure also seems to succeed?

  As it seems that instant 36 is not used so far - I was just going to throw it away and try again.

  To do this, you would change the line vmx file

  scsi0:0. FileName = 'suse11.2_x64 - cl1 - 000036.vmdk.

  TO

  scsi0:0. FileName = 'suse11.2_x64 - cl1 - 000035.vmdk.

  and then try to restart the virtual machine. If that works then remove all the

  suse11.2_x64 - cl1 - 000036-* files

  ___________________________________

  VMX-settings- Workstation FAQ -[MOA-liveCD | http://sanbarrow.com/moa241.html]- VM-infirmary

• The specified file is not a virtual disk - easy to fix?

  Ok.  So I know there are a lot of posts dealing with this problem, but most are with the merger.  I HOPE mine should be an easy fix...

  So my just bluescreened machine while running my Ubuntu VM.  The first thing that happened when the computer reboots, I opened VM Player and my my Ubuntu.vmdk file was missing, so I looked all around her.  Found it or a copy of it in the trash.  Reconstituted and then he said "the specified file is not a virtual disk"...  So I upgraded to VM Workstation and still get the same thing...  All the files look good...  How to find on which file is corrupt?  I tried with vmware-vdiskmanager-R option and he said: everything is good.  Help, please!

  Ubuntu.VMDK

  C:\Ubuntu-1010 > Ubuntu.vmdk more
  # Disk DescriptorFile
  version = 1
  CID = e37c3858
  parentCID = ffffffff
  isNativeSnapshot = 'no '.
  createType = "twoGbMaxExtentSparse.

  # Description of the measure
  RW SPARSE 4192256 "Ubuntu - s001.vmdk.
  RW SPARSE 4192256 "Ubuntu - s002.vmdk.
  RW SPARSE 4192256 "Ubuntu - s003.vmdk.
  RW SPARSE 4192256 "Ubuntu - s004.vmdk.
  RW SPARSE 4192256 "Ubuntu - s005.vmdk.
  RW SPARSE 4192256 "Ubuntu - s006.vmdk.
  RW SPARSE 4192256 "Ubuntu - s007.vmdk.
  RW SPARSE 4192256 "Ubuntu - s008.vmdk.
  RW SPARSE 4192256 "Ubuntu - s009.vmdk.
  RW SPARSE 4192256 "Ubuntu - s010.vmdk.
  RW SPARSE 20480 "Ubuntu - s011.vmdk.

  # The database disk
  #DDB

  DDB. Encoding = "windows-1252".
  ddb.adapterType = "free".
  DDB. Geometry.sectors = "63".
  DDB. Geometry.Heads = "255".
  DDB. Geometry.Cylinders = "2610".
  ddb.virtualHWVersion = "4".
  ddb.longContentID = "301956ccc44d62dcba724cc5e37c3858".
  ddb.toolsVersion = "8325.

  Directory;

  12/09/2011 14:50 < DIR >.
  12/09/2011 14:50 < DIR >...
  08/09/2011 10:59 1 073 741 824 564d29b3-9f68-5736-32f3-387596b53bbd.vmem

  08/09/2011 10:59 < DIR > 564d29b3-9f68-5736-32f3-387596b53bbd.vmem
  .lck
  13/03/2011 20:33 < DIR > caches
  01/09/2011 10:18 8 684 nvram
  13/03/2011 17:51 Readme.txt 887
  08/09/2011 10:58 13,172,736 Ubuntu - s001.vmdk
  08/09/2011 10:58 1,282,277,376 Ubuntu - s002.vmdk
  08/09/2011 10:58 1,145,896,960 Ubuntu - s003.vmdk
  08/09/2011 10:58 97,583,104 Ubuntu - s004.vmdk
  08/09/2011 10:58 297,467,904 Ubuntu - s005.vmdk
  08/09/2011 10:58 471,334,912 Ubuntu - s006.vmdk
  08/09/2011 10:58 1,678,901,248 Ubuntu - s007.vmdk
  08/09/2011 10:58 1,414,987,776 Ubuntu - s008.vmdk
  08/09/2011 10:59 796,327,936 Ubuntu - s009.vmdk
  08/09/2011 10:59 40,370,176 Ubuntu - s010.vmdk
  08/09/2011 10:59 65 536 Ubuntu - s011.vmdk
  10/09/2011 12:40 AM Ubuntu.log 39,356,019
  08/09/2011 10:59 Ubuntu.vmdk 830
  01/09/2011 09:18 Ubuntu.vmem 1 073 741 824
  13/03/2011 17:53 Ubuntu.vmsd 0
  01/09/2011 10:19 Ubuntu.vmss 30,979,100
  12/09/2011 13:07 4 328 Ubuntu.vmx
  13/03/2011 19:31 Ubuntu.vmxf 261
  2010-01-22 19:46 993 840 vmware - vdiskmanager.exe
  22 file (s) on 9,457,213,261 bytes
  4 dir 81,049,886,720 bytes free

  Sorry, but I'm a little confused. What do you mean by 'vmx-converted vmdk "?

  In any case, I took a look at the vmx file and found:

  scsi0:0. FileName = "Ubuntu - s001.vmdk.

  who should actually be

  scsi0:0. FileName = "Ubuntu.vmdk".

  because "Ubuntu.vmdk" is the file descriptor.

  André

• Play a suspended virtual machine, vmdk file not found or the specified file is not a virtual disk

  Hi, I have a problem that I can't solve with the usual methods.

  My data

  • software: VMVware Workstation 6.5.1 build 126130

  • Host: NB HP Compaq 2510p with 2 GB of ram

  • OS: Windows XP Pro SP3 5.12.2600

  I have a Win XP Pro SP3 computer virtual created for my work:

  • 6-5 - 7.0 VM workstation

  • RAM: 512 MB

  • Windows XP Pro operating system

  • Processors: 1

  • CDRom: Autodetect

  • Floppy: Autodetect

  • USB: present

  • Sound card: Autodetect

  • Display: Autodetect

  • HARD drive is divided into 2 GB files

  The problem lies in the HARD disk:

  • 40 GB declared

  • 0 MB recognized by the system

  My VM was functional complete. After a suspension

  • The State remains suspended

  • When I try to resume, a pop-up window will appear "file not found: IATROS VM.vmdk" go through it...

  the vmdk file exists (see my attached files).

  When I try to see the features on the parameters, appears "the specified file is not a virtual disk" and all data in the pop-up are unknown or missing.

  I tryied to use the vmware_vdiskmanager with the command vmware - vdiskmanager.exe - R 'e:\appo1\IATROS VM.vmdk' in vain also.

  I think that it is necessary to recreate a file descriptor for disc divided into 2 GB files.

  http://KB.VMware.com/selfservice/microsotes/search.do?language=en_US & cmd = displayKC & externalId = 1026266

  but, if we compare the contents of the VMDK file with the discussion in the article, there seems to be no problem of format or content.

  There are suggestions to solve the problem?

  can I await your response?

  _________________________

  VMX-settings- WS FAQ -[MOAcd | http://sanbarrow.com/moa241.html]- VMDK-manual

• After I restarted the PC, I get this error "error when switching on: the specified file is not a virtual disk".

  I enclose the list of files in the folder of the virtual machine.

  I have attached the log file.

  I attach the vmx file.

  I don't really know what to do next.

  Thank you for your help.

  Cristian

  Hello Cristian,

  Welcome to the forums.

  Looks like your virtual computer configuration file points to a slice file and not the original vmdk file. You can try to change your vmx file and replace:

  ide0:0. FileName = "E:\VMwareFiles\TR570_IMAGE_BIRT\cloned-000001-s011.vmdk".

  with

  ide0:0. FileName = "E:\VMwareFiles\TR570_IMAGE_BIRT\cloned-000001.vmdk".

  If that does not work, try to re-create the virtual disk damaged by using this thread.

  Good luck.

  Concerning

  Franck

• The specified file is not a virtual disk: could not open the vmdk

  I am running vmware player 5.0.1 for windows 7 x 64. I rebooted the host after the suspension of my VM, and when I try to play the virtual machine after the reboot, I get the error message in the topic. I have attached a screencap of the error, my vmware.log and the it refers to a vmdk file. I did some research on the knowledge base and he speaks using virtual disk (vmware-vdiskmanager) Manager to regenerate the vmdk file, but I don't seem to have this program. -What for vmware server/workstation? Can I download it somewhere? Is there an easy fix? My drive is stored in several files that I have to rebuild all of them?

  Thanks in advance for anyone who can help...

  The "EVANS - WHS 2011-0.vmdk" file is a virtual hard disk of metadata, which is a pointer to a physical hard disk and you are not supposed to suspend, snapshot, a Virtual Machine that uses a raw disk such as this and the physical drive could trash making!

  The only thing I can say without further information is to delete and add back.

• The specified file is not a virtual disk.

  Hello;

  I have anyhing on my VMware or folders setting. I do not know what file to download. If you tell me I can send. I want yet loss of my hard disk, please help me.

  Best account.

  VMDK encrypted is very fragile - if you can not decrypt using the GUI there is nothing you can do.
  Do not use encryped VMDK of important data!