Wednesday, March 28, 2012

Raid Array Failure/Rebuild SQL won''t run

Background... Server raid failed, rebuilt raid ran chkdsk but now I am
unable to run SQL service.

I've tried to manually start service but receive the following message

The MSSQLSERVER service on the local computer started and then stopped. Some
services stop automatically if they have no work to do.

Here's all I have in the error logs

2007-08-19 10:56:39.98 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

2007-08-19 10:56:39.99 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-08-19 10:56:39.99 server All rights reserved.
2007-08-19 10:56:39.99 server Server Process ID is 1812.
2007-08-19 10:56:39.99 server Logging SQL Server messages in file
'f:\MSSQL\log\ERRORLOG'.
2007-08-19 10:56:40.01 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-08-19 10:56:40.15 server SQL Server configured for thread mode
processing.
2007-08-19 10:56:40.18 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2007-08-19 10:56:40.23 server Attempting to initialize Distributed
Transaction Coordinator.
2007-08-19 10:56:42.29 spid4 Starting up database 'master'.
2007-08-19 10:56:42.31 spid4 Error: 5172, Severity: 16, State: 15.
2007-08-19 10:56:42.31 spid4 Error: 5173, Severity: 16, State: 1.
2007-08-19 10:56:42.31 spid4 Error: 5180, Severity: 22, State: 1.

Is sql server running under a service account and did you change the pwd ? is there any specific info in the event viewer ?

|||

With some assistance I ran rebuildm.exe and was able to get sql up and running.

I have been able to go through the steps to create a new database of same name then copy originals, restart SQL and bring the databases back in suspect mode.

I'm trying to read up on how to set the databases to emergency mode, check for errors and hopefully bring back to working, normal state....

No comments:

Post a Comment