cannot create volume due to S2D configuration issue about azurestackhci-evalguide

[ercohen19]

Thanks for letting us know about your issue. We will test the lab over the next few days and follow up.

[ercohen19]

Hi, can you clarify which script you ran that caused this error? If possible, please attach an image of the entire PowerShell window with the command you executed and the resulting error. Thanks!

[Ferasshehadeh]

Hello Eleanor, This was done by someone else and they opened a ticket with CSS MS. They went through the steps which the article intended to be for multiple times, but they always experienced the S2D error that does not have enough space to create a volume. Could not have time to repro, but if you could not most probably its a customer error. However wanted to highlight in case was not tested. Thanks Feras. From: Eleanor Cohen ***@***.***> Sent: Tuesday, January 4, 2022 8:14 PM To: Azure/AzureStackHCI-EvalGuide ***@***.***> Cc: Ferasshehadeh ***@***.***>; Author ***@***.***> Subject: Re: [Azure/AzureStackHCI-EvalGuide] cannot create volume due to S2D configuration issue (Issue #70) Hi, can you clarify which script you ran that caused this error? If possible, please attach an image of the entire PowerShell window with the command you executed and the resulting error. Thanks! — Reply to this email directly, view it on GitHub<#70 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AN6CRDM5AEHZM7BCQSETLDLUUNIH7ANCNFSM5KQDF63Q>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[ercohen19]

Hi Feras,

Yes, sorry I was not able to repro the issue. I reran the lab this week and successfully created a volume. I would recommend that the customer redeploy their cluster and try again. Let me know if they continue running into errors.

Thanks,
Ellie