Friday, October 12, 2007 7:52 AM
I had a working CCR configuration for some time. But "split-brain" situation occured - we lost the share witness server for too long and the two nodes became active. So the Majority Node Set became corrupted. Unfortunately /forcequorum command didn't succeed - cluster service failed to start with error - unexpected termination of the service. So I evicted the second node, which shlould be the passive one and I installed Local Quorum ressource, changed the quorum to it and tried to create new majority node set ressource. I succeeded but I can't bring the new majority node set to online. It just continue to fail. The most interesting thing about this situation is this error message when I tried to delete the corrupted majority node ressource -
Event Type: Warning
Event Source: ClusSvc
Event Category: Database Mgr
Event ID: 1064
Date: 08.10.2007 г.
The quorum resource was changed. The old quorum resource could not be marked as obsolete. If there is partition in time, you may lose changes to your database since the node that is down will not be able to get to the new quorum resource.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
So now I can't bring the new majority node set to online. Is there any solution to this tricky situation, except complete formate of the two nodes?
Friday, October 12, 2007 10:52 AM
Here it is what error was generated in cluster.log file when I tried to start the new "aaa" majority node set ressource:
00000fa0.00000f74::2007/10/12-10:36:02.087 ERR Majority Node Set <aaa>: Lost quorum resource 'aaa'.
00000fa0.00000be4::2007/10/12-10:36:02.087 ERR Majority Node Set <aaa>: Error 5004 bringing resource online.
000003f0.00000da8::2007/10/12-10:36:02.087 WARN [FM] FmpHandleResourceTransition: Resource Name = 0d1d8418-e2ff-4c89-95e5-435c966f707a [aaa] old state=129 new state=4
000003f0.00000da8::2007/10/12-10:36:02.087 WARN [FM] FmpHandleResourceTransition: Resource failed, post a work item
000003f0.00000da8::2007/10/12-10:36:02.087 WARN [FM] Group failure for 663856d6-4ef4-4f71-b4a1-d8cf956b692a, but can't move. Failure count = 1.
Friday, October 12, 2007 11:36 PMModeratorYou'll need to take Non-W2K8 cluster issues here - http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.windows.server.clustering to get a quicker response.