Info about syslog error

[Filosofo]

Hello Guys,
I would know I can "read" this information that I find in Syslog.

Mar 25 14:23:02 omih306 vmunix: SCSI: Reset detected -- lbolt: 327373, bus: 2
Mar 25 14:23:02 omih306 vmunix: lbp->state: 6060
Mar 25 14:23:02 omih306 vmunix: lbp->offset: ffffffff
Mar 25 14:23:02 omih306 vmunix: lbp->uPhysScript: f87ba000
Mar 25 14:23:02 omih306 vmunix: From most recent interrupt:
Mar 25 14:23:02 omih306 vmunix: ISTAT: 02, SIST0: 02, SIST1: 00, DSTAT: 80, DSPS: 0000000f
Mar 25 14:23:02 omih306 vmunix: lsp: 0000000000000000
Mar 25 14:23:02 omih306 vmunix: lbp->owner: 0000000000000000
Mar 25 14:23:02 omih306 vmunix: scratch_lsp: 0000000000000000
Mar 25 14:23:02 omih306 vmunix: Pre-DSP script dump [fffffffff87ba008]:
Mar 25 14:23:02 omih306 vmunix: f87ba5c0 80880000 000000e4 80000000
Mar 25 14:23:02 omih306 vmunix: 00000000 c0000004 00000000 00000000
Mar 25 14:23:02 omih306 vmunix: Script dump [fffffffff87ba028]:
Mar 25 14:23:02 omih306 vmunix: 41000000 f87ba290 980dff00 0000000a
Mar 25 14:23:02 omih306 vmunix: 78350000 00000000 0e000000 f87ba540

Thanks

Filo

[Jeff Schussele]

Hi Filo,

Did anybody reseat a disk drive or power cycle a device (tape / CD) on that SCSI bus?
That would cause a reset, which would be the normal course of events.
Else if this happens frequently, it could be an indication of an impending failure in the SCSI subsystem.

Rgds,
Jeff

[Ross Zubritski]

When I have seen this here, it has been either DVD/DAT module or a cabling issue.

Regards,

RZ

[Filosofo]

Thanks for your help;
but I would like know what information I can extract from this line for example:
lsp: 0000000000000000

or

vmunix: Script dump [fffffffff87ba028]:

I hope that you can understand me......my english is not good...

Filo

[erics_1]

Filo,

Your english is fine. Do you happen to see any EMS errors logged to syslog or any hex addresses preceded by b_dev? You'd have to have diagnostics installed on the system to see the EMS notification.

Regards,
Eric

[Steven E. Protter]

If its a hot swappapble disk and it was pulled out of the unit for a second, and lbolt will be generated. If the cable to a tape drive or CD drive were removed same issue.

Restarting the machine will clear the error.

If none of these things happen, you may have a bad disk and need to bring our HP hardware to replace it.

I reccomend a make_tape_recovery and a fbackup with databases down to preserve data prior to switching the disk.

Its important to know whats on it so you know how much of a backup will be required.

cabling, control card and drive cage(if present) issues can also trigger lbolts.

NOTE:I've never had an lbolt that didn't lead to equipment being replaced.

SEP