помогите восстановить работу локального sql-сервера

SQl Server 2005, с утра комп два раза сам перезагружался. фиг знает почему, бесперебойник стоит - не помог. Видимо что-то с блоком питания. Ну да фиг с ним.
После этого перестала стартовать служба MSSQLServer.
В логах такое вижу:
Сначала вроде стартует, потом
2012-09-18 10:37:44.78 spid12s Starting up database 'msdb'.
2012-09-18 10:37:44.79 spid16s Starting up database 'TestBase'.
2012-09-18 10:37:45.96 spid12s Error: 9003, Severity: 20, State: 1.
2012-09-18 10:37:45.96 spid12s The log scan number (118:408:34) passed to log scan in database 'msdb' 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.
2012-09-18 10:37:45.96 spid12s Error: 3414, Severity: 21, State: 1.
2012-09-18 10:37:45.96 spid12s An error occurred during recovery, preventing the database 'msdb' (database ID 4) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2012-09-18 10:37:46.02 spid16s 1 transactions rolled forward in database 'TestBase' (8). This is an informational message only. No user action is required.
2012-09-18 10:37:46.23 spid5s 0 transactions rolled back in database 'TestBase' (8). This is an informational message only. No user action is required.
2012-09-18 10:37:46.23 spid5s Recovery is writing a checkpoint in database 'TestBase' (8). This is an informational message only. No user action is required.
2012-09-18 10:37:46.33 spid9s Error: 824, Severity: 24, State: 2.
2012-09-18 10:37:46.33 spid9s SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x2fc01ada; actual: 0x2fc01986). It occurred during a read of page (2:0) in database ID 3 at offset 0000000000000000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
2012-09-18 10:37:46.34 spid12s Error: 926, Severity: 14, State: 1.
2012-09-18 10:37:46.34 spid12s Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
2012-09-18 10:37:46.34 spid12s Problems recording information in the msdb..suspect_pages table were encountered. This error does not interfere with any activity except maintenance of the suspect_pages table. Check the error log for more information.
2012-09-18 10:37:46.34 spid9s Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2012-09-18 10:37:46.34 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

ничерта не понятно, что делать то?
все локально у меня на компе, помогите...