topic Re: dmesg error help! in Operating System - HP-UX

dmesg error help!

rveri — Thu, 23 Mar 2006 02:55:59 GMT

Hi All ,

I got this in dmesg : please help!

SCSI: Unexpected Disconnect -- lbolt: 275943709, dev: cb04f002, io_id: 4000717
SCSI: Unexpected Disconnect -- lbolt: 275943710, dev: cb04f002, io_id: 4000717
SCSI: Unexpected Disconnect -- lbolt: 275943711, dev: cb04f002, io_id: 4000717
----------------------------------------

What does it mean and what needs to check,
Pls help.

Thanks.

Re: dmesg error help!

Muthukumar_5 — Thu, 23 Mar 2006 03:00:12 GMT

One of your disk is having problem.

# ioscan -fnC disk see NO_HW status disk for this problem.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=956715
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=232452

Refer this for more info.

--
Muthu

Re: dmesg error help!

rveri — Thu, 23 Mar 2006 03:09:07 GMT

Muthu ,
ioscan shows all the disks are in CLAIMED staus .

syslog messsage:
-----------
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943651, dev: cb042002, io_id: 400070b
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943651, dev: cb043002, io_id: 400070c
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943652, dev: cb043002, io_id: 400070c
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943653, dev: cb043002, io_id: 400070c
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943654, dev: cb043002, io_id: 400070c
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943655, dev: cb043002, io_id: 400070c
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943656, dev: cb043002, io_id: 400070c
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943656, dev: cb044002, io_id: 400070d
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943657, dev: cb044002, io_id: 400070d
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943658, dev: cb044002, io_id: 400070d
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943659, dev: cb044002, io_id: 400070d
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943660, dev: cb044002, io_id: 400070d
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943661, dev: cb044002, io_id: 400070d
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943661, dev: cb045002, io_id: 400070e
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943662, dev: cb045002, io_id: 400070e
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943663, dev: cb045002, io_id: 400070e
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943664, dev: cb045002, io_id: 400070e
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943665, dev: cb045002, io_id: 400070e
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943666, dev: cb045002, io_id: 400070e
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943666, dev: cb046002, io_id: 400070f
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943667, dev: cb046002, io_id: 400070f
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943668, dev: cb046002, io_id: 400070f
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943669, dev: cb046002, io_id: 400070f
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943670, dev: cb046002, io_id: 400070f
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943671, dev: cb046002, io_id: 400070f
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943671, dev: cb048002, io_id: 4000710
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943672, dev: cb048002, io_id: 4000710
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943673, dev: cb048002, io_id: 4000710
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943674, dev: cb048002, io_id: 4000710
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943675, dev: cb048002, io_id: 4000710
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943676, dev: cb048002, io_id: 4000710
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943676, dev: cb049002, io_id: 4000711
Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943677, dev: cb049002, io_id: 4000711
Mar 23 07:16:29 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943678, dev: cb049002, io_id: 4000711
Mar 23 07:16:29 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943679, dev: cb049002, io_id: 4000711
Mar 23 07:16:29 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943680, dev: cb049002, io_id: 4000711
Mar 23 07:16:29 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943681, dev: cb049002, io_id: 4000711
Mar 23 07:16:29 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943681, dev: cb04a002, io_id: 4000712
Mar 23 07:16:29 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943682, dev: cb04a002, io_id: 4000712
Mar 23 07:16:29 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943683, dev: cb04a002, io_id: 4000712
Mar 23 07:16:29 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943684, dev: cb04a002, io_id: 4000712
Mar 23 07:16:29 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943685, dev: cb04a002, io_id: 4000712
Mar 23 07:16:29 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943686, dev: cb04a002, io_id: 4000712
------------------------------------------

And the syslog shows many numbers of in dev: entry. at least 5 , 6 , and expecting that many disk will not be bad at a time.

Any idea!
thanks.

Re: dmesg error help!

Indira Aramandla — Thu, 23 Mar 2006 03:10:15 GMT

Hi rveri,

lbolt errors caused by badly connected cables on the external scsi device chains. Do an ioscan as mentioned above and if the ioscan results in NO_HW status disk. Then log a harware call with HP and they will ask you to run cstm (Support Tool Manager) commands ans send them the output for analysis.

Based on the analysis they will advice you on the disk replacement (if found stale) or check the cable connections.

Indira A

Re: dmesg error help!

Arunvijai_4 — Thu, 23 Mar 2006 03:14:16 GMT

Hi,

"lbolt" when you have bad connection or lose connection between disks. Check your cables are coubled properly.

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000079990759
http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000079991503

-Arun

Re: dmesg error help!

Muthukumar_5 — Thu, 23 Mar 2006 03:14:30 GMT

Use attached ACS script to find the problem making disk.

# chmod u+x script
# ./script

will give that.

--
Muthu

Re: dmesg error help!

RAC_1 — Thu, 23 Mar 2006 03:14:59 GMT

lbolts errors could be on account of many things.
Loose cables/connectors
Terminators
Patches-particularly scsi patches.

Check which device is it.
ll -R | grep 042002

Then check device with STM.

Re: dmesg error help!

Indira Aramandla — Thu, 23 Mar 2006 03:27:16 GMT

Hi rveri,

Mar 23 07:16:28 server3 vmunix: SCSI: Unexpected Disconnect -- lbolt: 275943651, dev: cb042002, io_id: 400070b

Could be a cable connection. here is the recode of your device "cb042002"

cb043002 decodes to
cb --> Major device 203
04 --> c4
3 --> t3
0 --> d0
02 --> driver specific.

Check with lsdev (llist device drivers in the system) to make sure that major device 203
see what is on HW path c4t3d0.

IA

Re: dmesg error help!

Muthukumar_5 — Thu, 23 Mar 2006 03:33:30 GMT

There is mailx lines in ACS script. Try to remove and simply put as, cat $dfile is enough there for that four line.

--
Muthu