topic Re: Syslog error in Operating System - HP-UX

Syslog error

George_Dodds — Thu, 11 Nov 2004 06:29:09 GMT

Can anyone shed any light on this entry?

THe server is a HP L2000

SCSI: First party detected bus hang -- lbolt: 535857374, bus: 4
lbp->state: 5060
lbp->offset: 80
lbp->uPhysScript: f9fff000
From most recent interrupt:
ISTAT: 09, SIST0: 00, SIST1: 00, DSTAT: 84, DSPS: 00000001
lsp: 0
lbp->owner: 2944f00
bp->b_dev: 1f048000
scb->io_id: 4d9b0ff
scb->cdb: 28 00 00 e3 08 2c 00 00 04 00
lbolt_at_timeout: 535854174, lbolt_at_start: 535854174
lsp->state: 10d
scratch_lsp: 2944f00
Pre-DSP script dump [f9fff030]:
78347d00 0000000a 78350800 00000000
0e000004 f9fff500 e0100004 f9fff7b4
Script dump [f9fff050]:
9f0b0000 00000006 98080000 00000005
721a0000 00000000 98080000 00000001
NCR chip register dump for: 0x20200a
00: SCNTL3: 5f SCNTL2: 80 SCNTL1: 10 SCNTL0: d8
04: GPREG: 0f SDID: 08 SXFER: 1f SCID: 47
08: SBCL: 26 SSID: 80 SOCL: 06 SFBR: 00
0c: SSTAT2: 00 SSTAT1: 06 SSTAT0: 00 DSTAT: 80
10: DSA: c0ffffff
14: RESV14: ff RESV15: ff RESV16: ff ISTAT: 28
18: CTEST3: 21 CTEST2: 75 CTEST1: f0 CTEST0: 00
1c: TEMP: f9fffd78
20: CTEST6: 04 CTEST5: 24 CTEST4: 00 DFIFO: 00
24: DCMDDBC: 9f0b0000
28: DNAD: f9fff050
2c: DSP: f9fff058
30: DSPS: 00000006
34: SCRATCHA: ff00087d
38: DCNTL: a1 DWT: 00 DIEN: 7f DMODE: 4c
3c: ADDER: f9fff05e
40: SIST1: 00 SIST0: 40 SIEN1: 87 SIEN0: 8f
44: GPCNTL: 0f MACNTL: d0 SWIDE: 00 SLPAR: 6b
48: RESPID1: 00 RESPID0: 80 STIME1: 00 STIME0: 0c
4c: STEST3: 80 STEST2: 00 STEST1: 0c STEST0: 76
50: RESV50: 80 RESV51: e0 SIDL1: 00 SIDL0: 04
54: RESV54: 80 RESV55: e0 SODL1: 00 SODL0: 0d
58: RESV58: 80 RESV59: e0 SBDL1: 00 SBDL0: 0d
5c: SCRATCHB: 00000000
60: SCRATCHC: 00000000
64: SCRATCHD: 00000000
68: SCRATCHE: 00000000
6c: SCRATCHF: 00000000
70: SCRATCHG: 00000000
74: SCRATCHH: 00000000
78: SCRATCHI: 00000000
7c: SCRATCHJ: 00000000
PCI configuration register dump:
Command: 0157
Latency Timer: ff
Cache Line Size: 10

SCSI: Resetting SCSI -- lbolt: 535857474, bus: 4

SCSI: Reset detected -- lbolt: 535857474, bus: 4
LVM: PV 2 has been returned to vg[2].

Re: Syslog error

Georg Tresselt — Thu, 11 Nov 2004 06:42:37 GMT

From the first line I would guess that you have a faulty device on SCSI bus 4 and from the last line that it is a hard disk connect to group vg[2].

Re: Syslog error

Cheryl Griffin — Thu, 11 Nov 2004 06:50:26 GMT

Looking at "LVM: PV 2 has been returned to vg[2]." This means that the second physical disk in the second volume group may need to have it's timeout increased with pvchange -t 180.

How often are the SCSI bus hang messages occuring? What was happening at the time time of the errors? There are numerous causes for these messages.

Re: Syslog error

George_Dodds — Thu, 11 Nov 2004 06:54:24 GMT

I've checked my records and the disks for vg02 are on our XP256 array.

Calling HP now to get them to check it out.

Re: Syslog error

Eric Antunes — Thu, 11 Nov 2004 08:01:03 GMT

Hi George,

From my experience, each time I had those "lbolt" messages, I did replace the disk...

Best Regards,

Eric Antunes

Re: Syslog error

Zeev Schultz — Thu, 11 Nov 2004 08:10:42 GMT

You shouldn't receive scsi bus reset errors
for XP disks, they are Fibre connected.
Run ioscan -fn, find "ext_bus" instance number 4 and see what kind of device with scsi id 8 is there.

Zeev