Azure堆栈部署在步骤18失败 [英] Azure Stack Deployment Failing at Step 18
问题描述
2插槽6核Intel CPU服务器
96GB内存
1 SSD 500GB（操作系统驱动器）
4每个连接到板载SATA控制器的2TB磁盘（未启用RAID）
磁盘显示如下：
PS C：\CloudDeployment\Configuration> Get-Disk |选择Number，FriendlyName，OperationalStatus，Size，PartitionStyle，BusType |排序号码ft -Autosize
Number FriendlyName       OperationalStatus的          Size PartitionStyle BusType
------ ------------ ;       -----------------          ---- -------------- -------
0三星SSD 850 EVO M.2 500GB在线 500107862016 MBR SATA
1 ST2000LM003 HN-M201RAD 在线            2000398934016 GPT
SATA
2 ST2000LM003 HN-M201RAD           在线            2000398934016 GPT
SATA
3 ST2000LM003 HN-M201RAD 在线            2000398934016 GPT
SATA
4 ST2000LM003 HN-M201RAD           在线            2000398934016 GPT
SATA
5 MSFT虚拟磁盘                       &NBSP ;   在线            
128849018880 MBR 文件支持虚拟
MAS部署在以下步骤失败：0.18错误：
VERBOSE：已成功创建存储群集S群集。 - 12/7/2016 11:11:37 AM
VERBOSE：等待群集上线。 - 12/7/2016 11:11:37 AM
VERBOSE：存储集群S-Cluster现已上线。 - 12/7/2016 11:11:41 AM
VERBOSE：开始使用群集FQDN。 - 12/7/2016 11:11:41 AM
VERBOSE：群集FQDN - S-Cluster.AzureStack.local。 - 12/7/2016 11:11:41 AM
VERBOSE：设置每个群集网络的角色。 - 12/7/2016 11:11:41 AM
VERBOSE：设置群集存储子系统默认属性 - 2016年12月7日上午11:11:41 VER
VERBOSE ：尝试建立到群集的CIM会话 - 12/7/2016 11:11:41 AM
VERBOSE：检查存储提供程序是否已注册到群集。 - 12/7/2016 11:11:41 AM
VERBOSE：连接到SMAPI集群存储子系统 - 12/7/2016 11:11:42 AM
VERBOSE ：检索聚簇子系统名称。 - 12/7/2016 11:11:42 AM
VERBOSE：开始诊断记录。 - 12/7/2016 11:11:43 AM
VERBOSE：删除已建立的集群CIM会话 - 2016年12月7日上午11:11:45
VERBOSE：在创建池/卷之前清除任何过时的存储配置。 - 12/7/2016 11:11:45 AM
VERBOSE：找不到陈旧的游泳池。 - 12/7/2016 11:11:45 AM
VERBOSE：建立集群的CIM会话... - 2016年12月7日上午11:11:45
VERBOSE：建立到群集的JEA PowerShell会话 - 2016年12月12日上午11:11:45由于
VERBOSE：启用Storage Space Direct - 12/7/2016 11:11:48 AM
VERBOSE： - 在此单节点环境中跳过S2D缓存资格磁盘检查。 - 12/7/2016 11:11:48 AM
警告：S-Cluster.AzureStack.local：2016/12 / 07-11：11：55.210节点WIN-7M4K20TKMJD：否发现用于S2D的支持总线类型的磁盘
- 12/7/2016 11:11:55 AM
Invoke-EceAction：任务：调用角色"Cloud\Inrastructure"\\Storage"的界面"部署"失败：
模块'Roles \Storage\Storage.psm1'中的函数'DeployStorage'引发了异常：
无法启用Storage Spaces Direct
在C：\ CloudDeployment \Roles \Storage \Storage.psm1：320 。
+ 跟踪错误"无法启用存储空间直接"在跟踪错误时为
，C：\CloudDeployment \ Common \ Tracer.psm1：第52行为
at DeployStorage，C：\CloudDeployment \Roles \Storage \Storage.psm1：第320行，
at< ScriptBlock>，< No file> ;:tline 18 - 12/7/2016 11 ：11：55 AM
在C：\ CloudDeployment\Configuration\InstallAzureStackPOC.ps1：353 char：1
+ Invoke-EceAction -RolePath Cloud -ActionType Deployment -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo ：OperationStopped :(无法启用... Spaces Direct"：String）[Invoke-EceAction]，例外
+ FullyQualifiedErrorId：无法直接启用存储空间
在C：\ CloudDeployment \Roles \Storage \Storage.psm1：320。
+ &NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;跟踪错误"无法启用存储空间直接"，CloudEngine.Cmdlets.InvokeCmdlet
VERBOSE：步骤：步骤状态'（STO）配置存储群集'是'错误"。 - 12/7/2016 11:11:55 AM
Invoke-EceAction：操作：调用步骤0.18失败。停止调用行动计划。 - 12/7/2016 11:11:55 AM
在C：\ CloudDeployment\Configuration\InstallAzureStackPOC.ps1：353 char：1
+ Invoke- EceAction -RolePath Cloud -ActionType Deployment -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo ：InvalidOperation：（:) [Invoke-EceAction]，例外情况
+ FullyQualifiedErrorId：未指定错误，CloudEngine.Cmdlets.InvokeCmdlet
VERBOSE：操作："部署 - 阶段0-DeployBareMetalAndBGPAndNAT"的状态为"错误"。 - 12/7/2016 11:11:55 AM
完成：任务云 - 部署 - 阶段0-DeployBareMetalAndBGPAndNAT
VERBOSE：任务：行动状态'部署 - 阶段0- DeployBareMetalAndBGPAndNAT'角色'Cloud'是'错误'。 - 12/7/2016 11:11:55 AM
VERBOSE：步骤：步骤'阶段0 - 配置物理机和外部网络'的状态为'错误'。 - 12/7/2016 11:11:55 AM
Invoke-EceAction：操作：调用步骤0失败。停止调用行动计划。 - 12/7/2016 11:11:55 AM
在C：\ CloudDeployment\Configuration\InstallAzureStackPOC.ps1：353 char：1
+ Invoke- EceAction -RolePath Cloud -ActionType Deployment -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo ：InvalidOperation：（:) [Invoke-EceAction]，例外情况
+ FullyQualifiedErrorId：未指定的错误，CloudEngine.Cmdlets.InvokeCmdlet
预部署检查脚本示出了如健康和没有问题的磁盘
由于在提前支持，
Charles
Charles A. Windom Sr。
Hello，
的我们正在检查查询并且会很快就会回复你。
为此带来的不便深表歉意，并感谢您在这件事上的时间和耐心。
问候，
与Pradeep
2 socket 6 core Intel CPU server
96GB of RAM
1 SSD 500GB (OS drive)
4 each 2TB disks connected to on-board SATA controller (No RAID enabled)
Disk show up as following:
PS C:\CloudDeployment\Configuration> Get-Disk | select Number, FriendlyName, OperationalStatus, Size, PartitionStyle, BusType | sort Number | ft -Autosize
Number FriendlyName OperationalStatus Size PartitionStyle BusType
------ ------------ ----------------- ---- -------------- -------
0 Samsung SSD 850 EVO M.2 500GB Online 500107862016 MBR SATA
1 ST2000LM003 HN-M201RAD Online 2000398934016 GPT
SATA
2 ST2000LM003 HN-M201RAD Online 2000398934016 GPT
SATA
3 ST2000LM003 HN-M201RAD Online 2000398934016 GPT
SATA
4 ST2000LM003 HN-M201RAD Online 2000398934016 GPT
SATA
5 Msft Virtual Disk Online
128849018880 MBR File Backed Virtual
MAS deployment is failing at the following step: 0.18 error is:
VERBOSE: Storage Cluster S-Cluster has been created successfully. - 12/7/2016 11:11:37 AM
VERBOSE: Waiting for the cluster to come online. - 12/7/2016 11:11:37 AM
VERBOSE: Storage Cluster S-Cluster is now online. - 12/7/2016 11:11:41 AM
VERBOSE: Start using the cluster FQDN. - 12/7/2016 11:11:41 AM
VERBOSE: Cluster FQDN - S-Cluster.AzureStack.local. - 12/7/2016 11:11:41 AM
VERBOSE: Set the roles for each cluster network. - 12/7/2016 11:11:41 AM
VERBOSE: Set the cluster storage subsystem default properties - 12/7/2016 11:11:41 AM
VERBOSE: Trying to establish a CIM Session to the cluster - 12/7/2016 11:11:41 AM
VERBOSE: Check if storage provider is already registered to the cluster. - 12/7/2016 11:11:41 AM
VERBOSE: Connecting to the SMAPI Clustered storage subsystem - 12/7/2016 11:11:42 AM
VERBOSE: Retrieving the clustered subsytem name. - 12/7/2016 11:11:42 AM
VERBOSE: Start the diagnostic logging. - 12/7/2016 11:11:43 AM
VERBOSE: Remove the Cluster CIM Session that has been established - 12/7/2016 11:11:45 AM
VERBOSE: Clean up any stale storage configuration before creating the pools/volumes. - 12/7/2016 11:11:45 AM
VERBOSE: No stale pool(s) found. - 12/7/2016 11:11:45 AM
VERBOSE: Establishing a CIM Session to the cluster... - 12/7/2016 11:11:45 AM
VERBOSE: Establishing a JEA PowerShell session to the cluster - 12/7/2016 11:11:45 AM
VERBOSE: Enable Storage Space Direct - 12/7/2016 11:11:48 AM
VERBOSE: - Skipping the S2D cache eligibility disk checks in this one-node environment. - 12/7/2016 11:11:48 AM
WARNING: S-Cluster.AzureStack.local: 2016/12/07-11:11:55.210 Node WIN-7M4K20TKMJD: No disks with supported bus types found to be used for S2D
- 12/7/2016 11:11:55 AM
Invoke-EceAction : Task: Invocation of interface 'Deployment' of role 'Cloud\Infrastructure\Storage' failed:
Function 'DeployStorage' in module 'Roles\Storage\Storage.psm1' raised an exception:
Failed to enable Storage Spaces Direct
At C:\CloudDeployment\Roles\Storage\Storage.psm1:320.
+ Trace-Error "Failed to enable Storage Spaces Direct"
at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 52
at DeployStorage, C:\CloudDeployment\Roles\Storage\Storage.psm1: line 320
at <ScriptBlock>, <No file>: line 18 - 12/7/2016 11:11:55 AM
At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:353 char:1
+ Invoke-EceAction -RolePath Cloud -ActionType Deployment -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (Failed to enabl... Spaces Direct":String) [Invoke-EceAction], Exception
+ FullyQualifiedErrorId : Failed to enable Storage Spaces Direct
At C:\CloudDeployment\Roles\Storage\Storage.psm1:320.
+ Trace-Error "Failed to enable Storage Spaces Direct",CloudEngine.Cmdlets.InvokeCmdlet
VERBOSE: Step: Status of step '(STO) Configure Storage Cluster' is 'Error'. - 12/7/2016 11:11:55 AM
Invoke-EceAction : Action: Invocation of step 0.18 failed. Stopping invocation of action plan. - 12/7/2016 11:11:55 AM
At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:353 char:1
+ Invoke-EceAction -RolePath Cloud -ActionType Deployment -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Invoke-EceAction], Exception
+ FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet
VERBOSE: Action: Status of 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' is 'Error'. - 12/7/2016 11:11:55 AM
COMPLETE: Task Cloud - Deployment-Phase0-DeployBareMetalAndBGPAndNAT
VERBOSE: Task: Status of action 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' of role 'Cloud' is 'Error'. - 12/7/2016 11:11:55 AM
VERBOSE: Step: Status of step 'Phase 0 - Configure physical machine and external networking' is 'Error'. - 12/7/2016 11:11:55 AM
Invoke-EceAction : Action: Invocation of step 0 failed. Stopping invocation of action plan. - 12/7/2016 11:11:55 AM
At C:\CloudDeployment\Configuration\InstallAzureStackPOC.ps1:353 char:1
+ Invoke-EceAction -RolePath Cloud -ActionType Deployment -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Invoke-EceAction], Exception
+ FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet
Pre-Deployment checker script shows the disks as healthy and with no issues.
Thanks In Advance For Your Support,
Charles
Charles A. Windom Sr.
Hello,
We are checking on the query and would get back to you soon on this.
Apologize for the inconvenience and appreciate your time and patience in this matter.
Regards,
Pradeep
这篇关于Azure堆栈部署在步骤18失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
