SCSI: Parity Error

[Nuria]

Hi all ,
I saw an error message in the log server , do you Know what can it be?? Thanks a lot!!!


SCSI: Resetting SCSI -- lbolt: 288379755, bus: 0
Aug 27 07:12:56 cchpu004 vmunix: SCSI: Reset detected -- lbolt: 288379755, bus: 0
Aug 27 07:13:06 cchpu004 vmunix: SCSI: Parity Error -- lbolt: 288380755, dev: 1f008000
Aug 27 07:13:06 cchpu004 vmunix: lbp->state: 4060
Aug 27 07:13:06 cchpu004 vmunix: lbp->offset: ffffffff
Aug 27 07:13:06 cchpu004 vmunix: lbp->uPhysScript: 8c100000
Aug 27 07:13:06 cchpu004 vmunix: From most recent interrupt:
Aug 27 07:13:06 cchpu004 vmunix: ISTAT: 0a, SIST0: 41, SIST1: 00, DSTAT: 80, DSPS: 045d0000
Aug 27 07:13:06 cchpu004 vmunix: lsp: 0000000042881700
Aug 27 07:13:06 cchpu004 vmunix: bp->b_dev: 1f008000
Aug 27 07:13:06 cchpu004 vmunix: scb->io_id: 74e927
Aug 27 07:13:06 cchpu004 vmunix: scb->cdb: 28 00 00 00 00 10 00 00 04 00
Aug 27 07:13:06 cchpu004 vmunix: lbolt_at_timeout: 0, lbolt_at_start: 0
Aug 27 07:13:06 cchpu004 vmunix: lsp->state: 5
Aug 27 07:13:06 cchpu004 vmunix: lbp->owner: 0000000000000000
Aug 27 07:13:06 cchpu004 vmunix: scratch_lsp: 0000000042881700
Aug 27 07:13:06 cchpu004 vmunix: Script dump [0000000044001000]:
Aug 27 07:13:06 cchpu004 vmunix: 09000800 045d0000 e25c0004 8c1007d8
Aug 27 07:13:06 cchpu004 vmunix: 80080000 8c100090 e25c0004 8c1007d8
Aug 27 07:13:07 cchpu004 vmunix: SCSI: Resetting SCSI -- lbolt: 288380855, bus: 0
Aug 27 07:13:07 cchpu004 vmunix: SCSI: Reset detected -- lbolt: 288380855, bus: 0
Aug 27 07:13:17 cchpu004 vmunix: LVM: Recovered Path (device 0x1f008000) to PV 0 in VG 0.
Aug 27 07:13:17 cchpu004 vmunix: LVM: Restored PV 0 to VG 0.

[Simone Benzi_1]

Ciao,

These errors can be due to:

1. The IO timeout setting for the physical disk being set too low
2. A problem with the SCSI connector for that device
3. Not having the latest SCSI patches installed

Regards,

Simone

[Nuria]

Ciao Simone ,
Thanks for the quick response , I will continue searching for this....
Take care and regards!
Nuria

[Kent Ostby]

Above you will note this line:

bp->b_dev: 1f008000

The first two digits are the major number while the last six are the minor number.

Do the following to see which disk we're trying to talk to:

ll /dev/dsk | grep 08000

This will likely bring back c0t8d0 and that is probably the disk that we are trying to talk to when we get the error.

Here's a couple of possible causes that you could fix on your own:

1) If you have made any changes on this bus of late, I would shut the box down when conveinent and check your cables and terminators.

2) You could use "logtool" within STM to see if it is reporting I/O errors on the card or disk.

There are many possible causes for SCSI issues so if the above doesnt fix it, you probably want to contact HP hardware support to troubleshoot the errors.

Best regards,

Kent Ostby

[Sarjerao]

I am also facing similar type of problem.
help me to find out problematic device.
for your reference pl see the syslog
vmunix: SCSI: bp: 0000000052a07c00
May 22 00:13:48 tr vmunix:
May 22 00:13:48 tr vmunix: SCSI: bp: 0000000052a07c00
May 22 00:13:48 tr vmunix: dev: cd020000
May 22 00:13:48 tr vmunix: cdb: 12 00 00 00 80 00
May 22 00:13:48 tr vmunix: residual: 80
May 22 00:13:48 tr vmunix: status: (400) None -- Incomplete
May 22 10:12:51 tr vmunix:
May 22 10:12:51 tr vmunix: SCSI: bp: 0000000048fc5000
May 22 10:12:51 uma vmunix: dev: cd020000
May 22 10:12:51 uma vmunix: cdb: 12 00 00 00 80 00
May 22 10:12:51 uma vmunix: residual: 80
May 22 10:12:51 uma vmunix: status: (400) None -- Incomplete