"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."
At the time when VM is connected to the port group, following events are recorded in Hostd logs:
2024-09-05T01:36:06.125Z warning hostd[2191144] [Originator@6876 sub=Hostsvc.NetworkProvider opID=lw1rh3ck-11168345-auto-6ndju-h5:71205339-a1-01-10-08e7 user=vpxuser] Error saving dvport 5488 to /vmfs/volumes/64a008f7-72af9518-93ea-b8599fef417c/.dvsData/50 13 7b e9 2e 03 f5 40-2e b0 78 5b 83 f5 42 88/5488: N7HostCtl3Lib16HostCtlExceptionE(Failed to write DV Port state to file /vmfs/volumes/64a008f7-72af9518-93ea-b8599fef417c/.dvsData/50 13 7b e9 2e 03 f5 40-2e b0 78 5b 83 f5 42 88/5488 Status (bad000a)= I/O error)
2024-09-05T01:36:06.128Z info hostd[2191144] [Originator@6876 sub=Hostsvc.NetworkProvider opID=lw1rh3ck-11168345-auto-6ndju-h5:71205339-a1-01-10-08e7 user=vpxuser] deleted port file /vmfs/volumes/64a008f7-72af9518-93ea-b8599fef417c/.dvsData/50 13 7b e9 2e 03 f5 40-2e b0 78 5b 83 f5 42 88/5488 : 5488
...
2024-09-05T01:36:06.133Z info hostd[2191144] [Originator@6876 sub=Solo.Vmomi opID=lw1rh3ck-11168345-auto-6ndju-h5:71205339-a1-01-10-08e7 user=vpxuser:OPTIVER\adm_rogedo] Result:
--> (vim.fault.DvsApplyOperationFault) {
--> objectFault = (vim.fault.DvsApplyOperationFault.FaultOnObject) [
--> (vim.fault.DvsApplyOperationFault.FaultOnObject) {
--> objectId = "5488",
--> type = "vim.dvs.DistributedVirtualPort",
--> fault = (vim.fault.PlatformConfigFault) {
--> text = "Failed to update port persistence location",
--> msg = "",
--> }
--> }
--> ],
--> msg = "",
--> }
…
…
2024-09-05T01:48:51.815Z info hostd[2481720] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 44089 : At least one corrupt resource metadata region was detected on volume 64a008f7-72af9518-93ea-b8599fef417c (<Datastore_name>). Other regions of the volume might be damaged too.
2024-09-05T01:48:51.815Z info hostd[2481720] [Originator@6876 sub=Hostsvc.VmkVprobSource] VmkVprobSource::Post event: (vim.event.EventEx) {
--> key = 90,
...
-->
2024-09-05T01:48:51.815Z info hostd[2481720] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 44090 : At least one corrupt resource metadata region was detected on volume 64a008f7-72af9518-93ea-b8599fef417c (mpkaussanc02_029). Other regions of the volume might be damaged too.
At the timestamp, vmkernel logs also recorded:
2024-09-05T01:48:51.774Z cpu2:4776106)WARNING: Res3: 7066: Volume 64a008f7-72af9518-93ea-b8599fef417c ("<Datastore_name>") might be damaged on the disk. Resource cluster metadata corruption has been detected.
2024-09-05T01:48:51.774Z cpu2:4776106)WARNING: FS3: 608: VMFS volume <Datastore_name>/64a008f7-72af9518-93ea-b8599fef417c on naa.600a098038314b43702b557865585a53:1 has been detected corrupted
2024-09-05T01:48:51.774Z cpu2:4776106)FS3: 610: While filing a PR, please report the names of all hosts that attach to this LUN, tests that were running on them,
2024-09-05T01:48:51.774Z cpu2:4776106)FS3: 634: and upload the dump by `voma -m vmfs -f dump -d /vmfs/devices/disks/naa.600a098038314b43702b557865585a53:1 -D X`
Reported error:
VMware vCenter Server
VMware vSphere ESXi
Workaround:
In order to resolve the volume corruption issue, please open a Support Request with the VMware by Broadcom's Storage team.