Hi ,,
when I run the command to test cluster config, it get error as below, it say cannot confim FabricDataRoot system drive. but I have defined the FabricDataRoot value at clusterConfig.json.
pls help .
Thanks.
PS C:\D365Install\Microsoft.Azure.ServiceFabric.WindowsServer.8.2.1571.9590> .\TestConfiguration.ps1 -ClusterConfigFilePath .\ClusterConfig.json
Trace folder already exists. Traces will be written to existing trace folder: C:\D365Install\Microsoft.Azure.ServiceFabric.WindowsServer.8.2.1571.9590\DeploymentTraces
Running Best Practices Analyzer...
Opening TraceWriter SFDeployer, path C:\D365Install\Microsoft.Azure.ServiceFabric.WindowsServer.8.2.1571.9590\DeploymentTraces\SFDeployer-637862273938616676.trace
FabricSettings FabricDataRoot system drive could not be confirmed for machine 192.168.99.5.
FabricSettings FabricDataRoot system drive could not be confirmed for machine 192.168.99.9.
FabricSettings FabricDataRoot system drive could not be confirmed for machine 192.168.99.7.
FabricSettings FabricDataRoot system drive could not be confirmed for machine 192.168.99.6.
FabricSettings FabricDataRoot system drive could not be confirmed for machine 192.168.99.11.
FabricSettings FabricDataRoot system drive could not be confirmed for machine 192.168.99.12.
System drive for FabricDataRoot could not be confirmed for a machine in the configuration. See DeploymentTraces for details.
Best Practices Analyzer determined environment has an issue. Please see additional BPA log output in DeploymentTraces folder.
Closing TraceWriter SFDeployer, path C:\D365Install\Microsoft.Azure.ServiceFabric.WindowsServer.8.2.1571.9590\DeploymentTraces\SFDeployer-637862273938616676.trace
LocalAdminPrivilege : True
IsJsonValid : True
IsCabValid :
RequiredPortsOpen : True
RemoteRegistryAvailable : True
FirewallAvailable : True
RpcCheckPassed : True
NoDomainController : True
NoConflictingInstallations : True
FabricInstallable : True
DataDrivesAvailable : False
DrivesEnoughAvailableSpace :
Passed : False
Test Config failed with exception: System.InvalidOperationException: Best Practices Analyzer determined environment has an issue. Please see additional BPA log output in DeploymentTraces folder.
at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
clusterConfig.json :
"name": "Setup",
"parameters": [
{
"name": "FabricDataRoot",
"value": "C:\\SF"
},
{
"name": "FabricLogRoot",
"value": "C:\\SF\\Log"
Trace log:
2022/04/22-04:55:24.611,Info,5452,SystemFabricDeployer.SFDeployer,Running Best Practices Analyzer...
2022/04/22-04:55:24.627,Verbose,5452,SystemFabricDeployer.SFDeployer,Validating executing user is an Administrator.
2022/04/22-04:55:24.627,Verbose,5452,SystemFabricDeployer.SFDeployer,Converting JSON config to model.
2022/04/22-04:55:24.861,Info,5452,ImageBuilder.FabricDeployer,Host name: Orch01.
2022/04/22-04:55:24.861,Info,5452,ImageBuilder.FabricDeployer,Network interface ip address: fe80::b003:3f9e:2982:2c5%4.
2022/04/22-04:55:24.861,Info,5452,ImageBuilder.FabricDeployer,Network interface ip address: 192.168.99.7.
2022/04/22-04:55:24.861,Info,5452,ImageBuilder.FabricDeployer,Network interface ip address: ::1.
2022/04/22-04:55:24.861,Info,5452,ImageBuilder.FabricDeployer,Network interface ip address: 127.0.0.1.
2022/04/22-04:55:24.861,Info,5452,ImageBuilder.FabricDeployer,Network interface ip address: fe80::5efe:192.168.99.7%2.
2022/04/22-04:55:26.168,Verbose,5452,SystemFabricDeployer.SFDeployer,Validating machines are reachable and have opened required ports.
2022/04/22-04:55:26.168,Verbose,5452,SystemFabricDeployer.SFDeployer,Using IPv4 address for 192.168.99.8
2022/04/22-04:55:26.168,Verbose,3628,SystemFabricDeployer.SFDeployer,Using IPv4 address for 192.168.99.5
2022/04/22-04:55:26.168,Verbose,3100,SystemFabricDeployer.SFDeployer,Using IPv4 address for 192.168.99.9
2022/04/22-04:55:26.168,Verbose,3100,SystemFabricDeployer.SFDeployer,Using IPv4 address for 192.168.99.6
2022/04/22-04:55:26.168,Verbose,5452,SystemFabricDeployer.SFDeployer,Using IPv4 address for 192.168.99.7
2022/04/22-04:55:26.183,Verbose,5452,SystemFabricDeployer.SFDeployer,Using IPv4 address for 192.168.99.11
2022/04/22-04:55:26.183,Verbose,3628,SystemFabricDeployer.SFDeployer,Using IPv4 address for 192.168.99.12
2022/04/22-04:55:26.183,Verbose,5452,SystemFabricDeployer.SFDeployer,Validating each machine has RemoteRegistry service enabled.
2022/04/22-04:55:26.215,Verbose,5452,SystemFabricDeployer.SFDeployer,Validating each machine has Windows Firewall MpsSvc service enabled.
2022/04/22-04:55:26.246,Verbose,5452,SystemFabricDeployer.SFDeployer,Verifying remote procedure call access against cluster machines.
2022/04/22-04:55:26.277,Verbose,5452,SystemFabricDeployer.SFDeployer,Validating against installation conflicts on each machine.
2022/04/22-04:55:26.528,Verbose,5452,SystemFabricDeployer.SFDeployer,Validating Fabric is not already set up on target machines.
2022/04/22-04:55:26.528,Verbose,5452,SystemFabricDeployer.SFDeployer,Validating Fabric is not already installed or configured on machine 192.168.99.8.
2022/04/22-04:55:26.528,Verbose,3100,SystemFabricDeployer.SFDeployer,Validating Fabric is not already installed or configured on machine 192.168.99.6.
2022/04/22-04:55:26.528,Verbose,3628,SystemFabricDeployer.SFDeployer,Validating Fabric is not already installed or configured on machine 192.168.99.12.
2022/04/22-04:55:26.528,Verbose,5452,SystemFabricDeployer.SFDeployer,IsFabricInstalled on machine 192.168.99.8 hit FabricException. Proceeding anyway. Details: FabricDataRoot is not provided or properly set..
2022/04/22-04:55:26.528,Verbose,5452,SystemFabricDeployer.SFDeployer,Fabric is set up on machine 192.168.99.8: False
2022/04/22-04:55:26.528,Verbose,3100,SystemFabricDeployer.SFDeployer,IsFabricInstalled on machine 192.168.99.6 hit FabricException. Proceeding anyway. Details: FabricDataRoot is not provided or properly set..
2022/04/22-04:55:26.528,Verbose,3100,SystemFabricDeployer.SFDeployer,Fabric is set up on machine 192.168.99.6: False
2022/04/22-04:55:26.528,Verbose,3628,SystemFabricDeployer.SFDeployer,IsFabricInstalled on machine 192.168.99.12 hit FabricException. Proceeding anyway. Details: FabricDataRoot is not provided or properly set..
2022/04/22-04:55:26.528,Verbose,3628,SystemFabricDeployer.SFDeployer,Fabric is set up on machine 192.168.99.12: False
2022/04/22-04:55:26.528,Verbose,3628,SystemFabricDeployer.SFDeployer,Validating Fabric is not already installed or configured on machine 192.168.99.5.
2022/04/22-04:55:26.543,Verbose,3628,SystemFabricDeployer.SFDeployer,IsFabricInstalled on machine 192.168.99.5 hit FabricException. Proceeding anyway. Details: FabricDataRoot is not provided or properly set..
2022/04/22-04:55:26.543,Verbose,3628,SystemFabricDeployer.SFDeployer,Fabric is set up on machine 192.168.99.5: False
2022/04/22-04:55:26.543,Verbose,3100,SystemFabricDeployer.SFDeployer,Validating Fabric is not already installed or configured on machine 192.168.99.7.
2022/04/22-04:55:26.543,Verbose,3100,SystemFabricDeployer.SFDeployer,IsFabricInstalled on machine 192.168.99.7 hit FabricException. Proceeding anyway. Details: FabricDataRoot is not provided or properly set..
2022/04/22-04:55:26.543,Verbose,3100,SystemFabricDeployer.SFDeployer,Fabric is set up on machine 192.168.99.7: False
2022/04/22-04:55:26.543,Verbose,3100,SystemFabricDeployer.SFDeployer,Validating Fabric is not already installed or configured on machine 192.168.99.11.
2022/04/22-04:55:26.543,Verbose,3100,SystemFabricDeployer.SFDeployer,IsFabricInstalled on machine 192.168.99.11 hit FabricException. Proceeding anyway. Details: FabricDataRoot is not provided or properly set..
2022/04/22-04:55:26.543,Verbose,3100,SystemFabricDeployer.SFDeployer,Fabric is set up on machine 192.168.99.11: False
2022/04/22-04:55:26.559,Verbose,3628,SystemFabricDeployer.SFDeployer,Validating Fabric is not already installed or configured on machine 192.168.99.9.
2022/04/22-04:55:26.559,Verbose,3628,SystemFabricDeployer.SFDeployer,IsFabricInstalled on machine 192.168.99.9 hit FabricException. Proceeding anyway. Details: FabricDataRoot is not provided or properly set..
2022/04/22-04:55:26.559,Verbose,3628,SystemFabricDeployer.SFDeployer,Fabric is set up on machine 192.168.99.9: False
2022/04/22-04:55:26.606,Error,3100,SystemFabricDeployer.SFDeployer,FabricSettings FabricDataRoot system drive could not be confirmed for machine 192.168.99.9.
2022/04/22-04:55:26.606,Error,5452,SystemFabricDeployer.SFDeployer,FabricSettings FabricDataRoot system drive could not be confirmed for machine 192.168.99.8.
2022/04/22-04:55:26.606,Error,3628,SystemFabricDeployer.SFDeployer,FabricSettings FabricDataRoot system drive could not be confirmed for machine 192.168.99.5.
2022/04/22-04:55:26.637,Error,3100,SystemFabricDeployer.SFDeployer,FabricSettings FabricDataRoot system drive could not be confirmed for machine 192.168.99.6.
2022/04/22-04:55:26.637,Error,3628,SystemFabricDeployer.SFDeployer,FabricSettings FabricDataRoot system drive could not be confirmed for machine 192.168.99.12.
2022/04/22-04:55:26.637,Error,5452,SystemFabricDeployer.SFDeployer,FabricSettings FabricDataRoot system drive could not be confirmed for machine 192.168.99.11.
2022/04/22-04:55:26.653,Error,5452,SystemFabricDeployer.SFDeployer,System drive for FabricDataRoot could not be confirmed for a machine in the configuration. See DeploymentTraces for details.
2022/04/22-04:55:26.653,Error,5452,SystemFabricDeployer.SFDeployer,Best Practices Analyzer determined environment has an issue. Please see additional BPA log output in DeploymentTraces folder.
