Error at syslog

[Carme Torca]

Hi,
At the syslog of one server, today has appers this messages...
Does anyone knows whats is about it?

Thanks very much!!!
Carmen.
--------------------------

Oct 13 07:50:45 openview vmunix: SCSI: Third party detected bus hang -- lbolt: 22381517, bus: 0
Oct 13 07:50:45 openview vmunix: lbp->state: 6060
Oct 13 07:50:45 openview vmunix: lbp->offset: f8
Oct 13 07:50:45 openview vmunix: lbp->uPhysScript: f87be000
Oct 13 07:50:45 openview vmunix: From most recent interrupt:
Oct 13 07:50:45 openview vmunix: ISTAT: 22, SIST0: 04, SIST1: 00, DSTAT: 80, DSPS: 0000000a
Oct 13 07:50:45 openview vmunix: lsp: 0000000000000000
Oct 13 07:50:45 openview vmunix: lbp->owner: 000000004279de00
Oct 13 07:50:45 openview vmunix: bp->b_dev: cb000002
Oct 13 07:50:45 openview vmunix: scb->io_id: 114
Oct 13 07:50:45 openview vmunix: scb->cdb: 12 00 00 00 80 00
Oct 13 07:50:45 openview vmunix: lbolt_at_timeout: 22381516, lbolt_at_start: 22380016
Oct 13 07:50:45 openview vmunix: lsp->state: 85
Oct 13 07:50:47 openview vmunix: SCSI: Resetting SCSI -- lbolt: 22381617, bus: 0
Oct 13 07:50:47 openview vmunix: SCSI: Reset detected -- lbolt: 22381617, bus: 0
Oct 13 07:50:51 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382117, dev: cb000002, io_id: 114
Oct 13 07:50:51 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382118, dev: cb000002, io_id: 114
Oct 13 07:50:51 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382119, dev: cb000002, io_id: 114
Oct 13 07:50:51 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382120, dev: cb000002, io_id: 114
Oct 13 07:50:51 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382121, dev: cb000002, io_id: 114
Oct 13 07:50:51 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382121, dev: cb001002, io_id: 115
Oct 13 07:50:51 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382122, dev: cb001002, io_id: 115
Oct 13 07:50:51 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382123, dev: cb001002, io_id: 115
Oct 13 07:50:51 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382124, dev: cb001002, io_id: 115
Oct 13 07:50:51 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382125, dev: cb001002, io_id: 115
(....)
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382181, dev: cb00d002, io_id: 120
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382182, dev: cb00d002, io_id: 120
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382183, dev: cb00d002, io_id: 120
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382183, dev: cb00e002, io_id: 121
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382184, dev: cb00e002, io_id: 121
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382185, dev: cb00e002, io_id: 121
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382186, dev: cb00e002, io_id: 121
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382187, dev: cb00e002, io_id: 121
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382188, dev: cb00e002, io_id: 121
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382188, dev: cb00f002, io_id: 122
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382189, dev: cb00f002, io_id: 122
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382190, dev: cb00f002, io_id: 122
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382191, dev: cb00f002, io_id: 122
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382192, dev: cb00f002, io_id: 122
Oct 13 07:50:54 openview vmunix: SCSI: Unexpected Disconnect -- lbolt: 22382193, dev: cb00f002, io_id: 122
Oct 13 07:51:15 openview vmunix: SCSI: First party detected bus hang -- lbolt: 22384550, bus: 0
Oct 13 07:51:15 openview vmunix: lbp->state: 7060
Oct 13 07:51:15 openview vmunix: lbp->offset: f8
Oct 13 07:51:15 openview vmunix: lbp->uPhysScript: f87be000
Oct 13 07:51:15 openview vmunix: From most recent interrupt:
Oct 13 07:51:15 openview vmunix: ISTAT: 22, SIST0: 04, SIST1: 00, DSTAT: 80, DSPS: 0000000a
Oct 13 07:51:15 openview vmunix: lsp: 0000000000000000
Oct 13 07:51:15 openview vmunix: lbp->owner: 000000004279de00
Oct 13 07:51:15 openview vmunix: bp->b_dev: cb000002
Oct 13 07:51:15 openview vmunix: scb->io_id: 123
Oct 13 07:51:15 openview vmunix: scb->cdb: 12 00 00 00 80 00
Oct 13 07:51:15 openview vmunix: lbolt_at_timeout: 22384350, lbolt_at_start: 22382850
Oct 13 07:51:15 openview vmunix: lsp->state: 85
Oct 13 07:51:15 openview vmunix: scratch_lsp: 0000000000000000
Oct 13 07:51:15 openview vmunix: Pr

[Massimo Bianchi]

One of your disks or cable is dying.

Check from an ioscan output..

ioscan -fnCdisk

You will get a NO_HW at the /dev/dsk/c0t0d0

Massimo

[Steven E. Protter]

You have a bad disk most likely.

Try the attached script to help identify the culprit.

If you have recently swapped out a hot swap disk, this message will go away next boot.



SEP

[MANOJ SRIVASTAVA]

Hi Carmen


It looks as if cotodo has gone bad , please do a ioscan -fnC disk and check for the disks , a realtively simpler way is to do a diskinfo /dev/rdsk/c0t0d0 but sometimes this may not report the correct status , also since your system is up and working you can look for the vgdisplay -v out and check for the avaialbitly of all physical volumes in thjat volume group.


Manoj

[A. Clay Stephenson · Accepted solution]

The most important bit of data is the 'dev'. The first two hex digits identify the major devive number. The next two hex digits identify the instance or controller (The 'c' part); the next hex digit is the SCSI ID or target - the 't' part; the next hex digit identifies the LUN - the 'd' part and the remaining hex digits are driver specific.

e.g. cb00e002 cb(hex) = 203(decimal); lsdev indicates that 203 is 'sctl' the SCSI pass-thru driver. 00 - c0; e - te 0 - d0; the remaining digits are devive driver dependent.

You need to look for devives for sctl (203) that are c0ted0. Because another device decodes as c0tfd0, this looks like a problem on the c0 bus -- possibly cabling or termination or the controller itself.

[Sanjay_6]

Hi,

Looks like you are either having a disk timeout problem or a loose or incorrectly installed scsi terminator. Check the scsi cable terminators and see if that helps.

Hope this helps.

Regds