System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Help needed with SCSI Unexpected Disconnects

System Administration_2
Occasional Contributor

Help needed with SCSI Unexpected Disconnects

We have a HP 7410 system that we have attached a compellant Storage box to and are getting the following errors:

SCSI: Unexpected Disconnect -- lbolt: 197179, dev: cb022002, io_id: 2000050

We also see the below information in the event log. The compellant box seems to not be reporting any errors and we are unsure where to go from here.
Any help would be much appreciated.


>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Tue Oct 26 12:01:04 2010

db sent Event Monitor notification information:

/adapters/events/TL_adapter/1_0_2_0_0 is >= 1.
Its current value is INFORMATION(1).



Event data from monitor:

Event Time..........: Tue Oct 26 12:01:04 2010
Severity............: INFORMATION
Monitor.............: dm_TL_adapter
Event #.............: 39
System..............: bwaydb.bwaycorp.com

Summary:
Adapter at hardware path 1/0/2/0/0 : Target rejected ADISC


Description of Error:


lbolt value: 13788465

Target rejected ADISC
nport ID = 0x10b01


Probable Cause / Recommended Action:

The target device rejected a request to verify
its name and address after a loop initialization.
If a new device has been installed on the loop,
check that its address setting does not conflict
with that of any other device.
If a device has been replaced on the loop, use
the fcms utility's "replace_dsk" command to
notify the driver to allow a different name
at the previously used address.


Additional Event Data:
System IP Address...: 192.168.10.146
System IP Address...: 192.168.3.243
Event Id............: 0x4cc6fb4000000000
Monitor Version.....: B.01.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x4cc6fb4000000000
Additional System Data:
System Model Number.............: 9000/800/rp7410
OS Version......................: B.11.11
EMS Version.....................: A.03.20
STM Version.....................: A.34.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#39

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



Component Data:
Physical Device Path....: 1/0/2/0/0
Vendor Id...............: 0x0000103C
Serial Number(WWN)......: 50060B000010F688

I/O Log Event Data:

Driver Status Code..................: 0x00000027
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 61 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:
00000006 00D26531 00000001 00000001 00010B01 2F75782F 6B65726E 2F6B6973
752F544C 2F737263 2F636F6D 6D6F6E2F 7773696F 2F74645F 6465762E 63





>---------- End Event Monitoring Service Event Notification ----------<
2 REPLIES
Steven E. Protter
Exalted Contributor

Re: Help needed with SCSI Unexpected Disconnects

Shalom,

A device can be claimed and working and still present an lbolt error.

It could be due to a hot swap disk being changed out.

dmesg - or dmesg -c might clear it.

It could be due to a disk time out. The default is 30 seconds, but doesn't look like that here.

It could be due to a cable going bad or possibly it was accidentally unplugged.

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
System Administration_2
Occasional Contributor

Re: Help needed with SCSI Unexpected Disconnects

Another question I have is on the device in question.
We show dev: cb022002 I converted it but seems that it would be SCSI device 32 which doesn't exist. Do I have a bad conversion?