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 <X64> (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 Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-03-06 19:02:51.02 Server Detected 2047 MB of RAM. This is an informational message; no user action is required.
2016-03-06 19:02:51.02 Server Using conventional memory in the memory manager.
2016-03-06 19:02:51.07 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2016-03-06 19:02:51.17 Server Query Store settings initialized with enabled = 1,
2016-03-06 19:02:51.18 Server This instance of SQL Server last reported using a process ID of 1696 at 3/2/2016 12:33:34 PM (local) 3/2/2016 8:33:34 PM (UTC). This is an informational message only; no user action is required.
2016-03-06 19:02:51.18 Server The maximum number of dedicated administrator connections for this instance is '1'
2016-03-06 19:02:51.18 Server Node configuration: node 0: CPU mask: 0x0000000000000001:0 Active CPU mask: 0x0000000000000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-03-06 19:02:51.18 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2016-03-06 19:02:51.20 Server CLR version v4.0.30319 loaded.
2016-03-06 19:02:51.44 spid8s Starting up database 'master'.
2016-03-06 19:02:51.47 spid8s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file M:\MSSQL12.SQLCLUST14INS1\MSSQL\DATA\master.mdf.
2016-03-06 19:02:51.48 spid8s Unable to create stack dump file due to stack shortage (ex_terminator - Last chance exception handling)
2016-03-06 19:02:51.48 spid8s Stack Signature for the dump is 0x0000000000000000
2016-03-06 19:02:51.51 spid8s [INFO] Identity Begin End | State Result Error Speculate Prepared LazyCommit ReadOnly | Transaction Database ThreadId | ReadSet WriteSet ScanSet Savepoint LogSizeRq | CommitDep TotalComm Dependent 0 Dependent 1 Dependent 2 Dependent 3 Dependent 4 Dependent 5 Dependent 6 Dependent 7 | Area Location |
2016-03-06 19:02:51.57 Server Software Usage Metrics is enabled.
2016-03-06 19:02:52.74 spid8s External dump process return code 0x20000001.
External dump process returned no errors.
Best Answer
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.