EMS issue

[hpuxhelp]

Can some1 help me to interprete this message below?
Jul 22 16:26:53 vmunix: SCSI: Resetting SCSI -- lbolt: 36112631, bus: 1
Jul 22 16:26:53 vmunix:
Jul 22 16:26:53 vmunix: SCSI: Reset detected -- lbolt: 36112631, bus: 1
Jul 22 16:26:50 syslog: FNSOD:SCSI interface returns SCTL_INCOMPLETE.
Jul 22 16:26:55 syslog: FNSOD:SCSI interface returns S_BUSY.
Jul 22 16:26:55 vmunix: SCSI: asense data-done -- lbolt: 36113133, dev: c
b012000, tag: 7c
Jul 22 16:27:18 vmunix: SCSI: asense data-done -- lbolt: 36113152, dev: c
b012000, tag: 7c
Jul 22 16:27:18 vmunix:
Jul 22 16:27:18 vmunix: SCSI: Unhandled phase mismatch -- lbolt: 36113171
, dev: cb012000
Jul 22 16:27:18 vmunix: lbp->state: 2020
Jul 22 16:27:18 vmunix: lbp->offset: ffffffff
Jul 22 16:27:18 vmunix: lbp->uPhysScript: 500000
Jul 22 16:27:18 vmunix: From most recent interrupt:
Jul 22 16:27:18 h vmunix: ISTAT: 2a, SIST0: c0, SIST1: 00, DSTAT:
00, DSPS: 005003c8

----Someone has suggested that I should disable EMS due to this error
Jul 22 16:26:50 syslog: FNSOD:SCSI interface returns SCTL_INCOMPLETE.
Jul 22 16:26:55 syslog: FNSOD:SCSI interface returns S_BUSY.

Can you help me to reason this out>???

[Eugeny Brychkov]

Steven,
PHKL_27003, device=c1t2d0 - what's this?
Eugeny

[Shannon Petry]

This error does not look like an EMS issue, but a bad SCSI device or non/badly terminated device.

Make sure that your device chain is terminated with the proper terminator, not over sized (too many devices, cable length in chain should be less than 3M)

This can be cause by a drive about to fail also, but not quite as common.

Regards,
Shannon

[hpuxhelp]

I ugene,
where did you get taht information???

[Paul Sperry]

check your cabling and termination

[S.K. Chan]

The "lbolt" message in general means the driver is not able to complete the operation or IO in the given time. The device cb012000 (cb in decimel is 203 ie the sctl driver .. from lsdev command), so I'm guessing this is probably a tape device of some sort autoloader or autochanger (on c1t2d0). You should not disable the EMS yet until you know for sure the hardware having problem commnunicating with EMS.

[Eugeny Brychkov]

It's secret :o)
The general idea is first to check that you have system well patched with Diags, GR and HWE patch bundles from the same CD revision, and check for hardware issues (as Shannon mentioned): cables, terminators....
BTW, what's this device (attach 'ioscan -fn')? If you have multiple devices on the bus (c1) and only this shows such behavior maybe device is misbehaving?
Eugeny

[hpuxhelp]

ioscan -funC disk doesn't who that device
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
disk 0 8/0.0.0 sdisk CLAIMED DEVICE DEC HSZ70
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 8/0.0.1 sdisk NO_HW DEVICE DEC HSZ70
/dev/dsk/c0t0d1 /dev/rdsk/c0t0d1
disk 2 8/0.0.2 sdisk NO_HW DEVICE DEC HSZ70
/dev/dsk/c0t0d2 /dev/rdsk/c0t0d2
disk 3 8/0.0.3 sdisk NO_HW DEVICE DEC HSZ70
/dev/dsk/c0t0d3 /dev/rdsk/c0t0d3
disk 4 8/0.0.4 sdisk CLAIMED DEVICE DEC HSZ70
/dev/dsk/c0t0d4 /dev/rdsk/c0t0d4
disk 5 8/0.0.5 sdisk NO_HW DEVICE DEC HSZ70
/dev/dsk/c0t0d5 /dev/rdsk/c0t0d5
disk 6 8/0.0.6 sdisk NO_HW DEVICE DEC HSZ70
/dev/dsk/c0t0d6 /dev/rdsk/c0t0d6
disk 45 8/0.0.7 sdisk CLAIMED DEVICE DEC HSZ70
/dev/dsk/c0t0d7 /dev/rdsk/c0t0d7
disk 16 8/0.1.0 sdisk NO_HW DEVICE DEC HSZ70
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
disk 26 8/0.1.1 sdisk NO_HW DEVICE DEC HSZ70
/dev/dsk/c0t1d1 /dev/rdsk/c0t1d1
disk 32 8/0.1.2 sdisk NO_HW DEVICE DEC HSZ70

[S.K. Chan]

What about ..
# ioscan -fnC ctl
instead ?

[hpuxhelp]

disk 44 8/4.2.0 sdisk CLAIMED DEVICE LMS LD 6100SER.
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0

[Eugeny Brychkov]

Hey Steven,
to allow us to help you should provide exactly all the information asked, not little pieces.
This device looks like
LMS LD 6100SER. 11.2 GB Plasmon LMS WORM drive
Eugeny

[hpuxhelp]

how do I remove those no HW device...i tried rmsf -H ...
and it doesnt' work

[Eugeny Brychkov]

These NO_HW devices are not those we troubleshooting right now (reboot will solve this issue). Where're 'ioscan -fn' and 'ioscan -fnC ctl' asked for?
Eugeny

[S.K. Chan]

So it's an optical drive then ..have you installed the latest "SCSI IO Subsystem Cumulative Patch" on your system. If I am not mistaken this could be a patch issue.

[hpuxhelp]

hi, it is the optical drive...how do I check if the patch is installed on the ssytem???

[hpuxhelp]

ioscan -fnC ctl
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
ctl 0 8/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ctl 1 8/4.6.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t6d0
ctl 2 8/8.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ctl 3 8/12.6.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t6d0
ctl 4 10/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c4t7d0
ctl 5 10/12/5.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c6t7d0

[S.K. Chan · Accepted solution]

Depending on your OS .. for 11i the patch you need is PHKL_28096. For 11.00 it's PHKL_28131. Double check it in ITRC and make sure all dependency patches are loaded as well (if any). To check for existing patch for example ..
# swlist -l patch | grep PHKL_28096

[hpuxhelp]

the O/S is 10.20

[S.K. Chan]

That would be ..
PHKL_26398 (s800 10.20 SCSI cumulative patch)

[hpuxhelp]

Thank you all for all of your helps.... You guys are always quick on helping us out...thank you