vCenter VC## is responding very slow with error "Some of the disks of the virtual machine VM## on host Host1 failed to load."
search cancel

vCenter VC## is responding very slow with error "Some of the disks of the virtual machine VM## on host Host1 failed to load."

book

Article ID: 405521

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:

  • On vCenter VM under Monitor>Events you may observe below events:

 

 

  • NFS datastore were vCenter VM is residing may report intermittent disconnections leading to datastore inaccessible state. This can be seen under NFS datastore>Monitor>Events

 

 

  • In /var/run/log/vmkernel.log you may see NFS datastore has undergone as APD (All path down) state with NFS server disconnections. 


2025-07-21T09:09:26.657Z: [vmfsCorrelator] 6276432978813us: [vob.vmfs.nfs.server.disconnect] Lost connection to the server ##.##.##.## mount point /DS1, mounted as########-########-0000-000000000000 ("DS1")
2025-07-21T09:09:26.657Z: [vmfsCorrelator] 6276541089343us: [esx.problem.vmfs.nfs.server.disconnect] ##.##.##.## /DS1 ########-########-0000-000000000000 DS1
2025-07-21T09:10:22.662Z: [APDCorrelator] 6276488982568us: [vob.storage.apd.timeout] Device or filesystem with identifier [########-########] has entered the All Paths Down Timeout state after being in the All Paths Down state for 140 seconds. I/Os will now be fast failed.
2025-07-21T09:10:22.662Z: [APDCorrelator] 6276597094095us: [esx.problem.storage.apd.timeout] Device or filesystem with identifier [########-########] has entered the All Paths Down Timeout state after being in the All Paths Down state for 140 seconds. I/Os will now be fast failed.
2025-07-21T09:11:57.499Z: [APDCorrelator] 6276583818014us: [vob.storage.apd.exit] Device or filesystem with identifier [########-########] has exited the All Paths Down state.
2025-07-21T09:11:57.499Z: [vmfsCorrelator] 6276583817875us: [vob.vmfs.nfs.server.restored] Restored connection to the server ##.##.##.## mount point /DS1, mounted as /########-########-0000-000000000000 ("DS1")

 

  • Packet capture from host using vmkernel port used for NFS traffic may report Duplicate IP address detected for NFS target.

pktcap-uw --vmk vmk2 --dir 2 -o - | tcpdump-uw -ner - | grep "NFS target IP ##.##.##.##"



Environment

VMware vSphere ESXi 7.0
VMware vSphere ESXi 8.0

Cause

Duplicate IP address detected on the NFS target IP causes intermittent NFS datastore disconnections leading to vCenter slowness.

Resolution

Engage storage vendor to resolve the duplicate IP address/conflict issues.

Powered by Wolken Software