Horkay Blog
The postings on this site are my own and do not represent my Employer's positions, advice or strategies.
Monday, 16 June 2014

Here is Vasilli working the best cane this side of Ukraine.

 

Eagle Cane and walking stick

Monday, 16 June 2014 12:37:30 (Central Standard Time, UTC-06:00) | Comments [0] | Web_Blog#
Friday, 06 June 2014

Cannot recover the master database.
-------------------------- From SQL Server Error Log ---------------------
Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
During redoing of a logged operation in database 'master', an error occurred at log record ID (2041:52:2). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
Error: 3313, Severity: 21, State: 1.
Could not redo log record (2041:52:2), for transaction ID (0:0), on page (1:19), allocation unit 458752, database 'master' (database ID 1). Page: LSN = (2040:369:229), allocation unit = 458752, type = 1. Log: OpCode = 18, context 2, PrevPageLSN: (2040:349:127). Restore from a backup of the database, or repair the database.
Error: 3456, Severity: 21, State: 1.
Starting up database 'master'.
-----------------------------

Never a good day when this happens, especially on a clustered sql server, there goes your HA and your 5 9's !

What now ?

Figure out what happened, why is my master database corrupt (in this case the cluster crashed because of an "unintended consequence" of a network change).  If it's something like hardware or some other physical problem, get that corrected.

Once that's corrected you still have to recover the master database.

If your like me, you have good backups, but they are all .BAK files.  How can your restore a .BAK file, if you can't even get SQL to start ?

There are ways and any of them work, here's what you do.

1.  Just in case things don't work, and time is critical, have someone else start a support call with Microsoft, just in case.
2.  Copy your existing master.mdf and ldf to some safe location (I usually make a sub-directory under where-ever the system databases are), this is "just in case".
3.  Get a copy of master.mdf and ldf from some where of the same version and preferably service-pack and CU.
       a.  You can get a copy from the installation media (mdf and ldf)
       b.  I think there is a rebuildm.exe utility on installation media.
           1.  I don't have time to mess around with installation media so I usually go with something else
       c.  You can grab another Master mdf and l
       d.  I restore the master_{some timestamp}.bak to another sql server
           1.  copy the .bak file to another sql server (of same version)
           2.  restore the .bak, but with a different database name, master_tmp
               - keep the data files named the same master.mdf and mastlog.ldf
               - you may need to ensure a different path than the existing master.mdf and ldf to avoid failure on restore
           3.  detach the newly restored database master_tmp
           4.  now you have master.mdf and mastlog.ldf
4.  Copy the master.mdf and ldf from step above, over-writing the existing master.mdf and ldf
5.  ensure in cluster manager to put the sql server services "offline" (they should be in a "failed" state now).
6.  Start SQL Server manually from a command prompt (enusre to start command prompt with administrative privileges)
7.  {find the correct path to }\sqlserver.exe -m -s {instance name}
8.  once started you really still need to restore the database from the .bak, as the overlay method of restoring master with a different name and then copying the files doesn't quite leave the state the same as a restore
9.  restore {master} from disk='' with replace
10.  SQL Server should automatically stop
11.  you should now be able to start sql from cluster manager and all should be good.

Friday, 06 June 2014 10:33:54 (Central Standard Time, UTC-06:00) | Comments [0] | SQL Server#
Search
Popular Posts
Unpatched Vulnerabiltiy discovered ...
Spring Fornicator brewed...
DTA - Failed to initialize MSDB dat...
SQL Server Security, not where it n...
Check the Uptime of a Windows Serve...
Recent Posts
Archive
May, 2017 (2)
April, 2017 (1)
March, 2017 (1)
February, 2017 (1)
December, 2016 (2)
October, 2016 (2)
September, 2016 (1)
August, 2016 (1)
July, 2016 (1)
March, 2016 (2)
February, 2016 (3)
December, 2015 (4)
November, 2015 (6)
September, 2015 (1)
August, 2015 (2)
July, 2015 (1)
March, 2015 (2)
January, 2015 (1)
December, 2014 (3)
November, 2014 (1)
July, 2014 (2)
June, 2014 (2)
May, 2014 (3)
April, 2014 (3)
March, 2014 (1)
December, 2013 (1)
October, 2013 (1)
August, 2013 (1)
July, 2013 (1)
June, 2013 (2)
May, 2013 (1)
March, 2013 (3)
February, 2013 (3)
January, 2013 (1)
December, 2012 (3)
November, 2012 (1)
October, 2012 (1)
September, 2012 (1)
August, 2012 (1)
July, 2012 (4)
June, 2012 (3)
April, 2012 (1)
March, 2012 (3)
February, 2012 (3)
January, 2012 (4)
December, 2011 (3)
October, 2011 (2)
September, 2011 (2)
August, 2011 (8)
July, 2011 (4)
June, 2011 (3)
May, 2011 (3)
April, 2011 (1)
March, 2011 (2)
February, 2011 (3)
January, 2011 (1)
September, 2010 (1)
August, 2010 (2)
May, 2010 (2)
April, 2010 (3)
March, 2010 (1)
February, 2010 (4)
January, 2010 (1)
December, 2009 (3)
November, 2009 (2)
October, 2009 (2)
September, 2009 (5)
August, 2009 (4)
July, 2009 (8)
June, 2009 (2)
May, 2009 (3)
April, 2009 (9)
March, 2009 (6)
February, 2009 (3)
January, 2009 (8)
December, 2008 (8)
November, 2008 (4)
October, 2008 (14)
September, 2008 (10)
August, 2008 (7)
July, 2008 (7)
June, 2008 (11)
May, 2008 (14)
April, 2008 (12)
March, 2008 (17)
February, 2008 (10)
January, 2008 (13)
December, 2007 (7)
November, 2007 (8)
Links
Categories
Admin Login
Sign In
Blogroll