oops...resize ESXi .vmdk prob /issue /how to fix?

atarione

2[H]4U
Joined
Mar 17, 2011
Messages
2,518
so yeah..

i have my home esxi (now 5) server set up... i wanted to resize the disk on my WSUS server, i shut down the machine went into the settings and entered 120GB (from 80GB) hit ok and started the machine... Unfortunately when i logged in and went to the disk manager I realized that instead of making the disk 120GB it had made it 314.9765625GB which isn't going to work. Thus far it refuses all efforts to adjust the size back down either to the desired 120GB or back to the orig 80GB, which is not that awesome.


so then WTF do i do now???

i would greatly appreciate any guidance / advice on resolving this


thank you very much indeed for taking the time to read this and in advance for any assistance.

if any other details are needed to advise please let me know

ESXi 5.0 // guest os is Win2k8R2 Enterprise
 
hi... so i was trying this but even with the --force option i get a "one parameter was incrorrect" messeage with in the link says blah blah blah smaller than the orig size...which is of course my goal i want to shrink the thing.

this is the command i entered (on a test disk)



vmkfstools -X 50G /vmfs/volumes/starwinds_vmTarget2/B_win8dev_test/B_win8dev_test.vmdk --force


which fails orig test disk was 60GB

however the same command but specifying 65G worked fine..which is great and all but the last thing i need is to make the disk even bigger..


if i'm going wrong here somewhere i would certainly appreciate tips.


thanx
 
at this point you're fairly well boned. your only option is to use something like norton ghost (acronis true image, clonezilla etc) then clone off your running VM, create a new disk and clone the old image to it.
 
you could also download vmware converter and v2v it and see if you can fix the disk size issue.
 
hello thanx for the so far Bad news :)


hmm..well ok so hopefully this works but I've made a new VM with the desired HD size of 120GB and am currently re-imaging that with my baremetal backup (windows server backup)

I'm am curious as to why my attempt to resize the orig VMs HD borked so badly as I would like to avoid having this much "fun" in future anyone have any idea why it decided to make the resized disk 314.9765562GB instead of 120GB?
 
No idea why it did it, but you can't use vmkfstools to safely decrease the size of a disk. You have to use converter to pop it back out to a new vm again.
 
kewl thanx for the additional reply


So not the only way to resolve it but i resolved the issue by using my windows server bare metal restore image to a new / properly sized virtual disk


still wish i know WTF happened before..but oh well..
 
Back
Top