On resize virtual disk

Similar Questions

• MD1220 disk expansion & expansion / resize virtual disk

  I seek to add 6 new MD1220 to a current configuration of 6 who are chained together.  Two quick questions on this...

  (1) is there as a limit to how many MD1220 can be connected?

  (2) once the virtual disks were created in all of my original 6 devices, is it possible to resize or add to this Setup?  Or I should blow away and recreate?

  Thank you
  Greg

  Hello Greg,.

  (1) is there as a limit to how many MD1220 can be connected?  You can put a maximum of 4 cases with the MD1220 can be chained together (which gives a total of 96 disks per SAS port).

  (2) once the virtual disks were created in all of my original 6 devices, is it possible to resize or add to this Setup?  Or I should blow away and recreate? You can add disks to your virtual drive and can increase the size, but depending on how much space you add that it can be faster to back up data and then recreate the virtual disk and restore your data.  A virtual disk expansion is really slow and it may take weeks or even months depending on the size of the virtual disk.

  Please let us know if you have any other questions.

• Help resize virtual disk

  Hello

  I have a single hypervisor, ESXi 4.1 (no VCenter), manage multiple virtual servers on the same physical server. I want to resize one of the disks in the virtual server (supplied thickness) to a smaller size. I did research a few posts on this, but it is not clear.

  If I understand correctly, you are supposed to use Standalone Converter to create a copy of an existing virtual machine and move it to another virtual machine with disk resize to the desired volume. In Standalone Converter, I can choose the source virtual machine, but I have no options to select a destination and do not receive the notice, "this virtual machine already exists.

  If anyone has any advice on the best way to do it, your help is greatly appreciated. Thanks in advance.

  It was perfectly clear to me. Apology. When you use the converter I use the "Powered on machine" as the type of source (obviously the machine must be turned on to make it work) follow the wizard and select the ESXi host as destination.

• Resize virtual disk

  I have the virtual machine that occupies about 25 GB. I increased space 60 GB using VMware Vsphere client VM hard drive. I have Ubuntu 9.10 installed on the virtual machine. The virtual machine when I type 'fdisk-l' always displays the main partition set to 25 GB. and a scope and partition PTAS. I do not see the additional 35 GB increase. Using the command "gparted" (graphic display) on a virtual machine instead of fdisk, I see the unallocated new partition 35 G. I have then assigned to the file system and the size of the new partition. NOW, when I type 'fdisk-l' I could see the new partition of 35GB.

  My question is that when the size of the virtual machine is increased using Vmware Vsphere client how is using "fdisk-l" does not show the new partition of unllocated. Which command can be used inside the virtual machine to see the new unallocated disk space? If I don't want to use the graphics command "gparted". Any advice would be nice.

  Hello

  You can use the separate utility that works in text mode, you must run "parted" / dev / whatever

  Then inside parted to be able to view free space to run "print free.

  (Another simpler way is to run "parted/dev/whatever print free")

  In any case, after the score more, is that you run "fdisk-l" with just a few calculations is easy to find free space.

  Just take special attention to the (total) number of cylinders vdisk (start and end columns) and the size of the partitions (blocks column).

  For example, you know the real size of vdisk (at the top of the output of 'fdisk-l'). The sum total of bytes blocks partitions less vdisk size will be the free space. Easy, isn't it?

  Hope this answer your doubt

  Best wishes / Saludos.

  Pablo

  Please consider providing any useful answer. Thank you!! - Por favor considered premiar las useful responses. ¡¡MUCHAS gracias!

  Virtually noob blog

• Cannot resize the virtual disk, the virtual machine by using a «child» vmdk file

  Release: VMWare workstation 9

  SE host: Windows 7 64-bit

  Screenshots below.

  I want to resize my VM from 50 GB to 100 GB.

  It seems that VMware workstation 9 uses a child for my VM vmdk.  In my case, using its "Windows Server 2008 R2 x 64 - 000001.vmdk" for its virtual disk file.  The correct file should be "Windows Server 2008 R2 x64.vmdk", I think.

  There are currently no snapshots registered for this virtual machine, I see.

  The virtual machine works well as is, but I can't resize the disk without the VMWare gui, saying I should be perform the operation on the parent vmdk file.

  It seems that I do run a snapshot that is not really a snapshot?  How to merge with the older files - Sxx.vmdk to 0000xx - Sxxx.vmdk

  I also tried to use the command line tool to manually resize the vmdk parent, but I get permission "access denied" errors.

  Kind regards

  Matt

  -------------------------------------------

  Parameters of the HARD disk:

  

  Error:

  

  Files:

  

  He no snapshots are displayed in the Manager of snapshot with the check box 'Show AutoProtect snapshots' verified then the snapshot is an orphan and the best way I use normally to fix this if I want the contents of the snapshot of orphan to be among the basic disk is with tab of the virtual machine in VMware Workstation GUI closed I simply delete the .vmsd file and then open the virtual machine tab in the VMware Workstation GUI and cover and immediately remove a snapshot in the Snapshot Manager.  This will force the orphan snapshot to merge with the parent disk.  Then to clean I still remove the .vmsd file and orphans, .vmsn and .vmem file.

  Note: Before the procedure you have a good backup of the virtual machine in case you accidentally mess something up.

• How to resize a virtual disk on vCloud?

  How can I resize a virtual disk to a virtual machine, the vCloud?

  I saw that even if I activate the customization of comments I you can not change the size of the disks, same vm is off power.

  How can I do?

  Concerning

  Yes, you can do so via the REST API. http://geekafterfive.com/2011/11/01/vCloud-apigui-Throwdown/

• cannot resize the virtual disk (vmdk) after successful hyper-v conversion

  Hello

  We are experiencing an environment vSphere 4.1. I have a problem on the Ramdisk resizing.

  We had managed to convert a hyper v VM. Virtual machine operating system is Windows 2008.

  After that, I can't resize the virtual disk (GB in disk options was gray-ed out, even when the virtual machine is power down)

  It's strange

  I have attached several screenshot of the virtual machine.

  Need your advice.

  Thank you

  His grace is on the IDE interface and you can not resize. the only way is to reclone using vmware converter and resize in the wizard. For more information: http://www.yellow-bricks.com/2010/05/28/resizing-your-ide-virtual-harddisk/

• How to resize hard disks of a virtual machine?

  Here's the scenario, we virtualized just a physical machine.

  The (c) is 20 GB, and (d) is 190 GB.  We had to maintain these sizes during the P2V, then re-run the P2V and resizing is not an option (the physical machine is in production and should maintain the current States of its disk).

  From what I can tell, these two (c) and (d) are on a virtual disk (vmdk), which is to ~ 210 GB in size.

  Now that we have virtualized, I could clean the disks and delete unnecessary data.  Now I need to change the (c) for 30 GB and I need to change the (d) to be 50 GB

  Can someone please advice of office?  How to cultivate the (c) and shrink (d) while they are both on a virtual disk (vmdk)?

  In which case it is important, we use a SAN with the left hand.  Our esx-data store is 1 TB, with plenty of room.

  Thanks in advance,

  Chris

  Highlight the host you want to convert to (could be the cluster), then right click and select "import machine".  It will then launch converter.  You can do it on by selecting 'Powered on machine' or if feed you first, you can import it as a virtual one by specifying the host / virtual center.

• Resize and repartition the virtual disk

  Hi all

  I'm under ESXi 4 Update 1 with a 1.6 to RAID 5, which is currently all dedicated to a machine virtual storage (it has no partition system on it, just the files). It currently has two partitions: a partition of 1.1 TB for files and a 500 GB partition with the old backups.

  What I want to do is to delete the partition of 500 GB, give 400GO of it to 1.1 TB partition and then resize the virtual disk so that there are 100GB left in the data store that I can attribute to another virtual machine.

  Who is? I searched, but never found any concrete answer on the subject and don't want to risk losing data to fumble with the controls.

  Thanks for any help.

  OK, now I understand your conifugration.

  You can't reach your end goal without going through a temporary storage in the Middle, like a usb orrr additiiiional on a San disk storage space or the local disk

  (1) create a vmfs on extra storage temp

  (2) use the vmware converter to clone your SBS installation to a new server with the correct (1.5 TB) disk size on the vmfs temp

  (3) delete your source VM

  (4) move the vm cloned to original VMFS

  BTW: it is not a good idea to have a 1.5 TB LUN/VMFS filled 1/2 virtual machines using the entire VMFS TB 1.5: you have no place for the exchange of memory (if needded) and for snapshots. Please allow more space on the VMFS for such tasks. Rule formula says (((maxVMs * avgSize) + 20%) + total vRAM)

• resize the disk space on the virtual machine

  Hello!

  I have a small problem, when I converted a virtual machine on my esx server so I chose 14FR for the virtual machine.

  But I now realize that I need more space on the virtual machine. but the problem is that I stop the virtual machine and

  give more space but the does not get more space than any alcolated in diskmgmt. and there I have to

  make a new partition.

  Can I add a disc more on C: by do not format the drive? or can I add more disk space to a new partition

  (if I add 20 GB now and want to add 20 extra GB to the same partition in 2 months or something like that?) ??

  Thank you

  / R

  http://malaysiavm.com/blog/how-to-resize-Windows-2003-Server-virtual-disk-on-VMware-ESX/

  Here is the guide. Hope is useful.

  Craig

  vExpert 2009

  Malaysia, VMware communities - http://www.malaysiavm.com

• How to resize the size of the virtual disk for Linux guest OS

  Hello

  I installed VMWare WS 6.5 on my host OS (Vista) and have created a guest VM with RedHat like OS.  When creating, I've specified to create a virtual disk with a size of 8 GB, but have not selected the option of immediate creation - it being understood that VM is assigned additional as needed.  But now, on the comments and space use is 100%.  How can I allocate extra space for the virtual machine?  Also, is it possible to go beyond 8 GB, if so how.

  Enjoy your time, help.

  Concerning

  VMware-vdiskmanager allows to extend the virtual disk and use a third-party utility to extend the partition of guest operating system after having developed the virtual disk.

  Make a backup of your virtual machine before you do anything and you ensure that you don't have any snapshots

• Consolidation of many to one of the virtual disks?

  Hello world

  I use a XP client inside a Windows 7 host (using 8 workstations).

  In the configuration of my XP virtual machine I previously assigned (of 50 gigabytes) of disk space into separate virtual folders, about 2 GB each, as shown below.

  

  I now want to have a single vmdk file, with the pre-allocated 50 GB of capacity.

  Is it possible that I can achieve this goal, while keeping my VM in tact? For example can I create a second virtual disk, and then use a cloning tool (from the client) BONE to make a copy to the new virtual drive?

  Here, any help will be greatly appreciated.

  Kind regards

  DAVO

  Hello world

  This can indeed be done! Because I started with a scalable, split, virtual disk, there were several steps; Here's the gist of these measures-

  (1) using the vmware-vdiskmanager merge files into a single.

  http://hostilecoding.blogspot.com.au/2013/06/VMware-merge-multiple-VMDKs-into-single.html

  Note: when running this utility do not forget to include the '2' parameter, which refers to the creation of a virtual disk prealloue, otherwise the following steps (use the shrinkvd program will NOT work!).

  Here is a screenshot of the order that worked for me-

  

  (2) add the newly created virtual disk, 'merged.vmdk' to the existing virtual machine, using these installation instructions.

  https://www.VMware.com/support/WS5/doc/ws_disk_add_virtual.html

  (3) remove the existing virtual machine virtual drive

  (4) to start the Virtual Machine (you will probably be asked if you have moved or copied the VM, I responded with "Proposed").

  (Optionally)-rename the virtual disk of "merged" into something else by renaming the files in the ".vmx" and "hard" files.

  (5) using the shrinkvd resize the virtual disk

  http://www.Softpedia.com/get/system/system-miscellaneous/shrinkvd.shtml

  

  Above, note that the first time, I ran the command it failed with the message "ddb.deletable" is the crux of the problem. I just deleted this line in the relevant file "hard" and the command is represented.

  Now, when I boot on my virtual XP I use only 24 GB of space, and I am able to transfer the Virtual Machine to a smaller drive. in this case a 30 Gig old SSD.

  I hope this helps others.

  Kind regards

  DAVO

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

• Cannot increase the size of the virtual disk

  I do this kind of maintenance all the time. Usually on Windows 2008 R2 servers where I can just go to the VM > settings > hard and develop it for my pleasure, and then add the space from the host 'to hot' without having to reload or use third-party tools 'boot' to develop (IE. GParted).

  We run vSphere 5.0. The virtual machine for this case is a Win2k8 R2 64 bit on a host 4.1. Our warehouses are NFS volumes on NetApp storage infrastructure. It is now the question:

  On the same data store, same OS (2 k 8 R2) I can change the settings on virtual machines to increase the disk space and the others, I can't. It is:

  • same data store (NFS - Yes, there is enough space to grow)
  • different hosts
  • same operating system
  • all of them are defined for Thin Provisioning
  • VMware tools are running and up to date

  For some reason some VMS allow me to develop their hard drive (size available xxx.xxGB) and others do not grow (available s/o): click the arrows to increase the hard drive is greyed out.

  Ideas?

  Thank you!

  Alex

  You can not. Unfortunately, it is not possible to resize a virtual disk with snapshots.

  André

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