1832616 Members
3191 Online
110043 Solutions
New Discussion

Re: SCSI lbolt error

 
SOLVED
Go to solution
Rick Garland
Honored Contributor

SCSI lbolt error

Hi all:

Got HPUX 11.11 on L1000 that is overseas. Getting these messages in syslog.

This is the sctl driver (lsdev 203)

vmunix: SCSI: Target detected parity error -- lbolt: 27723,
dev: cb012002

The ctl devices on the system are /dev/rscsi/c[1-3]t7d0.

What gives?

Thanks
9 REPLIES 9
Luk Vandenbussche
Honored Contributor

Re: SCSI lbolt error

Rick,

This is the way to calculate it

dev: cb012002

major device number: CB (hex) = 203 (decimal)
controller: 01
target: 2
device: 0

/dev/dsk/c1t2d0 has a problem
Rick Garland
Honored Contributor

Re: SCSI lbolt error

HEX cb is 203 decimal. lsdev 203 is the sctl driver.

There is no device c1t2d0 - CLAIMED or UNCLAIMED

System has not been rebooted for 30+ days andthese are recent messages
Sandman!
Honored Contributor

Re: SCSI lbolt error

More than likely it is the SCSI controller attached to /dev/dsk/c1t2d0s2 since the major number of the device "cb" points to one. Take a look at the TKB doc below.

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000080065993
Rick Garland
Honored Contributor

Re: SCSI lbolt error

There is no device c1t2d0 - CLAIMED or UNCLAIMED.

Steven E. Protter
Exalted Contributor
Solution

Re: SCSI lbolt error

Shalom Rick,

Bad disk or a recent hot swap was not followed by a dmesg reset.

dmesg -

Wait 15 minutes

If the message returns its realy a bad disk. A controller or drive cage can cause the same problem and is much harder to diagnose and convince HP hardware what part actually went bad.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Sandman!
Honored Contributor

Re: SCSI lbolt error

Could you post the output of the following:

# ioscan -funC ext_bus
# ioscan -funC ctl

~thanks
Rick Garland
Honored Contributor

Re: SCSI lbolt error

Here are the ioscans as requested.
I also did 'ioscan -fn | grep c1t2' and there were no responses.


# ioscan -fnCctl
Class I H/W Path Driver S/W State H/W Type Description
====================================================================
ctl 0 0/0/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ctl 1 0/0/1/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
ctl 2 0/0/2/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ctl 3 0/0/2/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t7d0
# ioscan -fnCext_bus
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C896 Fast Wide LVD
ext_bus 1 0/0/1/1 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide Single-Ended
ext_bus 2 0/0/2/0 c720 CLAIMED INTERFACE SCSI C87x Ultra Wide Single-Ended
ext_bus 3 0/0/2/1 c720 CLAIMED INTERFACE SCSI C87x Ultra Wide Single-Ended
#
Sandman!
Honored Contributor

Re: SCSI lbolt error

Whatever is connected to...

ext_bus 1 0/0/1/1 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide

...needs to be looked at. It may just be bad cables or bad/no SCSI termination.

Curious as to what does the following command return:

# ioscan -fnH 0/0/1/1.2.0

~hope it helps
Rick Garland
Honored Contributor

Re: SCSI lbolt error

Thanks all