Types of virtual disk

Similar Questions

• Discover the type of virtual disk

  Is it possible to know what type of disc I had selected during the creation of the virtual disk on Linux and Windows?

  Thank you!

  IMHO the createType is written in the first two lines of the vmdk itself file. Use a text editor or head xxx.vmdk under linux.

  Beppo

• question about creating virtual disks on my MD3220i

  I create a virtual disk where I put a SQL Server and it asks me to

  Choose the type of virtual disk IO characteristics. The file system (typical), database, multimedia and Custom options.

  I think the selection of data because it is a SQL Server. However I'm not sure because I have not much of

  experience with this. My question is that one should choose or perhaps not even matter?

  Thank you

  Being that the VD will be strictly for SQL, then you can go ahead and select the database option. Any other time, you must select the typical option. Please let me know if you have any questions or concerns.

• What is my type of virtual machine disk?

  How do I know what type of vm disk?

  I have a lot of files hard all less than 2 GB so I guess that I have a shared rather than a monolithic disc drive.

  How know if I have a sparse or pre-allocated drive?

  Topplay wrote:

  How do I know what type of vm disk?

  I have a lot of files hard all less than 2 GB so I guess that I have a shared rather than a monolithic disc drive.

  How know if I have a sparse or pre-allocated drive?

  The fact that they are all less then 2 GB it means a split disc are rare otherwise they would all be all of the 2 GB.

  Whether if it is a drive IDE or SCSI, you can view the settings of Virtual Machines for both the Bus type and so pre-alloacted.

• Virtual disk 1 gradient

  I have a Dell server that has 6 disks in Raid 1 3 bays. A drive has been replaced and came as "Foreign" so I followed the process to clean it, and now it shows "Ready". I need to add back into the Raid 1 mirror for virtual disk 1 as but it won't allow me. I chose the system-> Storage-> virtual disks in OMSA. For the second virtual disk (which is showing degraded) I've selected Assign/Unassign Dedicated Hot Spare, then run but I get a message that reads:

  Storage management shows only disks that can be used as a hot spare. There are at present no discs that are available, large enough, or the correct type to use as a hot spare for this virtual disk

  The disks are the same with the same product ID etc. I would jump just the drive and return as a test, but it's in a data center so I will try to use remote tools to solve the problem.

  RichRaymont,

  When you go to the page of the physical disks, is there a difference in the indicated for both drives? Also check if the controller firmware is current and up to date, I ask that this can be caused by firmware update. Finally, you have the opportunity to rebuild the disk in the bottom of the fall?

  Let me know what you see.

• OpenManage for VMWare ESXi has no possibility of tasks of virtual disk

  OMSA v 7.1 and 7.2 for Windows (and earlier versions) allow the user to perform many tasks on virtual disks, including reconfiguring - expand a RAID array with a new drive.

  This is not true for managing open for VMWare ESXi - although you can monitor the status of the RAID and disks with the browser of the OMSA interface type, you cannot perform tasks - can not even make a high beam Flash.

  It is a huge problem, because the PERC controllers (H700 and H800, for example) don't allow you to develop virtual using hard drives not Dell disks when you try this during startup in the bios.  (These controllers only allows you to create new virtual disks using drives not Dell).

  This test was conducted using the latest firmware (12.10.4 - 0001 A10) and drivers for the H700 and H800 and multi-server r610 ESXi 5.1.

  Other people with VMWare have been affected by the present?  The only solution is to have two player networks connected to the computer, and create a simple Windows with OMSA, boot in Windows Server to expand the table using OMSA for Windows.

  I would be interested in the comments of others, including those of Dell.  We spent hours on the phone with Dell; This seems to be the only solution.  (Yes, Dell released a firmware version last year that has ceased blocking non Dell readers, but it only works for the creation of a new virtual disk, do not expanding one existing).

  Yes.  It came through a discussion in the Dell | Servers | Discussion of the RAID community.

  en.Community.Dell.com/.../20263442.aspx

  There is a CD bootable linux called OMSA Live that you download from PowerEdge (linux OS) systems management.

  This OMSA PERC H700 and H800 control and allows you to do everything.  When you reconfigure the RAID and the PERC card starts the reconstruction, although it seems risky, you can restart under VMware and the reconstruction of the RAID continues on.  And you can analyze with OMSA for VMware.

• Machine virtual hard disk (virtual disk) of the upper size limit put into service

  Hi there, so I'm trying to create a hard drive or a virtual disk in a Virtual Machine in order to configure the virtual machine as a file server. The data store is a Promise VTrak M610P and I installed the vtrak as a type of VMFS5 5,46 TB of space (4 2 hard disks to each RAID 5). In the virtual machine, I added a hard drive and selected the store data vtrak and tried to set the provisioned to 5.46 TB size and type thick lazy disposition to zero, but I get an error of DiskCapControl with the range values. I changed the size set in service and 4 TB and he accepted the new hard drive. I can't find anything on the actual limit on the creation of hard disk in a virtual computer.

  
  

  I'm running a server Supermicro X7DAL-E with VMware ESXi 5.5 U2.

  Any ideas would be useful. Thank you.
  

  I forgot I asked a similar question on a different section of the forum (shame on me), but I found a solution. Please see the following post Re: SMB access using esxi host and manage with MS server 2008 storage

  Here's what I wrote on the link above:

  So it turns out that there seems to be something wrong with vClient when you add a hard disk (virtual disk) to a virtual machine of size greater than 4 TB. Article VMware KB: value of range error message when you add more than 4 TB capacity discs in vSphere Client describes this if you encounter this problem, add the hard drive via vSphere CLI, CLI power or vmkfstools. So this seems to be a known issue on vClient. What I ended up doing was using vClient, creation of hard disk, adding to the virtual machine (size of the hard drive is to 5.45) and when I would get the error message on the DiskCapControl out of reach, I would just click OK and then finalize the creation of the hard drive on the virtual machine. Once the process is complete, I selected the virtual machine and noticed that he indeed added a new HDD size 5.45 TB even if he's complained about it. I pulled to the top of the virtual machine with windows server 2008 R2 installed and was able to create a new disk under windows and set it up as a shared drive on the network. Looks like vClient must be updated by VMware and correct this bug, if it's a bug that I think. Thank you for the help vervoort!

• Converter does not have "an error occurred when opening a virtual disk. Verify that the Converter server and source running machines have network access to the ESX/ESXi hosts source and destination. »

  Hi all

  I'm having some trouble converting server physical windows using autonomous vConverter 5.5.

  error message:

  "An error occurred when opening a virtual disk. Verify that the Converter server and source running machines have network access to the ESX/ESXi hosts source and destination. "

  I have attached the bundle newspapers. Please notify.

  See you soon...

  Your error is:

  2014-11 - 04T 18: 27:27.587 - 08:00 [01236 info "Default"] GetManagedDiskName: Get disklib file name as vpxa-nfcssl: / / [a0110-vmgt70-001] WIN-MOVRCVCSITG/WIN-MOVRCVCSITG.vmdk@a0110tesxhyp01.datacenter.telenorservices.com: 902! 2 b 52 87 75 03 03 ff 49-67 2f 3 a 61 76 and 00 cd e1

  2014-11 - 04T 18: 27:27.587 - 08:00 [01236 WARNING 'Default'] [, 0] NfcNewAuthdConnectionEx [NFC ERROR]: unable to connect to peer. Error: Failed to search for host for a0110tesxhyp01.datacenter.telenorservices.com server address: the requested name is valid, but no data of the requested type was found

  2014-11 - 04T 18: 27:27.587 - 08:00 [01236 info "Default"] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code: 2338)

  Check the manual on the required ports.

  HTH

• Virtual disk became a file.

  During some household I've foolishly renamed virtual disk to a virtual machine in vSphere Client browser data store and displays as type: file. This now means that the virtual computer will not start. Any suggestions on how I can re - associate the file as a virtual drive.

  I can SSH to the server if need be.

  Thanks in advance for any help on getting this sorted out.

  Znook

  Have you looked at this? Fits this description quite well - VMware KB: turn on/off the virtual machine fails with the error: the specified file is not a virtual disk (15)

• Dell virtual disk are larger. You want to increase the size of the data store.

  Hello

  I started the implementation of a server ESXi 5.5 Update 1 this week. I didn't know Dell shipped the server with two virtual disks instead of one. I realized this _apres_ that I had already created the data store and setup a few virtual machines to the breast. I called Dell who sent specific instructions to increase the removal of the second (empty) virtual disk and add it to the main. In the end, I increased the single VD from 2 TB to 3 TB and I want to give the remaining space in my store of data.

  I tried to follow the article here that explains how to do this via the CLI.

  Well, he did not altogether. Fortunately, I was able to recover my datastore my setting start and end sectors to their original numbers. But I'm still left with this almost 1 TB of space that I can not attribute to the data store. After that I reread storage adapters in the client, the new Dell disk size resulted under measurement devices. Click on "increase...". ", generates the following error which led me on the way to the CLI method:

  Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" to object "ha-datastoresystem" on ESXi '[myservername]' failed.

  I will paste my notes that I took everything by jobs. Things have exploded the rails when I put 4 partition size to the largest size. Any help, please?

  ---

  I use that as a guide:

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2002461

  
  

  1 use start hardware device management tools to increase the capacity of additional disk to the device. For more information, commit your hardware provider.

  This has been done. The new size of the virtual disk is 2791,88 GB (TB 2,79188)

  
  

  2. open a console to the ESXi host.

  Pretty simple.

  
  

  3. get the DeviceID for the data store to change.

  ~ # vmkfstools Pei "/ vmfs/volumes/datastore1 / '.

  System file VMFS-5, 60 extending on 1 partition.

  File system label (if applicable): datastore1

  Mode: public

  Capacity 1971926859776 (blocks of files 1880576 * 1048576), 1042688245760 (994385 blocks) prevail, max size of the 69201586814976 file

  UUID: 534e5121 - 4450-19dc-f8bc1238e18a 260d

  Partitions split (on 'lvm'):

  NAA.6c81f660ef0d23001ad809071096d28a:4

  
  

  A couple of things to note:

  a. the device for Datastore1 ID is: naa.6c81f660ef0d23001ad809071096d28a

  b. the number of Partition on the disk is: 4 ' [...]: 4 "»

  c. the prefix, "naa," means "Network address authority" the number immediately after is a single logical unit number.

  4. Enter the amount of disk space available on the data store.

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 1. 8T 865.4 G 971,1 G 47% / vmfs/volumes/datastore1

  
  

  5 team of the device identifier, to identify the existing partitions on the device by using the partedUtil command.

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  ~ #

  
  

  According to the table in article KB

  4 13711360 3865468766 251 0 - primary #4, type 251 = 0xFB = VMFS, 13711360-3865468766 areas

  | |        |          |   |

  | |        |          |   \---attribut

  | |        |          \---type

  | |        \---se finishing sector

  | \---a starting from sector

  partition \---Numero

  
  

  Also note how the number of section start the old end sector number is + 1.

  
  

  6 identify the partitions that need to be resized and the size of the space to use.

  We want to resize partition 4. I don't really understand the last part of this sentence, however. Read more.

  
  

  7 the number of sector end you want for the target data store VMFS partitions. To use all out at the end of the disc space, remove 1 of the size of the disk in the areas as described in step 5 in order to get the last usable area.

  ESXi 5.x has a command to do this:

  ~ # partedUtil getUsableSectors "/ vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a".

  1 5854986239

  This means that we want 4 Partition of "naa.6c81f660ef0d23001ad809071096d28a" to be:

  13711360 - 5854986239 (i.e. the end of the disc)

  
  

  8 resize the partition containing the target VMFS Datastore using the command partedUtil, specifying the original existing partition and the desired end sector:

  Using the above information, our command is:

  resize # partedUtil ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 5854986239

  
  

  9 step 8, the partedUtil command can report the warning:

  He did not. Displacement.

  
  

  10. the tables of partitions have been adjusted, but the VMFS data within the partition store is always the same size. Now there is an empty space in the partition where the VMFS data store can be grown.

  
  

  11 launch this v vmkfstools command to perform a refresh for VMFS volumes.

  Fact.

  
  

  12 reach the VMFS Datastore in the new space using the command - growfs vmkfstools, specifying the partition containing the VMFS Datastore target twice.

  vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 '.

  
  

  It did not work. I got an error:

  / vmfs/volumes # vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' /vmfs/devices/disks/naa.6c81f660ef0d «»

  23001ad809071096d28a:4 ".

  Cannot get device head way /dev/disks/naa.6c81f660ef0d23001ad809071096d28a:4 information

  
  

  Also the partition was very different to what I asked:

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 1560018942 251 0

  
  

  I fixed it by running these commands:

  ~ # partedUtil resize ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 3865468766

  ~ # vmkfstools v

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  Update:

  Since it was such a new machine, not in active production, we have safeguarded the VMs management off the ESXi host. Then flattened the virtual disk, recreated, and then created a store of data with the right size. (TPG this time, naturally.) We put the management of virtual machines on the data store. For Windows virtual machines, we have restored the using AppAssure. Everything is ok now.

  Need to add a new item to the list of punch: check what Dell has done the configuration of the virtual disks. :-)

• Convert virtual disk from IDE to SCSI now Server 2008 does not start

  Hi all

  I hope that one of you guys can solve my problem.

  I'm new to vmware and have managed to convert my 2008 physical server to a virtual server, but when this virtual disk has been set to IDE, I read that I need to use SCSI for better performance then I attributed a new virtual disk to my server and clone the IDE hard drive on the SCSI disk using EASEUS disk copy software.

  After I cloned the drive I removed the IDE hard disk but my server continues to display the BSOD 0x0000007b error (inaccessible boot volume). I can't start normally or through safe mode. If I try to use the recovery mode no drives appear.

  I use the LSI Logic SAS controller type and have tried the parallel LSI Logic Controller without result.

  Is it possible to fix my guest operating system, without having to reinstall?

  Thank you very much

  Robbie

  Hello

  Visit this link

  http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1016192&sliceId=1&docTypeID=DT_KB_1_1&dialogID=965100100&StateID=1%200%20965102427

  Concerning

  Mohammed

• Installed ESXi on USB/Flash but swap does not seem to have been placed on the virtual disk

  Hello

  I've read several times that when you install ESXi 5.1 on flash media he creates a work space available on a virtual disk of 4 GB in/tmp/scratch so that the USB itself is not used for temporary data to extend the life of the USB.  However, this doesn't seem to be from my experience and I was wondering if someone can help me to confirm that my disc scratch is actually on a virtual disk or whatever on the USB.  I should mention as well as installing ESXi has identified correctly as 'flash' disc type and the disc as a "Generic USB drive»

  After installation, I noticed two things:

  1 log-in user activity logs are able to survive a reboot (I don't think they should the ramdisk is dissolved after a reboot)

  2. There is no directory with the path/tmp/scratch

  Unfortunately I can not directly determine where the partition scratch is (be it on USB or RAM) because I did not have a file ' / etc/fstab "watching (even if I under ESXi 5.0 disk a hard base install?) and it doesn't seem to be a 'mount' command I can use to look at the existing mounts either.

  Can anyone tell me what can I do to verify that the directory used for temporary files is actually a virtual disk and not on the USB drive itself?  Hours of research are presented only the forum messages and documentation clearly indicating that the file will use "/ tmp/scratch", but that just isn't the case.

  Thanks in advance for all your help.

  As you can see from the output

  ~ snip ~

  drwxr-xr-t 1 root root 1260 28 Dec 23:08 50de22a5-f4afafa0-f7b5-001517197ad8
  root drwxr-xr-x 1 root 8 1 January 1970 50df4c30-82b86e61-8522-001517197ad8
  lrwxr-xr-x 1 root root 35 1 Jan 22:21 640GB_WD_Black_AALS-1 -> 50de22a5-f4afafa0-f7b5-001517197ad8

  ~ snip ~

  the UUID is a store existing data "640GB_WD_Black_AALS-1".

  This proves that with an existing data store, a folder ".locker" (which is a ScratchLocation) is automatically created.

  André

• Please help: the virtual disk parent has changed...

  After a few days of research about this error, I decided that I had to ask for some evidence of your experts to help me recover from this error.

  Thank you!

  It is a small desktop application:

  -Dell T410 esxi Server 5

  -a virtual machine, Windows Server 2003 with 2 discs, no fixed size

  I was help this office by managing services and updates on this Server 2003.  I ran updates on Friday and restarted.  When he came I open vSphere and found the virtual machine does not.  I tried to start it and got the error.  So, it seems I may have the CID issue that needs to be corrected.

  I don't have a direct access to this server so I'm remoting with RDS on 2003 VM server and vSphere on the esxi.  Did I make the right diagnosis and is it possible for me to make the necessary corrections to distance or I need direct access to the server?  Everything I've read has files of people editing CID numbers and it seems that they directly access the esxi server.

  Shows the data store:

  hard 'server '.

  hard 'server_1.

  'server' - 000001.vmdk

  "server_1" - 000001.vmdk

  'server' - snapshot1.vmsn

  I stuck a few newspapers below...

  DISC: Scsi0:0 [OPEN ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' persistent R]
  2012-08 - 05T 20: 00:06.022Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001-delta.vmdk ': open with success (10) size = 5620404224, hd = 213826. Type 8
  2012-08 - 05T 20: 00:06.022Z | VMX | DISKLIB-DSCPTR: open [0]: "Server-000001 - delta.vmdk ' (0xa)
  2012-08 - 05T 20: 00:06.022Z | VMX | DISKLIB-LINK: open ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' (0xa): vmfsSparse, 35526656 sectors / 16.9 GB.
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-flat.vmdk ': open with success (14) size = 18189647872, hd = 181059. Type 3
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-DSCPTR: open [0]: 'server - flat hard' (0xe)
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-LINK: open ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server.vmdk' (0xe): vmfs, 35526656 sectors / 16.9 GB.
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB LINK: DiskLinkIsAttachPossible: incompatibility of the content ID (parentCID f72e60c7! = f05537b3) /vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server.vmdk.
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-STRING: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server.vmdk ': cannot open (the virtual disk parent has changed since the child was created.) The content of the virtual disk ID parent does not match the ID of parent for children's content).
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001-delta.vmdk ': closed.
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-VMFS: ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-flat.vmdk ': closed.
  2012-08 - 05T 20: 00:06.035Z | VMX | DISKLIB-LIB: can't open ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' with the virtual disk 0xa flags parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent for children (18) content.
  2012-08 - 05T 20: 00:06.035Z | VMX | DRIVE: Cannot open disk ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk ': the virtual disk parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent for children (18) content.
  2012-08 - 05T 20: 00:06.035Z | VMX | Msg_Post: error
  2012-08 - 05T 20: 00:06.035Z | VMX | [msg.disk.noBackEnd] unable to open drive ' / vmfs/volumes/4f4781a4-15d3bbb8-2681-782bcb6a6964/server/server-000001.vmdk' or one of the snapshot disks it depends on.
  2012-08 - 05T 20: 00:06.035Z | VMX | [msg.disk.configureDiskError] reason: the virtual disk parent has changed since the child was created. The content of the virtual disk ID parent does not match the ID of parent matching the child content.
  2012-08 - 05T 20: 00:06.035Z | VMX |

  Thanks again for any direction you can provide!

  / r

  John

  The parentCID of the snapshot must match the CID from its parent, as shown in the log file

  "... The content ID mismatch (parentCID f72e60c7! = f05537b3)... »

  Server.VMDK

  CID = f05537b3
  parentCID = ffffffff

  Server - 000001.vmdk

  CID = a2b9ba8b
  parentCID = f72e60c7---> f05537b3

  Make sure you change the file on the host using the vi editor or - if you want to change the file in Windows - use an editor who is aware of the line breaks Unix (do not use Notepad!)

  Once this is done, I highly recommend that you take another cliché before you on the virtual computer. This prevents existing virtual disk files to be modified, so that you can return to this State where you need. After that everything works as expected, consider deleting all snapshots.

  André

• thin virtual disk have full size allocated - seems

  I have created a virtual machine with the thin disc type, give it a capacity of 500 GB, install the operating system and its actuall size is 3.60 GB I can check of Vsphere, the disc name is "vmname.vmdk".

  now I want it moved to another server esxi, but when I started downloding, its size became very larg and reached same 171 GB of the drive was renamed "vmname - flat hard"(sur où j'étais le téléchargement) and ends my disk space on the local computer where I was downloading, how I can upload and download with the same size means 3.60 GB "» ,

  Please guide me

  Welcome to the community,

  provisioning is a feature of VMFS file system, this is why the virtual disk inflates its provisioned size when uploading it. What you could do is to export the virtual machine (file-> export) as an OVF and import it on the destination host.

  André

• 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