"Failed to update port persistence location" error reported when connecting VMs to distributed switch port groups.
search cancel

"Failed to update port persistence location" error reported when connecting VMs to distributed switch port groups.

book

Article ID: 377395

calendar_today

Updated On:

Products

VMware vSphere ESX 7.x VMware vSphere ESX 8.x

Issue/Introduction

  • When the VMs are powered on with vNICs connected to DVS port group, the task fails with error:

"A general system error occurred: vDS Host error: Cannot create DVPort of vDS on the host.An error occurred during host configuration: Failed to update port persistence location."

  • Connecting the VM to a standard switch port group is successful.
  • Migrating the VM to another ESXi host and then powering on the VM still reports same error.
  • Deleted the network adapter and powered ON the VM. Then recreating the vNIC and connecting still doesn't help with VM connectivity.

 

At the time when VM is connected to the port group, following events are recorded in Hostd logs:

[YYYY-MM-DDTHH:MM:SS] warning hostd[219####] [Originator@6876 sub=Hostsvc.NetworkProvider opID=lw1rh3ck-11168345-auto-6ndju-h5:71205339-a1-01-10-08e7 user=vpxuser] Error saving  dvport #### to /vmfs/volumes/64a008f7-########-93ea-############/.dvsData/## 13 7b ## 2e 03 f5 ## ## ## ## ## ## 83 f5 42 88/####: N7HostCtl3Lib16HostCtlExceptionE(Failed to write DV Port state to file /vmfs/volumes/64a008f7-########-93ea-############/.dvsData/## 13 7b ## 2e 03 f5 ## ## ## ## ## ## 83 f5 42 88/#### Status (bad000a)= I/O error)
[YYYY-MM-DDTHH:MM:SS] info hostd[219####] [Originator@6876 sub=Hostsvc.NetworkProvider opID=lw1rh3ck-11168345-auto-6ndju-h5:71205339-a1-01-10-08e7 user=vpxuser] deleted port file /vmfs/volumes/64a008f7-########-93ea-############/.dvsData/## 13 7b ## 2e 03 f5 ## ## ## ## ## ## 83 f5 42 88/#### : ####
...
2024-09-05T01:36:06.133Z info hostd[2191144] [Originator@6876 sub=Solo.Vmomi opID=lw##h3ck-1##68X##5-auto-6ndju-h5:##205339-X##-01-10-#### user=vpxuser:<user_id>] Result:
--> (vim.fault.DvsApplyOperationFault) {
-->    objectFault = (vim.fault.DvsApplyOperationFault.FaultOnObject) [
-->       (vim.fault.DvsApplyOperationFault.FaultOnObject) {
-->          objectId = "####",
-->          type = "vim.dvs.DistributedVirtualPort",
-->          fault = (vim.fault.PlatformConfigFault) {
-->             text = "Failed to update port persistence location",
-->             msg = "",
-->          }
-->       }
-->    ],
-->    msg = "",
--> }
…
…
[YYYY-MM-DDTHH:MM:SS] info hostd[248####] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 44089 : At least one corrupt resource metadata region was detected on volume 64a008f7-########-93ea-############ (<Datastore_name>). Other regions of the volume might be damaged too.
[YYYY-MM-DDTHH:MM:SS] info hostd[2481720] [Originator@6876 sub=Hostsvc.VmkVprobSource] VmkVprobSource::Post event: (vim.event.EventEx) {
-->    key = 90,
...
-->
[YYYY-MM-DDTHH:MM:SS] info hostd[2481720] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 44090 : At least one corrupt resource metadata region was detected on volume 64a008f7-########-93ea-############ (Datastore_name). Other regions of the volume might be damaged too.

 

At the same timestamp, vmkernel logs also record:

[YYYY-MM-DDTHH:MM:SS] cpu2:477####)WARNING: Res3: 7066: Volume 64a008f7-########-93ea-############ ("<Datastore_name>") might be damaged on the disk. Resource cluster metadata corruption has been detected.
[YYYY-MM-DDTHH:MM:SS] cpu2:477####)WARNING: FS3: 608: VMFS volume <Datastore_name>/64a008f7-########-93ea-############ on naa.600a09803831########b55##685a53:1 has been detected corrupted
[YYYY-MM-DDTHH:MM:SS] cpu2:477####)FS3: 610: While filing a PR, please report the names of all hosts that attach to this LUN, tests that were running on them,
[YYYY-MM-DDTHH:MM:SS] cpu2:477####)FS3: 634: and upload the dump by `voma -m vmfs -f dump -d /vmfs/devices/disks/naa.600a09803831########b55##685a53:1 -D X`

Environment

VMware vSphere ESX 8.x

Cause

  • The datastore volume where the VM was deployed has corruption issue.
  • Due to this, dvPort details cannot be modified on the ".dvsData" file for the VM.
  • Until the datastore corruption issue is resolved, VMs configured on the reported datastore will continue to report the error when connecting to DVS port groups.

Resolution

Workaround

  • Perform storage vMotion of the VM to another datastore and then re-connect to DVS port group.

For any further assistance open a case with Broadcom Creating and managing Broadcom support cases

For more information refer to Using vSphere On-disk Metadata Analyzer (VOMA) to check VMFS metadata consistency.

Additional Information

If "Failed to update port persistence location" error is observed, but the DVS is out of sync and the error reported is regarding unable to create directory in vSAN datastore, please refer to this article: Cannot create directory .dvsdata when using vSAN

Powered by Wolken Software