cHamBe
Contributor
Contributor

Error to expand disk

Hello,

I have a VM (Workstation Pro 16.2.2 build-19200509) in Windows 10 , when I want expand the disk I have

this error ``` There is not enough space on the file system for the selected operation. ``` my configuration

of the VM:

Conf.JPG

A greeting and Thanks

Labels (1)
  • lo

Reply
0 Kudos
continuum
Immortal
Immortal

What is the desired new size of the disk ?
How much free space do you have ?

Ulli


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
a_p_
Leadership
Leadership

Has the VM been created using the monolithic (single file) .vmdk file format?

André

Reply
0 Kudos
cHamBe
Contributor
Contributor

Hello,

I only have one file vmdk

 

A greeting and thanks

Reply
0 Kudos
RDPetruska
Leadership
Leadership

In order to do any disk operations on a single-file (monolithic) virtual disk, you need to have at least as much free space on your host computer as the maximum size of the virtual disk, plus a small amount of overhead.  So in your case, you need about 300 GB free space on your host hard disk.  And more, depending on how much space you are trying to expand it to.

Reply
0 Kudos
continuum
Immortal
Immortal

What is the desired new size of the disk ?
How much free space do you have ?

Do you OneDrive ?
Do you use compressed NTFS ?


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
a_p_
Leadership
Leadership

That explains it. Resizing a monolithic virtual disk basically creates a new .vmdk file because it requires more space for metadata, then copies the data over to the new file, before the old .vmdk file is deleted. Therefore this task requires a lot of temporary disk space (~the size of the current .vmdk file).

Expanding sparse virtual disks (split into multiple .vmdk files) simply adds additional .vmdk files, which doesn't require a lot of disk space and is done within seconds.

What you can do in the current situation is to convert the current virtual disk to a sparse disk using e.g. the vmware-vdiskmanager command line utility. Unless you can free up some more disk space on the host, you may e.g. use an external disk as the target, and - once converted - delete the original .vmdk file, and copy the new .vmdk file from the external disk to the VM's folder. Alternatively, copy the current .vmdk file to an external disk, and use the VM's folder as the conversion target.

André

Reply
0 Kudos
cHamBe
Contributor
Contributor

Hello,

the vdmk I have it in an external disk, the only option is to generate a new vdmk in my location and then pass it to the external disk.

 

I follow this step to convert the monolithic disk to sparse virtual disk :

vmware-vdiskmanager -r sourceDisk.vmdk -t 0 targetDisk.vmdk

 

 Once I finish the previous command I have tried again to expand the disc with the same error

``` There is not enough space on the file system for the selected operation. ```

 

 

A greeting and thanks

Reply
0 Kudos
continuum
Immortal
Immortal

Asking 3 times should eventually do ....

What is the desired new size of the disk ?
How much free space do you have ?

Do you use OneDrive ?
Do you use compressed NTFS ?


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
a_p_
Leadership
Leadership

>>> vmware-vdiskmanager -r sourceDisk.vmdk -t 0 targetDisk.vmdk

It's "-t 1" (growable virtual disk split into multiple files) what you need.

André

Reply
0 Kudos
cHamBe
Contributor
Contributor

Hello,

Oh, thanks but I've already done a new VM 

 

A greeting

Reply
0 Kudos