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

Error in Syslog

Venkat_11 — Mon, 01 May 2006 09:19:53 GMT

Hi,

One of the servers received error messages in syslog.
Does any body suggest us what is about it.?

May 1 05:05:01 usxsl004 vmunix:
May 1 05:05:01 usxsl004 vmunix: SCSI: Reset detected -- path: 0/1/1/1
May 1 05:05:01 usxsl004 vmunix: SCSI: -- lbolt: 301555642, bus: 3
May 1 05:05:01 usxsl004 vmunix: lbp->state: 30008
May 1 05:05:01 usxsl004 vmunix: lbp->offset: ffffffff
May 1 05:05:01 usxsl004 vmunix:
May 1 05:05:01 usxsl004 vmunix: lbp->nominalOffset: 0
May 1 05:05:01 usxsl004 vmunix: lbp->Cmdindex: 0
May 1 05:05:01 usxsl004 vmunix: lbp->last_nexus_index: 0
May 1 05:05:01 usxsl004 vmunix: lbp->nexus_index: 0
May 1 05:05:01 usxsl004 vmunix: uCmdSent: 0
uNexus_offset: 0
May 1 05:05:01 usxsl004 vmunix: last lbp->puStatus
[0000000041625600]:
May 1 05:05:01 usxsl004 vmunix: 00000000 00000000
00000000 00000000
May 1 05:05:01 usxsl004 vmunix: next lbp->puStatus
[00000000416257f0]:
May 1 05:05:01 usxsl004 vmunix: 00031000 00031000
00031000 00031000
May 1 05:05:01 usxsl004 vmunix: From most recent interrupt:
May 1 05:05:01 usxsl004 vmunix: ISTAT: 02, SIST0: 02,
SIST1: 00, DSTAT: 80, DSPS: 00000000
May 1 05:05:01 usxsl004 vmunix: lsp: 0x0000000000000000
May 1 05:05:01 usxsl004 vmunix: DSAtbl->host_iocb_index:
0
May 1 05:05:01 usxsl004 vmunix: DSAtbl->host_iocb_addr:
5d800
May 1 05:05:01 usxsl004 vmunix: scratch_lsp: 0x0000000000000000
May 1 05:05:01 usxsl004 vmunix: c8xx_iocb [ffffffff90010b00]:
May 1 05:05:01 usxsl004 vmunix: 1e00df80 0040007f
00000000 00000000
May 1 05:05:01 usxsl004 vmunix: 00000000 0005df60
00000000 0005df68
May 1 05:05:01 usxsl004 vmunix: Pre-DSP script dump
[ffffffff900101a0]:
May 1 05:05:01 usxsl004 vmunix: 90010264 c1000020
0005df40 90010b00
May 1 05:05:01 usxsl004 vmunix: f1340004 00000004
74364000 00000000
May 1 05:05:01 usxsl004 vmunix: Script dump [ffffffff900101c0]:
May 1 05:05:01 usxsl004 vmunix: 98040000 0000000f
f1700004 0000000c
May 1 05:05:01 usxsl004 vmunix: e0720001 900101e2
78492f00 00000000
May 1 05:05:01 usxsl004 vmunix: NCR chip register dump for:
0x4002002
May 1 05:05:01 usxsl004 vmunix: 00: SCNTL3: bf SCNTL2:
00 SCNTL1: 00 SCNTL0: da
May 1 05:05:01 usxsl004 vmunix: 04: GPREG: 0f SDID:
0f SXFER: 1f SCID: 47
May 1 05:05:01 usxsl004 vmunix: 08: SBCL: 00 SSID:
80 SOCL: 00 SFBR: 40
May 1 05:05:01 usxsl004 vmunix: 0c: SSTAT2: 02 SSTAT1:
0f SSTAT0: 00 DSTAT: 80
May 1 05:05:01 usxsl004 vmunix: 10: DSA: 90010b00
May 1 05:05:01 usxsl004 vmunix: 14: MBOX1: 00 MBOX0:
00 ISTAT1: 00 ISTAT: 02
May 1 05:05:01 usxsl004 vmunix: 1c: TEMP: 90010ac8
May 1 05:05:01 usxsl004 vmunix: 24: DCMDDBC: 98040000
May 1 05:05:01 usxsl004 vmunix: 28: DNAD: 900101c0
May 1 05:05:01 usxsl004 vmunix: 2c: DSP: 900101c8
May 1 05:05:01 usxsl004 vmunix: 30: DSPS: 0000000f
May 1 05:05:01 usxsl004 vmunix: 34: SCRATCHA: 0040007f
May 1 05:05:01 usxsl004 vmunix: 38: DCNTL: a1 DWT:
00 DIEN: 7f DMODE: 4c
May 1 05:05:01 usxsl004 vmunix: 3c: ADDER: 900101d7
May 1 05:05:01 usxsl004 vmunix: 40: SIST1: 10 SIST0:
00 SIEN1: 97 SIEN0: 8f
May 1 05:05:01 usxsl004 vmunix: 44: GPCNTL: 27 MACNTL:
00 SWIDE: 00 SLPAR: 00
May 1 05:05:01 usxsl004 vmunix: 48: RESPID1: 00 RESPID0:
80 STIME1: 00 STIME0: fc
May 1 05:05:01 usxsl004 vmunix: 4c: STEST3: 80 STEST2:
00 STEST1: 0c STEST0: 76
May 1 05:05:01 usxsl004 vmunix: 50: RESV50: 00 RESV51:
c0 SIDL1: 00 SIDL0: 00
May 1 05:05:01 usxsl004 vmunix: 54: CCNTL1: 01 CCNTL0:
01 SODL1: 00 SODL0: 00
May 1 05:05:01 usxsl004 vmunix: 58: RESV58: 00 RESV59:
00 SBDL1: 00 SBDL0: 00
May 1 05:05:01 usxsl004 vmunix: 5c: SCRATCHB: 000f0000
May 1 05:05:01 usxsl004 vmunix: 60: SCRATCHC: c0ffffff
May 1 05:05:01 usxsl004 vmunix: 64: SCRATCHD: 0005df7c
May 1 05:05:01 usxsl004 vmunix: 68: SCRATCHE: 90010c00
May 1 05:05:01 usxsl004 vmunix: 6c: SCRATCHF: 00058000
May 1 05:05:01 usxsl004 vmunix: 70: SCRATCHG: bf0f1f1e
May 1 05:05:01 usxsl004 vmunix: 74: SCRATCHH: 0005d600
May 1 05:05:01 usxsl004 vmunix: 78: SCRATCHI: 1901571f
May 1 05:05:01 usxsl004 vmunix: 7c: SCRATCHJ: 00000000
May 1 05:05:01 usxsl004 vmunix: bc: SCNTL4: 00
May 1 05:05:01 usxsl004 vmunix: PCI configuration register dump:
May 1 05:05:01 usxsl004 vmunix: Command: 0157
May 1 05:05:01 usxsl004 vmunix: Latency Timer: c0
May 1 05:05:01 usxsl004 vmunix: Cache Line Size: 20

Thanks In Advance
Eswar

Re: Error in Syslog

Steven E. Protter — Mon, 01 May 2006 09:29:19 GMT

Shalom Eswar,

bad disk.

- lbolt: 301555642, bus: 3

ll /dev/dsk or /dev/rdsk

to get the actual location.

This error can be triggered by swapping a hotswap disk

dmesg -
wait
dmesg

See if it stays clear.

SEP

Re: Error in Syslog

Venkat_11 — Mon, 01 May 2006 09:49:41 GMT

Hi,

Thanks for quick responce

Here is the output of dmesg

usxsl004:root# dmesg

May 1 09:42
...
disk
0/4/1/0.179.2.10.0.1.3 sdisk
0/4/1/0.179.2.10.0.1.4 sdisk
0/4/1/0.179.2.10.0.1.5 sdisk
0/4/1/0.179.2.10.0.1.6 sdisk
0/4/1/0.179.2.255.0 fcpdev
0/4/1/0.179.2.255.0.10 tgt
0/4/1/0.179.2.255.0.10.0 sctl
0/6 lba
0/6/1/0 igelan
0/7 lba
0/7/1/0 asio0
0/7/1/1 asio0
8 memory
16 ipmi
128 processor
igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0
igelan1: INITIALIZING HP A6825-60101 PCI 1000Base-T Adapter at hardware path 0/6/1/0

System Console is on the Built-In Serial Interface
Entering cifs_init...
Initialization finished successfully... slot is 9
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 4194304
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x21000; start = 314208, size = 2097152
Starting the STREAMS daemons-phase 1
Create STCP device files
$Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 2095104 Kbytes, lockable: 1610324 Kbytes, available: 1855984 Kbytes

NFS server usxsl003be not responding still trying
NFS server usxsl003be ok
SCSI: Bus mode change detected on bus: 3, path: 0/1/1/1. Bus will be reset.

SCSI: Resetting SCSI -- lbolt: 210532262, bus: 3 path: 0/1/1/1

SCSI: Reset detected -- lbolt: 210532262, bus: 3 path: 0/1/1/1
0/1/1/1.0 tgt
0/1/1/1.0.0 stape
xdr_opaque: decode FAILED
NOTICE: nfs_server: bad getargs for 2/16

SCSI: Reset detected -- path: 0/1/1/1

SCSI: -- lbolt: 301555642, bus: 3
lbp->state: 30008
lbp->offset: ffffffff
lbp->nominalOffset: 0
lbp->Cmdindex: 0
lbp->last_nexus_index: 0
lbp->nexus_index: 0
uCmdSent: 0 uNexus_offset: 0
last lbp->puStatus [0000000041625600]:
00000000 00000000 00000000 00000000
next lbp->puStatus [00000000416257f0]:
00031000 00031000 00031000 00031000
From most recent interrupt:
ISTAT: 02, SIST0: 02, SIST1: 00, DSTAT: 80, DSPS: 00000000
lsp: 0x0000000000000000
DSAtbl->host_iocb_index: 0
DSAtbl->host_iocb_addr: 5d800
scratch_lsp: 0x0000000000000000
c8xx_iocb [ffffffff90010b00]:
1e00df80 0040007f 00000000 00000000
00000000 0005df60 00000000 0005df68
Pre-DSP script dump [ffffffff900101a0]:
90010264 c1000020 0005df40 90010b00
f1340004 00000004 74364000 00000000
Script dump [ffffffff900101c0]:
98040000 0000000f f1700004 0000000c
e0720001 900101e2 78492f00 00000000
NCR chip register dump for: 0x4002002
00: SCNTL3: bf SCNTL2: 00 SCNTL1: 00 SCNTL0: da
04: GPREG: 0f SDID: 0f SXFER: 1f SCID: 47
08: SBCL: 00 SSID: 80 SOCL: 00 SFBR: 40
0c: SSTAT2: 02 SSTAT1: 0f SSTAT0: 00 DSTAT: 80
10: DSA: 90010b00
14: MBOX1: 00 MBOX0: 00 ISTAT1: 00 ISTAT: 02
1c: TEMP: 90010ac8
24: DCMDDBC: 98040000
28: DNAD: 900101c0
2c: DSP: 900101c8
30: DSPS: 0000000f
34: SCRATCHA: 0040007f
38: DCNTL: a1 DWT: 00 DIEN: 7f DMODE: 4c
3c: ADDER: 900101d7
40: SIST1: 10 SIST0: 00 SIEN1: 97 SIEN0: 8f
44: GPCNTL: 27 MACNTL: 00 SWIDE: 00 SLPAR: 00
48: RESPID1: 00 RESPID0: 80 STIME1: 00 STIME0: fc
4c: STEST3: 80 STEST2: 00 STEST1: 0c STEST0: 76
50: RESV50: 00 RESV51: c0 SIDL1: 00 SIDL0: 00
54: CCNTL1: 01 CCNTL0: 01 SODL1: 00 SODL0: 00
58: RESV58: 00 RESV59: 00 SBDL1: 00 SBDL0: 00
5c: SCRATCHB: 000f0000
60: SCRATCHC: c0ffffff
64: SCRATCHD: 0005df7c
68: SCRATCHE: 90010c00
6c: SCRATCHF: 00058000
70: SCRATCHG: bf0f1f1e
74: SCRATCHH: 0005d600
78: SCRATCHI: 1901571f
7c: SCRATCHJ: 00000000
bc: SCNTL4: 00
PCI configuration register dump:
Command: 0157
Latency Timer: c0
Cache Line Size: 20

And how to find the actual location of the disk from ll /dev/dsk or /dev/rdsk ?

Thanks
Venkat

Re: Error in Syslog

Jeff Schussele — Mon, 01 May 2006 11:59:31 GMT

Hi Eswar,

Looks to me like a tape drive issue - indicated by the call of stape. Do an ioscan -H 0/1/1/1 & note whether a tape drive is down that path. It could simply be a power cycle on the drive or even a reseat. But it could also be a bad tape.

HTH,
Jeff

Re: Error in Syslog

rariasn — Tue, 02 May 2006 06:47:16 GMT

Hi Venkat,

# grep LVM /var/adm/syslog/syslog.log

and similar messages to:

LVM: vg[0]: pvnum=0 (dev_t=0x1c0c0000) is POWERFAILED.
LVM: PV 0 has been returned to vg[0]

Sample:

0x1c0c0000 --> c12t0d0

0x1c -> ext_bus
0c -> c12 (dec)
0 -> t0
0 -> d0
00 -> slice

# strings /etc/lvmtab|grep c12t0d0

--> vg00

rgs,

ran

Re: Error in Syslog

HGN — Tue, 02 May 2006 08:02:31 GMT

Hi

If you feel this issue is resolved you can close this thread and assign points.
Looks like you have not assigned any points 0 out of 89, people are spending their valuable time helping out and it will be a nice way to appreciarte with points.

Rgds

HGN

Re: Error in Syslog

Ajitkumar Rane — Tue, 02 May 2006 10:05:27 GMT

Venkateswar,

Well the path for the tape drive causing the error is already listed in the error.

SCSI: Reset detected -- lbolt: 210532262, bus: 3 path: 0/1/1/1
0/1/1/1.0 tgt
0/1/1/1.0.0 stape
xdr_opaque: decode FAILED

xdr_opaque() translates between fixed size opaque data and its external epresentation. The parameter cp is the address of the opaque object, and cnt is its size in bytes. This routine returns TRUE if it succeeds, FALSE otherwise.

Seems like your tape library isn able to communicate.

/may be check if the library passes a self test, see if uma commands work, else call the vendor to take a look.

Rgds,

Ajit

Re: Error in Syslog

Venkat_11 — Mon, 15 May 2006 13:52:24 GMT

Thanks for all who replied.