Search

SQL Server 2012 Startup Error with Sector Size Reported as 1048576 by JerryM_YorkBI

Resolved
as External Help for as External

3
0
Sign in
to vote
Type: Bug
ID: 778042
Opened: 1/31/2013 7:26:36 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
I have an application that uses SQL Server Express 2012. It is a single-user application that is being installing on a customer server instead of a workstation. After the install completes, start-up of the service fails. There is a SQLServer_ERRORLOG log that has this:

Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Template Data\master.mdf'
because it was originally formatted with sector size 4096 and is now on a volume with sector size 1048576.
Move the file to a volume with a sector size that is the same as or smaller than the original sector size.

The server is a HP ProLiant ML350 G5 running Windows Server 2012. FSUTIL reports 4096 as the sector size. (FSUTIL FSINFO NTFSINFO).

Regards,
Jerry Metcoff
York Group BI LLC
Details (expand)

Product Language

English

Version

SQL Server 2012 - Express Edition

Category

SQL Express

Operating System

Windows Server 2012 Standard

Operating System Language

US English

Steps to Reproduce

Install SQL 2012 Express.

Actual Results

Service will not start. Error message indicates disk is not supported.

Expected Results

Service should start.

Platform

X64

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 5/10/2013 at 10:01 AM
Hi
Thanks for reporting this issue. We are not able to reproduce this behavior with the information provided and this item is being closed.

Thanks,
Ajay.
Senior Program Manager
Microsoft SQL Server
Posted by TUmphress on 2/13/2013 at 11:55 AM
We are having the same issue - the only difference is that your sector size is being reported as 2097152 instead of 1048576.

We are tring to install on Windows Server 2012 which is installed on a Cisco UCS B230M2 blade that is booting from a SAN.
Sign in to post a workaround.