Can you try putting the full path to the .vmdk file to see if it makes a difference?
Are you able to assign the vmdk file to a Virtual Machine and confirm if its ok?
Certainly the command is correct to expand the file
Yep, the VMDK is just fine, I boot from it all the time. Works great. It's just too small (6 GB).
Create a new VMDK and see if you can expand that one. Maybe there is some issue with just this one.
then if that works maybe you could try and import the vmdk to the newer bigger vmdk you have created.
\- the actual data disk file which has usually got a '-flat' in the name
\- a disk descriptor .vmdk file
The vmkfstools /bcommand is ESX 3.0 needs to be run against the disk descriptor file, which is a plain text file.
Are you running the extend against the disk descriptor file and not the data file?
If so, can you display the descriptor file contents here?
Arh huh, if I run that command on the actual data disk file I get the following error...
Failed to extend disk : The file specified is not a virtual disk. (15)
So I think the vmkfstools -X is being run on the wrong file.......
Use the full path but don't use the VMFS friendly name, use the long GUID instead...
Use the full path but don't use the VMFS friendly
name, use the long GUID instead...
I'm afraid that won't make any difference.
You are exactly correct. Running the command against the descriptor file solved the problem entirely. Thank you so much!
I'm trying to run the same command, however I'm stuck on the syntax !!
vmkfstools -X 10G /vmfs/volumes/vmsys3/New Virtual Machine/PS_Test.vmdk
....I've tried "g" for the size; full path, not full path, flat and non flat file. The current error I get is "Extra arguments at the end of the command line."
Any suggestion you could offer would be much appreciated
I believe the issue has to do with the "spaces" in the path (i.e. whitespace between "New", "Virtual", and "Machine." You need to surround the entire path with quotes " i.e., "/vmfs/volumes/vmsys3/New Virtual Machine/PS_Test.vmdk". Give that a whirl and let us know if it works.
If you copied an ESX 2.x vmdk file to an ESX 3 host then you cannot run the extend command on it. You get an error: "Failed to extend disk : One of the parameters supplied is invalid (1)".
To fix you must migrate the disk to and ESX 3 format.
vmkfstools -M diskname.vmdk
This takes about 10 seconds for a 6GB disk and then you can run the vmkfstools -X command as you always have. Note when you migrate the disk you will now have 2 .vmdk associated with the system, whereas before you had just 1.