SUMMARY: Nexan arrays/Chaparal controllers on DS20E/Tru64 v5.1

From: Kjell Andresen <kjell.andresen_at_usit.uio.no>
Date: Fri, 16 Feb 2001 15:38:43 +0100 (CET)

I got a really fast answer - but haven't got it tested/verified.
Thanks to Michael Polnick:

Regards,
Kjell Andresen Systems administrator, University of Oslo, Norway
                Center for Information Technology Services and
                Department of Geophysics

-------------------------------------------------------------
some times ago I had the same array for testing purpose and
got the same problem.

After contacting support I got several releases of newer (beta)
firmware, and the last one worked.
It was version k5412_k400b03.fla
In this version you can disable the so called BRIDGE LUN,
which is the lun for the Chaparal controller (your jka507).
But it works now also with enabled BRIDGE LUN.

With older firmware 2.0 the unix sees the same WWID for the
disk and for the controller, which confuses the driver.

If you have further questions, please contact
Gary Watson <gary_at_nexsan.com>
He was very helpful in solving this problem.

Greetings
Michael Polnick

-- 
------------------------------------------------------------
   Michael Polnick             PDV-Systeme Sachsen / Germany
   polnick_at_pdv-sachsen.net     Schillerstrasse 3
   Tel.: +49 3528 48030           01454 Radeberg
------------------------------------------------------------
I'm trying to connect a raidarray on my host and doesn't have much sucess.
The array is arranged by the dealer with a Sun/Solaris.
I'm interessted in contact with anyone who have experience with arrays
from Nexan/Chaparal. We will recieve a FC-array as well soon (I hope).
Here is some information:
Consolemode:
P00>>>show dev
dka0.0.0.7.1               DKA0              COMPAQ BB00913466  3B07
dka100.1.0.7.1             DKA100            SEAGATE ST118273W  5764
dka200.2.0.7.1             DKA200            SEAGATE ST118273W  6244
dka500.5.0.7.1             DKA500                CHAPTEC K5312  K2.0
dqa0.0.0.105.0             DQA0                        CD-224E  9.5B
dva0.0.0.0.0               DVA0
jka507.5.0.7.1             JKA507                CHAPTEC K5312  K2.0
eia0.0.0.9.1               EIA0              00-50-8B-AD-D5-CC
pga0.0.0.7.0               PGA0        WWN 2000-0000-c923-9b1d
pka0.7.0.7.1               PKA0                  SCSI Bus ID 7
pkb0.7.0.6.0               PKB0                  SCSI Bus ID 7
pkc0.7.0.106.0             PKC0                  SCSI Bus ID 7
Apart from the jka507.5.0.7.1 everything looks normal.
Booting to single-user og mounting all local disks with bcheckrc:
with the array connected:
>>>b -fl s
# bcheckrc
...
# /sbin/advfs/verify OpenSystems
verify: error [13] posting event: sys.unix.fs.advfs.fset.backup.lock
scsi0: HTH intr. on bus 0, SBCL = 0x21
cam_logger: SCSI event packet
cam_logger: bus 0
itpsa SCSI HBA
HTH intr. on bus 0, SBCL = 0x21
scsi0: SCSI Bus was reset
cam_logger: SCSI event packet
cam_logger: bus 0
itpsa SCSI HBA
SCSI Bus was reset
scsi0: HTH intr. on bus 0, SBCL = 0x21
cam_logger: SCSI event packet
SEAGATE ST118273W       5764
Active CCB at time of error
Bus reset sent/received
AdvFS I/O error:
    Volume: /dev/disk/dsk1c
    Tag: 0xfffffff7.0000
    Page: 126
    Block: 14229136
    Block count: 16
    Type of operation: Read
    Error: 5
    EEI: 0x6400
    I/O error appears to be due to a hardware problem.
    Check the binary error log for details.
advfs_logger: pg #125 is bad; truncating log
This error is also hanging the machine when booting directly into
multiusermode.
If I unconnect the array the domain of two ST118273W's is happilly
mounted.

Received on Fri Feb 16 2001 - 14:40:15 NZDT