Error messages in syslog.log

[Tim D Fulford]

I'm attaching two error msg from two syslog.log files. Usually when I see an lbolt msg I can deduce what it is (normally a tape device). But I can't seem to see fathom out this device (to my satisfaction)!

There are two K classes machine1/2 who share an AutoRAID system and DLT's. They are in a ServiceGuard cluster. The first gets a very verbose lbolt msg the second gets a short lbolt. I'm assuming it is a shared device as the times of the messages are close.

Any pointers?

Tim

[Rainer von Bongartz]

Tim,

nothing to worry about here.
I'm having this SCSI resets in my MC/SG Cluster too. I once asked HP what it was and they told me it had something to do with the cluser lock disk.
I' can't remember the exact reasons they told me, but this seems to be quite normal.

Regards
Rainer

[BFA6]

Where there any messages from cmcld at about the same time ?

I also get SCSI resets from ServiceGuard with regard to the cluster lock disk.

Hilary

[Alan Nicholson]

Quite normal, this is a link to the (very short) HP explanation:

http://europe-support.external.hp.com/cki/bin/doc.pl/sid=d18c08141036ac46bb/screen=ckiDisplayDocument?docId=200000057370871

[T G Manikandan]

Hello,
The scsi resets ae normally caused by a bad controller, a cable that is too
long, or bad termination.

PHKL_24004 s700_800 11.00 SCSI IO Subsystem Cumulative Patch
PHCO_23875 s700_800 11.00 cumulative SAM/ObAM patch
PHCO_24437 s700_800 11.00 LVM commands cumulative patch

[Mark Vollmers]

Tim-

I would get those messages from the RAID during backup. It turned out that the controller was unhappy, but there were real performance issues (crashing, etc). make sure you're patched up and if you're still seeing them or really worried about it, have the controller looked at. Maybe it needs a firmware update or something. I'd just keep an eye on it but you don't need to panic.

Mark

[Tim D Fulford]

Many thanks for the replies I'l will assign points but sometime next week!

o How do you know it is the AutoRAID that is causing these errors. Where in the jumble of numbers does it point to the AutoRAID?

o The AutoRAID had it's firmware upgraded and relavent AR patches.

Cheers

Tim

[Tim D Fulford]

Many thanks for the above, I still do not feel the question was fully answered [hence no 10's :( ], but close enough

Many thanks

Tim

[Mark Vollmers · Accepted solution]

Tim-

Sorry this is late, the thread got lost. Anyway, I think that you can identify the device from the syslog, but you'd have to be able to decifer the jumble of numbers there.

You could try to expand the timeout value to try to reduce the lbolts. Use pvchange -t 180 to change the default time from 30 to 180, which might help. If you don't have it, you could also throw OnlineDiagnostics (STM) on and run it through to see if any hardware issues pop up.

I was going to send you a link to a thread that had some info, but the entire thread vanished. Anyway, there was one that had how to read those things, so I'll put it in here. Maybe it will help.

{response by Michael Lampi}
{original error:}
SCSI:Abort Tag -- lbolt: 91143746, dev: 1f02a000, io_id: 26b2e26

{more stuff here}

The device driver handling the I/O is 0x1f = 31 decimal. This is the disk drive character device driver.

the bus handling the request is 0x02.

the SCSI ID of the device is 0xa, which translates into SCSI ID 10.

This particular drive did not respond to a SCSI command within the driver timeout period.

{end}
maybe that will help pin down where the problem was. Good luck!

Mark

[Mark Vollmers]

Tim-

Here is the link I was looking for. just for your reference.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xd0a1663ce855d511abcd0090277a778c,00.html

Mark

[Tim D Fulford]

Many thanks, we have some 10's (well it is one guy, but it just goes to show how appriciative I am)

Tim