message in syslog.log [HP-UX B.10.20]

[harjeet_3]

hello,

The following messages are coming in the log file named syslog.log :

jam1:vmunix: PRE-DSP script dump [B7F0C8]:
jam1:vmunix: 7c027f00 00000000 78350000 00000000
jam1:vmunix: 60000040 00000000 48000000 00000000
jam1:vmunix: Scrip dump [87f0e8]:
jam1:vmunix: 54000000 ffffff18 740a0f00 00000000
jam1:vmunix: 6c110800 00000000 808cf708 00000058
jam1:vmunix: NCR chip register dump:
jam1:vmunix: 00: SCNTRL3: 1b SCNTL2: 00 SCNTL1: 00 SCNTLO: d8
;;
;;
;;
;;
zalon register dump:
io_status: b900060
io_etm: 00000000

SCSI reset detected -- lbolt: 372501, bus: 0
SCSI reset detected -- lbolt: 372573, bus: 0
SCSI reset detected -- lbolt: 372640, bus: 0
SCSI reset detected -- lbolt: 372810, bus: 0
SCSI reset detected -- lbolt: 372848, bus: 0
SCSI reset detected -- lbolt: 375247, bus: 0

lbp->state: 40
lbp->offset: ffffffff
lbp->uPhysScript: 883000
from most recent interupt
ISTAT:02, SISTO:02, dstat:80 ds[s:ffffff18
lsp:0
lbp->owners:0
scratch_lsps: 0

THEN AGAIN ALL THE ABOVE MESSAGES REPEATED BEGNNING WITH PRE-DSP....

[Matti_Kurkela]

These are "lbolt" errors, caused by the SCSI controller resetting itself because of some problems with the SCSI bus.

Some possible causes:
- cable disconnected or loose?
- missing SCSI termination?
- hardware failure in a SCSI device (causing interference with the bus)?

MK

[harjeet_3]

hi Matti Kurkela,

thx for prompt response, well i would say that we have SCSI disk station that had till couple of days back mirror disk. One of the disk in the disk station had been crashed then we replace with the mirror disk of crash disk, hence from this day onward system is working fine but the error has been noticed today.

Ques1#: In this case what could be the reasons amongst u have mentioned in your reply could be the 3 third that SCSI termination has not been done. is it right or you feel something else.

Ques 2#: Tell the further steps I should do?