Re: New Cluster Questions
- From: "John Toner [MVP]" <jtoner@xxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 6 Oct 2007 17:11:34 -0400
Nah, that's the last thing to worry about ;-)
What he should be worried about is that he's using SCSI instead of
fibre...and it probably isn't terminated properly.
Regards,
John
Visit my blog: http://msmvps.com/blogs/jtoner
"Chuck [MSFT]" <ctimon@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:unTC0bBCIHA.464@xxxxxxxxxxxxxxxxxxxxxxx
First things first, did you verify your cluster solution is listed here -http://www.windowsservercatalog.com/results.aspx?bCatID=1291&cpID=0&ocID=20&OR=1
rights.
--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no
"bmbrown" <brian@xxxxxxxxxxxxx> wrote in message
news:1191636269.568107.311580@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am attempting (unsuccessfully) to create a simple file cluster. I
have two Dell 2950's that I'm connecting via SCSI to a Promise
Technologies VTrak 15110. I have a quorum logical drive defined at 500
MB, as well as a few data drives at 2TB each (that was the documented
limit, correct?). All drives are formatted MBR, with a single primary
partition. Both servers can see the quorum drive and have access to
create and delete files to the drive. Both servers are 2003 Ent. R2,
x64, SP2.
Anytime I try to create a cluster, upon configuring the resources, the
wizard (and command line tools for that matter) always fail at:
Failed to set resource 'Disk Q:' to be the quorum resource.
Error 0x800706be: The remote procedure call failed.
Then it also give the same error when trying to set the quorum
resource. This results in the system creating a Local Quorum and
utilizing that as the quorum drive.
When I go to the properties of the cluster and attempt to move the
quorum resource from the Local Quorum to Disk Q:, the system pauses
for a period, then comes back with the cluster no longer being
available due to the service stopping and starting again. It also
indicates the RPC server failed.
In the event log, I get a set of errors, the first being 1080 with a
description of:
Cluster service could not write to a file (Q:\MSCS\quolog.log). The
disk may be low on disk space, or some other serious condition exists.
The disk is not full, and I have even tried to increase the logical
drive to 1-10 GB with the same results, hence leading me to the
conclusion that some other serious condition exists (besides my mental
state at this point).
After that error, I get the error signifying that the cluster service
was halted, a restart error indicating that the service will be
restarted, then a series of errors (event ID 57) of:
The system failed to flush data to the transaction log. Corruption may
occur.
I understand the RPC server error could be due to OS problems, and
have gone through as many documents as possible to determine any OS
issues, but to no avail.
I would gladly take any suggestions anyone might have.
Thanks for your time.
Brian.
.
- Follow-Ups:
- Re: New Cluster Questions
- From: Chuck [MSFT]
- Re: New Cluster Questions
- From: Chuck [MSFT]
- Re: New Cluster Questions
- References:
- New Cluster Questions
- From: bmbrown
- Re: New Cluster Questions
- From: Chuck [MSFT]
- New Cluster Questions
- Prev by Date: Re: MNSFileShare - FSW Configuration
- Next by Date: Re: MNSFileShare - FSW Configuration
- Previous by thread: Re: New Cluster Questions
- Next by thread: Re: New Cluster Questions
- Index(es):
Relevant Pages
|
Loading