locked
ASDK install - 'AzS-DC01' failed to start RRS feed

  • Question

  • As part of the ASDK install process - running asdk-installer.ps1 I get the error shown below. I have confirmed I can start a VM using a copy of the same vhd and using the same settings but the one deployed as part of the asdk-installer.ps1 process failed to start as below. Previoulsy ran older version of ASDK on this hardware successfully.

    Type 'Deployment' of Role 'Domain' raised an exception:

    'AzS-DC01' failed to start.
    'AzS-DC01' could not initialize.
    Failed to create partition: The hypervisor could not perform the operation because an invalid parameter was specified. (0xC0350005).
    'AzS-DC01' failed to start. (Virtual machine ID 17074F58-9A22-4D30-8AFF-8956AFA881DC)
    'AzS-DC01' failed to start worker process: The hypervisor could not perform the operation because an invalid parameter was specified. (0xC0350005). (Virtual machine ID 17074F58-9A22-4D30-8AFF-8956AFA881DC)
    'AzS-DC01' could not initialize. (Virtual machine ID 17074F58-9A22-4D30-8AFF-8956AFA881DC)
    Failed to create partition: The hypervisor could not perform the operation because an invalid parameter was specified. (0xC0350005).
    at New-ManagementVM, C:\Program Files\WindowsPowerShell\Modules\NewManagementVM\NewManagementVM.psm1: line 510
    at DeployOneVM, C:\CloudDeployment\Classes\Common\Image\VirtualMachineRole.psm1: line 1415
    at DeployVms, C:\CloudDeployment\Classes\Common\Image\VirtualMachineRole.psm1: line 1596
    at Deployment, C:\CloudDeployment\Classes\Common\Image\VirtualMachineRole.psm1: line 1695
    at <ScriptBlock>, <No file>: line 39
    at <ScriptBlock>, <No file>: line 37
    2018-10-03 09:57:30 Verbose  Step: Status of step 'PhysicalMachineAndInitialConfiguration.15 - (DEP) Deploy AD Virtual Machine' is 'Error'.
    2018-10-03 09:57:30 Verbose  Checking if any of the in progress steps are complete. The following steps are currently in progress: 'PhysicalMachineAndInitialConfiguration.15'.
    2018-10-03 09:57:30 Verbose  Action: Action plan 'Deployment-Phase0-DeployBareMetal' failed. Finish running all steps that are currently in progress before exiting.
    2018-10-03 09:57:30 Verbose  Draining all steps that are still in progress. The following steps are still in progress or just completed: 'PhysicalMachineAndInitialConfiguration.15'.
    2018-10-03 09:57:30 Verbose  Action: Action plan 'Deployment-Phase0-DeployBareMetal' failed.
    2018-10-03 09:57:30 Error    Action: Invocation of step PhysicalMachineAndInitialConfiguration.15 failed. Stopping invocation of action plan.
    2018-10-03 09:57:30 Verbose  Action: Status of 'Deployment-Phase0-DeployBareMetal' is 'Error'.
    2018-10-03 09:57:30 Verbose  Task: Status of action 'Deployment-Phase0-DeployBareMetal' of role 'Cloud' is 'Error'.
    2018-10-03 09:57:30 Verbose  Step: Status of step 'PhysicalMachineAndInitialConfiguration - Phase 0 - Configure physical machine and external networking' is 'Error'.
    2018-10-03 09:57:30 Verbose  Checking if any of the in progress steps are complete. The following steps are currently in progress: 'PhysicalMachineAndInitialConfiguration'.
    2018-10-03 09:57:30 Verbose  Action: Action plan 'Deployment' failed. Finish running all steps that are currently in progress before exiting.
    2018-10-03 09:57:30 Verbose  Draining all steps that are still in progress. The following steps are still in progress or just completed: 'PhysicalMachineAndInitialConfiguration'.
    2018-10-03 09:57:30 Verbose  Action: Action plan 'Deployment' failed.
    2018-10-03 09:57:30 Error    Action: Invocation of step PhysicalMachineAndInitialConfiguration failed. Stopping invocation of action plan.

    Wednesday, October 3, 2018 1:03 PM

Answers

  • Hi 

    Not sure if you ever got past this error.  I had the exact same error with Azure Stack SDK 1809 which led me to this post.  I was able to figure out what the issue was for me, hopefully it will help you.

    This fix only applies to AMD CPUs that do not do hyperthreading

    In one of the PowerShell scripts for Azure Stack SDK they changed a parameter to change the AzS-DC01 vm to hyperthread, great and all if you are using Intel, not so great for unsupported AMD chips.

    To fix this:

    On the Azure Stack SDK server

    Open this file C:\Program Files\WindowsPowerShell\Modules\NewManagementVM\NewManagementVM.psm1

    Find this line here and comment out Set-VMProcessor (as shown below) and save the file.  

        # Set VM to use guest SMT
       # Set-VMProcessor -VM $vm -HwThreadCountPerCore 2

    Now to rerun the setup, if you are still in the middle of it. 

    On the Azure Stack SDK server, open an elevated PowerShell window and type the following to start up at the failed step.

     Import-Module C:\CloudDeployment\CloudDeployment.psd1 -Force
     Import-Module C:\CloudDeployment\ECEngine\EnterpriseCloudEngine.psd1 -Force

     Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start "PhysicalMachineAndInitialConfiguration.15" -Verbose

    If you are doing a brand new install, just mount the vhdx for cloudbuilder.vhdx then edit the file NewManagementVM\NewManagementVM.psm1 as described above.

    One way to check if this will fix your issue, providing you are still in the middle of the install. 

    On the Azure Stack SDK server, open an elevated PowerShell window and type 

    Set-VMProcessor -VMName "AzS-DC01" -HwThreadCountPerCore 1

    Then try start-vm -vmname "AzS-DC01" 

    If you are able to start the VM now, you should be good to follow the above steps and continue your install.

    Best of luck

    Robby Garon


    Robby Garon

    Saturday, December 15, 2018 8:04 AM

All replies

  • We are investigating your issue and will reply ASAP.

    To expedite this investigation, please provide the following information:

     

    Build/Version:  

    Get-Content "C:\CloudDeployment\Configuration\Version\version.xml"

     

    Directory type: 

    Azure AD or ADFS

     

    Hardware: 

    How many CPU Cores, RAM, Get-Disk output

     

    Network: 

    Static or DHCP.

     

    The method used to access the Internet:

    NAT, Web Proxy, Transparent  Proxy, DMZ or Closed

     

    BareMetal or Nested Hyper-V:

     

    Please review the Hardware planning doc to make sure that your hardware meets specifications. Were you able to successfully run the Deployment checker for Azure Stack Development Kit before your install?


    Wednesday, October 3, 2018 11:39 PM
  • Build/Version:  
    Get-Content "C:\CloudDeployment\Configuration\Version\version.xml"
    <Version>1.1808.0.97</Version>

    Directory type:
    Azure AD or ADFS
    ADFS

    Hardware:
    How many CPU Cores, RAM, Get-Disk output
    Memory - using 10/256gb, CPU - Speed 2.30GHz, Sockets 2, Cores 2

    Network:
    Static or DHCP.
    Static

    The method used to access the Internet:
    NAT, Web Proxy, Transparent  Proxy, DMZ or Closed
    NAT

    BareMetal or Nested Hyper-V: BareMetal

    Successfully run the Deployment checker for Azure Stack Development Kit before the install
    Thursday, October 4, 2018 9:54 AM
  • Thank you. I am currently reaching out to get more information, and will update you as soon as I am able. 
    Thursday, October 4, 2018 10:24 PM
  • Ran asdk-prechecker.ps1 again with the following results:
    We believe the
    "Failed to connect to AAD endpoint" is due to using ADFS

    PS C:\Temp> .\asdk-prechecker.ps1
    [ 10:52:08 ] Starting Deployment Checker for Microsoft Azure Stack Development Kit (ASDK)...
    [ 10:52:08 ] There are several prerequisites checks to verify that your machine meets all the minimum requirements for deploying ASDK.
    [ 10:52:08 ] For more details, please refer to the online requirements : https://azure.microsoft.com/en-us/documentation/articles/azure-stack-deploy/
    [ 10:52:08 ] Checking for Administrator priviledge...
    [ 10:52:09 ] This machine seems to host an existing successful or failed installation of Azure Stack Development Kit. The prerequisite checker is meant to be run prior to installation, and will return errors post-install, as some of the configuration may already have been applied (joining the domain, setting up storage pools,...)
    Do you want to continue anyway (Y/N)?: y
    [ 10:52:34 ] This script can be run on the host where you will be configuring boot from VHD, for example prior to downloading the ASDK files. Or it can be run after booting from the provided Cloudbuilder.vhdx file where the ASDK will be installed. In the first case, it will only check for hardware specifications like memory, cores, hard disk configuration, as well as free space for extracting the ASDK files. In the second case, it will run both hardware and software tests, and other items like domain membership, OS version, NIC configuration will be checked.
    Are you running this script on the host before booting in the provider VHDX file [1] or after booting into it [2] (any other input will exit the script)?: 2
    [ 10:52:53 ] User chose to run post-boot from VHD checks (all checks except free space)
    [ 10:52:53 ] Checking for physical/virtual machine status...
    [ 10:52:53 ]  -- This is a physical machine.
    [ 10:52:53 ] Checking system disk capacity...
    [ 10:52:55 ]  -- Check system disk passed successfully.
    [ 10:52:55 ] Checking physical disks...
    [ 10:52:55 ]  -- Listing of all physical disks on this server:

    FriendlyName      SerialNumber     CanPool BusType             OperationalStatus HealthStatus Usage               Size
    ------------      ------------     ------- -------             ----------------- ------------ -----               ----
    Msft Virtual Disk                    False File Backed Virtual OK                Healthy      Auto-Select 128849018880
    HP LOGICAL VOLUME 5001438011F738F0    True RAID                OK                Healthy      Auto-Select 299966445568
    HP LOGICAL VOLUME 5001438011F738F0   False RAID                OK                Healthy      Auto-Select 299966445568
    HP LOGICAL VOLUME 5001438011F738F0    True RAID                OK                Healthy      Auto-Select 299966445568
    HP LOGICAL VOLUME 5001438011F738F0    True RAID                OK                Healthy      Auto-Select 299966445568
    HP LOGICAL VOLUME 5001438011F738F0    True RAID                OK                Healthy      Auto-Select 299966445568
    HP LOGICAL VOLUME 5001438011F738F0    True RAID                OK                Healthy      Auto-Select 299966445568
    HP LOGICAL VOLUME 5001438011F738F0    True RAID                OK                Healthy      Auto-Select 299966445568



    [ 10:52:56 ]  -- Listing of all physical disks meeting ASDK requirements:

    FriendlyName      SerialNumber     BusType OperationalStatus HealthStatus Usage               Size
    ------------      ------------     ------- ----------------- ------------ -----               ----
    HP LOGICAL VOLUME 5001438011F738F0 RAID    OK                Healthy      Auto-Select 299966445568
    HP LOGICAL VOLUME 5001438011F738F0 RAID    OK                Healthy      Auto-Select 299966445568
    HP LOGICAL VOLUME 5001438011F738F0 RAID    OK                Healthy      Auto-Select 299966445568
    HP LOGICAL VOLUME 5001438011F738F0 RAID    OK                Healthy      Auto-Select 299966445568
    HP LOGICAL VOLUME 5001438011F738F0 RAID    OK                Healthy      Auto-Select 299966445568
    HP LOGICAL VOLUME 5001438011F738F0 RAID    OK                Healthy      Auto-Select 299966445568
    HP LOGICAL VOLUME 5001438011F738F0 RAID    OK                Healthy      Auto-Select 299966445568



    [ 10:52:56 ]  -- Check physical disks passed successfully. Note that ASDK handles situations where there is a pre-existing storage pool, and will delete/recreate it.
    [ 10:52:56 ] Checking Memory...
    [ 10:52:56 ]  -- Memory on this server = 256
    [ 10:52:56 ]  -- System memory check passed successfully. ASDK requires a minimum of 96 GB of RAM, with 128 GB recommended.
    [ 10:52:56 ] Checking processor information...
    [ 10:52:58 ]  -- Number of CPU sockets = 2
    [ 10:52:58 ]  -- Number of physical cores =  24
    [ 10:52:59 ]  -- CPU socket count (2) and core count (12) meet the minimum requirements for ASDK.
    [ 10:52:59 ] Checking Hyper-V support on the host...
    [ 10:53:00 ]  -- Hyper-V is already installed. Note that the installer would enable it otherwise.
    [ 10:53:00 ] Checking domain join status...
    [ 10:53:00 ]  -- The host is not domain joined.
    [ 10:53:00 ] Checking Internet access...
    [ 10:53:00 ] The remote name could not be resolved: 'login.windows.net'
    [ 10:53:00 ]  -- Failed to connect to AAD endpoint 'https://login.windows.net'.
    [ 10:53:00 ] Checking Host OS version...
    [ 10:53:00 ]  -- Host OS version: 10.0.14393, SKU: 8
    [ 10:53:00 ]  -- The host OS version matches the requirements for ASDK (10.0.14393).
    [ 10:53:00 ] Checking NIC status...
    [ 10:53:02 ]  -- Multiple NICs, virtual switches or NIC teaming are not allowed. Please only keep one physical NIC enabled and remove virtual switches or NIC teaming. This message can be ignored if you are planning to leverage the ASDK Installer from GitHub, as it provides a way to configure the NICs.
    [ 10:53:02 ] Checking NIC requirements...
    [ 10:53:10 ]  -- Please make sure to leverage the ASDK Installer for deployment, per the documentation. This installer will apply an update to this host prior to deployment.
    [ 10:53:11 ] Checking server name...
    [ 10:53:11 ]  -- Server name is WIN-CTJD0QQUPJB
    [ 10:53:11 ]  -- Server name does not conflict with future domain name AzureStack.local.
    [ 10:53:11 ] FAILURE: 1 prerequisite check(s) failed out of 12 . Please review previous entries to understand where the requirements are not met.
    [ 10:53:11 ] Deployment Checker has finished checking Azure Stack Development Kit requirements

    Tuesday, October 9, 2018 11:14 AM
  • Same issue here, anyone else have any advice to get through this?
    Friday, October 19, 2018 9:12 PM
  • Invoke-EceAction : Type 'Deployment' of Role 'Domain' raised an exception:
    'AzS-DC01' failed to start.
    'AzS-DC01' could not initialize.
    Failed to create partition: The hypervisor could not perform the operation because an invalid parameter was specified.
    (0xC0350005).
    'AzS-DC01' failed to start. (Virtual machine ID 11383BFC-26F5-4C6C-BD25-451AAA76432F)
    'AzS-DC01' failed to start worker process: The hypervisor could not perform the operation because an invalid parameter
    was specified. (0xC0350005). (Virtual machine ID 11383BFC-26F5-4C6C-BD25-451AAA76432F)
    'AzS-DC01' could not initialize. (Virtual machine ID 11383BFC-26F5-4C6C-BD25-451AAA76432F)
    Failed to create partition: The hypervisor could not perform the operation because an invalid parameter was specified.
    (0xC0350005).
    at New-ManagementVM, C:\Program Files\WindowsPowerShell\Modules\NewManagementVM\NewManagementVM.psm1: line 510
    at DeployOneVM, C:\CloudDeployment\Classes\Common\Image\VirtualMachineRole.psm1: line 1415
    at DeployVms, C:\CloudDeployment\Classes\Common\Image\VirtualMachineRole.psm1: line 1596
    at Deployment, C:\CloudDeployment\Classes\Common\Image\VirtualMachineRole.psm1: line 1695
    at <ScriptBlock>, <No file>: line 39
    at <ScriptBlock>, <No file>: line 37
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:809 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [Invoke-EceAction], InterfaceInvocationFailedException
        + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StartVM,CloudEngine.Cmdlets.InvokeC
       mdlet

    Invoke-EceAction : Action: Invocation of step PhysicalMachineAndInitialConfiguration.15 failed. Stopping invocation of
    action plan.
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:809 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    Invoke-EceAction : Action: Invocation of step PhysicalMachineAndInitialConfiguration failed. Stopping invocation of
    action plan.
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:809 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet
    Friday, October 19, 2018 9:13 PM
  • Hi 

    Not sure if you ever got past this error.  I had the exact same error with Azure Stack SDK 1809 which led me to this post.  I was able to figure out what the issue was for me, hopefully it will help you.

    This fix only applies to AMD CPUs that do not do hyperthreading

    In one of the PowerShell scripts for Azure Stack SDK they changed a parameter to change the AzS-DC01 vm to hyperthread, great and all if you are using Intel, not so great for unsupported AMD chips.

    To fix this:

    On the Azure Stack SDK server

    Open this file C:\Program Files\WindowsPowerShell\Modules\NewManagementVM\NewManagementVM.psm1

    Find this line here and comment out Set-VMProcessor (as shown below) and save the file.  

        # Set VM to use guest SMT
       # Set-VMProcessor -VM $vm -HwThreadCountPerCore 2

    Now to rerun the setup, if you are still in the middle of it. 

    On the Azure Stack SDK server, open an elevated PowerShell window and type the following to start up at the failed step.

     Import-Module C:\CloudDeployment\CloudDeployment.psd1 -Force
     Import-Module C:\CloudDeployment\ECEngine\EnterpriseCloudEngine.psd1 -Force

     Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start "PhysicalMachineAndInitialConfiguration.15" -Verbose

    If you are doing a brand new install, just mount the vhdx for cloudbuilder.vhdx then edit the file NewManagementVM\NewManagementVM.psm1 as described above.

    One way to check if this will fix your issue, providing you are still in the middle of the install. 

    On the Azure Stack SDK server, open an elevated PowerShell window and type 

    Set-VMProcessor -VMName "AzS-DC01" -HwThreadCountPerCore 1

    Then try start-vm -vmname "AzS-DC01" 

    If you are able to start the VM now, you should be good to follow the above steps and continue your install.

    Best of luck

    Robby Garon


    Robby Garon

    Saturday, December 15, 2018 8:04 AM
  • You're a genius Rob, it worked!  The only caveat is that the cloudbuilder.vhdx doesn't have the NewManagementVM.psm1 script until you run the deployment (2nd part) where it extract it from somewhere, I just edited that file as you described above early in the deployment stage.  Thanks again!  Hope someone else found this useful, BTW I'm using version 1811 (Dec 2018) version of the AzureStack SDK.
    Thursday, January 10, 2019 6:22 PM