Datastore creation fails with the error: “Failed to update disk partitions for /vmfs/devices/disks/naa.###########”

Products

• VMware vSphere ESXi

Issue/Introduction

When attempting to create a datastore in vSphere Client, the operation fails with an error similar to the following:

Failed to update disk partitions for /vmfs/devices/disks/naa.###########

 

vpxd.log

YYYY-MM-DDT15:48:07.656+09:00 error vpxd[09807] [Originator@6876 sub=Default opID=###########] [VpxLRO] -- ERROR task-79017 -- #####-- datastoreSystem-#### -
- vim.host.DatastoreSystem.createVmfsDatastore: :vim.fault.HostConfigFault
--> Result:
--> (vim.fault.HostConfigFault) {
-->    faultCause = (vmodl.MethodFault) null, 
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.vim.hostsvc.storage.updateDiskFailed", 
-->          arg = (vmodl.KeyAnyValue) [
-->             (vmodl.KeyAnyValue) {
-->                key = "disk", 
-->                value = "/vmfs/devices/disks/naa.###########"
-->             }
-->          ], 
-->          message = "Failed to update disk partitions for /vmfs/devices/disks/naa.###########."
-->       }
-->    ]
-->    msg = "Received SOAP response fault from [<<io_obj p:0x00007f39b87626d8, h:35, <UNIX ''>, <UNIX '/var/run/envoy-hgw/hgw-pipe'>>, /hgw/host-####/vpxa>]: createVmfsDatastore
--> Received SOAP response fault from [<<io_obj p:0x0000009fa21d1aa8, h:17, <TCP '127.0.0.1 : 54589'>, <TCP '127.0.0.1 : 8307'>>, /sdk>]: createVmfsDatastore
--> Cannot change the host configuration."
--> }

vmkernel.log

YYYY-MM-DDT06:48:07.578Z Wa(180) vmkwarning: cpu5:17633255)WARNING: iscsi_vmk: iscsivmk_StopConnection:735: vmhba64:CH:# T:0 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)
YYYY-MM-DDT06:48:07.582Z Wa(180) vmkwarning: cpu0:2097611)WARNING: iscsi_vmk: iscsivmk_TaskMgmtIssue:637: vmhba64:CH:# T:0 L:0 : Task mgmt "Abort Task" with itt=0x382 (refITT=0x37d) timed out.

Environment

VMware vSphere ESXi 7.x

VMware vSphere ESXi 8.x

Cause

This issue occurs due to an incorrect configuration in the storage array, host networking, or ESXi environment — including mismatched MTU settings across the network.

Resolution

To resolve connectivity errors:

• Verify that the iSCSI initiator configuration is correct.
• Confirm that the storage array is operational and supported. To check compatibility, see the VMware Compatibility Guide.
• Ensure that the storage array has a default gateway configured and that the array can successfully ping the host.
• Verify that the host can reach the array using ping or vmkping. For details, see Testing VMkernel network connectivity with the vmkping command
• Check end-to-end network connectivity for the configured MTU (standard or jumbo frames). See Troubleshooting ESXi connectivity to iSCSI arrays using software initiators.
• If port binding is enabled, verify that it is configured correctly. Try unbinding and re-binding the VMkernel ports if necessary. See Considerations for using software iSCSI port binding in ESX/ESXi (2038869).

For additional troubleshooting guidance, refer to Troubleshooting ESXi connectivity to iSCSI arrays using software initiators.
If the issue persists, engage your storage and network vendors for further investigation.