VMware Chaging Disk Size Error

We have an ESX 3.5 environment with a guest running Windows Server 2003 on a C:\ drive that is out of space.

I went to the summary tab for the guest, Edit Settings, Hard Drive1, and increased the disk size and clicked OK. After a few seconds, the following error dialog comes up:
--- --- ---
a general system error occurred: Internal error
--- --- ---

Any thoughts?
Who is Participating?
jn1480Connect With a Mentor Author Commented:
Sorry guys - none of these solutions are what I need - I was looking for help as to why this would happen, what the error is from, and how I could fix it to expand it live like I have done so many times before.
Thanks anyway all!
vmwarun - ArunCommented:
I assume that the VM has only one partition and you are using Basic Disks within Windows Server 2003.

1.What is your ESX 3.5 Build Number ? This info can be found in the VI Client on top of the Summary page.

2.How much free space is available on the VMFS Datastore ?(This info can be obtained from the summary page as well)

3.What was the intended disk size you wanted to increase ?
jn1480Author Commented:
1. 3.5.0, 163429
2. 150+ GB
3. Currently 20GB, have tried 25, 30, 35
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Joseph GanSystem AdminCommented:
Have you got VMware-esx-tools rpm installed?
Paul SolovyovskySenior IT AdvisorCommented:
Have you tried it while it's running or shutdown? If running shut it down first
The below method has worked for me many times

1. Download the GParted Live CD ISO and upload it to a datastore so it can be mounted by the virtual machine’s CD-ROM (http://gparted.sourceforge.net/livecd.php)
2. Shutdown the virtual machine you want to resize
3. Edit the Virtual machine configuration and increase the disk size to whatever size you want.
4. Power on the Virtual Machine and make sure it boots properly, load Disk Management and you will see the new unallocated space
5. Now to join the unallocated space to the primary partition, first shutdown the Virtual Machine
6. Connect the Virtual Machine to the GParted ISO file and make sure you enable Connected at Power On
7. Power on the Virtual Machine
8. Press ESC at the Bios screen to get to the Boot Menu
9. Select CD-ROM as the Boot device
10.Gnome Partition Editor will load, press Enter at the boot screen
11. At the Boot option screen select Manual Video Card and then select Done
12. Select required language at the Language screen
13. Select your keyboard at the Keyboard screen
14. Select Generic VESA Compatiable at the Video Driver screen
15. Select 1024×768 at the Resolution screen
16. Once the partition editor loads, click on /dev/sda1 in the partition list
17. Click the Resize/Move button
18. Click and drag the arrow to extend the size of the partition, make sure you do a resize (double arrow) and not a move (four way arrow) so you should have 0 free space preceding and following and then click the Resize/Move button
19. Next click the Apply button and then the operation will start, you can expand Details to see the progress, once completed click the Close button
20. Click the power button in the top left corner, then select reboot
21. Edit the VM and remove the ISO from the CD/ROM device (change to Client)
22. When the server restarts it will do a Check Disk, let this complete, Windows will prompt for a reboot after you login
23. Reboot and load Disk Management and your Primary Partion will be the new size without any unallocated space

You can also try using  vmware converter for this. Convert this VM to another VM. The only thing you need to take care of in this option is at the Source Data screen you should select your volumes and change “Maintain Size” to “Type Size in GB” and enter your new disk size before starting conversion

jn1480Author Commented:
Thanks guys!

I am ON VACATION! until next Monday now - will give these ideas a shot when I get back.
I didn't have any luck with gparted and Windows 2008. I haven't tested it with Windows 2003. It worked well, however, with Windows 7.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.