SQL 2008 R2 - Starting SQL Causes 5178 error in log - Segment Size Different

Question

The SQL Server 2008 R2 was running fine.
I cloned the 320 Gb harddrive to a 500 GB harddrive. The oriignal drive was 8/ 4096 structure. After the drive was cloned the new drive is 8/4096 structure

Chckdsk had no issues with original drive
Chckdsk has no issues with new cloned driver
When I try to start SQL, the below log shows the master db with issues regarding sector size. Any suggestions would be appreciated.


segment size: 2012-04-12 14:38:08.28 spid7s      Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MYSQL2008\MSSQL\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-04-12 14:38:08.28 spid7s      Error: 5178, Severity: 16, State: 1.
2012-04-12 14:38:08.28 spid7s      Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MYSQL2008\MSSQL\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-04-12 14:38:08.30 spid7s      Error: 5178, Severity: 16, State: 1.
2012-04-12 14:38:08.30 spid7s      Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MYSQL2008\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.
2012-04-12 14:38:08.30 spid7s      Error: 5178, Severity: 16, State: 1.
2012-04-12 14:38:08.30 spid7s      Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MYSQL2008\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.

Answer 1

Check the below one..

http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/94d62e2a-7a9b-4ba0-a408-8e30e7fe47f4

---

Rama Udaya.K ramaudaya.blogspot.com

Answer 2

Rama, thanks.

For all that are viewing this issue. The problem was resolve but it is complex. Notice in my original emaiil I said I cloned the drive. After doing hours of resaerch I discovered that the new drive I was using was an Advanced Format drive - and that was the cause of everthing.  Apparently the drives we buy now are all Advanced Format.    A little more detail....

SQL was not the only thing that was causing issues, I could not even get windows update to work after I cloned the original to new drive. After discovering that the new drive I had was Adnvacned Format design, the old one was NOT, that had me finding patches available for this. One from MS and antoher one that may have helped from Lenova. None of them worked for me. I worked on this task, off-and-on for weeks. Tried different combinations of what I installed first and tried things over and over again - cloneing, pathc installs. Nothing fixed it. The only thing that worked for me was to find ANTOHER 500 gig drive that DID NOT HAVE Advanced Formatting - the old style. I found one, I cloned my orignal disk and everything worked fine - everything!!!  You will find many people that have issues with this as I did.

Hope this helps someone.