vSAN host disconnected and VMs are inaccessible
Article ID: 413669
Updated On:
Products
Issue/Introduction
A single host in the cluster shows as disconnected while uptime shows a reboot within the last day. At the same time, VMs show as inaccessible. Further investigation will confirm the backing vSAN objects are inaccessible as well. This can be viewed in vCenter Skyline health, should vCenter be accessible.
Environment
vSAN 7.x
vSAN 8.x
Cause
Reviewing vSAN virtual objects and placement details, it shows only one active vSAN component, which indicates loss of quorum and thus an inaccessible object.
In the image below, Component State shows the following
- Absent - resyncing - This indicates this component was resyncing when it became absent. This is also known as being stale.
- Absent - This indicates that, given the last known component placement (the physical vSAN disk it was stored on), the component is not currently accessible to vSAN.
Given the disconnected host with a recent reboot, and the state of the components, it can be deduced that two separate events occurred leading to the two component states above. Investigating the "Absent" component, we find the owning host is in a Decom state (Event 1). The "Absent - resyncing" state of the second component proves that at some point, during the resync, Event 1 occurred which caused Event 2 - "Absent - resyncing" state.
Resolution
- Identify the Absent component and its owning host. Follow KB vSAN objects unhealthy due to DECOM state to remove the host Decom state.
- Reconnect the disconnected host.
Additional Information
For further analysis and assistance in understanding these states when confronted with a situation as this issue, please contact support.
Feedback
