none
Operating system error 2(error not found) occurred while creating or opening file 'E:\xxx\s9a\MSSQL.1\MSSQL\DATA\mastlog.ldf -T 3608'

    Question

  • There was a power failure and now we have this. Checked the disk files are there a checkdisk reports no errors. Other than redoing the setup any other options ?


    yup
    Friday, May 13, 2011 4:16 AM

Answers

  • Do you have a backup of your model database?  If so, just restore it. 

    If you don't have a backup of your model database and have another working SQL Server instance, you can just backup its model database and restore it on the broken server.

    The model database is generic (Unless you've done modifications to it in which case, you should have a tested backup that you could restore from) so restoring it from another SQL Server instance won't cause any problems.


    Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt) MCT, MCPD, MCITP, MCDBA, MCSD, MCAD
    Friday, May 13, 2011 6:15 AM

All replies

  • Are you getting this when you try and start  SQL Server (I'm guessing that mastlog.ldf is the log file for the Master Database)?  If so, what version of SQL Server do you have installed?

     


    Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt) MCT, MCPD, MCITP, MCDBA, MCSD, MCAD
    Friday, May 13, 2011 4:21 AM
  • This is SQL 9 dev ed. In case 3608 is not used the error comes for model.
    yup
    Friday, May 13, 2011 5:48 AM
  • Are you 100% sure it's the model database as by default, mastlog.ldf is the log file for the Master Database?

    If it is as I suspect and the error is caused by the Master Database  logfile being corrupt or missing, read http://msdn.microsoft.com/en-us/library/ms143269(v=sql.90).aspx


    Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt) MCT, MCPD, MCITP, MCDBA, MCSD, MCAD
    Friday, May 13, 2011 5:54 AM
  • When TF 3608 is used the error comes for master else its happening on model here is a part from the logs

    2011-05-13 09:19:58.17 spid5s      Starting up database 'master'.
    2011-05-13 09:19:59.05 spid5s      SQL Trace ID 1 was started by login "sa".
    2011-05-13 09:20:00.34 spid5s      Starting up database 'mssqlsystemresource'.
    2011-05-13 09:20:00.37 spid5s      The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
    2011-05-13 09:20:00.79 spid5s      Server name is 'WIN-RC\S9A'. This is an informational message only. No user action is required.
    2011-05-13 09:20:00.79 spid9s      Starting up database 'model'.
    2011-05-13 09:20:00.80 spid9s      Error: 9003, Severity: 20, State: 1.
    2011-05-13 09:20:00.80 spid9s      The log scan number (919:40:1) passed to log scan in database 'model' 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.

     

    Redoing setup / rebilding master will be the last option....


    yup
    Friday, May 13, 2011 5:59 AM
  • Do you have a backup of your model database?  If so, just restore it. 

    If you don't have a backup of your model database and have another working SQL Server instance, you can just backup its model database and restore it on the broken server.

    The model database is generic (Unless you've done modifications to it in which case, you should have a tested backup that you could restore from) so restoring it from another SQL Server instance won't cause any problems.


    Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt) MCT, MCPD, MCITP, MCDBA, MCSD, MCAD
    Friday, May 13, 2011 6:15 AM