Azure Stack 开发工具包 (ASDK) 故障排除Azure Stack Development Kit (ASDK) troubleshooting

本文提供 ASDK 的常见故障排除信息。This article provides common troubleshooting information for the ASDK. 如果本文未阐述你所遇到的问题,请务必查看 Azure Stack MSDN 论坛以获取更多帮助和信息。If you are experiencing an issue that is not documented, make sure to check the Azure Stack MSDN Forum for further assistance and information.

Important

由于 ASDK 是一个评估环境,因此我们不会通过 Azure 客户支持服务 (CSS) 提供官方支持。Because the ASDK is an evaluation environment, there is no official support offered through Azure Customer Support Services (CSS).

本部分针对故障排除问题提供的建议派生自多个来源,不保证能够解决具体的问题。The recommendations for troubleshooting issues that are described in this section are derived from several sources and may or may not resolve your particular issue. 代码示例按原样提供,不保证生成预期的结果。Code examples are provided "as is" and expected results cannot be guaranteed. 随着产品的不断改进,本部分的内容可能会频繁更新。This section is subject to frequent edits and updates as improvements to the product are implemented.

部署Deployment

部署失败Deployment failure

如果安装期间发生失败,可以使用部署脚本的 -rerun 选项从失败的步骤重新开始部署,如以下示例所示:If you experience a failure during installation, you can restart the deployment from the failed step by using the -rerun option of the deployment script as in the following example:

cd C:\CloudDeployment\Setup
.\InstallAzureStackPOC.ps1 -Rerun

部署结束时,PowerShell 会话仍保持打开状态,但不显示任何输出At the end of the deployment, the PowerShell session is still open and doesn't show any output

此行为可能是选择 PowerShell 命令窗口后的默认行为。This behavior is probably just the result of the default behavior of a PowerShell command window, when it has been selected. 开发工具包部署成功,但选择窗口时,脚本已暂停。The development kit deployment has succeeded but the script was paused when selecting the window. 可以通过在命令窗口的标题栏中查找“select”一词,来验证安装是否已完成。You can verify setup has completed by looking for the word "select" in the titlebar of the command window. 按 ESC 键取消选择窗口,然后即会显示完成消息。Press the ESC key to unselect it, and the completion message should be shown after it.

虚拟机Virtual machines

在 Azure Stack 中部署 VM 之前,必须先添加 Windows Server 映像和库项。A Windows Server image and gallery item must be added before deploying VMs in Azure Stack.

重启 Azure Stack 主机之后,某些 VM 可能不会自动启动。After restarting my Azure Stack host, some VMs may not automatically start.

将重新启动主机之后,可能会发现,Azure Stack 服务并非立即可用。After rebooting your host, you may notice Azure Stack services are not immediately available. 这是因为 Azure Stack 基础结构 VM 与 RP 需要花费一段时间来检查一致性,但最终会自动启动。This is because Azure Stack infrastructure VMs and RPs take some time to check consistency, but will eventually start automatically.

另外还可能发现,在重新启动 Azure Stack 开发工具包主机之后,租户 VM 不会自动启动。You may also notice that tenant VMs don't automatically start after a reboot of the Azure Stack development kit host. 这是一个已知问题,只需执行几个手动步骤就能让它们联机:This is a known issue, and just requires a few manual steps to bring them online:

  1. 在 Azure Stack 开发工具包主机上,从“开始”菜单启动“故障转移群集管理器”。 On the Azure Stack development kit host, start Failover Cluster Manager from the Start Menu.
  2. 选择群集“S-Cluster.azurestack.local”。 Select the cluster S-Cluster.azurestack.local.
  3. 选择“角色” 。Select Roles.
  4. 租户 VM 显示为“已保存”状态。 Tenant VMs appear in a saved state. 所有基础结构 VM 运行后,右键单击租户 VM,并选择“启动”以恢复该 VM。 Once all Infrastructure VMs are running, right-click the tenant VMs and select Start to resume the VM.

我已删除某些虚拟机,但仍在磁盘上看到 VHD 文件。I have deleted some virtual machines, but still see the VHD files on disk. 这是预期行为吗?Is this behavior expected?

是的,这是预期行为。Yes, this is behavior expected. 设计此行为的原因如下:It was designed this way because:

  • 删除 VM 时,不会删除 VHD。When you delete a VM, VHDs are not deleted. 磁盘是资源组中的独立资源。Disks are separate resources in the resource group.
  • 删除存储帐户后,Azure 资源管理器会立即反映删除结果,但其中的磁盘仍保留在存储中,直到运行垃圾收集为止。When a storage account gets deleted, the deletion is visible immediately through Azure Resource Manager, but the disks it may contain are still kept in storage until garbage collection runs.

如果看到“孤立的”VHD,必须知道它们是否包含在已删除的存储帐户的文件夹中。If you see "orphan" VHDs, it is important to know if they are part of the folder for a storage account that was deleted. 如果未删除存储帐户,则正常情况下,这些 VHD 仍在存储帐户中。If the storage account was not deleted, it's normal they are still there.

可以在管理存储帐户中详细了解如何配置保留阈值和按需回收。You can read more about configuring the retention threshold and on-demand reclamation in manage storage accounts.

存储Storage

存储回收Storage reclamation

回收的容量最长可能需要在 14 小时后才显示在门户中。It may take up to 14 hours for reclaimed capacity to show up in the portal. 空间回收取决于多种因素,包括块 Blob 存储中内部容器文件的用量百分比。Space reclamation depends on various factors including usage percentage of internal container files in block blob store. 因此,我们无法保证运行垃圾收集器时可回收的空间量,这取决于删除的数据量。Therefore, depending on how much data is deleted, there is no guarantee on the amount of space that could be reclaimed when garbage collector runs.

后续步骤Next steps

访问 Azure Stack 支持论坛Visit the Azure Stack support forum