topic Re: decoding SCSI driver error messages in Operating System - HP-UX

decoding SCSI driver error messages

t keaveny — Tue, 03 Jun 2014 04:34:43 GMT

are there any documents that describe how
to decode console (dmesg) logs for
the Symbios-based SCSI adapters?

In particular, to determine which specific target
device is having a problem?

E.g., from the following:

SCSI: Request Timeout -- lbolt: 34294280, dev: cb0f6042

What exactly does "dev" map to? Is
the target device (and logical unit number)
encoded in this record?

Thanks!

P.S. This thread has been moved from Disk to HP-UX > sysadmin. - Hp Forum moderator

Re: decoding SCSI driver error messages

Mike Brown_3 — Wed, 20 Nov 2002 12:48:34 GMT

There was a reference to this in the knowledge base, but it appears to be unavailable right now.

I think what you can do is note down the string after "cb" in the dev: field of the "Request Timeout" error above.
You can then get the corrsponding device name by doing a:
ll /dev/dsk |grep #string
(or /dev/rmt, depending on if it is a disk or tape device).

Re: decoding SCSI driver error messages

Mike Brown_3 — Wed, 20 Nov 2002 14:28:10 GMT

You can use the following information to determine which device generates lbolt/timeout errors:

cb 0f 6 0 42
__ __ _ _ __
| | | | |
major# | target | flags
| |
bus# lun

Using this information:
- major# (cb) is 203 in decimal which, I think, maps to device type `sdisk`.
- bus# (0f) is the card instance number (15 in decimal) to which the device is attached.
- target (6) is the device's scsi id.
- lun (0) is the device's logical unit number.

Therefore, this device maps to /dev/dsk/c15t6d0 - would that make sense with your system?

Re: decoding SCSI driver error messages

t keaveny — Mon, 02 Dec 2002 21:01:07 GMT

(note, that it is not clear how to reply to the thread chain
directly, so I'm replying to my base message...)

from what I can see the major code of 203 refers to
the SCSI host adapter controller, itself (which is located
at SCSI ID#7), which does have an instance for #15.

there is a tape device connected at SCSI ID#6

so it looks like the message is telling me that there was
a problem with the library at SCSI-ID#6
connected to controller#15, and
that the error message originated with the controller as opposed
to the library (or I would have seen major number 205).

in any case, our sys-admin is going to see whether that
particular device is giving the library fits

at least we're on the right track, now...
==
tom