Problem with SAS Volumes
Heads Up: I had to add a couple of extra steps to get this to work correctly. Apparently failover clustering by default will assume all SAS volumes are meant to be shared cluster storage and try to commandeer them, which makes SQL unable to come up because its data and log volumes aren't mounted. Workaround is essentially to release them with the Failover Cluster Manager and then bring them online with Disk Management:
https://blog.sqlauthority.com/2016/11/08/sql-server-added-new-node-windows-cluster-alwayson-availability-databases-stopped-working/
https://support.microsoft.com/en-za/help/2813005/local-sas-disks-getting-added-in-windows-server-2012-failover-cluster
@tmustain I'm getting a similar issue. Was able to get it to manually work.
I apologize for not responding sooner, we recently made some updates to this Quick Start. Can you verify if you see this issue still existing? We did drop support for Windows 2012 in the quick start, and support Windows 2019. Please let us know if this still exist.