locked
Unable to deploy VM onto ASDK 1805 1.1805.1.47 RRS feed

  • Question

  • Hi

    We have just deployed the 1805 1.1805.1.47 ASDK onto a physical system for testing. Currently we are unable to undertake a simple task of provisioning a VM. We have attempted Ubuntu 14.04 and Serve Core 2016, both come back as failed to deploy.  All provisioning is being done via the GUI with the default images downloaded from the Azure Marketplace, nothing magical.

    During this time, in Hyper-V we can see the VM spin up and sit at login, then after a time (most likely when AS believes the VM hasnt deployed) it powers itself off. Just wondered if anyone else had hit the same issue out there?

    **** NOTE ****
    We have completely redeployed the 1805 ASDK, and exactly the same issue has happened again.

    Are we able to download 1804, or older ASDKs anywhere if 1805 does have an issue?

    Any help on troubleshooting or resolving this issue would be appreciated.

    Cheers


    • Edited by G2017 Tuesday, June 12, 2018 8:56 AM
    Tuesday, June 12, 2018 8:51 AM

Answers

  • Further to this, we cleared the D drive, ran the vm deployment, it worked, and the drive a little later filled again. It appears this is the issue that is causings VMs to fail deployment. Is it possible in the next ASDK release the logs drive can be allocated more space?

    I don't think they even make pen drives at 346MB anymore :-)

    Tuesday, June 12, 2018 10:06 AM
  • Hello Chris,

    Direct links to legacy builds is no longer supported.

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

    If you experience any issues with Azure Stack or the current ASDK release, please feel free to contact us.

         

     Thanks,


    Gary Gallanes


    Thursday, June 14, 2018 10:28 PM

All replies

  • At the moment we believe this may be due to the D: volume being out of space. We assume this is required to write log information to, but currently it is unable to. One of the pieces of information it may write is the success of a VM being deployed, and thus notifying the Stack the deployment is complete.

    Currently the D: is only allocated 346MB of space which seems extremely small.

    This is purely a guess at this stage, please let us know if anyone else has encountered similar. Also the resolution to this.

    Tuesday, June 12, 2018 9:09 AM
  • Further to this, we cleared the D drive, ran the vm deployment, it worked, and the drive a little later filled again. It appears this is the issue that is causings VMs to fail deployment. Is it possible in the next ASDK release the logs drive can be allocated more space?

    I don't think they even make pen drives at 346MB anymore :-)

    Tuesday, June 12, 2018 10:06 AM
  • Hello,

    You are correct in your assumption that lack of space on D: is causing that deployment failure.

    Can you go to “Disk Management” on the Host and expand the D: drive?

     

    Note: If no space is available, you can shrink another partition by 1 or 2 GB and use the free space to expand the D: drive.

      

    This issue will be addressed on the next build and we are currently putting together some guidance to workaround the lack of space of D:.

     

    Let us know how it goes.

     

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

    If you continue experience any issues with ASDK release, feel free to contact us.

           

     Thanks, 


    Gary Gallanes

    Tuesday, June 12, 2018 5:55 PM
  • Thanks Gary, sadly you cannot expand that partition but you can do what we did, see below.

    The way we fixed it:

    Just for everyone to see and know what the issue is.

    We narrowed it down to be 100% the D: size issues. When the drive is full, logs cannot be written and all provisioning tasks cannot report back that they are successful.

    In Hyper-V you can see VMs deploying, have internet access, and get configured correctly but Stack is not aware of it due to the logging issue.

    The way we have "solved" it, or rather worked around it is as follows:

    1. Shrink C: by about 5 GB
    2. Create new FAT32 partition on the newly carved shrunk space
    3. Change 346 MB D: partition to a different letter
    4. Assign D: letter to the new 5 GB partition

    You will notice that not all of the folders get re-created like EFI etc... but it does not matter as the Stack starts to function properly regardless.

    I hope this will help someone.


    Wednesday, June 13, 2018 6:11 AM
  • Thank you for the replies to this. We would still like to know if older versions can also be downloaded anywhere?
    Wednesday, June 13, 2018 7:15 AM
  • Hello Chris,

    Direct links to legacy builds is no longer supported.

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

    If you experience any issues with Azure Stack or the current ASDK release, please feel free to contact us.

         

     Thanks,


    Gary Gallanes


    Thursday, June 14, 2018 10:28 PM