999 GB Limit When Resizing.

[emcclend]

I have a W2K3 physical machine that I want to convert into virtual. It has 6 drives, however 1 of the drives is currently 1.6 TB (1677 GB). I created a new datastore 1.8 TB with 8 MB block size that the single large drive will go on. The other 5 drives will go on a different datastore. Everything is setup and ready to go, so I started up the standalone converter tool and have gone throught all of the prompts. I got to the part where you can resize the disk and change the target datastore. I but 5 drives on 1 datastore and the TB drive on the new datastore. However when I try to rezie it from 16677 GB (1.6 TB)to 1834 GB (1.8 TB, the max size) it tell me, "Please enter a size less than or equal to 999 GB". I thought the largest VMDK could be 2 TB or slightly less with 8 MB block size.

Am I doing something wrong? I simply want to increase the disk size from 1.6 TB to 1.8 TB and it will be the only drive on the datastore.

[vmroyale]

Hello.

It might be a case of Converter keeping you from making a potentially bad choice. You don't want the VMDK to be so large that it fills up the VMFS volume (datastore). If you take the 1677 GB option, that leaves you with slightly less than 10% free space on that 1834 GB VMFS volume. What happens if you choose 1677 in Converter, does that produce an error as well?

Good Luck!

[continuum]

why do you want to include such a large disk in the import-process ?

Looks like it is a data-disk - not required for booting - so I would copy the contents later with robocopy or the tool of your choice

___________________________________

VMX-parameters- VMware-liveCD - VM-Sickbay

[emcclend]

continuum

The large disk in question is a data disk so copying it after the conversion may be an option. The reason for the conversion is because I want it to be a vmdk file and not a rdm. I currently have rdm's for my MSCS bit I'm thinking about breaking the cluster since I loose vmotion and ha features. Just earlier this week was the first time I used robocopy on a differt server when moving P2P. I did not think about using it in his situation.

Later today I'll try the conversion again with all of the small drives and manually create a large vmdk after the conversion. I'll try using robocopy to copy the 1.6 TB old drive to the newly created 1.8 TB drive on the VM. It sounds like it should work so i can't wait to try it. I'll update once I try again.