Some time ago, I asked the following question:
>We recently added a Seagate ST15150N to a DEC 3000-800S running
>DEC OSF/1 v3.2 (no letters, numbers or dashes). This was added to the
>scsi1 (external bus) as device 0 lun 0, the only device at the end of a 2
>meter cable and the device is properly terminated. After about a month
>of usage without any problems rebooting, we began getting the
>following sequence of errors each time upon a normal system startup:
>cam_logger: CAM_ERROR packet
>cam_logger: bus 1 target 0 lun 0
>dme_tcds_resume()
>Invalid DME DAT element.
>cam_logger: CAM_ERROR packet
>cam_logger: bus 1 target 0 lun 0
>sim_error_sm
>Target went to data in phase
>at which point the machine hangs. If one simply halts and hits "b <cr>"
>at the ensuing console prompt, the machine boots up fine. I maintain that
>this should not happen.
>After calling DEC, their response was, "Firmware problem on the drive.
>Contact Seagate and get a firmware upgrade." After talking to Seagate,
>their response was, "The O/S is not allowing enough time (60 seconds
>by SCSI-2 spec) for the device to come up. It is an O/S problem." I am
>by no stretch of the imagination a SCSI expert.
>So, we're getting the good old bi-directional finger pointing. I thought that
>this had vanished at DEC; I guess not. My question: has anyone else
>seen this problem? If so, what is the fix? There are a couple of
>ST11200Ns on bus 0 which work beautifully.
First off, I'd like to thank the following people for their responses:
Selden E Ball Jr <SEB_at_LNS62.LNS.CORNELL.EDU>
Bill Budenholzer <bluemax_at_esm3max.esmrahd.com>
Norman Wilson <norman_at_hprc.utoronto.ca>
<alan_at_nabeth.cxo.dec.com>
Robert Lott <rnlott_at_milp.lsis.loral.com>
I think that Robert Lott got it right when he responded simply:
in the printenv increase scsi_reset time to 5 or 6 to resolve this problem.
After seeing Robert's message I checked my console manual and found
that the scsi_reset value "Causes a time delay (in milliseconds) after a
SCSI reset and before booting the system (value range is 0-7, with 4 as
the default). The value is n in the expression 2^n. For example, a value of
3 is 2^3 and means 8 seconds." There is a discrepancy between these
two statements; one says milliseconds and one says seconds. I would
suspect that it should be seconds. Maybe someone from Digital can
verify this for the list.
I have not had a chance to test the change, but I suspect that this
change at monitor mode will fix the problem.
Bob
haskins_at_myapc.com
Received on Thu Jan 18 1996 - 16:49:52 NZDT