Changing LUNS morris 12/9/2008 4:21:01 AM 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 then re-present them and change the luns to 1,2, and 3 like the first node? I don't know if changing the LUNS will cause any problem with the cluster or if everything is just run off the drive letters. Thanks!

Re: Changing LUNS "Robert Smit" <Robert.smit-nospam-aca-computers.nl> 12/9/2008 7:08:13 AM Hi Morris, This is how windows shows his disks, I won't change the disk, and I guess unpresent the disk won't change your thing. the Id is the disk signature that must be changed. you can see this in hklm\system\currentcontrolset\services\cludisk\parameters\signatures Here you can see the ID matching the Disk name and these settings are different on both nodes. You can change this on the passive node but you can also meshup your cluster. The basic Idea is the signature holds the windows disk with the disk name and device number. If you change this than your windows disk moved from 1 to 4. Sample node 1 ID 1c0e170e = device\hardisk1 ID 2c0e170e = device\hardisk2 ID 3c0e170e = device\hardisk3 ID 4c0e170e = device\hardisk4 node 2 ID 1c0e170e = device\hardisk4 ID 2c0e170e = device\hardisk2 ID 3c0e170e = device\hardisk3 ID 4c0e170e = device\hardisk1 You can change the disk 4 with 1 but the ID 4c0e170e = device\hardisk1 must be the same disk as on node 1 ID 4c0e170e = device\hardisk4 You must be sure that this is the presented disk. I have done this but it is always tricky. -- Greetings, Robert Smit Blog : http://fiberman.spaces.live.com/ "morris" <morris[ at ]discussions.microsoft.com> schreef in bericht news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... [Quoted Text] > 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 then > re-present them and change the luns to 1,2, and 3 like the first node? I > don't know if changing the LUNS will cause any problem with the cluster or > if > everything is just run off the drive letters. Thanks!

Re: Changing LUNS "Edwin vMierlo [MVP]" <EdwinvMierlo[ at ]discussions.microsoft.com> 12/9/2008 9:57:56 AM 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[ at ]discussions.microsoft.com> wrote in message news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... [Quoted Text] > 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 then > re-present them and change the luns to 1,2, and 3 like the first node? I > don't know if changing the LUNS will cause any problem with the cluster or if > everything is just run off the drive letters. Thanks!

Re: Changing LUNS morris 12/10/2008 3:06:01 AM 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: [Quoted Text] > 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[ at ]discussions.microsoft.com> wrote in message > news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... > > 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 then > > re-present them and change the luns to 1,2, and 3 like the first node? I > > don't know if changing the LUNS will cause any problem with the cluster or > if > > everything is just run off the drive letters. Thanks! > > >

Re: Changing LUNS "Robert Smit" <Robert.smit-nospam-aca-computers.nl> 12/10/2008 3:07:54 PM Hi Morris, Is the disk correctly published to the server, So If you bringdown all your nodes and the new node sees the disk ? Or can you see the disk with the Fiberchannel/iscsi tools ? -- Greetings, Robert Smit Blog : http://fiberman.spaces.live.com/ "morris" <morris[ at ]discussions.microsoft.com> schreef in bericht news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... [Quoted Text] > 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[ at ]discussions.microsoft.com> wrote in message >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... >> > 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 then >> > re-present them and change the luns to 1,2, and 3 like the first node? >> > I >> > don't know if changing the LUNS will cause any problem with the cluster >> > or >> if >> > everything is just run off the drive letters. Thanks! >> >> >>

Re: Changing LUNS "John Fullbright" <fjohn[ at ]donotspamnetappdotcom> 12/10/2008 10:13:01 PM click advanced. "morris" <morris[ at ]discussions.microsoft.com> wrote in message news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... [Quoted Text] > 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[ at ]discussions.microsoft.com> wrote in message >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... >> > 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 then >> > re-present them and change the luns to 1,2, and 3 like the first node? >> > I >> > don't know if changing the LUNS will cause any problem with the cluster >> > or >> if >> > everything is just run off the drive letters. Thanks! >> >> >>

Re: Changing LUNS morris 12/11/2008 12:05:01 AM 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: [Quoted Text] > click advanced > > > "morris" <morris[ at ]discussions.microsoft.com> wrote in message > news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... > > 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[ at ]discussions.microsoft.com> wrote in message > >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... > >> > 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 then > >> > re-present them and change the luns to 1,2, and 3 like the first node? > >> > I > >> > don't know if changing the LUNS will cause any problem with the cluster > >> > or > >> if > >> > everything is just run off the drive letters. Thanks! > >> > >> > >> > > >

Re: Changing LUNS morris 12/11/2008 2:23:00 PM Yes the disk is published to the node. When I failed over to this new node the disk would also stay online for 30-60 seconds before failing back to another node. Could it be because I don't have sql installed on this node yet? I didn't take the other nodes offline to see if it would stay online if there wasn't another node to failover to. "Robert Smit" wrote: [Quoted Text] > Hi Morris, > > Is the disk correctly published to the server, So If you bringdown all your > nodes and the new node sees the disk ? > Or can you see the disk with the Fiberchannel/iscsi tools ? > > > -- > Greetings, > > Robert Smit > Blog : http://fiberman.spaces.live.com/ > > "morris" <morris[ at ]discussions.microsoft.com> schreef in bericht > news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... > > 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[ at ]discussions.microsoft.com> wrote in message > >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... > >> > 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 then > >> > re-present them and change the luns to 1,2, and 3 like the first node? > >> > I > >> > don't know if changing the LUNS will cause any problem with the cluster > >> > or > >> if > >> > everything is just run off the drive letters. Thanks! > >> > >> > >> >

Re: Changing LUNS "Edwin vMierlo [MVP]" <EdwinvMierlo[ at ]discussions.microsoft.com> 12/12/2008 9:27:53 AM 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[ at ]discussions.microsoft.com> wrote in message news:3C0C66E1-6127-4BD7-8497-B52B830FE920[ at ]microsoft.com... [Quoted Text] > 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[ at ]discussions.microsoft.com> wrote in message > > news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... > > > 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[ at ]discussions.microsoft.com> wrote in message > > >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... > > >> > 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 then > > >> > re-present them and change the luns to 1,2, and 3 like the first node? > > >> > I > > >> > don't know if changing the LUNS will cause any problem with the cluster > > >> > or > > >> if > > >> > everything is just run off the drive letters. Thanks! > > >> > > >> > > >> > > > > > >

Re: Changing LUNS morris 12/12/2008 10:48:01 PM 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: [Quoted Text] > 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[ at ]discussions.microsoft.com> wrote in message > news:3C0C66E1-6127-4BD7-8497-B52B830FE920[ at ]microsoft.com... > > 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[ at ]discussions.microsoft.com> wrote in message > > > news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... > > > > 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[ at ]discussions.microsoft.com> wrote in message > > > >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... > > > >> > 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 > then > > > >> > re-present them and change the luns to 1,2, and 3 like the first > node? > > > >> > I > > > >> > don't know if changing the LUNS will cause any problem with the > cluster > > > >> > or > > > >> if > > > >> > everything is just run off the drive letters. Thanks! > > > >> > > > >> > > > >> > > > > > > > > > > > >

Re: Changing LUNS "Edwin vMierlo [MVP]" <EdwinvMierlo[ at ]discussions.microsoft.com> 12/13/2008 9:46:55 AM 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[ at ]discussions.microsoft.com> wrote in message news:A4F081AB-5864-442E-B8DF-8E70C188E913[ at ]microsoft.com... [Quoted Text] > 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[ at ]discussions.microsoft.com> wrote in message > > news:3C0C66E1-6127-4BD7-8497-B52B830FE920[ at ]microsoft.com... > > > 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[ at ]discussions.microsoft.com> wrote in message > > > > news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... > > > > > 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[ at ]discussions.microsoft.com> wrote in message > > > > >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... > > > > >> > 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 > > then > > > > >> > re-present them and change the luns to 1,2, and 3 like the first > > node? > > > > >> > I > > > > >> > don't know if changing the LUNS will cause any problem with the > > cluster > > > > >> > or > > > > >> if > > > > >> > everything is just run off the drive letters. Thanks! > > > > >> > > > > >> > > > > >> > > > > > > > > > > > > > > > > > >

Re: Changing LUNS morris 12/14/2008 4:37:00 AM 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: [Quoted Text] > 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[ at ]discussions.microsoft.com> wrote in message > news:A4F081AB-5864-442E-B8DF-8E70C188E913[ at ]microsoft.com... > > 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[ at ]discussions.microsoft.com> wrote in message > > > news:3C0C66E1-6127-4BD7-8497-B52B830FE920[ at ]microsoft.com... > > > > 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[ at ]discussions.microsoft.com> wrote in message > > > > > news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... > > > > > > 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[ at ]discussions.microsoft.com> wrote in message > > > > > >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... > > > > > >> > 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 > > > then > > > > > >> > re-present them and change the luns to 1,2, and 3 like the > first > > > node? > > > > > >> > I > > > > > >> > don't know if changing the LUNS will cause any problem with the > > > cluster > > > > > >> > or > > > > > >> if > > > > > >> > everything is just run off the drive letters. Thanks! > > > > > >> > > > > > >> > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > >

Re: Changing LUNS "Robert Smit" <Robert.smit-nospam-aca-computers.nl> 12/15/2008 12:00:47 PM 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[ at ]discussions.microsoft.com> schreef in bericht news:F177B2AB-0074-47D6-9967-0D9F7EAA01A0[ at ]microsoft.com... [Quoted Text] > 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[ at ]discussions.microsoft.com> wrote in message >> news:A4F081AB-5864-442E-B8DF-8E70C188E913[ at ]microsoft.com... >> > 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[ at ]discussions.microsoft.com> wrote in message >> > > news:3C0C66E1-6127-4BD7-8497-B52B830FE920[ at ]microsoft.com... >> > > > 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[ at ]discussions.microsoft.com> wrote in message >> > > > > news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... >> > > > > > 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[ at ]discussions.microsoft.com> wrote in message >> > > > > >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... >> > > > > >> > 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 >> > > then >> > > > > >> > re-present them and change the luns to 1,2, and 3 like the >> first >> > > node? >> > > > > >> > I >> > > > > >> > don't know if changing the LUNS will cause any problem with >> > > > > >> > the >> > > cluster >> > > > > >> > or >> > > > > >> if >> > > > > >> > everything is just run off the drive letters. Thanks! >> > > > > >> >> > > > > >> >> > > > > >> >> > > > > >> > > > > >> > > > > >> > > >> > > >> > > >> >> >>

Re: Changing LUNS morris 12/15/2008 2:28:01 PM 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: [Quoted Text] > 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[ at ]discussions.microsoft.com> schreef in bericht > news:F177B2AB-0074-47D6-9967-0D9F7EAA01A0[ at ]microsoft.com... > > 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[ at ]discussions.microsoft.com> wrote in message > >> news:A4F081AB-5864-442E-B8DF-8E70C188E913[ at ]microsoft.com... > >> > 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[ at ]discussions.microsoft.com> wrote in message > >> > > news:3C0C66E1-6127-4BD7-8497-B52B830FE920[ at ]microsoft.com... > >> > > > 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[ at ]discussions.microsoft.com> wrote in message > >> > > > > news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... > >> > > > > > 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[ at ]discussions.microsoft.com> wrote in message > >> > > > > >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... > >> > > > > >> > 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 > >> > > then > >> > > > > >> > re-present them and change the luns to 1,2, and 3 like the > >> first > >> > > node? > >> > > > > >> > I > >> > > > > >> > don't know if changing the LUNS will cause any problem with > >> > > > > >> > the > >> > > cluster > >> > > > > >> > or > >> > > > > >> if > >> > > > > >> > everything is just run off the drive letters. Thanks! > >> > > > > >> > >> > > > > >> > >> > > > > >> > >> > > > > > >> > > > > > >> > > > > > >> > > > >> > > > >> > > > >> > >> > >> > >

Re: Changing LUNS "Robert Smit" <Robert.smit-nospam-aca-computers.nl> 12/17/2008 7:05:36 AM 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[ at ]discussions.microsoft.com> schreef in bericht news:24371878-746A-4E29-8DBB-A950FB40339A[ at ]microsoft.com... [Quoted Text] > 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[ at ]discussions.microsoft.com> schreef in bericht >> news:F177B2AB-0074-47D6-9967-0D9F7EAA01A0[ at ]microsoft.com... >> > 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[ at ]discussions.microsoft.com> wrote in message >> >> news:A4F081AB-5864-442E-B8DF-8E70C188E913[ at ]microsoft.com... >> >> > 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[ at ]discussions.microsoft.com> wrote in message >> >> > > news:3C0C66E1-6127-4BD7-8497-B52B830FE920[ at ]microsoft.com... >> >> > > > 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[ at ]discussions.microsoft.com> wrote in message >> >> > > > > news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... >> >> > > > > > 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[ at ]discussions.microsoft.com> wrote in >> >> > > > > >> message >> >> > > > > >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... >> >> > > > > >> > 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 >> >> > > then >> >> > > > > >> > re-present them and change the luns to 1,2, and 3 like >> >> > > > > >> > the >> >> first >> >> > > node? >> >> > > > > >> > I >> >> > > > > >> > don't know if changing the LUNS will cause any problem >> >> > > > > >> > with >> >> > > > > >> > the >> >> > > cluster >> >> > > > > >> > or >> >> > > > > >> if >> >> > > > > >> > everything is just run off the drive letters. Thanks! >> >> > > > > >> >> >> > > > > >> >> >> > > > > >> >> >> > > > > >> >> > > > > >> >> > > > > >> >> > > >> >> > > >> >> > > >> >> >> >> >> >> >> >>

Re: Changing LUNS "Edwin vMierlo [MVP]" <EdwinvMierlo[ at ]discussions.microsoft.com> 12/17/2008 8:44:35 AM Sorry Morris, but this still is not showing me a failed condition or ERR message. All you can see is INFO messages, no WARN or ERR. are you sure that this is the right sniplet of the log ? "morris" <morris[ at ]discussions.microsoft.com> wrote in message news:F177B2AB-0074-47D6-9967-0D9F7EAA01A0[ at ]microsoft.com... [Quoted Text] > 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[ at ]discussions.microsoft.com> wrote in message > > news:A4F081AB-5864-442E-B8DF-8E70C188E913[ at ]microsoft.com... > > > 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[ at ]discussions.microsoft.com> wrote in message > > > > news:3C0C66E1-6127-4BD7-8497-B52B830FE920[ at ]microsoft.com... > > > > > 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[ at ]discussions.microsoft.com> wrote in message > > > > > > news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... > > > > > > > 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[ at ]discussions.microsoft.com> wrote in message > > > > > > >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... > > > > > > >> > 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 > > > > then > > > > > > >> > re-present them and change the luns to 1,2, and 3 like the > > first > > > > node? > > > > > > >> > I > > > > > > >> > don't know if changing the LUNS will cause any problem with the > > > > cluster > > > > > > >> > or > > > > > > >> if > > > > > > >> > everything is just run off the drive letters. Thanks! > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >

Re: Changing LUNS morris 12/19/2008 4:01:02 PM 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: [Quoted Text] > 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[ at ]discussions.microsoft.com> schreef in bericht > news:24371878-746A-4E29-8DBB-A950FB40339A[ at ]microsoft.com... > > 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[ at ]discussions.microsoft.com> schreef in bericht > >> news:F177B2AB-0074-47D6-9967-0D9F7EAA01A0[ at ]microsoft.com... > >> > 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[ at ]discussions.microsoft.com> wrote in message > >> >> news:A4F081AB-5864-442E-B8DF-8E70C188E913[ at ]microsoft.com... > >> >> > 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[ at ]discussions.microsoft.com> wrote in message > >> >> > > news:3C0C66E1-6127-4BD7-8497-B52B830FE920[ at ]microsoft.com... > >> >> > > > 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[ at ]discussions.microsoft.com> wrote in message > >> >> > > > > news:1BA228DA-2C51-45B2-A8FA-D52B67F2659C[ at ]microsoft.com... > >> >> > > > > > 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[ at ]discussions.microsoft.com> wrote in > >> >> > > > > >> message > >> >> > > > > >> news:1ED31EC6-AD4F-4295-950B-A9C6EA6A29C3[ at ]microsoft.com... > >> >> > > > > >> > 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

Re: Changing LUNS "Robert Smit" <Robert.smit-nospam-aca-computers.nl> 12/22/2008 12:54:12 PM Morris, But on the other thest node you use different disks. With this test you proved that the new cluster node is working fine there is not a direct problem with the new cluster node. Still there is no proof that the disk are correct published to the node. And this test node is this also a 3 node cluster ? In this case the next step would be, bring both nodes down and see if the disk are correct presented on the new node only than are you sure that the config is correct. but this means downtime from production. Below is a link, maybe you have seen this and is not totaly your problem but is shows HBA stuff that maybe get you on the right track http://www.emulex.com/white/hba/san_microsoft_hyperv.pdf Still you must be sure the disks are accessable to the new node, did you use the clusdiag tool from the resource kit ? Greetings, Robert "morris" <morris[ at ]discussions.microsoft.com> schreef in bericht news:2AE3B189-F210-4243-B22B-648E49D00E1C[ at ]microsoft.com... [Quoted Text] > 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/ >> >> .live.com/