Error while Extending VM disk - 'failed to extend disk : one of the parameters supplied is invalid (1)'
search cancel

Error while Extending VM disk - 'failed to extend disk : one of the parameters supplied is invalid (1)'

book

Article ID: 396953

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms: 

  • below error occurred while trying to expand the vmdk through ESXi command line,

     'failed to extend disk : one of the parameters supplied is invalid (1)'

  • The fault is not resolved by rescan storage.

  • Powering on the virtual machine fails.

Environment

vSphere ESXi 7.0

vSphere ESXi 8.0

Cause

This issue occurs if the disk is not in a compatible format for multiwriter mode.

This issue most commonly occurs in configurations where an eagerzeroedthick virtual disk is shared across multiple virtual machines and is extended using the vSphere Client. When the disk is extended using the vSphere Client, it becomes lazyzeroedthick as the extended portion of the disk is LazyZeroed.
 
Below logs display error
/var/log/hostd.log

YYYY-MM-DDTHH:MM:SS verbose hostd[2101141] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/6350c257-304c0730-00a4-d4f5ef6c9aa8/xxxxxxxxxxxxxx/xxxxxxxxxxxxxx.vmx opID=m5pxsknu-11626430-auto-6x70f-h5:70392371-24-01-01-01-02-cc-3a77] Handling vmx message 39429248: VMware ESX cannot open the virtual disk "/vmfs/volumes/6350c257-304c0730-00a4-d4f5ef6c9aa8/xxxxxxxxxxxxxxx/D:xxxx03 [xxxx03].vmdk" for clustering. Verify that the virtual disk was created using the thick option.
--> File system specific implementation of OpenFile[file] failed
--> Thin/TBZ/Sparse disks cannot be opened in multiwriter mode
--> Cannot open the disk '/vmfs/volumes/6350c257-304c0730-00a4-d4f5ef6c9aa8/xxxxxxxxxxxxxxxx/D:xxxx03 [xxxx03].vmdk' or one of the snapshot disks it depends on.
-->
YYYY-MM-DDTHH:MM:SS info hostd[2101141] [Originator@6876 sub=Vimsvc.ha-eventmgr 

YYYY-MM-DDTHH:MM:SS verbose hostd[2101353] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/6350c257-304c0730-00a4-d4f5ef6c9aa8/xxxxxxxxxxxxxx/xxxxxxxxxxxxxxx.vmx opID=m5pxsknu-11626430-auto-6x70f-h5:70392371-24-01-01-01-02-cc-3a77] Handling vmx message 39429249: VMware ESX cannot open the virtual disk "/vmfs/volumes/6350c257-304c0730-00a4-d4f5ef6c9aa8/xxxxxxxxxxxxxxx/D:xxxxxx01 [xxxxxx01].vmdk" for clustering. Verify that the virtual disk was created using the thick option.
--> File system specific implementation of OpenFile[file] failed
--> Thin/TBZ/Sparse disks cannot be opened in multiwriter mode
--> Cannot open the disk '/vmfs/volumes/6350c257-304c0730-00a4-d4f5ef6c9aa8/xxxxxxxxxxxxxxx/D:xxxxxx01 [xxxxxx01].vmdk' or one of the snapshot disks it depends on.
-->
  • Cannot open Thin/TBZ disks in a multiwriter mode, VMware ESX cannot open the virtual disk.

Resolution

If the above symptoms and log match, please refer below article and perform steps.

Powering on the virtual machine fails with the error: Thin/TBZ disks cannot be opened in multiwriter mode