Expanding VMDK residing at VVOL datastore fails with Error : "A specified parameter was not correct: spec.deviceChange.device. The disk extend operation failed: One of the parameters supplied is invalid"

Products

• VMware vSphere ESXi

Issue/Introduction

This article provides steps to validate the error and take recommended step. Log snippets can be referenced below, to correlate the issue occurrence encountered during disk extend operation failure.

vmware.log of the affected virtual machine has log snippets similar to:

/vmfs/volumes/vvol:####/naa.600###58/vmware.log

YYYY-MM-DDTHH:MIN:SEC In(05) worker-78607180 - DISKLIB-LIB   : Pre-growing disk '/vmfs/volumes/vvol:####/naa.600###58/examplevm.vmdk': new capacity = 21474836480 sectors - 10 TB                                               
YYYY-MM-DDTHH:MIN:SEC In(05) worker-78607180 - 78607180:VVOLLIB : VVolLib_QueryReferenceVVol:5791: successful .. analyzing result.                                                      
YYYY-MM-DDTHH:MIN:SEC Wa(03) worker-78607180 - OBJLIB-VVOLOBJ : VVolObjTruncateInt: Failing resize request for vvol, as it has referencesContainerId=####,VVolId=naa.600###58
YYYY-MM-DDTHH:MIN:SEC In(05) worker-78607180 - OBJLIB-VVOLOBJ : VVolObjTruncate: Failed to resize VVol 'naa.600###58' to size 10995116277760 (One of the parameters supplied is invalid)
YYYY-MM-DDTHH:MIN:SEC In(05) worker-78607180 - OBJLIB-LIB: ObjLib_Truncate: Failed to truncate handle 13: One of the parameters supplied is invalid (0x9).                              
YYYY-MM-DDTHH:MIN:SEC Er(02) worker-78607180 - DISKLIB-FLAT  : ObjLib_TruncateByObjID failed: One of the parameters supplied is invalid (9)                                             
YYYY-MM-DDTHH:MIN:SEC Er(02) worker-78607180 - DISKLIB-LINK  : DiskLinkGrow: Failed to create extent 'vvol://####/naa.600###58': One of the parameters supplied is invalid
YYYY-MM-DDTHH:MIN:SEC Er(02) worker-78607180 - DISKLIB-LIB   : Unable to grow disk '/vmfs/volumes/vvol:####/naa.600###58/examplevm.vmdk' : One of the parameters supplied is invalid (1).
YYYY-MM-DDTHH:MIN:SEC Er(02) worker-78607180 - DISKLIB-LIB   : DiskLibGrowInt: Unable to grow disk '/vmfs/volumes/vvol:####/naa.600###58/examplevm.vmdk': One of the parameters supplied is invalid
YYYY-MM-DDTHH:MIN:SEC Er(02) worker-78607180 - DISKLIB-LIB   : Failed to grow disk '/vmfs/volumes/vvol:####/naa.600###58/examplevm.vmdk' : One of the parameters supplied is invalid (1). 
YYYY-MM-DDTHH:MIN:SEC Er(02) vmx - HotExtendPreGrowWorkerCompletionCB: DiskLib_PreGrowExtent failed: One of the parameters supplied is invalid (1)

 

In the /var/run/log/vvold.log file, similar entries are seen: 

YYYY-MM-DDTHH:MM:SEC Er(163) VVold[2099472]: [Originator@6876 sub=IpcSvc IpcCtx=2101469-14] HandleRequest: Error handling function QueryUuidForFriendlyName: Empty response
YYYY-MM-DDTHH:MM:SEC In(166) VVold[2099510]: [Originator@6876 sub=Default] SI:QueryIncompleteVirtualVolumes@5743 Empty response For Container:####

Environment

VMware vSphere ESXi 8.x
VMware vSphere ESXi 7.x

Cause

When a snapshot is taken on vvol, both the array and vSphere maintain records of it. Upon snapshot deletion, vSphere sends a delete request to the VVOL array but the array does not confirm it. This can result in a stale snapshot, which appears as an "Empty response".

Resolution

To fix the issue, it is suggested to engage the storage vendor and clean up the stale snapshots left on the array. After which hot extend operation can be retried.

As a workaround, virtual machine needs to be cloned providing the desired disk size.