locked
Facing deployment error "Verbose Failure during mount attempt: 'The specified VHD does not have a system volume. Choose a VHD that has a single system volume for operation with DISM." RRS feed

  • Question

  • I'm facing error while deploying Azure Stack TP3. Can someone please guide me as <g class="gr_ gr_131 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="131" id="131">i'm</g> very new in <g class="gr_ gr_152 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="152" id="152">azure</g>.

    Following are the log file details.

    Filename:  Deployment.2017-07-01.09-40-31.0.log

    2017-07-01 09:40:31 Verbose  Action: Running action plan 'Deployment'.
    2017-07-01 09:40:31 Verbose  Step: Running step 0 - Phase 0 - Configure physical machine and external networking
    2017-07-01 09:40:31 Verbose  Task: Running action type 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' of role 'Cloud'.
    2017-07-01 09:40:31 Verbose  Action: Running action Deployment-Phase0-DeployBareMetalAndBGPAndNAT.
    2017-07-01 09:40:31 Verbose  Action: Running action plan 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT'.
    2017-07-01 09:40:31 Verbose  Step: Running step 0.10 - (DEP) Generate base images for hosts and virtual machines.
    2017-07-01 09:40:31 Verbose  Task: Running interface 'Build' of role 'Cloud'. Attempt #1. 
    2017-07-01 09:40:31 Verbose  Interface: Path to module: C:\CloudDeployment\Classes\Cloud\Cloud.psm1
    2017-07-01 09:40:31 Verbose  Interface: Running interface Build (Classes\Cloud\Cloud.psm1, Cloud:Build)
    2017-07-01 09:40:42 Verbose  Enabling Code Integrity policy in Audit mode
    2017-07-01 09:40:42 Verbose  OEM Code Integrity policy XML: C:\CloudDeployment\Security\CodeIntegrity\OEMPolicy.xml not found. Skipping host policy file generation.
    2017-07-01 09:40:42 Verbose  Converting MAS Code Integrity policy to binary form
    2017-07-01 09:40:49 Verbose  Clean up old content as build did not complete during previous run.
    2017-07-01 09:40:49 Verbose  Creating build folder C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp
    2017-07-01 09:40:49 Verbose  Copying C:\CloudDeployment\Images\en-us\WindowsServerCore.vhdx to C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp\WindowsServerCore.vhdx
    2017-07-01 09:41:14 Verbose  Copying C:\CloudDeployment\Images\en-us\WindowsServerFull.vhdx to C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp\WindowsServerFull.vhdx
    2017-07-01 09:42:14 Verbose  Trying to update the image WindowsServerCore.vhdx with windows updates.
    2017-07-01 09:44:10 Verbose  Exclude mount folders C:\Temp\41d74996-f7aa-438e-b4d0-89e1efb31059 from Windows Defender scan to speed up configuration.
    2017-07-01 09:44:11 Verbose  Mount 'C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp\WindowsServerCore.vhdx' to 'C:\Temp\41d74996-f7aa-438e-b4d0-89e1efb31059'.
    2017-07-01 09:53:51 Verbose  Performing Windows Update injection for: MountedImage.ImagePath
    2017-07-01 09:53:51 Warning  Windows update folder: C:\CloudDeployment\WindowsUpdates not found. Skipping windows update injection.
    2017-07-01 09:53:51 Verbose  Performing Code Integrity policy injection for: MountedImage.ImagePath
    2017-07-01 09:53:51 Verbose  Injecting Code Integrity policy from: C:\CloudDeployment\Security\CodeIntegrity\MASPolicy.bin
    2017-07-01 09:53:52 Verbose  Updating image status by Setting Version: 1.0.170331.1  StatusId: 0  Status: BaseBuildCompleted
    2017-07-01 09:53:52 Verbose  Dismount and save mounted image.
    2017-07-01 09:53:58 Verbose  Remove Windows Defender exclusions for paths C:\Temp\41d74996-f7aa-438e-b4d0-89e1efb31059.
    2017-07-01 09:53:59 Verbose  Trying to update the image WindowsServerFull.vhdx with windows updates.
    2017-07-01 09:53:59 Verbose  Exclude mount folders C:\Temp\1a3e08f3-f9f7-4a8b-acd4-932ecc5c8e99 from Windows Defender scan to speed up configuration.
    2017-07-01 09:53:59 Verbose  Mount 'C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp\WindowsServerFull.vhdx' to 'C:\Temp\1a3e08f3-f9f7-4a8b-acd4-932ecc5c8e99'.
    2017-07-01 09:54:06 Verbose  Failure during mount attempt: 'The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.
    '.  Retrying.
    2017-07-01 09:54:08 Verbose  Failure during mount attempt: 'The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.
    '.  Retrying.
    2017-07-01 09:54:11 Verbose  Failure during mount attempt: 'The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.
    '.  Retrying.
    2017-07-01 09:54:14 Warning  Task: Invocation of interface 'Build' of role 'Cloud' failed: 

    Function 'Cloud:Build' in module 'Classes\Cloud\Cloud.psm1' raised an exception:

    The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.

    at Mount-WindowsImageWithRetry<Process>, C:\CloudDeployment\Common\Helpers.psm1: line 283
    at MountedImage, C:\CloudDeployment\Roles\Common\MountedImage.psm1: line 67
    at UpdateBaseImages, C:\CloudDeployment\Classes\Cloud\Cloud.psm1: line 395
    at Build, C:\CloudDeployment\Classes\Cloud\Cloud.psm1: line 156
    at <ScriptBlock>, <No file>: line 9
    2017-07-01 09:54:14 Warning  Task: Retrying interface 'Build' of role 'Cloud'...
    2017-07-01 09:54:14 Verbose  Task: Running interface 'Build' of role 'Cloud'. Attempt #2. (Retry 1 of 2.)
    2017-07-01 09:54:14 Verbose  Interface: Path to module: C:\CloudDeployment\Classes\Cloud\Cloud.psm1
    2017-07-01 09:54:14 Verbose  Interface: Running interface Build (Classes\Cloud\Cloud.psm1, Cloud:Build)
    2017-07-01 09:54:28 Verbose  Enabling Code Integrity policy in Audit mode
    2017-07-01 09:54:28 Verbose  OEM Code Integrity policy XML: C:\CloudDeployment\Security\CodeIntegrity\OEMPolicy.xml not found. Skipping host policy file generation.
    2017-07-01 09:54:28 Verbose  Converting MAS Code Integrity policy to binary form
    2017-07-01 09:54:37 Verbose  Clean up old content as build did not complete during previous run.
    2017-07-01 09:54:37 Verbose  Creating build folder C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp
    2017-07-01 09:54:37 Verbose  Copying C:\CloudDeployment\Images\en-us\WindowsServerCore.vhdx to C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp\WindowsServerCore.vhdx
    2017-07-01 09:55:35 Verbose  Copying C:\CloudDeployment\Images\en-us\WindowsServerFull.vhdx to C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp\WindowsServerFull.vhdx
    2017-07-01 09:58:37 Verbose  Trying to update the image WindowsServerCore.vhdx with windows updates.
    2017-07-01 09:59:47 Verbose  Exclude mount folders C:\Temp\790cb829-2925-4bd5-bb81-a02f345280b5 from Windows Defender scan to speed up configuration.
    2017-07-01 09:59:51 Verbose  Mount 'C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp\WindowsServerCore.vhdx' to 'C:\Temp\790cb829-2925-4bd5-bb81-a02f345280b5'.
    2017-07-01 10:07:49 Verbose  Performing Windows Update injection for: MountedImage.ImagePath
    2017-07-01 10:07:49 Warning  Windows update folder: C:\CloudDeployment\WindowsUpdates not found. Skipping windows update injection.
    2017-07-01 10:07:49 Verbose  Performing Code Integrity policy injection for: MountedImage.ImagePath
    2017-07-01 10:07:49 Verbose  Injecting Code Integrity policy from: C:\CloudDeployment\Security\CodeIntegrity\MASPolicy.bin
    2017-07-01 10:07:49 Verbose  Updating image status by Setting Version: 1.0.170331.1  StatusId: 0  Status: BaseBuildCompleted
    2017-07-01 10:07:50 Verbose  Dismount and save mounted image.
    2017-07-01 10:07:56 Verbose  Remove Windows Defender exclusions for paths C:\Temp\790cb829-2925-4bd5-bb81-a02f345280b5.
    2017-07-01 10:07:56 Verbose  Trying to update the image WindowsServerFull.vhdx with windows updates.
    2017-07-01 10:07:56 Verbose  Exclude mount folders C:\Temp\8244347c-fa76-48d8-9e98-556dce8aee46 from Windows Defender scan to speed up configuration.
    2017-07-01 10:07:56 Verbose  Mount 'C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp\WindowsServerFull.vhdx' to 'C:\Temp\8244347c-fa76-48d8-9e98-556dce8aee46'.
    2017-07-01 10:08:03 Verbose  Failure during mount attempt: 'The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.
    '.  Retrying.
    2017-07-01 10:08:06 Verbose  Failure during mount attempt: 'The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.
    '.  Retrying.
    2017-07-01 10:08:09 Verbose  Failure during mount attempt: 'The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.
    '.  Retrying.
    2017-07-01 10:08:13 Warning  Task: Invocation of interface 'Build' of role 'Cloud' failed: 

    Function 'Cloud:Build' in module 'Classes\Cloud\Cloud.psm1' raised an exception:

    The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.

    at Mount-WindowsImageWithRetry<Process>, C:\CloudDeployment\Common\Helpers.psm1: line 283
    at MountedImage, C:\CloudDeployment\Roles\Common\MountedImage.psm1: line 67
    at UpdateBaseImages, C:\CloudDeployment\Classes\Cloud\Cloud.psm1: line 395
    at Build, C:\CloudDeployment\Classes\Cloud\Cloud.psm1: line 156
    at <ScriptBlock>, <No file>: line 9
    2017-07-01 10:08:13 Warning  Task: Retrying interface 'Build' of role 'Cloud'...
    2017-07-01 10:08:13 Verbose  Task: Running interface 'Build' of role 'Cloud'. Attempt #3. (Retry 2 of 2.)
    2017-07-01 10:08:13 Verbose  Interface: Path to module: C:\CloudDeployment\Classes\Cloud\Cloud.psm1
    2017-07-01 10:08:13 Verbose  Interface: Running interface Build (Classes\Cloud\Cloud.psm1, Cloud:Build)
    2017-07-01 10:08:28 Verbose  Enabling Code Integrity policy in Audit mode
    2017-07-01 10:08:28 Verbose  OEM Code Integrity policy XML: C:\CloudDeployment\Security\CodeIntegrity\OEMPolicy.xml not found. Skipping host policy file generation.
    2017-07-01 10:08:28 Verbose  Converting MAS Code Integrity policy to binary form
    2017-07-01 10:08:36 Verbose  Clean up old content as build did not complete during previous run.
    2017-07-01 10:08:36 Verbose  Creating build folder C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp
    2017-07-01 10:08:36 Verbose  Copying C:\CloudDeployment\Images\en-us\WindowsServerCore.vhdx to C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp\WindowsServerCore.vhdx
    2017-07-01 10:09:26 Verbose  Copying C:\CloudDeployment\Images\en-us\WindowsServerFull.vhdx to C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp\WindowsServerFull.vhdx
    2017-07-01 10:11:50 Verbose  Trying to update the image WindowsServerCore.vhdx with windows updates.
    2017-07-01 10:13:00 Verbose  Exclude mount folders C:\Temp\1746d876-c0f9-439d-bf4e-22747f513f5c from Windows Defender scan to speed up configuration.
    2017-07-01 10:13:01 Verbose  Mount 'C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp\WindowsServerCore.vhdx' to 'C:\Temp\1746d876-c0f9-439d-bf4e-22747f513f5c'.
    2017-07-01 10:22:19 Verbose  Performing Windows Update injection for: MountedImage.ImagePath
    2017-07-01 10:22:19 Warning  Windows update folder: C:\CloudDeployment\WindowsUpdates not found. Skipping windows update injection.
    2017-07-01 10:22:19 Verbose  Performing Code Integrity policy injection for: MountedImage.ImagePath
    2017-07-01 10:22:19 Verbose  Injecting Code Integrity policy from: C:\CloudDeployment\Security\CodeIntegrity\MASPolicy.bin
    2017-07-01 10:22:19 Verbose  Updating image status by Setting Version: 1.0.170331.1  StatusId: 0  Status: BaseBuildCompleted
    2017-07-01 10:22:19 Verbose  Dismount and save mounted image.
    2017-07-01 10:22:24 Verbose  Remove Windows Defender exclusions for paths C:\Temp\1746d876-c0f9-439d-bf4e-22747f513f5c.
    2017-07-01 10:22:24 Verbose  Trying to update the image WindowsServerFull.vhdx with windows updates.
    2017-07-01 10:22:24 Verbose  Exclude mount folders C:\Temp\c40c6014-53fa-47e2-a73b-5b753cfc118f from Windows Defender scan to speed up configuration.
    2017-07-01 10:22:24 Verbose  Mount 'C:\CloudDeployment\Images\en-us\1.0.170331.1_Temp\WindowsServerFull.vhdx' to 'C:\Temp\c40c6014-53fa-47e2-a73b-5b753cfc118f'.
    2017-07-01 10:22:30 Verbose  Failure during mount attempt: 'The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.
    '.  Retrying.
    2017-07-01 10:22:32 Verbose  Failure during mount attempt: 'The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.
    '.  Retrying.
    2017-07-01 10:22:34 Verbose  Failure during mount attempt: 'The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.
    '.  Retrying.
    2017-07-01 10:22:35 Warning  Task: Invocation of interface 'Build' of role 'Cloud' failed: 

    Function 'Cloud:Build' in module 'Classes\Cloud\Cloud.psm1' raised an exception:

    The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.

    at Mount-WindowsImageWithRetry<Process>, C:\CloudDeployment\Common\Helpers.psm1: line 283
    at MountedImage, C:\CloudDeployment\Roles\Common\MountedImage.psm1: line 67
    at UpdateBaseImages, C:\CloudDeployment\Classes\Cloud\Cloud.psm1: line 395
    at Build, C:\CloudDeployment\Classes\Cloud\Cloud.psm1: line 156
    at <ScriptBlock>, <No file>: line 9
    2017-07-01 10:22:35 Error    Task: Invocation of interface 'Build' of role 'Cloud' failed: 

    Function 'Cloud:Build' in module 'Classes\Cloud\Cloud.psm1' raised an exception:

    The specified VHD does not have a system volume.
    Choose a VHD that has a single system volume for operation with DISM.

    at Mount-WindowsImageWithRetry<Process>, C:\CloudDeployment\Common\Helpers.psm1: line 283
    at MountedImage, C:\CloudDeployment\Roles\Common\MountedImage.psm1: line 67
    at UpdateBaseImages, C:\CloudDeployment\Classes\Cloud\Cloud.psm1: line 395
    at Build, C:\CloudDeployment\Classes\Cloud\Cloud.psm1: line 156
    at <ScriptBlock>, <No file>: line 9
    2017-07-01 10:22:35 Verbose  Step: Status of step '0.10 - (DEP) Generate base images for hosts and virtual machines.' is 'Error'.
    2017-07-01 10:22:35 Error    Action: Invocation of step 0.10 failed. Stopping invocation of action plan.
    2017-07-01 10:22:35 Verbose  Action: Status of 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' is 'Error'.
    2017-07-01 10:22:35 Verbose  Task: Status of action 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' of role 'Cloud' is 'Error'.
    2017-07-01 10:22:35 Verbose  Step: Status of step '0 - Phase 0 - Configure physical machine and external networking' is 'Error'.
    2017-07-01 10:22:35 Error    Action: Invocation of step 0 failed. Stopping invocation of action plan.



    Saturday, July 1, 2017 6:02 PM

Answers

All replies

  • In addition, for better investigation attaching following results as per following link:

    https://social.msdn.microsoft.com/Forums/en-US/876dc061-01cd-4ebf-8030-73be78fa46b9/azure-stack-tp3-deployment-fails-at-step-20?forum=AzureStack

    Build/Version:  

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

    <Version>1.0.170331.1</Version>

    Directory type: ADFS

    Hardware: CPU - 8 core, Memory - 64 GB

    Get-Disk

    Number Friendly Name Serial Number                    HealthStatus         OperationalStatus      Total Size Partition
                                                                                                                 Style
    ------ ------------- -------------                    ------------         -----------------      ---------- ----------
    4      <g class="gr_ gr_61 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="61" id="61">Msft</g> Virtu...                                  Healthy              Online                     120 GB MBR
    0      VMware, VM...                                  Healthy              Online                     400 GB MBR
    1      VMware, VM...                                  Healthy              Online                     200 GB MBR
    2      VMware, VM...                                  Healthy              Online                     200 GB MBR
    3      VMware, VM...                                  Healthy              Online                     200 GB MBR

    Network: Static 

    The method used to access the Internet: NAT

    BareMetal or Nested Hyper-V:  Nested Hyper-V


    Monday, July 3, 2017 6:30 AM
  • Hello,

    Unfortunately, your deployment host doesn’t meet the requirements for deploying Azure Stack.  At 8 cores and 64 gigs of memory, your server doesn’t have enough resources to start the Management VMs.  

    Also - Azure Stack TP3 POC is only supported on a single Baremetal Server.

      

    The Azure Stack POC runs processes and workloads on a Single machine that ordinarily run on thousands servers in Azure.  A forced 64 GB the Azure Stack POC deployment is very unstable and doesn’t accurately represent the Azure Stack user experience.    

     

    Make sure your DVM Host meets the minimum requirements by running the prerequisite check script.

    https://gallery.technet.microsoft.com/Deployment-Checker-for-50e0f51b

     Required Hardware

            
      

    Component

      
      

    Minimum

      
      

    Recommended

      

    Disk drives:   Operating System

    1 OS disk with   minimum of 200 GB available for system partition (SSD or HDD)

    1 OS disk with   minimum of 200 GB available for system partition (SSD or HDD)

    Disk drives:   General Azure Stack POC Data*

    4 disks. Each   disk provides a minimum of 140 GB of capacity (SSD or HDD). All available   disks will be used.

    4 disks. Each   disk provides a minimum of 250 GB of capacity (SSD or HDD). All available   disks will be used.

    Compute: CPU

    Dual-Socket: 12   Physical Cores (total)

    Dual-Socket: 16   Physical Cores (total)

    Compute: Memory

    96 GB RAM

    128 GB RAM (This   is the minimum to support PaaS resource providers.)

    Compute: BIOS

    Hyper-V Enabled   (with SLAT support)

    Hyper-V Enabled   (with SLAT support)

    Network: NIC

    Windows Server   2012 R2 Certification required for NIC; no specialized features required

    Windows Server   2012 R2 Certification required for NIC; no specialized features required

    HW logo   certification

    Certified   for Windows Server 2012 R2

    Certified   for Windows Server 2012 R2

      

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

    If you experience any issues with the TP3 release, feel free to contact us.

       

    Azure Stack TP3R Docs:

    https://docs.microsoft.com/en-us/azure/azure-stack/

    https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-troubleshooting

    https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-diagnostics

    https://aka.ms/GetAzureStackLogs

     

    PowerShell giving you the Blues? Try my Azure Stack PowerShell Helper scripts

    AzureStack Automation: RM Module Check/Fix ver.1.2.9 plus AzureStack-Tools

    AzureStack Automation: Setup & Validate AdminStackAdmin/User ARM Endpoints

    AzureStack Automation: Validate and Set Default Image                                    

    AzureStack Automation: Register Azure Stack for Azure Marketplace Syndication

     

     Thanks,


    Gary Gallanes

    Monday, July 3, 2017 4:37 PM
  • Thanks Gary for your reply. Additionally, can you answer followings questions asked by our hardware engineer?

    I need some clarifications for getting a correct quote on the POC data disks, will the 4 disks be in a RAID configuration, or are they just 4 single disks no RAID?  Why 4 disks and not just one large logical disk in RAID configuration in which the number of disks doesn’t matter?   If in RAID configuration, what level of RAID?  This is needed to get the correct quote.  Is it for separate disks because the Azure stack is going to manage each disk individually?  The OS disks are listed as one disk, but why not two disks in RAID 1 configuration to provide high availability?

     

    If you have just 4 single disks as single disks, then there is no redundancy, so are you guys asking for 4 single disks with no redundancy and 1 OS disk with no redundancy or are you asking for 4 logical disks which has redundancy which is different because then I need to make sure the RAID controller supports at least 5 logical disks, 4 for the POC data and 1 for the OS

    Friday, July 7, 2017 8:02 AM