SUMMARY: Seagate ST43400N on an AlphaStation 600 5/266

From: Hellebo Knut <Knut.Hellebo_at_nho.hydro.com>
Date: Thu, 21 Mar 1996 10:44:04 +0100

Regards managers,

Here's a brief summary on getting a Seagate ST43400N (3.6GB) to work with an
AlphaStation 600 5/266.

First a short recap:

When attaching a Seagate ST43400N (2.9GB) to the Fast SCSI2 port on the back
of an AlphaStation 600 5/266 the machine had difficulties discovering the
disk through 'sho dev'. There were also some errormessages in the systemlogs
telling

Mar 13 15:41:02 bgubda01 vmunix: cam_logger: CAM_ERROR packet
Mar 13 15:41:02 bgubda01 vmunix: cam_logger: bus 0 target 1 lun 0
Mar 13 15:41:02 bgubda01 vmunix: cdisk_op_spin
Mar 13 15:41:02 bgubda01 vmunix: Device Not Ready
Mar 13 15:41:03 bgubda01 vmunix: Hard Error Detected
Mar 13 15:41:03 bgubda01 vmunix: UNKNOWN
Mar 13 15:41:03 bgubda01 vmunix: Active CCB at time of error
Mar 13 15:41:03 bgubda01 vmunix: BUS free
Mar 13 15:51:42 bgubda01 vmunix: isp0: restarting
.
.
.
Rebooting the machine led to failure in initialising the LSM volume because
this disk was regarded as failed.

The rudimentary solution (and hopefully not the permanent one) is one of the
 following two:

1. Do NOT reboot. Halt the machine, wait approx. 45 secs until the disk shows
up when doing a 'sho dev', then boot. Note that LSM failed initialising the
volume that had this disk as one of its members even when using this 'wait
until ready' approach.

2. From LSM (after rebooting):
voldg -g diskgroup -k rmdisk seagatedisk
voldg -g diskgroup -k addisk seagatedisk
volume -obg -f start failedvolume
mount

I had responses from several others having difficulties in attaching non DEC
disks to this kind of system (I believed those days were gone !!!). Most of
them suggested that cablelength was exceeded (3m). If this is the case then
the internal cablelength on the AlphaStation have to exceed 1.5 m !! (I used
a 1m cable and calculated in addition to this .5m for the external
disk+cabinet).
What I did not mention was that I was NOT able to connect a Micropolis 1936
(3.6GB) disk. This disk did NOT show up no matter how long I waited before
doing a 'sho dev', BUT it worked fine on all other systems I tried (even on a
f/w Ultra) ! (I posted a query about this Feb 8th but got no responses).
Until DEC comes up with some other kind of solution I guess I'll just have to
monitor this system very tight !!

Thanks to all responders, especially

Don Weyel, weyel_at_bme.unc.edu
John Macallister, j.macallister1_at_physics.oxford.ac.uk
Stan Huhman, huhman_at_rg.deere.com

-- 
      ******************************************************************
      *         Knut Helleboe                    | DAMN GOOD COFFEE !! *
      *         Norsk Hydro a.s                  | (and hot too)       *
      * Phone: +47 55 996870, Fax: +47 55 996342 |                     *
      * Pager: +47 96 500718                     |                     *
      * E-mail: Knut.Hellebo_at_nho.hydro.com       | Dale Cooper, FBI    *
      ******************************************************************
Received on Thu Mar 21 1996 - 11:18:21 NZST

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