I am having problems adding certain SCSI peripherals on to the external
SCSI bus 'B' on our 3000/M400.
I currently have one SEAGATE disk on the external bus which works fine:
vmunix: rz8 at asc1 bus 1 target 0 lun 0 (SEAGATE ST410800N 0016)
Attempts to add either of two other SCSI devices result in failure. The
primary indicator is at the boot PROM monitor prompt. I forget the complete
output, the relavent data would be:
(with only one of the "failing devices attached to the B bus")
>>> sho device
DKB100 B/0/0 DISK
B/0/1
B/0/2
B/0/3
B/0/4
B/0/5
B/0/6
B/0/7
The two failing devices are a Micropolis 10 GB drive and a MaxOptics
TNT-3 Magneto-optical drive. If I boot from this stage the cam system
will give me various messages:
Apr 3 16:18:56 betical vmunix: phase
Apr 3 16:18:56 betical vmunix: cam_logger: CAM_ERROR packet
Apr 3 16:18:56 betical vmunix: cam_logger: bus 1 target 0 lun 4
Apr 3 16:18:56 betical vmunix: sim_err_sm
Apr 3 16:18:56 betical vmunix: Target went to bus free phase
Apr 3 16:18:56 betical vmunix: cam_logger: CAM_ERROR packet
Apr 3 16:18:56 betical vmunix: cam_logger: bus 1 target 0 lun 5
Apr 3 16:18:56 betical vmunix: sm_status
Apr 3 16:18:56 betical vmunix: Invalid status phase
all the way up to lun 7... I also see:
May 3 08:57:58 betical vmunix: sim94_sel
May 3 08:57:58 betical vmunix: Flushing residual bytes from FIFO
May 3 08:57:58 betical vmunix: cam_logger: CAM_ERROR packet
May 3 08:57:58 betical vmunix: cam_logger: bus 1 target 0 lun 0
and
May 8 08:31:39 betical vmunix: tcdsintr
May 8 08:31:39 betical vmunix: TCDS DB bus parity error
May 8 08:31:39 betical vmunix: cam_logger: CAM_ERROR packet
May 8 08:31:39 betical vmunix: cam_logger: bus 1
May 8 08:31:39 betical vmunix: ascintr
May 8 08:31:39 betical vmunix: Bus reset detected
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The SEAGATE listed above simply reports LUN 0 ...
(only the seagate 10 GB drive attached)
>>> sho device
DKB100 B/0/0 DISK
and gets mounted just fine.
I have installed another Micropolis disk on our AlphaServer 2100 with no
trouble at all. I suspect I might need a firmware upgrade, (think we are
at V3.2) I am running OSF/1 2.0 right now. Think I could upgrade firmware
without an OS upgrade?
Thanks...
--
---------------------------------------------------------------------------
Ted Asocks tra_at_ucolick.org
Systems Administrator VOICE: (408)459-4020
UCO/Lick Observatory FAX: (408)454-9863
Received on Wed Jun 14 1995 - 01:13:52 NZST