Expanding shared vmdk fails "The operation is not supported on the object. The operation can not be performed because datastore is inaccessible."
Article ID: 390438
Updated On:
Products
Issue/Introduction
An Administrator attempted to "hot" expand/extend a shared vVOL VMDK and the task failed. vCenter event indicates the following error:
"The operation is not supported on the object. The operation can not be performed because datastore is inaccessible."
Environment
ESX 8.0u2 or newer
Cause
The root cause of the problem stemmed from the vSphere VASA provider was offline.
Troubleshooting VASA providers is needed to return the VASA provider to an online state which resolves the issue with hot expanding.
In determining the cause you may examine the host logs for the following data points. If needed please work with global support to determine if this is a match.
The following messaging can be observed in the ESXi host vmkernel logs:
vmkernel: cpu5:2106142)VMW_SATP_ALUA: satp_alua_issueCommandOnPath:1019: Path "vmhba#:##:###:###" (PERM LOSS) command 0x12 failed with status Device is permanently unavailable. H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x25 0x0. vmkwarning: cpu5:2106142)WARNING: VMW_SATP_ALUA: satp_alua_getTargetPortInfo:190: Could not get page 83 INQUIRY data for path "vmhba#:##:###:###" - Device is permanently unavailable (195887410)
Resolution
Review VASA providers on all hosts that are connected to the vVOL and if the following articles do not resolve the issue on the software side, It may be necessary to troubleshoot further with the storage support entity or vendor.
https://knowledge.broadcom.com/external/article/327020/vasa-storage-providers-are-missing-or-ha.html
or
https://knowledge.broadcom.com/external/article/327066/vasa-provider-registration-troubleshooti.html
Additional Information
Hot extension of a shared vVol disk is supported with ESXi 8.0 Update 2 or later. This allows you to increase the size of a shared disk without deactivating the cluster.
Feedback
