Symptoms

VxVerify runs several tests on each node by uploading a program (seen as a 'minion'), which includes 'df_service'.The 'df_service' test checks the local Service datastore available capacity on each node. The results of this health-check are listed as a health-check with one of the following results: Test ResultResult codeResult Interpretation Pass 0 The Service datastore is named correctly and has sufficient free capacity Warning 1 The Service datastore has under 25% available capacity remaining Failure 2 The Service datastore has under 15% available capacity remaining.Alternatively, the Service datastore does not match its expected name. Critical 3 This test has no critical result. Each test that passes is not listed in the summary report, for ease of reading.An example of the health-check output is shown below: #========================#======#=========#====================================================================#==============# | Hostname / Category |Status Dell_KB | Warnings or Failures, unless tests Passed ; Product S.N. | #========================#======#=========#====================================================================#==============# | node03 | Failure 181119 | df_service: Service datastore may have been renamed .|

Cause

The 'df_service' test checks the local Service datastore available capacity on each node. The Service capacity warning thresholds produce alerts when the percentage of free space gets low.If the 'service-datastore' has been renamed, or is missing, this test returns a failure, with the description: Service datastore may have been renamed The minion log entries in can be found in VxRail Manager, which lists details about this health-check. For example, /var/log/mystic/vxv/minion_lab-42-esxi-01.log ... 2024-06-11 12:27:39 INFO [df_service] Testing Service Datastore available capacity 2024-06-11 12:27:39 INFO Service DS path: /vmfs/volumes/8Y8Y1230000001-01-01-service-datastore1 2024-06-11 12:27:39 INFO Service Datastore is 37% used, from 319 GB ...

Resolution

Service Datastore available capacity Check the datastore list in the minion logs, in the VxVerify folder, looking at the statistics for the service-datastore. This can also be checked from the node, running the following command: df -m It may be necessary to free up more capacity by deleting older log, trace, and other temporary files. vSAN naming Navigate in vCenter > Storage > VxRail Datacenter > VxRail vSAN.The default name should be in the format: VxRail-Virtual-SAN-Datastore-<UUID> Example: VxRail-Virtual-SAN-Datastore-99d2e03d-4ce1-41a0-9820-c20fb1e5a9a2 Service Datastore naming The vSAN nodes should also have a default format: DExxxxx-01-01-service-datastore1 DE600180000001-01-01-service-datastore1 If this test marks up a renamed service datastore, then this should be renamed back to match the formatting above.This does not apply to the local datastore on Satellite nodes, which have a different naming format and should not be renamed.

Support Cases