Problems with SQL 2000 with SP3

I have a Windows 2000 Server with SQL 2000 SP3 installed. It is partitioned
into to seperate logical drives. The first partition is the OS and the
second partition is SQL and its databases. Both partitions have seperate
RAID controllers and drives associated with it. I recently had problems my
RAID controller relating to the second partition. I was able to recover the
hardware failure and can still read the SQL partition and its data.
Unfortunately, I cannot get the SQL service to start anymore. I get the
following errors in event viewer:
Source: MSSQLSERVER
Category: (2)
Event ID: 17055
Description:
17052 :
Cannot recover the master database. Exiting.
Source: MSSQLSERVER
Category: (2)
Event ID: 17055
Description:
18052 :
Error: 9003, Severity: 20, State: 1.
Cannot anyone get me started on what I need to do? I have a backup of
everything but I didn't know if their was an easier way to get this working.
ThanksHave you considered uninstalling and reinstalling SQL Server completely?
Then it should just be a matter of restoring your user databases, which is
what you have backups for anyway...
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Allison" <no@.email.com> wrote in message
news:uwW3RaJIEHA.3848@.tk2msftngp13.phx.gbl...
>I have a Windows 2000 Server with SQL 2000 SP3 installed. It is
>partitioned
> into to seperate logical drives. The first partition is the OS and the
> second partition is SQL and its databases. Both partitions have seperate
> RAID controllers and drives associated with it. I recently had problems
> my
> RAID controller relating to the second partition. I was able to recover
> the
> hardware failure and can still read the SQL partition and its data.
> Unfortunately, I cannot get the SQL service to start anymore. I get the
> following errors in event viewer:
> Source: MSSQLSERVER
> Category: (2)
> Event ID: 17055
> Description:
> 17052 :
> Cannot recover the master database. Exiting.
> Source: MSSQLSERVER
> Category: (2)
> Event ID: 17055
> Description:
> 18052 :
> Error: 9003, Severity: 20, State: 1.
> Cannot anyone get me started on what I need to do? I have a backup of
> everything but I didn't know if their was an easier way to get this
> working.
> Thanks
>|||From the error messages that I listed and the problem I have described, what
do you think happened? Was it the master database? Can't figure out why
the service will not start. Looks like all the data is there.
Thanks
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:%23qOL$oJIEHA.3144@.TK2MSFTNGP10.phx.gbl...
> Have you considered uninstalling and reinstalling SQL Server completely?
> Then it should just be a matter of restoring your user databases, which is
> what you have backups for anyway...
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
>
> "Allison" <no@.email.com> wrote in message
> news:uwW3RaJIEHA.3848@.tk2msftngp13.phx.gbl...
> >I have a Windows 2000 Server with SQL 2000 SP3 installed. It is
> >partitioned
> > into to seperate logical drives. The first partition is the OS and the
> > second partition is SQL and its databases. Both partitions have
seperate
> > RAID controllers and drives associated with it. I recently had problems
> > my
> > RAID controller relating to the second partition. I was able to recover
> > the
> > hardware failure and can still read the SQL partition and its data.
> > Unfortunately, I cannot get the SQL service to start anymore. I get the
> > following errors in event viewer:
> >
> > Source: MSSQLSERVER
> > Category: (2)
> > Event ID: 17055
> > Description:
> > 17052 :
> > Cannot recover the master database. Exiting.
> >
> > Source: MSSQLSERVER
> > Category: (2)
> > Event ID: 17055
> > Description:
> > 18052 :
> > Error: 9003, Severity: 20, State: 1.
> >
> > Cannot anyone get me started on what I need to do? I have a backup of
> > everything but I didn't know if their was an easier way to get this
> > working.
> >
> > Thanks
> >
> >
>|||Also, would there be a nice KB article describing SQL restore operations.
Thanks
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:%23qOL$oJIEHA.3144@.TK2MSFTNGP10.phx.gbl...
> Have you considered uninstalling and reinstalling SQL Server completely?
> Then it should just be a matter of restoring your user databases, which is
> what you have backups for anyway...
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
>
> "Allison" <no@.email.com> wrote in message
> news:uwW3RaJIEHA.3848@.tk2msftngp13.phx.gbl...
> >I have a Windows 2000 Server with SQL 2000 SP3 installed. It is
> >partitioned
> > into to seperate logical drives. The first partition is the OS and the
> > second partition is SQL and its databases. Both partitions have
seperate
> > RAID controllers and drives associated with it. I recently had problems
> > my
> > RAID controller relating to the second partition. I was able to recover
> > the
> > hardware failure and can still read the SQL partition and its data.
> > Unfortunately, I cannot get the SQL service to start anymore. I get the
> > following errors in event viewer:
> >
> > Source: MSSQLSERVER
> > Category: (2)
> > Event ID: 17055
> > Description:
> > 17052 :
> > Cannot recover the master database. Exiting.
> >
> > Source: MSSQLSERVER
> > Category: (2)
> > Event ID: 17055
> > Description:
> > 18052 :
> > Error: 9003, Severity: 20, State: 1.
> >
> > Cannot anyone get me started on what I need to do? I have a backup of
> > everything but I didn't know if their was an easier way to get this
> > working.
> >
> > Thanks
> >
> >
>|||Hi Allison,
Based on my experience, the error "Cannot recovery the master database"
always indicates the master database is corrupted. In this cause, it is
suspected the corruption of the master database is caused by the hardware
failure. Unfortunately since this is critical error on master, not much can
be done. Only possible thing we can do is creating similar master on some
empty device and load the old GOOD master backup and go from there.
1. Copy all the mdf and LDF to another location as a backup and verify that
a good backup exists.
2. Rebuild a new master database using Rebuild master utility. Note:
Rebuilding the master database removes all database objects and data. For
more information regarding Rebuild master utility, please refer to the
following articles.
How to rebuild the master database (Rebuild Master utility)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht
_install_8w8p.asp
Rebuild master Utility
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp
_rebuildm_6dbt.asp
3. To verify that the rebuild is successful, start SQL Server normally
4. Restore the master database from your old backup.
5. Reattach all the databases
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||> be done. Only possible thing we can do is creating similar master on some
> empty device and load the old GOOD master backup and go from there.
How about just uninstalling SQL Server and reinstalling, then restoring all
the *good* backups of the user databases? Surely we don't need that old
master database if we have acceptable backups of all the existing DBs? This
rebuild/re-attach process seems like far too much work, when a clean start
is probably the best thing to do anyway...
A|||Well, I think everything is working again. I uninstalled SQL 2000 and
reinstalled it with the same directory structure. At that same time, I kept
all 100 of my user databases in the same folder, therefore I didn't have to
restore over all of them. I then went into single-user mode and restore
only the master database. Once the master database restored, it
automatically attached to all 100 databases to SQL. I then exited
single-user mode, restarted the SQL service, and accessed my front-end
program. Everything looked good. I could access my databases and query
them. I'm still kind of suspicious because it wasn't as bad as I thought.
Hopefully I did it right.
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:OLKcm$PIEHA.3248@.TK2MSFTNGP12.phx.gbl...
> > be done. Only possible thing we can do is creating similar master on
some
> > empty device and load the old GOOD master backup and go from there.
> How about just uninstalling SQL Server and reinstalling, then restoring
all
> the *good* backups of the user databases? Surely we don't need that old
> master database if we have acceptable backups of all the existing DBs?
This
> rebuild/re-attach process seems like far too much work, when a clean start
> is probably the best thing to do anyway...
> A
>