vmkfstools -X fails to expand VMDK file

[Bill_Oyler]

When I attempt to exapnd a VMDK file using vmkfstools -X, I get the following error message:

Failed to extend disk : The file specified is not a virtual disk. (15)[/b]

However, I am certain that the file I specified is in fact a VMDK file. Have things changed in 3.0 such that this method no longer works to expand a VMDK file?

The VMDK file is located on a standard VMFS 3.0 partition. Here is a complete copy and paste of my command sequence:

\[root@lab-esx2 VM1]# vmkfstools -X 8G VM1.vmdk

Failed to extend disk : The file specified is not a virtual disk. (15)[/b]

The current size of the VMDK file is 6GB.

Thanks to anyone who can help solve this mystery!

Bill

[nfailla]

I have followed the same instructions with no luck. It is not a migrated disk, used the full path, executed from the directory where the vmdk lives. The disk I want to expand is a d: drive on the current vm. So it is vmname_1.vmdk because it is the second disk on this vm.

I get the error "Failed to extend disk : One of the parameters supplied is invalid. (1)

[Jeff_Shaw]

Hi,

Try to use the way described here:

http://www.vmweekly.com/articles/expanding_the_virtual_disk_size_in_4_steps/1/

The method is very fast and simple. I think it should help.

Jeff

[Capt_Byte]

The Command is Ubuntu Linux. You should use CFDISK instead of Diskpart (MSwindows).

The following is working with our ESX 3 Production VM server:

12. How to increase Virtual Disk Capacity

Step 1:

\[root@vm2 cx100gb (1)]# ls -lah VM-Ubuntu1-Byte

\[root@vm2 VM-Ubuntu1-Byte]# vmkfstools -X 40G VM-Ubuntu1-Byte-flat.vmdk

Failed to extend disk : The file specified is not a virtual disk. (15)

\[root@vm2 VM-Ubuntu1-Byte]# pwd

/vmfs/volumes/cx100gb (1)/VM-Ubuntu1-Byte

\[root@vm2 VM-Ubuntu1-Byte]# vmkfstools -X 40G /vmfs/volumes/cx100gb\ \(1\)/VM-Ubuntu1-Byte/VM-Ubuntu1-Byte-flat.vmdk

Failed to extend disk : The file specified is not a virtual disk. (15)

\[root@vm2 VM-Ubuntu1-Byte]# vmkfstools -X 40G /vmfs/volumes/cx100gb\ \(1\)/VM-Ubuntu1-Byte/VM-Ubuntu1-Byte.vmdk

Check new size

root@vm2 cx100gb (1)]# ls -lah VM-Ubuntu1-Byte

Step 2:

Sudo su

Cfdisk

Create/check new partition >type>write

Step 3:

System>Administration>disks

Storage List> Partition List

Format >extended 3 > Access Path> enable>ok

[garysoucy1]

The other thing I just discovered, is that the -X switch is NOT how much you are extending the VMDK file, but what you want the final size to be. Took me a while to wrap my head around that one.