Re: Changing LUNS

To test I tried adding this node to another test cluster and it added fine,
so i'm not thinking its an issue with the disks. We are using emulex HBA's so
thats what software we use.

"Robert Smit" wrote:

Hi morris,

Yes I think it has something to do with publishing or read/write to the
disks. only from the new node.

what software do you use for the HBA's is it the same on the other nodes ?
versions/settings.


--
Greetings,

Robert Smit
Blog : http://fiberman.spaces.live.com/



"morris" <morris@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:24371878-746A-4E29-8DBB-A950FB40339A@xxxxxxxxxxxxxxxx
No this is actually our production sql cluster that has 2 other nodes and
i'm
trying to add a third. So you think its something with the disks?

"Robert Smit" wrote:

Morris,

So this cluster is non production, so what if you rebuild the cluster
config
and start with the second node as first node.
but build it to a minium just add the Quorum disk and no other disks. If
this runs then add the old first node, if this fails then seek it in the
disk connection.

just to make sure you can always do some testing to make sure the disk is
correct configured from the san to the published servers and that the HBA
drivers are ok.

Sometimes there are this easy things that you forget and everybody says
yes
but check and make sure this is correct.


--
Greetings,

Robert Smit
Blog : http://fiberman.spaces.live.com/





"morris" <morris@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:F177B2AB-0074-47D6-9967-0D9F7EAA01A0@xxxxxxxxxxxxxxxx
OK I think this is from when it comes online to when it stops. Let me
know
if
you see anything or if you need more of the log. Thanks!

000012d4.000013c8::2008/11/28-21:44:34.206 INFO Physical Disk <Disk
Q:>:
Online, setting ResourceState 2 .
000012d4.000013c8::2008/11/28-21:44:34.206 INFO [RM]
RmpSetResourceStatus,
Posting state 2 notification for resource <Disk Q:>
00001248.000012e8::2008/11/28-21:44:34.206 INFO [FM]
NotifyCallBackRoutine:
enqueuing event
000012d4.000013c8::2008/11/28-21:44:34.206 INFO Physical Disk <Disk
Q:>:
Online, returning final error 0 ResourceState 2 Valid 1
000012d4.000012f8::2008/11/28-21:44:34.206 INFO Physical Disk <Disk
Q:>:
[PnP] Start watching PnP events for disk 79be60d3
00001248.000012e8::2008/11/28-21:44:34.206 INFO [FM] Calling
RmNotifyChanges
in monitor 12d4.
00001248.00001288::2008/11/28-21:44:34.206 INFO [FM]
FmpCreateResStateChangeHandler: Entry
00001248.00001288::2008/11/28-21:44:34.206 INFO [FM]
FmpCreateResStateChangeHandler: Exit, status 0
00001248.000013d8::2008/11/28-21:44:34.206 INFO [FM]
FmpHandleResStateChangeProc: Entry...
00001248.000013d8::2008/11/28-21:44:34.206 INFO [DM] DmpQuoObjNotifyCb:
Quorum resource is online
00001248.000013d8::2008/11/28-21:44:34.206 INFO [DM] DmpQuoObjNotifyCb:
Own
quorum resource, try open the quorum log
00001248.000013d8::2008/11/28-21:44:34.206 INFO [Qfs] QfsFindFirstFile
Q:\MSCS\ => ffffffff, error 2
00001248.000013d8::2008/11/28-21:44:34.206 INFO [DM] DmpQuoObjNotifyCb:
FindFirstFile on path Q:\MSCS\ failed, Error=2 !!!
00001248.000013d8::2008/11/28-21:44:34.206 INFO [Qfs]
QfsCreateDirectory
Q:\MSCS\, status 183
00001248.000013d8::2008/11/28-21:44:34.206 INFO [DM] DmpQuoObjNotifyCb:
the
name of the quorum file is Q:\MSCS\quolog.log
00001248.000013d8::2008/11/28-21:44:34.206 INFO [DM] DmpQuoObjNotifyCb:
Will
try to reset Quorum log if file not found or if corrupt
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM] LogCreate : Entry
FileName=Q:\MSCS\quolog.log MaxFileSize=0x00400000
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM] LogpCreate : Entry
00001248.000013d8::2008/11/28-21:44:34.206 INFO [Qfs] QfsOpenFile
Q:\MSCS\quolog.log => 4, 758 status 0
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM] LogpMountLog :
Entry
pLog=0x0014b0b8
00001248.000013d8::2008/11/28-21:44:34.206 INFO [Qfs] QfsGetFileSize
758
32768
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM]
LogpMountLog::Quorumlog
File size=0x00008000
00001248.000013d8::2008/11/28-21:44:34.206 INFO [Qfs] ReadFile 758
(....)
1024 0, (0=>0) 14b0ec status 997
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM]
LogpMountLog::reading
1024 bytes at offset 0x00000400
00001248.000013d8::2008/11/28-21:44:34.206 INFO [Qfs] ReadFile 758
(....)
1024 0, (0=>0) 14b0ec status 997
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM]
LogpMountLog::checking
LSN 0x00000408
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM]
LogpMountLog::checking
LSN 0x00000438
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM]
LogpMountLog::checking
LSN 0x00000678
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM]
LogpMountLog::checking
LSN 0x000006a8
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM]
LogpMountLog::checking
LSN 0x000006d8
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM]
LogpMountLog::checking
LSN 0x00000708
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM] LogpMountLog:
Reached
last record, RecordLSN=0x00000708...
00001248.000013d8::2008/11/28-21:44:34.206 INFO [LM]
LogpValidateChkPoint:
Entry
00001248.000013d8::2008/11/28-21:44:34.206 INFO [Qfs] QfsOpenFile
Q:\MSCS\chk6A36.tmp => 3, 75c status 0
00001248.000013d8::2008/11/28-21:44:34.206 INFO [Qfs]
QfsMapFileAndCheckSum
Q:\MSCS\chk6A36.tmp, compatibility 1, ret 1 status 87
00001248.000013d8::2008/11/28-21:44:34.222 INFO [Qfs]
QfsMapFileAndCheckSum
Q:\MSCS\chk6A36.tmp, compatibility 0, ret 0 status 0
00001248.000013d8::2008/11/28-21:44:34.222 INFO [LM]
LogpValidateChkPoint:
Exit, returning 0x00000000
00001248.000013d8::2008/11/28-21:44:34.222 INFO [Qfs] QfsCloseHandle
75c,
status 0

"Edwin vMierlo [MVP]" wrote:

OK, so now you need to find out why "Disk Q:" is failing on your
second
node

any entries in the cluster.log file ?
please note the date stamp of the cluster.log file is in GMT, so you
might
have to calculate the offset of the log file, depending on the
Timezone
configured on your node.

Rgds,
Edwin.



"morris" <morris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A4F081AB-5864-442E-B8DF-8E70C188E913@xxxxxxxxxxxxxxxx
I never got to the point of installing sql so that answers #2. As
for
#1
the
event logs are as follows:
a. Cluster resource 'Disk Q:' in Resource Group 'EX Cluster Quorum'
failed.

b. Cluster service was halted to prevent an inconsistency within the
server
cluster. The error code was 5027.

c.The Cluster Service service terminated unexpectedly. It has done
this 1
time(s). The following corrective action will be taken in 60000
milliseconds: Restart the service.

Once the disk failed back to the other node the cluster service
actually
stopped as you can see in c above.

"Edwin vMierlo [MVP]" wrote:

it seems that you have 2 problems

1) your "Cluster Group" does not stay online on your second node
2) installation problems with SQL

I would suggest we tackle the first one first

can you please sent us more info on the "Cluster Group" moving
back
to
the
node 1 after 30 seconds,
What errors are logged in the system event log when this happens ?

thanks,
Edwin.


"morris" <morris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3C0C66E1-6127-4BD7-8497-B52B830FE920@xxxxxxxxxxxxxxxx
I have tried that also and everythign adds fine. The problem I
ran
into
was
once the new node was up I moved the cluster name and ip and
quorum
to
the
new node and it would stay on that node for maybe 30 seconds and
then
fail
back to another node. Should this be expected being I didn't
install
sql
on
this node yet or does this sound like a problem. I had the sql
cluster
group
offline during this time and was just trying to move the quorum
and
name
and
ip.

"John Fullbright" wrote:

click advanced


"morris" <morris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C@xxxxxxxxxxxxxxxx
Ok well here is my problem. I am trying to add a new node to
my
sql
cluster
but when I run through the wizard it is failing. I have read
on
other
websites that this is because the disks are on different
luns
on
the
different nodes?

"Edwin vMierlo [MVP]" wrote:

Robert is right, but to shorten the story; don't try to
change
this,
and
certainly do not change anything in that registry key.

Rgds,
Edwin.

"morris" <morris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3@xxxxxxxxxxxxxxxx
We currently have a sql server 2005 server clustered. One
one
node
the
disks
are on luns 1, 2, and 3, and on the other node they are
on
luns
1,
4,
and
5.
My question is can I un-present the disks on the second
node
and
.

Relevant Pages

  • SUMMARY: changed WWID on cluster member boot disk
    ... disk and quorum disk of a single-member cluster, ... I could no longer boot from the cluster disks, ... the pre-cluster stand-alone system disk; ... the root1_domain on LUN containing the member boot disk was found ...
    (Tru64-UNIX-Managers)
  • Phisical disk resource
    ... I'm setting up a 2 node cluster under 2003 ent. ... is working but I am not able to bring the shared disk ... INFO FmpPropagateResourceState: resource a94c4968- ... INFO Physical Disk: ...
    (microsoft.public.windows.server.clustering)
  • Re: Split brain scenario in cluster server system
    ... Whenever the cluster cannot determine who owns the quorum, ... Eachnode in the cluster renews the disk reservation that it owns, ... tries to reserve the quorum disk. ...
    (microsoft.public.windows.server.clustering)
  • RE: Move quorum to new disk
    ... The procedure for actually replacing the quorum disk is identical to ... required to startup the cluster in the event of a quorum disk failure. ... replacement procedure outlined in Recovering a shared disk to replace the ...
    (microsoft.public.windows.server.clustering)
  • Re: Checking that all nodes have access to the quorum resource!
    ... match from one node to another so the cluster thinks it's a different disk. ... to ping each other the remote storage, which contains the quorum drive. ... to the quorum resource... ...
    (microsoft.public.windows.server.clustering)
Loading