V-class error message

[Sachin Patel]

Hi All,
I have following error message in my syslog

Dec 3 08:37:10 cousteau vmunix: SCSI: Target detected parity error -- lbolt: 7664541, dev: bc069000
Dec 3 08:37:11 cousteau vmunix: SCSI: Resetting SCSI -- lbolt: 7664641, bus: 6
Dec 3 08:37:11 cousteau vmunix: SCSI: Reset detected -- lbolt: 7664641, bus: 6
Dec 3 08:37:11 cousteau vmunix:
Dec 3 08:37:10 cousteau vmunix: scb->cdb: 12 00 00 00 80 00
Dec 3 08:37:12 cousteau above message repeats 8 times
Dec 3 08:37:11 cousteau vmunix: SCSI: bp: 0000000061081c00
Dec 3 08:37:11 cousteau vmunix: dev: bc069000
Dec 3 08:37:11 cousteau vmunix: cdb: 12 00 00 00 80 00
Dec 3 08:37:11 cousteau vmunix: residual: 80
Dec 3 08:37:11 cousteau vmunix: status: (400) None -- Incomplete
Dec 3 08:37:16 cousteau vmunix: SCSI: Target detected parity error -- lbolt: 7665141, dev: bc069000

We have number of internal disk. They all are not accessable currently.
We think that one of the disk is bad.
How do we find out the I/O path of which disk is bad?

Sachin

[Rainer von Bongartz]

Sachin,

The following document describes how to figure out the disk

http://europe-support.external.hp.com/cki/bin/doc.pl/sid=7fb2a6e11c140d1e77/screen=ckiDisplayDocument?docId=200000048373145

Regards
Rainer

[Sridhar Bhaskarla]

One easy way to find the disk is to do a

ll /dev/dsk|grep 069000

Ignore bc

This could mostly be c6t9d0.

-Sri

[Sanjay_6]

Hi Sachin,

Like sridhar said,

The disk you should be looking for is c6t9d0

Hope this helps.

Regds

[Roger Baptiste · Accepted solution]

<>


The first two characters of the dev gives you a clue on what the device is :
bc (hex) -> 188 (decimal)
-> this is the major number of the device having the problem. in this instance, rdsk.

The remaining digits in the dev entry points to the specific device;
Next controller c0; target.-t6
and then d9.

That makes this /dev/rdsk/c0t6d9

Check what this device is and take it from there.

HTH
raj

[Deshpande Prashant]

Sachin

I think the device should be c0t6d9 .

Thanks.
Prashant.

[Sanjay_6]

Hi Sachin,

Rainer link should have helped you, This is the same link, only it refers to us-support in place of europe-support

http://us-support2.external.hp.com/cki/bin/doc.pl/sid=d97e3b950b70d896ba/screen=ckiDisplayDocument?docId=200000048373145

Hope this helps.

Regds

[Sachin Patel]

Hi All,
I am working on it. I will let you know how it goes.
Looks like it is same disk as you guys mention.

Sachin

[Sachin Patel]

Rainer
That link never took me to the doc.
Sanjay your link work

Thanks All of your for your help

Sachin Patel

[Sanjay_6]

hi Sachin,

If you wanted to use Rainer's link, you have to replace "europe-support" in that link with "us-support" since you are accessing the hp US itrc site. That link would have worked if your login id was on europe site.

Thanks
Sanjay

[Rainer von Bongartz]

What can we learn from this 'us-support' and 'europe-support'
mess ??

I think there should be one !!! support site for all of us .
Don't you aggree guys.

Regards
Rainer

[Sachin Patel]

Thanks you guys. My problem is solved. That was the same disk c6t9d0. replace the disk and
pvcreate /dev/rdsk/c6t9d0
vgimport, vgchange and fsck everything is back to normal.

Rainer I am agree with you we need one site.

Sachin