Does anyone know how to interpret dia scsi messages. I have an IB M 36gb in a XP1000 that is locking things up.

From: MacDonell, Dennis <DennisMacDonell_at_auslig.gov.au>
Date: Wed, 15 Nov 2000 18:32:15 +1100

Hi,

I have put a 36gb 7200rpm IBM half low profile disk in an XP1000 that is
running factory installed 5.0A. Things seem to be working, except that the
disk seems to lock up the XP1000 and the machine has to be rebooted. Well it
doesn't completely lock up the machine, but access to that disk starts to
fail and init 0 hangs and never comes down to the >>> prompt. So far it has
meant using the magic power switch, to get the machine to reboot. The
machine seems to go through the whole boot process OK. It does an fsck on
the suspect disk, but never seems to loose anything, keeps going with the
boot sequence, and eventually comes up as if nothing has happened. The
machine then proceeds to work peacefully for days.

The following is a resume of the events that appeared in the error log, as
produced by dia
(a)
Timestamp of occurrence 10-NOV-2000 16:35:04
Entry type 310. Time Stamp
(b)
Timestamp of occurrence 10-NOV-2000 16:42:28
Routine Name cdisk_check_sense
                                     Event - No Sense
Error Type Information Message Detected
(recovered)

Device Name IBM DDYS-T36950N S80D
                                     Active CCB at time of error
                                     CCB request completed with an error
(c)
Timestamp of occurrence 10-NOV-2000 16:42:45
Class x22 DEC SIM - SCSI Interface Module
Subsystem x22 DEC SIM - SCSI Interface Module
Number of Packets 5.
------ Packet Type ------ 258. Module Name String
Routine Name ss_perform_timeout
------ Packet Type ------ 256. Generic String
                                     timeout on disconnected request
(d)
Timestamp of occurrence 10-NOV-2000 16:42:45
Number of Packets 2.
------ Packet Type ------ 258. Module Name String
Routine Name ss_abort_done
(e)
Timestamp of occurrence 10-NOV-2000 16:42:45
Routine Name cdisk_resp_complete
------ Packet Type ------ 256. Generic String
                                     Device monitoring event for Test Unit
                                     Ready CCB
------ Packet Type ------ 262. Info Error String
Error Type Information Message Detected
(recovered)
------ Packet Type ------ 257. Device Name String
Device Name IBM DDYS-T36950N S80D
------ Packet Type ------ 256. Generic String
                                     Active CCB at time of error
------ Packet Type ------ 256. Generic String
                                     Command timed out

It seems to me that something triggers a request for information that gets
garbled, and that starts up a sequence of abort, timeouts that it never gets
out of. At times I think its tried to reset the bus and fails to do that as
well. I guess this is not just a Tru64 5.0A problem since we have a DS20E
(with no foreign disks, however), which is behaving quite well. Perhaps
there is some mismatch in the version of scsi that 5.0A uses and the version
for the IBM disk. I have put a couple these IBM disks in machines running
4.0F with no ill effects (they arn't XP1000s however).

Any ideas anyone.

Dennis.

######################################
Dennis Macdonell
Systems Administrator
AUSLIG
mail: PO Box 2, Belconnen, ACT 2617
email: mcdonell_at_auslig.gov.au
ph: 61 2 6201 4326
fax: 61 2 6201 4377
######################################
Received on Wed Nov 15 2000 - 07:33:57 NZDT

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