[ASDK] Are you having issues with available D:\ drive space (due to the EFI partition)? RRS feed

  • General discussion

  • Whether you have deployed 1804 or 1805, are planning to redeploy, or are just curious about this issue, I have created a document and updated the asdk-installer.ps1 to mitigate the issue in this area.

    Document: https://msdnshared.blob.core.windows.net/media/2018/06/Preventing-the-EFI-Partition-from-getting-a-drive-letter.pdf

    As you will see in the document, the resolution involved a simple change to the asdk-installer.ps1, to make sure the EFI partition of the CloudBuilder.vhdx does not get a drive letter once the CloudBuilder.vhdx is booted into. This eliminates it from becoming the D:\ drive, which was happening in a small number of environments.

    Recommended Action: For your next redeployment of ASDK, be sure to download and use the latest asdk-installer.ps1 (which is a good idea, either way, especially if you haven't downloaded a copy of it recently).


    BTW - if you prefer not to redeploy just yet, the document does outline a potential manual workaround you can try. But it will involve a ASDK host reboot.


    Charles Joy [MSFT] https://twitter.com/OrchestratorGuy

    Thursday, June 28, 2018 4:30 PM

All replies

  • Thanks, Charles!   I'm looking forward to hearing from people whether they needed this and if it solved their problem.

    Thursday, June 28, 2018 4:54 PM
  • Excellent Charles!

    We have been experiencing this issue, on one of our ASDK environment, with a recovery partition, since 1804.

    I am going to pull the latest and rebuild the ASDK environment Will report back.

    Thank you for addressing!


    Thursday, June 28, 2018 7:22 PM
  • I can report success. Thank you! Very much appreciated!


    Friday, June 29, 2018 2:17 AM
  • Hi 

    I resolve this differently. Some play around through Disk Management.

    1: Shrink the 2 GB C: drive and created free disk space.

    2: Create a partition from empty space (2 GB) assign the drive letter H:

    3: Copy the Data from D drive to H:

    4: Interchange the drive letter D to H and H to D (Change Drive letter ) 

    5: Run the command: "bcdboot C:\Windows /s D: /f ALL"

    6: Stop the Azure Stack. ( https://bit.ly/2uQTwtx  )

    7: Restart the Server.

    8: Start the Azure Stack.

    I faced some challenges eg. Portal was not accessible but after start the Cluster (FC) and restart few VMs (NC, SLB, GWY etc on hyper-v)

    But issue was resolved. If hope this will help!

    (Redeploy ASDK is not a good idea it takes 8 hrs. In my case it was success on 4th attempt after a lots of Troubleshooting)




    Wednesday, July 25, 2018 11:24 PM