scu not seeing disks that the console does

From: Tom Leffingwell (tom_at_sba.miami.edu)
Date: 05/23/03

  • Next message: Dave Sill: "Administrivia: Tru64-UNIX-Managers information and policy statement"
    Date: Fri, 23 May 2003 12:21:42 -0400 (EDT)
    To: tru64-unix-managers@ornl.gov
    
    

    I'm trying to bring up a TruCluster, but I can't seem to get the first
    system to recognize the disks on the shared bus. So far the OS has been
    installed, but I've yet to run clu_create.

    I have a DS10 system (two actually) both connected to an RA3000. DKA0, 1,
    and 2 show up just fine in SRM:

    >>>show dev
    dka0.0.0.16.0 DKA0 HSZ22 d11x
    dka1.0.0.16.0 DKA1 HSZ22 d11x
    dka2.0.0.16.0 DKA2 HSZ22 d11x
    dkb0.0.0.17.0 DKB0 COMPAQ BB009222B5 B016
    dkb100.1.0.17.0 DKB100 COMPAQ BB009222B5 B016
    dkb200.2.0.17.0 DKB200 COMPAQ BB009222B5 B016
    dqa0.0.0.13.0 DQA0 COMPAQ CDR-8435 0013
    dva0.0.0.0.0 DVA0
    ewa0.0.0.9.0 EWA0 08-00-2B-86-77-FA
    ewb0.0.0.11.0 EWB0 08-00-2B-86-78-5C
    pka0.7.0.16.0 PKA0 SCSI Bus ID 7 5.57
    pkb0.7.0.17.0 PKB0 SCSI Bus ID 7 5.57

    I then boot the system off of a local disk DKB0, and run scu:

    # scu show edt

    CAM Equipment Device Table (EDT) Information:

        Bus/Target/Lun Device Type ANSI Vendor ID Product ID Revision N/W
        -------------- ----------- ------ --------- ---------------- -------- ---
         0 0 0 CD-ROM SCSI-2 COMPAQ CDR-8435 0013 N
         3 0 0 Direct SCSI-2 COMPAQ BB009222B5 B016 W
         3 1 0 Direct SCSI-2 COMPAQ BB009222B5 B016 W
         3 2 0 Direct SCSI-2 COMPAQ BB009222B5 B016 W

    The only disks that show up are DKB0, DKB100, and DKB200. Running an scu
    scan edt does not change anything either.

    The OS is 5.1B, patch kit 1. Both systems can see the disks from SRM, the
    second system isn't installed yet, because I can't do clu_create until I
    can see the disks. The first system has the controller using ID 7, and
    the other is using 6. Am I missing something obvious here?

    Thanks,

    Tom


  • Next message: Dave Sill: "Administrivia: Tru64-UNIX-Managers information and policy statement"

    Relevant Pages

    • Re: Problem with Hard disk upgrade
      ... It could be that SRM doesn't know how to deal with large disks. ... booting off a small disk on the onboard controller. ... Do I need the PCI ATA Controller? ...
      (comp.os.linux.alpha)
    • Re: KZPBR-CY
      ... VMS V8.2 on an Alpha Server 1200 with the latest firmware installed. ... The card is recognized in SRM as a Qlogic ISP10x0 but no disks are visible. ...
      (comp.os.vms)
    • DWZZA-VW and Qlogic ISP1020
      ... in an AlphaServer 1000A 5/300. ... RZ26-L's) were recognized by SRM and VMS found them. ... I connected the same cabinet to a Qlogic ISP1020. ... no disks were recognized by SRM. ...
      (comp.os.vms)
    • Re: eSATA Cluster Support?
      ... Cluster cares about Basic disks and those disks being on a shared SCSI ... Can this eSATA solution be on a shared bus for ...
      (microsoft.public.windows.server.clustering)
    • RE: How is a disk determined to be a sharable?
      ... I ask this as I'm having an issue with 2003 enterprise declaring that the iSCSI devices it finds are not on a shared bus and cant be used as a "quorum capable device". ... Also during the initial Cluster node installation In 2003 server,The process will bring the sharable physical disks into the cluster "automatically" using the smallest disk as the quorum. ... Microsoft, the person providing the advice, nor any ...
      (microsoft.public.windows.server.clustering)