@r3dpand4 said in Configuring Multi-Resilient Volume with Storage Spaces:

Should be noted that any server running 1709 cannot be added to S2D pools as it stands currently since it's not considered production ready....

Correct. S2D is gone from non-GA WS2016.

https://docs.microsoft.com/en-us/windows-server/get-started/server-1709-relnotes

Storage Spaces Direct

Storage Spaces Direct is not included in Windows Server, version 1709. If you call Enable-ClusterStorageSpacesDirect or its alias Enable-ClusterS2D, on a server running Windows Server, version 1709, you will receive an error with the message "The requested operation is not supported". It is also not supported to introduce servers running Windows Server, version 1709 into a Windows Server 2016 Storage Spaces Direct deployment.

@scottalanmiller said:

This means that resilvers expected to fail when we look at the math model that only gives has an average (mean) failure rate we get successful resilver after success resilver. This also means that array expansion operations (replacing one drive at a time with a larger drive) would also be far more likely to be successful than expected based solely on the math averages.

And that's how my boss got away with it heheh (well so far)