進行 ASDK 疑難排解Troubleshoot the ASDK

本文提供 Azure Stack 開發套件 (ASDK) 的常見疑難排解資訊。This article provides common troubleshooting info for the Azure Stack Development Kit (ASDK). 如需 Azure Stack 整合式系統的說明,請參閱 Microsoft Azure Stack 疑難排解For help with Azure Stack integrated systems, see Microsoft Azure Stack troubleshooting.

因為 ASDK 屬於評估環境,因此 Microsoft 支援服務不會提供支援。Because the ASDK is an evaluation environment, Microsoft Support does not provide support. 如果您遇到未記載的問題,您可以從 Microsoft Q&For Azure Stack的專家取得協助。If you're experiencing an issue that isn't documented, you can get help from experts on Microsoft Q&A for Azure Stack.

部署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. 例如:For 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's been selected. ASDK 部署已成功,但當您選取視窗時,指令碼已暫停。The ASDK deployment has succeeded but the script was paused when selecting the window. 您可以尋找命令視窗標題列的「選取」字樣以驗證已完成安裝。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.

不允許範本驗證錯誤參數 osProfileTemplate validation error parameter osProfile is not allowed

如果您在範本驗證期間收到不允許 'osProfile' 參數的錯誤訊息,請確定您使用這些元件的正確 API 版本:If you get an error message during template validation that the parameter 'osProfile' is not allowed, make sure you are using the correct versions of the APIs for these components:

若要將 VHD 從 Azure 複製到 Azure Stack,請使用 AzCopy 7.3.0To copy a VHD from Azure to Azure Stack, use AzCopy 7.3.0. 與您的廠商合作,一起解決映像本身的問題。Work with your vendor to resolve issues with the image itself. 如需 Azure Stack 的 WALinuxAgent 需求詳細資訊,請參閱 Azure Linux 代理程式For more information about the WALinuxAgent requirements for Azure Stack, see Azure LinuX Agent.

因為缺少外部存取而部署失敗Deployment fails due to lack of external access

當部署在需要外部存取的階段失敗時,會傳回如下列範例的例外狀況:When deployment fails at stages where external access is required, an exception like the following example will be returned:

An error occurred while trying to test identity provider endpoints: System.Net.WebException: The operation has timed out.
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()at, <No file>: line 48 - 8/12/2018 2:40:08 AM

如果發生此錯誤,請檢閱部署網路流量文件,確定符合所有最低網路需求。If this error occurs, make sure all minimum networking requirements have been met by reviewing the deployment network traffic documentation. 另外也提供合作夥伴的網路檢查工具,作為協力廠商工具組的一部分。A network checker tool is also available for partners as part of the Partner Toolkit.

其他部署失敗通常是因為連線到網際網路上的資源時發生問題。Other deployment failures are typically due to problems connecting to resources on the Internet.

若要確認網際網路上資源的連線能力,您可以執行下列步驟:To verify connectivity to resources on the Internet, you can perform the following steps:

  1. 開啟 PowerShell。Open PowerShell.
  2. 進入 WAS01 或任何 ERC VM 的 PSSession。Enter-PSSession to the WAS01 or any of the ERCs VMs.
  3. 執行下列 Cmdlet:Run the following cmdlet:
    Test-NetConnection login.windows.net -port 443
    

如果此命令失敗,請確認 TOR 交換器和任何其他網路裝置已設定為允許網路流量If this command fails, verify the TOR switch and any other network devices are configured to allow network traffic.

虛擬機器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 don't automatically start

將您的主機重新開機之後,您可能會注意到 Azure Stack 服務並非立即可用。After rebooting your host, you may notice Azure Stack services aren't 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.

您可能也會注意到當 ASDK 主機重新開機之後,租用戶 VM 未自動重新啟動。You might also notice that tenant VMs don't automatically start after a reboot of the ASDK host. 您可以使用幾個手動步驟讓它們上線:You can bring them online with a few manual steps:

  1. 在 ASDK 主機上,從 [開始] 功能表啟動 [容錯移轉叢集管理員]。On the ASDK host, start Failover Cluster Manager from the Start Menu.
  2. 選取叢集 S-Cluster.azurestack.localSelect 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.

我已刪除某些 VM,但仍在磁碟上看到 VHD 檔案。I've deleted some VMs, but still see the VHD files on disk

這是設計預設的行為:This behavior is by design:

  • 當您刪除 VM 時,不會刪除 VHD。When you delete a VM, VHDs aren't deleted. 磁碟是資源群組中的獨立資源。Disks are separate resources in the resource group.
  • 刪除儲存體帳戶後,Azure Resource Manager 將會立即反映刪除情況,但其中可能包含的磁碟仍保留在儲存體中,直到執行記憶體回收為止。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's important to know if they're part of the folder for a storage account that was deleted. 若儲存體帳戶並未刪除,則 VHD 仍然存在就是正常情況。If the storage account wasn't deleted, it's normal that the VHDs remain.

您可以在管理儲存體帳戶中深入了解如何設定保留閾值與隨選回收。You can read more about configuring the retention threshold and on-demand reclamation in manage storage accounts.

儲存體Storage

儲存體回收Storage reclamation

已回收的容量最多可能需要 14 小時才會顯示在入口網站中。It can 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's 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