Can't get Quorum disk to come online for cluster?

[NipsMG]

I'm trying to successfully create a win2003 enterprise cluster.

I'm following a microsoft guide to setting this up. First I configured the networks on both machines. Then I booted node 1, configured the quorum disk (NTFS MBR basic disk) on the SHared bus, tried to write a file to it, no problem. Shut down Node 1, booted node 2, made sure drive letters were right, wrote files to the quorum disk, no problems.

Then I turned off node 2 and booted node 1 up. I start the cluster administrator and created the cluster, no problems at all. The first check goes through without even a warning, and it finds the q: quorum device without issue. I then select the IP, give it the account name, etc. At the very end, when it tries to bring resources online, the quorum disk fails, and it reverts to local quorum. i've tried EVERYTHING (updating to the most recent Adaptec drivers, changing scsi configuration, etc) and it just won't bring the disk online. I see "Failed" consistently. In the Cluster Administrator new cluster wizard, the message is :

0x80004005 Unspecified Error. Could not bring resouce "Disk q:" online. Check the event log, blah blah blah.

The event log shows only this:

In the event viewer, I get the following:

Event Type: Error
Event Source: ClusSvc
Event Category: Failover Mgr
Event ID: 1069
Date: 9/22/2004
Time: 11:20:28 AM
User: N/A
Computer: BS-NODE1
Description:
Cluster resource 'Disk Q:' in Resource Group 'Cluster Group' failed.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

Can anyone help with this? Thanks!
--Mike

 

[SDMNumpie]

Dude,

I experienced the exact same issue.

The nature of the fault is to do with naming convention.

Make sure that your using some sort of app that shuts down links that links back to your SAN like secure path.

I tried labelling it "Quorum" or "Disk Q" as it kept complaining about "Disk Q" but its kept failing to bring the Disk Q online. What was strange was that the Quoram was then unaccessible when the Cluster services was started. Once you evited the server, the Quorum was accessible again. Puzzling.

Anyway, What I did was on the SAN (Shared resource) created two logical drives. "Drive Q" and a "Drive Z". Please note the the Volume label is key! Then after I had cleared up any ref to the cluster group from the Domain and WINS database. The Cluster application was then able to see and bring online the the shared Quorum.

Best of luck and hope this helps!

 

[NipsMG]

Actually, for me it ended up being purely that there were hardware issues between the Adaptec SCSI cards I bought and the dell servers. After purchasing a Dell PERC3/Di, it worked without issue.