Virtual disk is not expanding

Similar Questions

• Virtual disk MD3000i not on the preferred path

  Our MD3000i rpet table is not optimal and that a virtual disk is not on the preferred path.

  We have two RAID sets on it with a VD each.  The former says her favorite way is controller 0, the second said his preferred path is controller 1.  But the controller 0 like take charge of both.

  Using MD storage manager, I can change VD2 owned by controller 1.   But in the current for the next several hours, it passes backward, and the MD3000i starts orange flashing again.

  If I restart the server that is attached to it, the question usually begins without having to wait a few hours.

  I changed out Ethernet cables, and it did not help.  Either way, it all started when we changed the MD3000i attached to hosts.  It was attached to two Dell servers, now it is only attached to one.

  After looking through everything, it seems that the iSCSI initiator is configured incorrectly. It seems that you only have one configuration of IP and the MD has two available. Here is a link that has a step by step on setting up the MD3000i and the MPIO.

  http://paulgrevink.WordPress.com/2012/02/21/configure-Dell-MD3000i-MPIO-with-Windows-2008-R2/

  I would like to know how this happens. Also the only link that you have custody fall itself which normally points to a network problem may therefore need to look in the configuration of the switch as well.

• Expanded the bad virtual disk but not Guest OS - Shrink?

  Not quite another question generic "shrink the VMDK.

  I accidentally spread the bad virtual disk in vCenter 725 GB to 1 TB. Fortunately, I realized that until I expanded the partition to use the new space in Windows. Is it possible to reclaim that space? In the virtual machine settings, I have the options of arrow to "reduce" the size down, but I'm not sure on the impact at the prompt to do. Certainly if the guest has not been extended to consume this space then it should be recoverable?

  as you're talking about: the option arrow in the virtual machine settings

  This does not leave you reduce (Shrink) the size of the virtual disk, which has already been strengthened. This option is useful in the case when we say you went into settings of the virtual machine, the disk size increased from 10 to 20 GB, but not yet committed that change and you want to return to 15 you can then use this arrow to do.

  Please visit following KB, is the answer to your question, use VMware converter.

  VMware KB: Increasingly, the thinning and shrinking of the virtual disks for VMware ESX and ESXi

• 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.

• Additional virtual disk space not usable in Windows

  I resized a virtual disk of virtual machines by changing properties and then used a live CD partitioning tool to resize the partition.  Inside windows disk manager, it shows that the additional disk space as if the size of the Windows partition has been increased with success.  However, when I look at the properties of the hard drive in Windows, the extra size does NOT appear and it is not usable or accessible to the file system.  Any ideas what went wrong and how to fix it?

  Thank you

  I had exactly this before strange point of view and could not explain it. Seemed rather strange that the operating system will appear to display the disk space as allocted but the extra space was not available (even when checking the query WMI etc.)

  Ultimately, however, EXTPart has remedied the problem for me. (and quickly)

  If you do not use EXTPart, you can use the converter to recreate the disk.

• Virtual disk MD3000i not on the path preferred because of the AVT/RDAC failover

  Hello

  I am having some problems with my MD3000i failover to a non-prefere path.

  The MD3000i up the old mistake "Not on virtual disk preferred path due the AVT/RDAC failover" several times a day.

  It happened from time to time with ESX 3.5, but not much more happenging with version 4.

  In the var, I get the following:

  24 July 11:49:12 tdvserver1 vobd: 24 Jul 11:49:12.926: 355597326227us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000436ab80000067c48281b88. Vmhba40:C2:t0:L2 path is down. 2 remaining active paths. Touch of data warehouses: «DataStore3 - MD3000i (1 mb)»

  24 July 11:49:12 tdvserver1 vobd: 24 Jul 11:49:12.934: 355597333792us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000438fa20000068b482818af. Vmhba40:C2:t0:L3 path is down. 2 remaining active paths. Touch of data warehouses: «DataStore4 - MD3000i (8 MB)»

  24 July 11:49:12 tdvserver1 vobd: 24 Jul 11:49:12.942: 355597341892us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000436ab8000017ae48d8991a. Vmhba40:C2:t0:L4 path is down. 2 remaining active paths. Touch of data warehouses: «DataStore1 - MD3000i (1 mb)»

  24 July 11:49:12 tdvserver1 vobd: 24 Jul 11:49:12.949: 355597348866us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000438fa20000170448d8965d. Vmhba40:C2:t0:L5 path is down. 2 remaining active paths. Touch of data warehouses: «DataStore2 - MD3000i (1 mb)»

  24 July 11:49:12 tdvserver1 vobd: 24 Jul 11:49:12.995: 355597394915us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000436ab800002d8149242090. Vmhba40:C2:t0:L7 path is down. 2 remaining active paths. Touch of data warehouses: «VDIStore2 - MD3000i (1 mb)»

  24 July 11:49:13 tdvserver1 vobd: 24 Jul 11:49:13.004: 355597404112us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000436ab800003d4c4a2ba941. Vmhba40:C2:t0:L8 path is down. 2 remaining active paths. Touch of data warehouses: «VDIStore1 - MD3000i (2 MB)»

  24 July 11:49:13 tdvserver1 vobd: 24 Jul 11:49:13.013: 355597413405us: http://vprob.storage.redundancy.degraded redundant path to the storage device degraded naa.6001e4f000436ab800006a5e4a6474e4. Vmhba40:C2:t0:L9 path is down. 2 remaining active paths. Touch of data warehouses: unknown.

  24 July 11:49:13 tdvserver1 vobd: 24 July 11:49:13.020: 355597420334us: connectivity lost http://vprob.storage.connectivity.lost to naa.6001e4f000436ab800006b684a65595d of storage device. Vmhba40:C2:t0:L10 path is down. Touch of data warehouses: «DataStore5 - MD3000i (4 MB)»

  24 July 11:49:17 tdvserver1 vobd: 24 July 11:49:17.375: 355601775018us: http://vprob.vmfs.heartbeat.timedout 49248754-672e53f0 - 38 b 7-00151778736 d VDIStore2 - MD3000i (1 MB).

  24 July 11:49:22 tdvserver1 vobd: 24 July 11:49:22.006: 355606406026us: http://vprob.vmfs.heartbeat.recovered 49248754-672e53f0 - 38 b 7-00151778736 d VDIStore2 - MD3000i (1 MB).

  And the following in/var/log/vmkernel:

  July 24, 11:51:03 tdvserver1 vmkernel: 4:02:48:27.601 cpu7:4206) WARNING: NMP: nmp_DeviceAttemptFailover: try tipping unit "naa.6001e4f000436ab800002d8149242090" world - order 0x41000812bc80

  July 24, 11:51:03 tdvserver1 vmkernel: 4:02:48:27.601 cpu2:6691) NMP: nmp_CompleteRetryForPath: Retry world the component 'naa.6001e4f000436ab800002d8149242090 '.

  July 24, 11:51:06 tdvserver1 vmkernel: 4:02:48:30.549 cpu0:4107) NMP: nmp_CompleteCommandForPath: command 0 x 12 (0x4100081c8300) for device NMP 'mpx.vmhba32:C0:T0:L0' failed on the physical path 'vmhba32:C0:T0:L0' H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 5 0 x 24 0 x 0.

  July 24, 11:51:06 tdvserver1 vmkernel: 4:02:48:30.549 cpu0:4107) ScsiDeviceIO: 747: command 0 x 12 for the device "mpx.vmhba32:C0:T0:L0" has no sense H:0 x 0 D:0 x 2 P:0 x 0 valid data: 0 x 5 24 0 x 0 x 0.

  July 24, 11:51:06 tdvserver1 vmkernel: 4:02:48:30.693 cpu1:4097) NMP: nmp_CompleteCommandForPath: command 0 x 12 (0 x 410008106500) for device "mpx.vmhba33:C0:T0:L0" NMP failed on the physical path 'vmhba33:C0:T0:L0' H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 5 0 24 x 0 x 0.

  July 24, 11:51:06 tdvserver1 vmkernel: 4:02:48:30.693 cpu1:4097) ScsiDeviceIO: 747: command 0 x 12 for device "mpx.vmhba33:C0:T0:L0" has no sense H:0 x 0 D:0 x 2 P:0 0 valid x-data: 0 x 5 0 24 x 0 x 0.

  July 24, 11:51:13 tdvserver1 vmkernel: 4:02:48:38.059 cpu0:4107) NMP: nmp_CompleteCommandForPath: command 0 x 12 (0x41000811f800) for device NMP 'mpx.vmhba32:C0:T0:L0' failed on the physical path 'vmhba32:C0:T0:L0' H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 5 0 x 24 0 x 0.

  July 24, 11:51:13 tdvserver1 vmkernel: 4:02:48:38.059 cpu0:4107) ScsiDeviceIO: 747: command 0 x 12 for the device "mpx.vmhba32:C0:T0:L0" has no sense H:0 x 0 D:0 x 2 P:0 x 0 valid data: 0 x 5 24 0 x 0 x 0.

  July 24, 11:51:13 tdvserver1 vmkernel: 4:02:48:38.202 cpu1:4097) NMP: nmp_CompleteCommandForPath: command 0 x 12 (0x4100081d2300) for device "mpx.vmhba33:C0:T0:L0" NMP failed on the physical path 'vmhba33:C0:T0:L0' H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 5 0 24 x 0 x 0.

  July 24, 11:51:13 tdvserver1 vmkernel: 4:02:48:38.202 cpu1:4097) ScsiDeviceIO: 747: command 0 x 12 for device "mpx.vmhba33:C0:T0:L0" has no sense H:0 x 0 D:0 x 2 P:0 0 valid x-data: 0 x 5 0 24 x 0 x 0.

  I spoke with people from Dell and Vmware support.

  Support for VMWare counterpart said that it is a matter of Dell... that VMware is a path problem and do what it is supposed to do.

  The Dell guy says there is nothing wrong with the MD3000i and the problem is with VMWare.

  None of them seem interested in helping me out more.

  I tried using MRU (default) & political pathing Round-Robin and set up iscsi on the host esx, in accordance with the following document:

  http://www.delltechcenter.com/page/VMware ESX4.0andPowerVault MD3000i

  I can vmkping for all the guests of all the peoples on the MD3000i without any problem.

  If someone saw, I would be very grateful.

  Thank you

  Jason

  Hmmm...  Well, if they are flipping back has nothing to do with VMWare, it is certainly a matter of Dell.  Have you tried their repatriation to the correct drives and then just reboot the stupid thing?

  Jason Litka

  http://www.jasonlitka.com

• Virtual disk is not valid or needs repaired

  We have problems try to import our backups of VMware Consolidated Backup for ESX 3.5 using the VMware vCenter converter standalone 4.0. The error we receive is "vitrual disk is invalid or needs repaired. We used the following steps.

  created the VM snapshot with the following script

  cscript C:\Program Files (x 86) \VMware\VMware Consolidated Backup Framework\generic\pre-command.wsf C:\Program Files (x 86) \VMware\VMware Consolidated Backup Framework vcbtest.otc.edu fullvm

  copied the folder mounted where VCB

  delete the virtual machine

  Open the VMware Converter and tried to import the virtual machine

  Here is the part of the logs

  DISKLIB-SPARSECHK: Grain #32694 @4185472 is an orphan.

  DISKLIB-SPARSECHK: Grain #32695 @4185600 is an orphan.

  DISKLIB-SPARSECHK: 32696 orphan (s) detected

  DISKLIB are RARE: "Snapshot Backup Test C:\vcbtest.otc.edu-fullVM\scsi0-0-0-ESX - s001.vmdk ': cannot open (14): disc needs to be repaired.

  DISKLIB-LINK: 'C:\vcbtest.otc.edu-fullVM\scsi0-0-0-ESX Snapshot Backup Test.vmdk': cannot open (the specified virtual disk must be repaired).

  DISKLIB-STRING: 'Snapshot Backup Test.vmdk C:\vcbtest.otc.edu-fullVM\scsi0-0-0-ESX': cannot open (the specified virtual disk must be repaired).

  DISKLIB-LIB: unable to open "C:\vcbtest.otc.edu-fullVM\scsi0-0-0-ESX Snapshot Backup Test.vmdk" with flags 0xe (the specified virtual disk must be repaired).

  14 error opening drive Snapshot Backup Test.vmdk C:\vcbtest.otc.edu-fullVM\scsi0-0-0-ESX.

  Virtual disk is invalid or needs repair

  TaskImpl failed with MethodFault::Exception: converter.fault.MalformedDiskFault

  Any help would be greatly appreciated

  that corrupt vmdk - best thing you can try is copying the vmdk on a Windows host and try to read with vdk

  ___________________________________

  Description of the vmx settings: http://sanbarrow.com/vmx.html

  VMware-liveCD: http://sanbarrow.com/moa.html

• Virtual disk is not accessible, cannot access file

  Hello

  I am unable to vMotion 2 VM from ESX 3.5 to another host. See attached screenshot. When I change the settings of the two VM, the location of their data VMDK files starts with "[]". None of my other virtual machines appear like that, and they can all vMotion successfully.

  Also, I can only power over these 2 VM if I point my VI client directly to the ESX host. If I try to turn on/off or the other VM when my client VI points to Virtual Center, I get this error "unable to access disk.

  The Datastore LUN containing these 2 VM have recently migrated to one EMC CLARiiON to another using SAN based EMC SANCopy. After the LUNS migrated, we detattched the ESX hosts and old CLARiiON system attached to the new. I had to will nothing because prior to attaching hosts to the new San, I deleted all the VMS to their inventories, them restarted without any SAN connectivity, then attached to the new San and OK reappeared data warehouses and then I got to browse\ for each file .vmx and re - add to the inventory.

  Help!

  I recommend that you use a direct connection to the host ESX by VI Client for troubleshooting but cancellation of registration and registration of the virtual machine would require the virtual machine be turned off.

  Direct connection to the ESX host would make things a bit easy to troubleshoot.

  Good luck and let me know if you have any other questions

• 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.

• 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é

• 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é

• Virtual disk don't is not displayed after creation

  Host - XP SP3-running VMWorkstation 6.5 system

  The use of VMWorkstation with the Virtual Machine, a virtual disk is created (IDE) to be used with the virtual machine. When creating of success of the virtual disk in a new folder called "Virtual disk" on the host drive, the VM is launched (XP SP2). Virtual Windows starts without a problem, however the newly created virtual disk is not displayed. How can I get the VM to see?

  Thanks, newbie TM

  Which means that your issue is resolved?

  If you have additional questions, feel free to ask them.

  If your problem is resolved, could you please mark it as answered? It helps other people who search the Forum because it is always easier to just check the question correctly answered not all after a search.

  While you're there, you are invited to also mark messages as useful/correct, this also affects virtual points to the person who helped you. Not nearly as important as the marking which is OK, but for sure appreciated

  --

  Wil

• The virtual disk parent has changed since the child was created

  Hi all, need your help with this one.

  I deleted two snapshots and now I can not start the virtual machine.

  Get the following error:

  Reason: The virtual disk parent has changed since the child was created.
  Cannot open disk ' / vmfs/volumes/4c483d34-a8c778c4-46a5-001cc460f09e/WEBPDXXXY/WEBPDXXXY_1-000003.vmdk' or one of the snapshot disks it depends on.

  I tried that link but still did not work KB: http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 1007969

  I can still see the WEBPDXXXY_1 - 000003.vmdk, WEBPDXXXY_1 - 000002.vmdk and WEBPDXXXY_1 - 000001.vmdk when I browse the data store.

  WEBPDXXXY_1 - 000003.vmdk

  # Disk DescriptorFile
  version = 1
  Encoding = 'UTF-8 '.
  CID = 59fab513
  parentCID = a4a63bd5
  isNativeSnapshot = 'no '.
  createType = "vmfsSparse."
  parentFileNameHint = "WEBPDXXXY_1 - 000002.vmdk".
  # Description of the measure
  RW 157286400 VMFSSPARSE ' WEBPDWEBPDXXXY_1-000003 - delta.vmdk.

  # The database disk
  #DDB

  WEBPDXXXY_1 - 000002.vmdk
  # Disk DescriptorFile
  version = 1
  Encoding = 'UTF-8 '.
  CID = a4a63bd5
  parentCID = 0f8995f3
  isNativeSnapshot = 'no '.
  createType = "vmfsSparse."
  parentFileNameHint = "WEBPDXXXY_1 - 000001.vmdk".
  # Description of the measure
  RW 157286400 VMFSSPARSE ' WEBPDXXXY_1-000002 - delta.vmdk.

  # The database disk
  #DDB

  DDB. Deletable = 'true '.
  ddb.longContentID = "ab1b7008e386c884ae920930a4a63bd5".

  WEBPDXXXY_1 - 000001.vmdk

  # Disk DescriptorFile
  version = 1
  Encoding = 'UTF-8 '.
  CID = 0f8995f3
  parentCID = 926f96fa
  isNativeSnapshot = 'no '.
  createType = "vmfsSparse."
  parentFileNameHint = "WEBPDXXXY_1.vmdk".
  # Description of the measure
  RW 157286400 VMFSSPARSE ' WEBPDXXXY_1-000001 - delta.vmdk.

  # The database disk
  #DDB

  ddb.longContentID = "0336846d9f849b4b97ad028f0f8995f3".
  DDB. Deletable = 'true '.

  WEBPDXXXY_1.VMDK

  # Disk DescriptorFile
  version = 1
  Encoding = 'UTF-8 '.

  CID = 926f96fa

  parentCID = ffffffff
  isNativeSnapshot = 'no '.
  createType = "vmfsRawDeviceMap."

  # Description of the measure
  RW 209715200 VMFSRDM ' WEBPDXXXY_1 - rdm.vmdk '.

  # The database disk
  #DDB

  ddb.toolsVersion = "8295.
  ddb.adapterType = "free".
  DDB. Geometry.sectors = "63".
  DDB. Geometry.Heads = "255".
  DDB. Geometry.Cylinders = "13054.
  DDB. UUID = "60 00 C2 92 41 62 5 d 8f-10 59 12 60 53 0 to a8 94.
  ddb.longContentID = "b204c5bc523bbc83c01dd3ed926f96fa".
  ddb.virtualHWVersion = "7".
  DDB. Deletable = 'true '.

  Is there a chance to run ls-lisa from the command line (SSH) in the virtual machine folder and provide the output!

  I ask because I'm a little worried about the timestamp of the hard (May 2011). Depending on the size of the files in the snapshot, it seems that the second virtual disk is not really used by the guest operating system and we could come back manually (by editing the .vmx file) on the resized basic disk (100 GB compared to 75 GB for snapshots) without losing important data!

  If you want to revert manually,

  • delete the virtual machine of the inventory
  • backup and then edit the .vmx file (replace "WEBPDMAPPD_1 - 000003.vmdk" with "WEBPDMAPPD_1.vmdk")
  • Move 3 snapshots in a directory temporary sub
  • Add the virtual machine to inventory
  • create a new snapshot to prevent the current hard files to be modified
  • Turn on the virtual machine

  If everything works as expected, you can delete the snapshot files moved and remove the snapshot created in the Snapshot Manager again.

  André

• Narrowing of a virtual disk

  Hello

  I found the following document http://www.VMware.com/PDF/VirtualDiskManager.PDF -page 12, it indicates that you can reduce the virtual disk, but not if it uses snapshots.

  I have a machine host with a VM running off a dedicated raid 5, it has used all but 250 MB of hard drive guests.  We took a snapshot a number of months, which took most of the space.  The virtual machine itself is only using 50 CONCERTS, but the VM it take up to 120, so I need to boom the vm disk.  But as above, I have a snapshot which leads me to believe that I can not use this meathod.

  Can someone point me in the right direction how to do to reduce the disk?  As I am afraid the disc will be filled and the virtual machine will stop, that the virtual machine is our Exchange Server - so its pretty important

  See you soon!

  When you open the Snapshot Manager, you see a "you are here". It comes to the real state of the guest. If you have pictures that you'll see named with the name that was given during their creation - they are all former States of the machine.

  If you want to reduce the disk, you must delete all the. So the question which can be deleted or that are not really here.

  You must delete all and thus keep you real state.

  AWo

  VCP 3 & 4

  \[:o]===\[o:]

  = You want to have this ad as a ringtone on your mobile phone? =

  = Send 'Assignment' to 911 for only $999999,99! =

• VMware Tools: Shrinkage of the virtual disks - what is - this intended?

  Hello

  Maybe I'm missing something, but what is the "Reduction of the virtual disks' in VMware Tools used for?  It seems to me that 'reduce the virtual disks' is the only thing that it does not.

  I have a virtual disk in a virtual machine with Windows 2003 Std x 64.  A 'volume' (a partition on a dynamic disk) disk occupies 10 GB on a virtual disk.  The rest of the space on the virtual disk is not assigned.  I want to "shrink" the virtual disk to recover the unallocated space.  But the function "reduce virtual disks" VMware Tools seems to allow me only to "shrink" the disk volume or partition.  I want to reduce the virtual disk.

  What Miss me?

  Thank you.

  Your best best for shrink disk is to use VMware vCenter Converter.  The fret is more than one optimization tool, a bit like a Defrag tool, but will not reduce the size of the disk of the virtual computer.

  Here is a good article

  http://www.RTFM-ed.co.UK/?p=40