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.
Thanks,
Bob
haskins_at_myapc.com
Received on Tue Dec 26 1995 - 22:54:39 NZDT