Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

Syslog Error : vmunix: SCSI: Unexpected Disconnect -- lbolt: 313573669, dev: cb083002, io_id: 800006

Shalabh
Occasional Visitor

Syslog Error : vmunix: SCSI: Unexpected Disconnect -- lbolt: 313573669, dev: cb083002, io_id: 800006

I am working on a N Class HP 9000 Server with an FC60 disk array.
We keep getting these errors in syslog. Also in the amdsp, one of the disk 5:4 is not recognized, although there are no errors in amdsp, no rebuilding, no hot spare being used.
The sam gui shows a blank space in the FC60 trays display.

Syslog :
Apr 16 16:38:46 sp_PRD vmunix: SCSI: Unexpected Disconnect -- lbolt: 417814506, dev: cb083002, io_id: 80000ac
Apr 16 16:38:47 sp_PRD vmunix: SCSI: Unexpected Disconnect -- lbolt: 417814507, dev: cb083002, io_id: 80000ac
Apr 16 16:38:47 sp_PRD vmunix: SCSI: Unexpected Disconnect -- lbolt: 417814508, dev: cb083002, io_id: 80000ac
Apr 16 16:38:47 sp_PRD vmunix: SCSI: Unexpected Disconnect -- lbolt: 417814509, dev: cb083002, io_id: 80000ac
Apr 16 16:38:47 sp_PRD vmunix: SCSI: Unexpected Disconnect -- lbolt: 417814510, dev: cb083002, io_id: 80000ac
Apr 16 16:38:47 sp_PRD vmunix: SCSI: Unexpected Disconnect -- lbolt: 417814511, dev: cb083002, io_id: 80000ac
Apr

EMS [2829]: ------ EMS Event Notification ------ Value: "MAJORWARNING (3)" for Resource: "/storage/e
vents/disk_arrays/FC60/AM60Srvr" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/r
esmon/bin/resdata -R 185401351 -r /storage/events/disk_arrays/FC60/AM60Srvr -n 185401355 -a

Any ideas ?
4 REPLIES
Luk Vandenbussche
Honored Contributor

Re: Syslog Error : vmunix: SCSI: Unexpected Disconnect -- lbolt: 313573669, dev: cb083002, io_id: 800006

Have you executed

/opt/r
esmon/bin/resdata -R 185401351 -r /storage/events/disk_arrays/FC60/AM60Srvr -n 185401355 -a

The output of this command will point you to a website, which gives more info
Shalabh
Occasional Visitor

Re: Syslog Error : vmunix: SCSI: Unexpected Disconnect -- lbolt: 313573669, dev: cb083002, io_id: 800006

Yes, but the website still says same error.

/opt/resmon/bin/resdata -R 185401351 -r /storage/events/disk_arrays/FC60/AM60Srvr -n 185401363 -a

CURRENT MONITOR DATA:

Event Time..........: Thu Apr 19 05:50:41 2007
Severity............: MAJORWARNING
Monitor.............: fc60mon
Event #.............: 4
System..............: sp_PRD

Summary:
Disk Array at hardware path :
Array at hardware path Unknown, path Unknown: The computer can not connect to
the AM60Srvr.
The status on the disk array is not currently available.



Description of Error:


This event message is displayed when a connection cannot be made to
the AM60Srvr. The resource monitor will continue to attempt to
connect to the AM60Srvr at regular polling intervals. When the
AM60Srvr is restored, the connection will succeed and normal
operation will continue. Until the AM60Srvr is operating normally,
it is not possible to obtain the current status of any of the disk
arrays.


Probable Cause / Recommended Action:


Restart AM60Srvr, or if still running, stop and restart the AM60Srvr.

Possible Causes Include:
1. The AM60Srvr is not running.
2. The wrong version of the AM60Srvr is running.
3. The correct AM60Srvr is running, but is hung.

Additional Event Data:
System IP Address...: 10.39.141.11
Event Id............: 0x4626f52100000000
Monitor Version.....: B.01.02
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_fc60mon.clcfg
Client Configuration File Version...: A.01.01
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: 9000/800/N4000-55
EMS Version.....................: A.04.20
STM Version.....................: A.49.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/fc60mon.htm#4

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



Product/Device Data:

Logger ID.........: (not available/applicable)
Product Identifier: (not available/applicable)
Product Qualifier.: (not available/applicable)
SCSI Target ID....: (not available/applicable)
SCSI LUN..........: (not available/applicable)
Luk Vandenbussche
Honored Contributor

Re: Syslog Error : vmunix: SCSI: Unexpected Disconnect -- lbolt: 313573669, dev: cb083002, io_id: 800006

so, this is the solution HP proposes

Event 4

Severity: MAJOR_WARNING
Event Summary: Disk Array at hardware path : Array at hardware path 8/12.8.0.5.0.0.0, path 8/8.8.0.4.0.0.0: The computer can not connect to the AM60Srvr. The status on the disk array is not currently available.
Event Class: Array
Problem Description:
This event message is displayed when a connection cannot be made to the AM60Srvr (Array management daemon for FC60 Storage Array). The resource monitor will continue to attempt to connect to the AM60Srvr at regular polling intervals. When the AM60Srvr is restored, the connection will succeed and normal operation will continue. Until the AM60Srvr is operating normally, it is not possible to obtain the current status of any of the disk arrays.
Probable Cause / Recommended Action:
Possible Causes Include:

The AM60Srvr is not running.
The wrong version of the AM60Srvr is running.
The correct AM60Srvr is running, but is hung.
Recommended Action: Restart AM60Srvr, or if still running, stop and restart the AM60Srvr.

Restart AM60Srvr using the command /opt/hparray/bin/AM60Srvr, or if still running;
Stop (kill -9 pid; pid: process id of AM60Srvr) and restart the AM60Srvr.
Shalabh
Occasional Visitor

Re: Syslog Error : vmunix: SCSI: Unexpected Disconnect -- lbolt: 313573669, dev: cb083002, io_id: 800006

We've done that several times in the past few days. ArmSrvr still keeps stopping, gets restarted on its own at times, or we have to manually start it, and these errors keep accumulating in syslog.