locked
Issue with Azure Stack TP3 Deployment RRS feed

  • Question

  • Hey Guys,

    Every time I try to install the Azure stack, its failing at the test-cluster that it cant detect the drives. I have 4 physical drives in the host with 1 OS drive.

    The error is below. I have tried rerun and redeploy from scratch and the results are same. Any recommendation would be great.

    Error

    at <ScriptBlock>, <No file>: line 9 - 4/7/2017 10:06:01 AM

    Invoke-EceAction : Task: Invocation of interface 'Deployment' of role

    'Cloud\Infrastructure\Storage' failed:

    Function 'Storage:Deployment' in module 'Classes\Storage\Storage.psm1' raised an exception:

    On one-node setup, at least 3 disks are required. Actual number of available disks:

    Command            Arguments

                  Locatio

                   n

    -------             ---------

                   -------

    Test-StorageCluster {Parameters=CloudEngine.Configurations.EceInterfaceParameters}

                   Stor...

                        {}

                   Stor...

    <ScriptBlock>       {C:\CloudDeployment\CloudDeployment.psd1,

    CloudEngine.Configurations.EceInterfaceParameters} <No ...

    at Trace-Error, C:\CloudDeployment\Common\Tracer.psm1: line 44

    at Test-StorageCluster, C:\CloudDeployment\Classes\Storage\StorageHelpers.psm1: line 372

    at Deployment, C:\CloudDeployment\Classes\Storage\Storage.psm1: line 185

    at <ScriptBlock>, <No file>: line 9 - 4/7/2017 10:06:01 AM

    At line:5 char:2

    +  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 0.17  ...

    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : OperationStopped: (On one-node set...} <No ...

    :String) [Invoke-EceAction], Exception

        + FullyQualifiedErrorId : On one-node setup, at least 3 disks are required. Actual number of

       available disks:

        Command             Arguments

                           Locatio

                           n

        -------             ---------

                           -------

        Test-StorageCluster {Parameters=CloudEngine.Configurations.EceInterfaceParameters}

                           Stor...

                            {}

                           Stor...

        <ScriptBlock>       {C:\CloudDeployment\CloudDeployment.psd1, CloudEngine.Configurations.EceI

       nterfaceParameters} <No ...

    ,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: Step: Status of step '0.20 - (STO) Configure Storage Cluster' is 'Error'. - 4/7/2017

    10:06:01 AM

    Invoke-EceAction : Action: Invocation of step 0.20 failed. Stopping invocation of action plan. -

    4/7/2017 10:06:01 AM

    At line:5 char:2

    +  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 0.17  ...

    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception

        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: Action: Status of 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' is 'Error'. - 4/7/2017

    10:06:01 AM

    COMPLETE: Task Cloud - Deployment-Phase0-DeployBareMetalAndBGPAndNAT

    VERBOSE: Task: Status of action 'Deployment-Phase0-DeployBareMetalAndBGPAndNAT' of role 'Cloud' is

     'Error'. - 4/7/2017 10:06:01 AM

    VERBOSE: Step: Status of step '0 - Phase 0 - Configure physical machine and external networking'

    is 'Error'. - 4/7/2017 10:06:01 AM

    Invoke-EceAction : Action: Invocation of step 0 failed. Stopping invocation of action plan. -

    4/7/2017 10:06:01 AM

    At line:5 char:2

    +  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Start 0.17  ...

    +  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception

        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    Friday, April 7, 2017 6:37 PM

Answers

  • Hello,

    Please make sure there is no data or existing volumes residing on the drives to be used for Azure Stack The output from the following script should provide some clues as to what the issue is.

     

    Please run the script and post the output back to the Forum.

      

    ####################### CheckAzSPOCDisks.ps1 START ##########################

     

    function CheckSystemDisk {

        write-host -ForegroundColor yellow "["(date -format "HH:mm:ss")"]" "Checking system disk capacity..."

     

        $systemDisk = Get-Disk | ? {$_.IsSystem -eq $true}

        If ($systemDisk.Size -lt 180 * 1024 * 1024 * 1024)

            {

                write-host -ForegroundColor red "["(date -format "HH:mm:ss")"]" " -- Check system disk failed - Size should be 180 GB minimum."

                $Global:ChecksFailure++

            }

            else

            {

                write-host -ForegroundColor green "["(date -format "HH:mm:ss")"]" " -- Check system disk passed successfully."

                $Global:ChecksSuccess++

            }  

    }

    function CheckDisks {

        write-host -ForegroundColor yellow "["(date -format "HH:mm:ss")"]" "Checking physical disks..."

       

        write-host -ForegroundColor gray "["(date -format "HH:mm:ss")"]" " -- Listing of all physical disks on this server:"

        write-host -ForegroundColor gray (Get-PhysicalDisk | Format-Table -Property @("FriendlyName", "SerialNumber", "CanPool", "BusType", "OperationalStatus", "HealthStatus", "Usage", "Size") | Out-String)

        $physicalDisks = Get-PhysicalDisk | Where-Object { ($_.BusType -eq 'RAID' -or $_.BusType -eq 'SAS' -or $_.BusType -eq 'SATA') -and $_.Size -gt 135 * 1024 * 1024 * 1024 }

        $selectedDisks = $physicalDisks | Group-Object -Property BusType | Sort-Object -Property Count -Descending | Select-Object -First 1

     

        if ($selectedDisks.Count -ge 3) {

            write-host -ForegroundColor gray "["(date -format "HH:mm:ss")"]" " -- Listing of all physical disks meeting Azure Stack requirements:"

            write-host -ForegroundColor gray ($physicalDisks | Format-Table -Property @("FriendlyName", "SerialNumber", "BusType", "OperationalStatus", "HealthStatus", "Usage", "Size") | Out-String)

            write-host -ForegroundColor green "["(date -format "HH:mm:ss")"]" " -- Check physical disks passed successfully. Note that Azure Stack Technical Preview will now handle situations where there is a pre-existing storage pool, and will delete/recreate it."

            $Global:ChecksSuccess++

        }

     

        if ($selectedDisks.Count -lt 3) {

            write-host -ForegroundColor red "["(date -format "HH:mm:ss")"]" " -- Check physical disks failed - At least 4 disks or more of the same bus type (RAID/SAS/SATA), and of capacity 135 GB or higher are strongly recommended. 3-disk configurations may work but are not tested by Microsoft."

            $Global:ChecksFailure++

         }   

     

    }

    function CheckFreeSpaceForExtraction {

        write-host -ForegroundColor gray "["(date -format "HH:mm:ss")"]" " Checking free space for extracting the Azure Stack files..."

        write-host -ForegroundColor gray "["(date -format "HH:mm:ss")"]" " -- Listing disks and their free space"

        write-host -ForegroundColor gray (Get-Disk | Get-Partition | Get-Volume | Sort-Object -Property SizeRemaining -Descending | Out-String)

        $volumes = (Get-disk | ? {$_.BusType -ne 'File Backed Virtual' -or $_.IsBoot} | Get-Partition | Get-Volume |`

             ? {-not [String]::IsNullOrEmpty($_.DriveLetter)} | sort -Property SizeRemaining -Descending)

        if (!$volumes -or ($volumes | Measure-Object).count -le 0) {

            Write-Host -ForegroundColor red "["(date -format "HH:mm:ss")"]" " -- Free space check failed. No volumes are available."

            $Global:ChecksFailure++

        }

        if ($volumes[0].SizeRemaining -lt 120 * 1024 * 1024 * 1024) {

            write-host -ForegroundColor red "["(date -format "HH:mm:ss")"]" " -- Free space check failed. Azure Stack requires 130 GB for the expansion of the Cloudbuilder.vhdx file. An additional 40 GB may be needed if you want to keep the ZIP and self extractor files."

            $Global:ChecksFailure++

        }

        else

        {

            write-host -ForegroundColor green "["(date -format "HH:mm:ss")"]" " -- Free space check passed successfully."

            $Global:ChecksSuccess++

        }

    }

     

    CheckSystemDisk

    CheckDisks

    CheckFreeSpaceForExtraction

     

    ####################### CheckAzSPOCDisks.ps1 END ###########################

       

    NOTE: All data drives must be of the same type (all SAS or all SATA) and capacity. If SAS disk drives are used, the disk drives must be attached via a single path (no MPIO, multi-path support is provided).+ 

     

    HBA configuration options

    •(Preferred) Simple HBA

    •RAID HBA – Adapter must be configured in “pass through” mode

    •RAID HBA – Disks should be configured as Single-Disk, RAID-0

      

    Supported bus and media type combinations

    •SATA HDD

    •SAS HDD

    •RAID HDD

    •RAID SSD (If the media type is unspecified/unknown*)

    •SATA SSD + SATA HDD

    •SAS SSD + SAS HDD

      

    * RAID controllers without pass-through capability can’t recognize the media type. Such controllers will mark both HDD and SSD as Unspecified. In that case, the SSD will be used as persistent storage instead of caching devices. Therefore, you can deploy the Microsoft Azure Stack POC on those SSDs.

    Example HBAs: LSI 9207-8i, LSI-9300-8i, or LSI-9265-8i in pass-through mode

     

    Azure Stack TP3 refresh has been released on April 6, 2017.

    If you are experiencing any issues with the March 2017 TP3 release, please download and redeploy using the latest Azure Stack POC deployment package. 

     

    Please see the updated TP3 refresh deployment documentation Azure Stack 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

    We truly appreciate your time and interest in Azure Stack.

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

     

    Thanks,


    Gary Gallanes

    Friday, April 7, 2017 7:22 PM