master database corrupted

  • I got below error after rebooting one of my production SQL server 2012 enterprise,

    The log scan number (151082:691:0) 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.

    This seems master database is corrupted, the SQL server service is not starting, i have latest full back of master, where do i restore master when sql service is not running? If i restore master what will happen to user db's? is there any difference in restoring master and re-installing sql server?

    Very much appriciate your replies.

    Thanks

  • Can you start the instance in single-user mode (-m startup parameter)? You might need to use sqlcmd.

    https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/restore-the-master-database-transact-sql?view=sql-server-2017

  • Beatrix Kiddo - Thursday, June 21, 2018 9:10 AM

    Can you start the instance in single-user mode (-m startup parameter)? You might need to use sqlcmd.

    https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/restore-the-master-database-transact-sql?view=sql-server-2017

    I am getting same error when i try to start SQL server in single user mode, Can we still start the SQL server even when the master files corrupted?

  • Take a look at scenario 2 as written in this article. With this scenario you create a new [master] database after which you can replace it with the restore from your back-up.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
  • This was removed by the editor as SPAM

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply