scu not seeing disks that the console does

From: Tom Leffingwell <tom_at_sba.miami.edu>
Date: Fri, 23 May 2003 12:21:42 -0400 (EDT)

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
Received on Fri May 23 2003 - 16:22:22 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:44 NZDT