Hi

I have a 2 node windows 2000 Cluster with a problem. I think the quorum log
became corrupted and now on both nodes the cluster service cannot start.
Without the cluster service running i cannot access any of the resources. On
the event viewer i have some error messages indicating that the quorum log is
corrupted, is there a way of getting the cluster service to start?
I already tried starting the service with the -noquerylogging parameter, the
service started and i could clear the old log from the quorum disk, but after
that i'm trying to restart the service and he just stays on starting state
indefinetly. Is there anything i can do to save my neck...because i noticed a
few minutes ago that bmy backups were not running properly.
Please help me out, i have to start cluster on the next 8 hours!!!!
Thanks a lot

My messenger is f_batista69 (AT) hotmail (DOT) com

Hi

Look at

"To recover from a corrupted quorum log or quorum disk"
http://www.microsoft.com/windows2000...luad_pr_70.htm

and

http://support.microsoft.com/default...b;en-us;872970


--
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike (AT) epprecht (DOT) net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"francisco - Portugal" <francisco - Portugal (AT) discussions (DOT) microsoft.com>
wrote in message news:48441502-D241-488E-A26F-CB9E6C1F5FC3 (AT) microsoft (DOT) com...

Hi Mike,

First of all, thanks for your post

About the first article you sugest:
I did already that, the cluster service started and i could put online
everything, then i went to the MSCS folder and deleted the Quolog.log file
then i tried to restart the services withou any aditional startup parameters,
but the cluster service remains on a starting state "forever"........

About the second article:
I was searching trought the web in order to get the hotfix, but i think only
microsoft can give it to me, is there any place else where i could download
the fix?

Thanks


--
Francisco Batista
Portugal
f_batista69 (AT) hotmail (DOT) com


"Mike Epprecht (SQL MVP)" wrote:

You have to ask Microsoft Product Support for the Fix.

Have you rebooted all the nodes after the quorum fix?

--
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike (AT) epprecht (DOT) net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"francisco - Portugal" <f_batista69 (AT) hotmail (DOT) com> wrote

I did, but still the same thing the service stays on that starting state ,
and it don't matters if i try to start the service on Node 1 or node
2.........
I can see that the drives are there with compaq array configuration utility,
but i cannot access the drives because they are a resource of the cluster
that i can't get back online......
On the disk management i have both drives on unreadable state, a few hours
ago when i managed to start the service they became online...... i'm becaming
desperate

:-(

--
Francisco Batista
Portugal
f_batista69 (AT) hotmail (DOT) com


"Mike Epprecht (SQL MVP)" wrote:

Still no progress, no mater what, the cluster service starts and enters the
starting state and then remains in starting state, even if i start the
services with parameters like -noquorumlogging , -resetquorumlog ou
-fixquorumlog
In microsofts knowledge base i found an article saying that a fiz KB872979
(i think) could fix this problem, but i have to request it directly to
microsoft support.

I was thinking in contacting microsoft support, someone has the number for
their 24x7 support line?
Another thing that i thought it could work is to reinstal the cluster
services that are installed in the physicall nodes, that would not mess with
the logical drives on the storage right?
Does anyone know a way of having access to the disks of a controller without
the cluster service up and running?

Thank for all the help.



--
Francisco Batista
Portugal
f_batista69 (AT) hotmail (DOT) com


"francisco - Portugal" wrote:

Try
http://support.microsoft.com/?LN=pt&x=14&y=11

I don't speek Portugese so I have no clue if that is correct. If not, here
is the International support start page.
http://support.microsoft.com/common/international.aspx

Geoff N. Hiten
Microsoft SQL Server MVP

"francisco - Portugal" <f_batista69 (AT) hotmail (DOT) com> wrote

Francisco

Have you tried this.

Power off one of the nodes.

On the remaining NODE start cluster service with -noquorumlogging

Delete Everything inside of the MSCS directory on the Quroum drive (I know
you stated you deleted the quolog.log file previously).

Stop the cluster service and then start it with the -resetquorumlog

If this works then stop the cluster service and start it normally. I have
seen quorum logs become so corrupt that resetquorumlog does not work this
usually fixes it. If this does not work I would recommend the following:

Reboot the only node that is powered up with the cluster service set to
manual.

Go to the command promp c:\Windows\Cluster\clussvc -debug >c:\debug.txt

cut and paste the output into the news groups.

Regards

CT

"francisco - Portugal" wrote: