Re: clustering win2k3 enterprise problem.

From: JoseN (JoseN_at_discussions.microsoft.com)
Date: 10/21/04


Date: Thu, 21 Oct 2004 16:53:03 -0700

Hola Mike,

It is actually s SAN.Doc document: "Microsoft Windows Clustering: Storage
Area Networks"
Pages 27 and 28.

Yes, that's the version of Storport we are using(838894).

Thanks.

 

"Mike Rosado [MSFT]" wrote:

> Hola Jose,
>
> 1. What Knowledgebase article might that be that discusses
> 'ManageDisksOnSystemBuses' you reference?
>
> 2. What version of Storport.sys are you using? The one mentioned in the
> article below?
>
> 838894 An updated Storport storage driver (version 5.2.3790.173) is
> available
> http://support.microsoft.com/?id=838894
>
> --
> Hope this helps,
> Mike Rosado
> Windows 2000 MCSE + MCDBA
> Microsoft Enterprise Platform Support
> Windows NT/2000/2003 Cluster Technologies
>
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> <http://www.microsoft.com/info/cpyright.htm>
>
> -----Original Message-----
>
> "JoseN" <JoseN@discussions.microsoft.com> wrote in message
> news:CE20CE61-0ECC-4068-960F-8134881DAA8C@microsoft.com...
> > We have a similar problem with a single storage bus configuration. We
> > upgraded the HBA driver to the storport miniport and we set the registry
> key
> >
> HKLM\SYSTEM\CurrentControlSet\Services\ClusSvc\Parameters\ManageDisksOnSyste
> mBuses
> > 0x01 as recommennded in a Knowledge base article but we still cannot use
> the
> > drives.
> >
> > Any Advise?
> >
> > Thanks,
> > Jose.
> >
> >
> > "arvid" wrote:
> >
> > > Found the solution for one node: a firmware upgrade did the trick!!
> > >
> > > Greetz Arvid
> > >
> > >
> > > "Mike Rosado [MSFT]" <mikeros@online.microsoft.com> wrote in message
> news:<416943ed@news.microsoft.com>...
> > > > Arvid,
> > > >
> > > > It sounds like both your local drives and shared storage drive are
> using the
> > > > same SCSI or Fibre controllers or are on the same bus. If they are
> two
> > > > totally different controllers, then my questions would be:
> > > >
> > > > Was this an installation using the original media CD?
> > > > Was it and installation using RiPrep?
> > > > Was it and installation using RIS?
> > > >
> > > > From your original posting it sounds like you are indeed using two
> > > > controllers, but they each need to be on separate bus. If you need
> further
> > > > assistance configuring them to be on separate buses, then you may need
> to
> > > > contact HP Technical Support.
> > > >
> > > > 309186 How the Cluster Service Takes Ownership of a Disk on the Shared
> Bus
> > > > <http://support.microsoft.com/?id=309186>
> > > >
> > > > --
> > > > Hope this helps,
> > > > Mike Rosado
> > > > Windows 2000 MCSE + MCDBA
> > > > Microsoft Enterprise Platform Support
> > > > Windows NT/2000/2003 Cluster Technologies
> > > >
> > > > ====================================================
> > > > When responding to posts, please "Reply to Group" via your newsreader
> so
> > > > that others may learn and benefit from your issue.
> > > > ====================================================
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > > > <http://www.microsoft.com/info/cpyright.htm>
> > > >
> > > > -----Original Message-----
> > > >
> > > > "arvid" <arvid@inpact.nl> wrote in message
> > > > news:37965645.0410092350.3f5fb115@posting.google.com...
> > > > > Hi Mike,
> > > > >
> > > > > The configuration on the shared disk ( MSA) is exectly the same as
> > > > > discribed in the article. I have 2 partiotions , one for quorum and
> > > > > one for data, on the RAID 5 SCSI disks which are accesable from both
> > > > > nodes.
> > > > >
> > > > > The part below from the log concerns me the most:
> > > > > 2004-10-04 21:02:10.109 [INFO] xcl1: The physical disk "Disk D:"
> > > > > cannot be managed because it is on the same storage bus as the boot
> > > > > disk. (hr=00000000, {13E84779-125E-4B76-8C0D-1F5DB92EFE0F},
> > > > > {1EFA8906-A36E-43BF-AF65-7F74413672EE}, 1, 1, 1), The cluster
> cannot
> > > > > manage physical disks that are on the same storage bus as the
> volume
> > > > > that contains the operating system because other nodes connected to
> > > > > the storage bus cannot distinguish between these volumes and
> volumes
> > > > > used for data.
> > > > >
> > > > > So it looks like that the solution lies within the re-assigning of
> the
> > > > > bus location which are used bij both Raid controllers. Do you have
> any
> > > > > idea how i can acomplish that?
> > > > >
> > > > > greetz Arvid
> > > > >
> > > > >
> > > > > "Mike Rosado [MSFT]" <mikeros@online.microsoft.com> wrote in message
> > > > news:<416742a9$1@news.microsoft.com>...
> > > > > > Hi Arvid,
> > > > > >
> > > > > > You are probably correct in assuming "it appears that the problem
> is
> > > > that
> > > > > > the clustering service cannot find the quorum disk". Have you
> seen the
> > > > > > following article?
> > > > > >
> > > > > > 280345 Quorum Drive Configuration Information
> > > > > > http://support.microsoft.com/?id=280345
> > > > > >
> > > > > > --
> > > > > > Hope this helps,
> > > > > > Mike Rosado
> > > > > > Windows 2000 MCSE + MCDBA
> > > > > > Microsoft Enterprise Platform Support
> > > > > > Windows NT/2000/2003 Cluster Technologies
> > > > > >
> > > > > > ====================================================
> > > > > > When responding to posts, please "Reply to Group" via your
> newsreader so
> > > > > > that others may learn and benefit from your issue.
> > > > > > ====================================================
> > > > > >
> > > > > > This posting is provided "AS IS" with no warranties, and confers
> no
> > > > rights.
> > > > > > <http://www.microsoft.com/info/cpyright.htm>
> > > > > >
> > > > > > -----Original Message-----
> > > > > >
> > > > > > "arvid" <arvid@inpact.nl> wrote in message
> > > > > > news:37965645.0410080710.2f3d94f7@posting.google.com...
> > > > > > > HI,
> > > > > > >
> > > > > > > I'm trying to setup clustering on win2k3 enterprise edition. We
> have 2
> > > > > > > Proliant dl380 servers and a Modular Smart Array used as a
> shared
> > > > > > > disk. The proliant servers both have 2 scsi disks configured as
> raid
> > > > > > > 1. The MSA has 3 scsi disks configured as raid 5. The MSA has 2
> basic
> > > > > > > partitions, one for Data(d:) and one for quorum ( e: , size
> 100mb)
> > > > > > >
> > > > > > > When i want to configure clustering for both nodes the log shows
> some
> > > > > > > errors. It seems that the cluster setup fails because the OS
> (MBR)
> > > > > > > share the same bus as the quorum which is needed by the
> clustering.
> > > > > > > Here a part of the logfile:
> > > > > > >
> > > > > > > 1.Could not locate a sharable quorum resource and a local quorum
> > > > > > > cluster will be created.
> > > > > > > The quorum disk could not be located by the cluster service.
> > > > > > >
> > > > > > > 2004-10-04 21:02:06.031 [INFO] [MT] Connection to 'SQL-XCL' with
> > > > > > > binding string '213.169.237.217' failed because the RPC is not
> > > > > > > 2004-10-04 21:02:09.296 [INFO] xcl1: Found SCSI disk
> > > > > > > '\\.\PHYSICALDRIVE1' on Bus '4' and Port '2'; at TID '1' and LUN
> '0'
> > > > > > > (hr=00000000, {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:09.375 [INFO] xcl1: Physical disk
> PHYSICALDRIVE1 has
> > > > > > > signature 67c2a58. (hr=00000000,
> > > > > > > {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:09.546 [INFO] xcl1: Found physical disk
> > > > > > > "\\.\PHYSICALDRIVE1" with partition "Disk #1, Partition #0"
> which has
> > > > > > > the logical disk "D:". (hr=00000000,
> > > > > > > {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:09.609 [INFO] [SRV] The disks on SCSI port 2
> are
> > > > > > > cluster capable.
> > > > > > > 2004-10-04 21:02:09.656 [INFO] xcl1: Found SCSI disk
> > > > > > > '\\.\PHYSICALDRIVE0' on Bus '4' and Port '2'; at TID '0' and LUN
> '0'
> > > > > > > (hr=00000000, {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:09.703 [INFO] xcl1: Physical disk
> PHYSICALDRIVE0 has
> > > > > > > signature 704c704c. (hr=00000000,
> > > > > > > {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:09.859 [INFO] xcl1: Found physical disk
> > > > > > > "\\.\PHYSICALDRIVE0" with partition "Disk #0, Partition #0"
> which has
> > > > > > > the logical disk "C:". (hr=00000000,
> > > > > > > {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:09.906 [INFO] [SRV] The disks on SCSI port 2
> are
> > > > > > > cluster capable.
> > > > > > > 2004-10-04 21:02:09.953 [INFO] xcl1: Looking for disks on the
> same
> > > > > > > storage bus as the boot disk... (hr=00000000,
> > > > > > > {036BF567-2377-4BB3-8AE1-E4104E2EB3C5},
> > > > > > > {13E84779-125E-4B76-8C0D-1F5DB92EFE0F}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:10.000 [INFO] xcl1: Looking for disks on the
> same
> > > > > > > storage bus as the boot disk... (hr=00000000,
> > > > > > > {036BF567-2377-4BB3-8AE1-E4104E2EB3C5},
> > > > > > > {13E84779-125E-4B76-8C0D-1F5DB92EFE0F}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:10.062 [INFO] xcl1: Pruning SCSI disk
> > > > > > > '\\.\PHYSICALDRIVE1', on Bus '4' and Port '2'; at 'SCSI Tid 1,
> SCSI
> > > > > > > Lun 0' (hr=00000000, {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:10.109 [INFO] xcl1: The physical disk "Disk D:"
> > > > > > > cannot be managed because it is on the same storage bus as the
> boot
> > > > > > > disk. (hr=00000000, {13E84779-125E-4B76-8C0D-1F5DB92EFE0F},
> > > > > > > {1EFA8906-A36E-43BF-AF65-7F74413672EE}, 1, 1, 1), The cluster
> cannot
> > > > > > > manage physical disks that are on the same storage bus as the
> volume
> > > > > > > that contains the operating system because other nodes connected
> to
> > > > > > > the storage bus cannot distinguish between these volumes and
> volumes
> > > > > > > used for data.
> > > > > > > 2004-10-04 21:02:10.156 [INFO] xcl1: The physical disk "Disk D:"
> > > > > > > cannot be managed because it is on the same storage bus as the
> boot
> > > > > > > disk. (hr=00000000, {13E84779-125E-4B76-8C0D-1F5DB92EFE0F},
> > > > > > > {1EFA8906-A36E-43BF-AF65-7F74413672EE}, 1, 1, 1), The cluster
> cannot
> > > > > > > manage physical disks that are on the same storage bus as the
> volume
> > > > > > > that contains the operating system because other nodes connected
> to
> > > > > > > the storage bus cannot distinguish between these volumes and
> volumes
> > > > > > > used for data.
> > > > > > > 2004-10-04 21:02:10.203 [INFO] xcl1: Pruning SCSI disk
> > > > > > > '\\.\PHYSICALDRIVE0', on Bus '4' and Port '2'; at 'SCSI Tid 0,
> SCSI
> > > > > > > Lun 0' (hr=00000000, {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:10.250 [INFO] xcl1: The physical disk "Disk C:"
> > > > > > > cannot be managed because it is on the same storage bus as the
> boot
> > > > > > > disk. (hr=00000000, {13E84779-125E-4B76-8C0D-1F5DB92EFE0F},
> > > > > > > {39C7A02C-0713-4694-9652-48C9313A9663}, 1, 1, 1), The cluster
> cannot
> > > > > > > manage physical disks that are on the same storage bus as the
> volume
> > > > > > > that contains the operating system because other nodes connected
> to
> > > > > > > the storage bus cannot distinguish between these volumes and
> volumes
> > > > > > > used for data.
> > > > > > > 2004-10-04 21:02:10.312 [INFO] xcl1: The physical disk "Disk C:"
> > > > > > > cannot be managed because it is on the same storage bus as the
> boot
> > > > > > > disk. (hr=00000000, {13E84779-125E-4B76-8C0D-1F5DB92EFE0F},
> > > > > > > {39C7A02C-0713-4694-9652-48C9313A9663}, 1, 1, 1), The cluster
> cannot
> > > > > > > manage physical disks that are on the same storage bus as the
> volume
> > > > > > > that contains the operating system because other nodes connected
> to
> > > > > > > the storage bus cannot distinguish between these volumes and
> volumes
> > > > > > > used for data.
> > > > > > > 2004-10-04 21:02:10.390 [INFO] [SRV] The cluster service is not
> > > > > > > running. Creating a dummy Majority Node Set resource.
> > > > > > > 2004-10-04 21:02:11.000 [INFO] xcl1: The following networks will
> not
> > > > > > > be managed by the cluster: (hr=00000000,
> > > > > > > {036BF567-2377-4BB3-8AE1-E4104E2EB3C5},
> > > > > > > {00AF4C3F-47D5-4E6A-9EF0-6D719A32EE5C}, 1, 1, 1), The network
> adapters
> > > > > > > shown cannot be managed by the cluster. Please ensure that they
> have
> > > > > > > valid TCP/IP configurations and are connected to the network.
> Once
> > > > > > > these network adapters have a valid TCP/IP configuration they
> will be
> > > > > > > automatically added to the cluster.
> > > > > > >
> > > > > > > 2004-10-04 21:02:12.296 [WARN] xcl1: Local quorum 'is not' the
> quorum
> > > > > > > device. (hr=0x000001, {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:12.343 [INFO] xcl1: Located a quorum-capable
> resource
> > > > > > > "Local Quorum". (hr=00000000,
> {01297D4D-0C7C-44B1-AECE-604C710A65CC},
> > > > > > > {D29FB842-F9F9-44C1-A04B-C73BFC810C66}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:12.406 [INFO] xcl1: (null) (hr=00000000,
> > > > > > > {FDC75680-7DBB-42CA-8003-E4CDB01FF062},
> > > > > > > {6279EE6C-E99C-47CA-A61E-039C75C5C982}, 0, 6, 2), (null)
> > > > > > > 2004-10-04 21:02:12.468 [WARN] xcl1: Majority Node Set 'is not'
> the
> > > > > > > quorum device. (hr=0x000001,
> {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:12.531 [INFO] xcl1: Located a quorum-capable
> resource
> > > > > > > "Majority Node Set". (hr=00000000,
> > > > > > > {01297D4D-0C7C-44B1-AECE-604C710A65CC},
> > > > > > > {511E37C6-6EA1-4737-B977-D8B911EB0A56}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:02:12.578 [INFO] xcl1: (null) (hr=00000000,
> > > > > > > {FDC75680-7DBB-42CA-8003-E4CDB01FF062},
> > > > > > >
> > > > > > > (hr=00000000, {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:04:05.421 [INFO] xcl1: The physical disk "Disk D:"
> > > > > > > cannot be managed because it is on the same storage bus as the
> boot
> > > > > > > disk. (hr=00000000, {13E84779-125E-4B76-8C0D-1F5DB92EFE0F},
> > > > > > > {579AFE20-32FF-4409-A3FB-9F5169210567}, 1, 1, 1), The cluster
> cannot
> > > > > > > manage physical disks that are on the same storage bus as the
> volume
> > > > > > > that contains the operating system because other nodes connected
> to
> > > > > > > the storage bus cannot distinguish between these volumes and
> volumes
> > > > > > > used for data.
> > > > > > > 2004-10-04 21:04:05.468 [INFO] xcl1: The physical disk "Disk D:"
> > > > > > > cannot be managed because it is on the same storage bus as the
> boot
> > > > > > > disk. (hr=00000000, {13E84779-125E-4B76-8C0D-1F5DB92EFE0F},
> > > > > > > {579AFE20-32FF-4409-A3FB-9F5169210567}, 1, 1, 1), The cluster
> cannot
> > > > > > > manage physical disks that are on the same storage bus as the
> volume
> > > > > > > that contains the operating system because other nodes connected
> to
> > > > > > > the storage bus cannot distinguish between these volumes and
> volumes
> > > > > > > used for data.
> > > > > > > 2004-10-04 21:04:05.531 [INFO] xcl1: Pruning SCSI disk
> > > > > > > '\\.\PHYSICALDRIVE0', on Bus '4' and Port '2'; at 'SCSI Tid 0,
> SCSI
> > > > > > > Lun 0' (hr=00000000, {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > > 2004-10-04 21:04:05.578 [INFO] xcl1: The physical disk "Disk C:"
> > > > > > > cannot be managed because it is on the same storage bus as the
> boot
> > > > > > > disk. (hr=00000000, {13E84779-125E-4B76-8C0D-1F5DB92EFE0F},
> > > > > > > {C6DBB8DA-B17C-4712-8A2A-DB6D9FBEDC76}, 1, 1, 1), The cluster
> cannot
> > > > > > > manage physical disks that are on the same storage bus as the
> volume
> > > > > > > that contains the operating system because other nodes connected
> to
> > > > > > > the storage bus cannot distinguish between these volumes and
> volumes
> > > > > > > used for data.
> > > > > > > 2004-10-04 21:04:05.640 [INFO] xcl1: The physical disk "Disk C:"
> > > > > > > cannot be managed because it is on the same storage bus as the
> boot
> > > > > > > disk. (hr=00000000, {13E84779-125E-4B76-8C0D-1F5DB92EFE0F},
> > > > > > > {C6DBB8DA-B17C-4712-8A2A-DB6D9FBEDC76}, 1, 1, 1), The cluster
> cannot
> > > > > > > manage physical disks that are on the same storage bus as the
> volume
> > > > > > > that contains the operating system because other nodes connected
> to
> > > > > > > the storage bus cannot distinguish between these volumes and
> volumes
> > > > > > > used for data.
> > > > > > > 2004-10-04 21:04:05.718 [INFO] [SRV] The cluster service is not
> > > > > > > running. Creating a dummy Majority Node Set resource.
> > > > > > > 2004-10-04 21:04:05.812 [WARN] xcl1: [SRV] Enumerating
> resources.
> > > > > > > Total Requested:10; Current enum index:0; Total Enums:4.
> (hr=0x000001,
> > > > > > > {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> > > > > > > {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
> > > > > > >
> > > > > > > So it appears that the problem is that the clustering service
> cannot
> > > > > > > find the quorum disk. The OS part of the system which uses the
> raid 1
> > > > > > > and embedded 5I raid controler the same storage bus location
> ( 4 ) as
> > > > > > > the external scsi partitions which have an external 5I
> controller.(
> > > > > > > d: and e:).
> > > > > > >
> > > > > > >
> > > > > > > I have tried to remove and remake the array and partitions on
> the
> > > > > > > storage through the smartstart cd from HP. But i cannot find a
> option
> > > > > > > where i can assign a different bus.
> > > > > > >
> > > > > > > Can anyone give me a solution for this problem?
> > > > > > >
> > > > > > > Thnx in advance.
> > >
>
>
>



Relevant Pages

  • Re: Booting HP-UX 11 server using O.S. on EMC disks
    ... Finding storage that comes up quicker is not an option as I'm ... The reason the OS is on the EMC disks and not the internal is that the ... boot time, to be expected really! ... > Rick Jones wrote: ...
    (comp.sys.hp.hpux)
  • Re: blue screen error message
    ... boot from XP Disc ... >hardware and the was nothing under hardware in device manager. ... with storage hardware and drivers. ... If you cannot boot to the Recovery Console from the CD then there are ...
    (microsoft.public.windowsxp.hardware)
  • Re: Odd startup issues.
    ... Dig out the storage box, ... unless perhaps you have installed SP2 ... If so you should see an option on the boot menu to "Disable ... > to a command prompt,I could manually run the restore tool. ...
    (microsoft.public.windowsxp.basics)
  • Re: bootmgr is missing message on boot/start up Vista 32 bit
    ... drive in the BIOS boot sequence right after the optical disk drive. ... Re-connecting the "storage" drives results once agin in the ... Sounds like the computer is trying to boot from one of the other drives, ... clean install of Vista on new HD. ...
    (microsoft.public.windows.vista.installation_setup)
  • Re: Core 3 issues
    ... I got in to the Rescue boot, ... or is it looking for a storage network??? ... Initializing hardware storage network ...
    (Fedora)