vSAN File Service Node does not start
Article ID: 425939
Updated On:
Products
Issue/Introduction
After replacing the failed vSAN capacity disk and adding the disk to the vSAN disk group, the vSAN File Service Node on that host fails to start.
- The following log message is repeatedly output in the vCenter event log:
Agent cannot be provisioned due to insufficient resources on host "ESXi hostname" (vsan-file-services)
Environment
vSAN 8.0
Cause
The vSAN File Service Node virtual machine can not start because it does not have the required vmdk file.
vSAN File Service Node is created on each host in the vSAN cluster, with a "number of failures to tolerate" of "0" (RAID-0).
As a result, in the event of a vSAN disk failure, the vSAN File Service Node objects located on that disk will be lost.
Example
Normal
/vmfs/volumes/<vsandatastore>/<objectUUID>/vSAN File Service Node (8)-000001.vmdk (Exists)
/vmfs/volumes/<vsandatastore>/<objectUUID>/vSAN File Service Node (8)_1-000001.vmdk (Exists)
/vmfs/volumes/<vsandatastore>/<objectUUID>/vSAN File Service Node (8)_2-000001.vmdk (Exists)
/vmfs/volumes/<vsandatastore>/<objectUUID>/vSAN File Service Node (8)_1.vmdk (Exists)
/vmfs/volumes/<vsandatastore>/<objectUUID>/vSAN File Service Node (8).vmdk (Exists)
/vmfs/volumes/<vsandatastore>/<objectUUID>/vSAN File Service Node (8)_2.vmdk (Exists)
After a failure occured
/vmfs/volumes/<vsandatastore>/<objectUUID>/vSAN File Service Node (8)-000001.vmdk (Exists)
/vmfs/volumes/<vsandatastore>/<objectUUID>/vSAN File Service Node (8)_2-000001.vmdk (Exists)
/vmfs/volumes/<vsandatastore>/<objectUUID>/vSAN File Service Node (8).vmdk (Exists)
/vmfs/volumes/<vsandatastore>/<objectUUID>/vSAN File Service Node (8)_2.vmdk (Exists)
-> vSAN File Service Node (8)_1.vmdk and vSAN File Service The object for Node (8)_1-000001.vmdk do not exist.
Resolution
Recreate the vSAN File Service Node by the following steps.
1. Perform "Remove from Inventory" on the target vSAN File Service Node (#).
If "Remove from Inventory" is grayed out and can not be selected, place the host into maintenance mode.
After entering maintenance mode, the node will become inaccessible, so perform "Remove from Inventory".
After "Remove from Inventory", exit the maintenance mode.
2. Perform "REMEDIATE FILE SERVICE" from the vSAN Health Infrastructure Health troubleshooting screen.
3. Confirm that a new vSAN File Service Node (#) (this may differ from the original number) has been created and started on the host.
4. If the old vSAN File Service Node (#) directory still exists, delete it.
Go to vCenter Client -> Storage -> vSAN Datastore -> Files -> and check if the old vSAN File Service Node (#) directory still exists.
If it remains, check the directory and delete it.
Additional Information
Feedback
