SQL Server 2008 R2 installation error 5178

Question

Kevin.L.Li on Wed, 11 Jan 2012 03:52:51


Hi All,

Can anyone shed some light on this? I've been searching answer on the web but with no luck. basically i got the following error in the sql error log while i was trying to intall SQL Server 2008 R2 Express.

2012-01-03 11:58:26.26 spid7s      Starting up database 'master'.
2012-01-03 11:58:26.28 spid7s      Error: 5178, Severity: 16, State: 1.
2012-01-03 11:58:26.28 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.QSRNVIVO9\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2012-01-03 11:58:26.28 spid7s      Error: 5178, Severity: 16, State: 1.
2012-01-03 11:58:26.28 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.QSRNVIVO9\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2012-01-03 11:58:26.30 spid7s      Error: 5178, Severity: 16, State: 1.
2012-01-03 11:58:26.30 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.QSRNVIVO9\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2012-01-03 11:58:26.30 spid7s      Error: 5178, Severity: 16, State: 1.
2012-01-03 11:58:26.30 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.QSRNVIVO9\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.

Below is some details about the machine.

Machine processor count:       2
  OS version:                    Windows Vista Home Premium
  OS service pack:               Service Pack 2
  OS region:                     United States
  OS language:                   German
  OS architecture:               x86
  Process architecture:          32 Bit
  OS clustered:                  No

C drive has 200GB+ free space and is formatted with 'Allocation unit size' = 4096 bytes

Also, chkdsk initially found a file system problem but it had been fixed by running the 'chkdsk /F' command.

Thanks,

Kevin





Replies

Alberto Morillo on Wed, 11 Jan 2012 11:33:28


Hello,

Try you stop SQL Server services and move the databases to a USB drive, then move them back to the original location, and try to start the SQL Services. You may not be able to move the databases, because there are still some issues with the hard drive.

If you restart the machine, does chkdsk tries to repair again the drive?

Hope this helps.


Regards,

Alberto Morillo
SQLCoffee.com

Richard Douglas on Wed, 11 Jan 2012 13:59:16


Interesting what size allocation unit does it say when you run "fsutil fsinfo ntfsinfo c:" from the CMD prompt as an administrator?

I would be very worried about the state of that drive.

Kevin.L.Li on Fri, 13 Jan 2012 04:38:18


thanks for your suggestion. i'll try that when i get access to the machine next time (probably sometime next week). In case i can move database files fine but still not able to start the SQL Server service, what else do you think i can try to narrow down the problem? I've tried to re-install SQL Server after fixed the chkdsk problem but that doesn't help.  

No, the chkdsk no longer reports any errors.

Cheers, Kevin

Kevin.L.Li on Fri, 13 Jan 2012 04:53:00


Thanks Richard. I've asked our customer (whose machine has the problem) to run this command, probably can get some result back early next week.

Ricardo Muramatsu on Sun, 18 Mar 2012 16:11:56


I've the same problem.

What do you did to solve this?

C:\Windows\system32>fsutil fsinfo ntfsinfo c:
NTFS Volume Serial Number :       0xc22c916a2c915a6d
NTFS Version   :                  3.1
LFS Version    :                  2.0
Number Sectors :                  0x000000001d11596b
Total Clusters :                  0x0000000003a22b2d
Free Clusters  :                  0x0000000002e33349
Total Reserved :                  0x0000000000000650
Bytes Per Sector  :               512
Bytes Per Physical Sector :       512
Bytes Per Cluster :               4096
Bytes Per FileRecord Segment    : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length :           0x0000000007800000
Mft Start Lcn  :                  0x00000000000c0000
Mft2 Start Lcn :                  0x0000000000000002
Mft Zone Start :                  0x0000000000c253e0
Mft Zone End   :                  0x0000000000c31c00
Resource Manager Identifier :     1B35AE90-7116-11E1-B055-8AA60C2F56BB

George P Boutwell on Mon, 16 Apr 2012 02:27:12


Have you received anything back from Microsoft on this issue?  Have you been able to work around it or get any version of SQL Server installed on the Windows 8 Client that you have?  I am having this same problem/issue.

Thanks,

George

AdamOndracek on Mon, 27 Aug 2012 19:46:41


Hello.

I had similar issue after I have cloned my system drive to a new hybrid hard drive.

Problem disappeared after SATA driver update. I simply installed Intel Rapid Storage.

Intel Rapid Storage driver download


TomMcEwen on Sun, 09 Dec 2012 03:29:14


After lots of frustration trying to figure this out -After upgrade to 2008R2 SP2 on 1TB drive the Intel Rapid Storage Driver download and install fixed this problem. I checked to make sure my Intel chipset was supported, installed in about a minute, rebooted, and it was fixed. Thanks Adam.

PaulErnsdorff on Mon, 18 Feb 2013 19:54:17


Wanted to share that I had similar problem with the reported sector size issue

Windows 8 x64 RAID 0

Had SQL Express installed and running with no problems. Not sure what happened but noticed service failed to start because of reported sector size of 3072 - fsutil reported 4096.

I then uninstalled and attempted to reinstall but no matter what I did the database engine component failed to install/initialize. After reviewing the SQL logs it seemed to be related to the mounted filesystem during install - just a guess on my part. So I extracted the files from the single exe installer and ran from there - this time installed fine.

I had at one point also reinstalled the Intel Matrix Storage Manager drivers but it did not appear to solve this.

JohnC3 on Wed, 20 Nov 2013 18:24:45


I ran into this as well, but was able to resolve it using the Intel Rapid Storage Download link referenced earlier in this thread. 

Here's the scenario:  Dell Latitude E6500, Win 7 x64.  I run 3 instances of SQL Server on this machine (05,08, and 12); it is a development machine.

Recently, the 500gb drive in my spare media bay drive, where my database files are, started reporting USB device errors.  After scanning it, I discovered that the Dell utilities were reporting a Western Digital drive error code.  So, I backed the drive up (it was still functioning), and then replaced it with a 1TB Western Digital Scorpio Blue drive.  (Same brand and type as the original, drive, just in the large format 1TB option).

Everything "seemed" ok... until I started accessing SQL Server 2008 databases.  SQL 2k5 and 2k12 didn't seem to mind, but SQL 2k8 started throwing:

Cannot use file 'd:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2K8\MSSQL\DATA\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.

I fell back to my "dying" 500gb drive while I tried to figure out what to do.  I found some information about bios/firmware issues with Dell, that turned out to be a bad path.  I ran the Intel Rapid Storage Win 7 x64 installer (didn't need all that floppy/non floppy stuff the Intel site talked about).  I put my 1TB drive back in the bay...and tada, all 3 instances of SQL Server (and my instance of DB2) are all happy... so far. 

I did find in the windows event log the following for both the SQL 2k8 and 2k12 instances after coming back up on the 1tb drive with the Intel Driver update:

The tail of the log for database DataMart is being rewritten to match the new sector size of 4096 bytes.  1024 bytes at offset 553905152 in file D:\MSSQL\LOGs\DataMart5.ldf will be written.

So far no ill effects...

-Vinny- on Mon, 24 Nov 2014 22:30:03


I know 2 years have passed...

I just had the same problem with SQL2014 after I cloned a drive onto a new hybrid drive, the motherboard in the machine is an Intel but is too old to have a new version of the Intel storage driver loaded so I reverted to the Standard AHCI 1.0 Serial ATA Controller driver and it fixes the problem.