title: Prevent MS SQL 2005 master DB from being corrupted
body: <p>I am trying to resolve what cause the following corruption.</p>
  
  <blockquote>
    <p>2011-06-29 10:47:26.42 spid5s      Starting up database 'master'. </p>
    
    <p>2011-06-29 10:47:26.53 spid5s      Error: 9003, Severity: 20, State: 1.</p>
    
    <p>2011-06-29 10:47:26.53 spid5s      The log scan number (216:72:1) passed to log scan in database 'master' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. </p>
    
    <p>2011-06-29 10:47:26.53 spid5s 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.</p>
  </blockquote>
  
  <p>I can find plenty of threads and information on how to recover databases when master db is corrupt. I can recover them succussfully.</p>
  
  <p>HOWEVER, this is not very satisfactory for customers to have perform these operations. I have been able to examine event log files of when the corruption occurs. From there I can see server working fine then computer is shutdown, few hours later the computer is switched on and master db is corrupted.</p>
  
  <p>Any help greatly appreciated</p>