SQL Server Cluster Installation Failed

I need help trying to solve this as I've spent tons of time trying to figure this out but have had no luck. I created a VMWare Workstation test environment and I have been trying to install SQL Cluster on one of my Nodes.

From the looks of it, it looks like it's a storage configuration problem but at this point I have no idea what else I could do and there isn't much online about it. Please look at the log and any input would be appreciated.

`2016-03-06 19:02:50.76 Server Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
Feb 20 2014 20:04:26
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor)

2016-03-06 19:02:50.76 Server UTC adjustment: -8:00
2016-03-06 19:02:50.76 Server (c) Microsoft Corporation.
2016-03-06 19:02:50.76 Server All rights reserved.
2016-03-06 19:02:50.76 Server Server process ID is 1860.
2016-03-06 19:02:50.76 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2016-03-06 19:02:50.76 Server Authentication mode is WINDOWS-ONLY.
2016-03-06 19:02:50.76 Server Logging SQL Server messages in file 'M:\MSSQL12.SQLCLUST14INS1\MSSQL\Log\ERRORLOG'.
2016-03-06 19:02:50.76 Server The service account is 'UVIT\administrator'. This is an informational message; no user action is required.
2016-03-06 19:02:50.76 Server Registry startup parameters:
-d M:\MSSQL12.SQLCLUST14INS1\MSSQL\DATA\master.mdf
-e M:\MSSQL12.SQLCLUST14INS1\MSSQL\Log\ERRORLOG
-l M:\MSSQL12.SQLCLUST14INS1\MSSQL\DATA\mastlog.ldf
2016-03-06 19:02:50.76 Server Command Line Startup Parameters:
-s "SQLCLUST14INS1"
2016-03-06 19:02:51.02 Server SQL Server detected 1 sockets with 1 cores per socket and 1 logical processors per socket, 1 total logical processors; using 1 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2016-03-06 19:02:51.02 Server SQL Ser

I wanted to respond with my fix to the issue just incase anyone is doing a test environment with VMWorkstation/FreeNas. So it looks like my issue was in the formatting of the physical drive on my PC. I had done the above and while everything matched to SQL best practices I still received the error. It was until I scrapped everything and formatted the physical drive on my pc that I was assigning to the FreeNas that everything seemed to work. Til this day I don't completely 100% understand it but since I did that, installed with zero issues.

My Scenario looked like this:
Physical SSD on PC -> VMWare HDD Image -> FreeNas -> SQLNodes Shared Storage
Physical SSD was formatted with
512 512 4096 1024 while when on FreeNas shared storage it was 512 4096 64k 1024.
This scenario didn't work.

Once I set my Physical SSD to 512 512 64k 1024 and Shared Storage to 512 4096 64k 1024. It worked on first try with zero issues.

Again this to me makes no sense at least don't understand it 100% but it works now. At first I was going crazy with the formatting the storage within the VMs/FreeNas that I tried multiple combinations and nothing worked until I did this.

StackExchange Database Administrators Q#131461, answer score: 2