Hello team,
We were installing SQL Server 2014 as a part of setting up our SharePoint 2013 environment.
In the "installation section" the setup failed giving the following error:
Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.
We checked the details of the E: partition as follows by running command "Fsutil fsinfo ntfsinfo e:" --
Bytes Per Sector : 512
Bytes Per Physical Sector : 4096
Bytes Per Cluster : 4096
Now we are not sure if the formatting has gone wrong or any other thing. For reference, the error log is as follows:
2015-06-02 07:07:39.71 Server Microsoft SQL Server 2014 - 12.0.2000.8 (X64) Feb 20 2014 20:04:26 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) 2015-06-02 07:07:39.71 Server UTC adjustment: -4:00 2015-06-02 07:07:39.71 Server (c) Microsoft Corporation. 2015-06-02 07:07:39.71 Server All rights reserved. 2015-06-02 07:07:39.71 Server Server process ID is 3100. 2015-06-02 07:07:39.71 Server System Manufacturer: 'IBM', System Model: 'System x3550 M3 -[7944AC1]-'. 2015-06-02 07:07:39.71 Server Authentication mode is MIXED. 2015-06-02 07:07:39.71 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'. 2015-06-02 07:07:39.72 Server The service account is 'domain\sql_services'. This is an informational message; no user action is required. 2015-06-02 07:07:39.72 Server Registry startup parameters: -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf 2015-06-02 07:07:39.72 Server Command Line Startup Parameters: -s "MSSQLSERVER" -m "SqlSetup" -Q -q "SQL_Latin1_General_CP1_CI_AS" -T 4022 -T 4010 -T 3659 -T 3610 -T 8015 2015-06-02 07:07:39.98 Server SQL Server detected 2 sockets with 4 cores per socket and 8 logical processors per socket, 16 total logical processors; using 16 logical processors based on SQL Server licensing. This is an informational message; no user action is required. 2015-06-02 07:07:39.98 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2015-06-02 07:07:39.98 Server Detected 16372 MB of RAM. This is an informational message; no user action is required. 2015-06-02 07:07:39.98 Server Using conventional memory in the memory manager. 2015-06-02 07:07:40.26 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033) 2015-06-02 07:07:40.30 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled. 2015-06-02 07:07:40.32 Server Query Store settings initialized with enabled = 1, 2015-06-02 07:07:40.32 Server The maximum number of dedicated administrator connections for this instance is '1' 2015-06-02 07:07:40.33 Server Node configuration: node 0: CPU mask: 0x000000000000ffff:0 Active CPU mask: 0x000000000000ffff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 2015-06-02 07:07:40.35 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. 2015-06-02 07:07:40.35 Server Lock partitioning is enabled. This is an informational message only. No user action is required. 2015-06-02 07:07:40.38 Server Database Mirroring Transport is disabled in the endpoint configuration. 2015-06-02 07:07:40.38 spid8s Warning ****************** 2015-06-02 07:07:40.39 spid8s SQL Server started in single-user mode. This an informational message only. No user action is required. 2015-06-02 07:07:40.39 spid8s Starting up database 'master'. 2015-06-02 07:07:40.47 Server CLR version v4.0.30319 loaded. 2015-06-02 07:07:40.49 Server Software Usage Metrics is disabled. 2015-06-02 07:07:40.70 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\. 2015-06-02 07:07:40.81 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required. 2015-06-02 07:07:40.81 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required. 2015-06-02 07:07:40.88 spid8s SQL Trace ID 1 was started by login "sa". 2015-06-02 07:07:40.90 spid8s Server name is 'INTRAUATDB2013'. This is an informational message only. No user action is required. 2015-06-02 07:07:40.91 spid17s Password policy update was successful. 2015-06-02 07:07:40.96 spid17s A self-generated certificate was successfully loaded for encryption. 2015-06-02 07:07:40.96 spid17s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. 2015-06-02 07:07:40.96 spid17s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required. 2015-06-02 07:07:40.96 spid17s SQL Server is now ready for client connections. This is an informational message; no user action is required. 2015-06-02 07:07:40.96 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required. 2015-06-02 07:07:40.98 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/IntraUATDB2013.***.****.com ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 2015-06-02 07:07:40.98 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/IntraUATDB2013.***.****.com:1433 ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 2015-06-02 07:07:42.48 spid18s A new instance of the full-text filter daemon host process has been successfully started. 2015-06-02 07:07:42.66 spid8s Starting up database 'msdb'. 2015-06-02 07:07:42.67 spid11s Starting up database 'mssqlsystemresource'. 2015-06-02 07:07:42.69 spid11s The resource database build version is 12.00.2000. This is an informational message only. No user action is required. 2015-06-02 07:07:42.83 spid11s Starting up database 'model'. 2015-06-02 07:07:43.09 spid11s Clearing tempdb database. 2015-06-02 07:07:43.60 spid11s Starting up database 'tempdb'. 2015-06-02 07:07:43.71 spid8s Recovery is complete. This is an informational message only. No user action is required. 2015-06-02 07:07:43.81 spid51 Changed database context to 'master'. 2015-06-02 07:07:43.81 spid51 Changed language setting to us_english. 2015-06-02 07:07:44.03 spid51 Setting database option RECOVERY to FULL for database 'model'. 2015-06-02 07:07:44.09 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.12 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.13 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.14 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.26 spid51 Setting database option NEW_BROKER to ON for database 'tempdb'. 2015-06-02 07:07:44.30 spid51 Setting database option NEW_BROKER to ON for database 'msdb'. 2015-06-02 07:07:44.43 spid51 The file "tempdev" has been modified in the system catalog. The new path will be used the next time the database is started. 2015-06-02 07:07:44.44 spid51 The file "templog" has been modified in the system catalog. The new path will be used the next time the database is started. 2015-06-02 07:07:44.59 spid51 Changed database context to 'master'. 2015-06-02 07:07:44.59 spid51 Changed language setting to us_english. 2015-06-02 07:07:44.86 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.88 spid51 Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.90 spid51 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required. 2015-06-02 07:07:44.94 spid51 Using 'xpstar.dll' version '2014.120.2000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required. 2015-06-02 07:07:44.96 spid51 Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install. 2015-06-02 07:07:44.97 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. 2015-06-02 07:07:46.11 spid51 Changed database context to 'master'. 2015-06-02 07:07:46.11 spid51 Changed language setting to us_english. 2015-06-02 07:07:46.27 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:07:46.27 spid51 Cannot use file 'F:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer_log.ldf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:07:46.27 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:07:46.27 spid51 Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:07:46.27 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:07:46.27 spid51 Cannot use file 'F:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer_log.ldf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:07:46.27 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:07:46.27 spid51 Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:07:46.27 spid51 Error: 1802, Severity: 16, State: 4. 2015-06-02 07:07:46.27 spid51 CREATE DATABASE failed. Some file names listed could not be created. Check related errors. 2015-06-02 07:42:06.49 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:42:06.49 spid51 Cannot use file 'F:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer_log.ldf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:42:06.49 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:42:06.49 spid51 Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:42:06.49 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:42:06.49 spid51 Cannot use file 'F:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer_log.ldf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:42:06.49 spid51 Error: 5179, Severity: 16, State: 1. 2015-06-02 07:42:06.49 spid51 Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size. 2015-06-02 07:42:06.49 spid51 Error: 1802, Severity: 16, State: 4. 2015-06-02 07:42:06.49 spid51 CREATE DATABASE failed. Some file names listed could not be created. Check related errors. 2015-06-02 07:48:37.45 Logon Error: 18461, Severity: 14, State: 1. 2015-06-02 07:48:37.45 Logon Login failed for user 'domain\sql_admin'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>] 2015-06-02 07:49:43.17 Logon Error: 18461, Severity: 14, State: 1. 2015-06-02 07:49:43.17 Logon Login failed for user 'domain\sql_services'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>] 2015-06-02 07:49:43.19 Logon Error: 18461, Severity: 14, State: 1. 2015-06-02 07:49:43.19 Logon Login failed for user 'domain\sql_services'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>] 2015-06-02 08:01:23.49 Logon Error: 18461, Severity: 14, State: 1. 2015-06-02 08:01:23.49 Logon Login failed for user 'sa'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
Kindly give your expert sugessions. Thanks.
Regards, Nayan