vSAN File service fails to enable on newly added host.
Article ID: 439641
Updated On:
Products
Issue/Introduction
After adding a new host to an existing vSAN OSA cluster, the following behaviors are observed:
- From vSAN skyline health, alarm for "
File Service is not enabled"
- vSphere DRS may refuses to migrate Virtual Machines to the new host automatically.
- If VMs are manually migrated to the host, DRS may immediately triggers an evacuation to move them back to other nodes.
- Clicking Remediate File Service or attempting to toggle the vSAN File service at the cluster level may fails to resolve the status for the new node.
Environment
VMware ESXi 8.x
Cause
The failure is due to a configuration mismatch where the new compute-only host lacks the local disk group required to deploy a mandatory vSAN File Service Node (FSN). Because the host cannot support this cluster-wide service, vSphere DRS automatically evacuates all VMs from the node to maintain service integrity and compliance.
Resolution
To resolve this configuration mismatch, choose one of the following two methods based on your hardware availability and business requirements:
Method 1: Add Storage to the Host
If the host is intended to participate fully in the vSAN cluster:
- Install the required number of Flash/HDD devices into the new host.
- Navigate to the vSphere Client > Cluster > Configure > vSAN > Disk Management.
- Create a new Disk Group on the host.
- Once the host contributes storage to the vSAN Datastore, navigate to Skyline Health and select Remediate File Service. The FSN appliance will deploy successfully.
Method 2: Disable vSAN File Service
If the host must remain a compute-only node, the vSAN File Service cannot be supported on the current cluster configuration:
- Navigate to Cluster > Configure > vSAN > Services.
- Locate File Service and click Disable.
Note: This will remove all existing File Service Nodes and any configured File Shares. Only perform this if file services are no longer required for the environment.
Feedback
