Problem with rp3410 and bus scsci

[David_711]

Hi,
I have a rp3410 server conected to a scsi ds2300 unit.
Please, Somebody can help me, i see sometimes this error on my hpux server:
Is a problem with mys disk?
I patched this until supportplus of december of 2006.
Please help, thanks
>---------- End Event Monitoring Service Event Notification ----------<

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

Notification Time: Thu Sep 6 18:24:24 2007

maestro0 sent Event Monitor notification information:

/storage/events/disks/default/0_4_1_1.0.0 is >= 1.
Its current value is MAJORWARNING(3).



Event data from monitor:

Event Time..........: Thu Sep 6 18:24:24 2007
Severity............: MAJORWARNING
Monitor.............: disk_em
Event #.............: 100091
System..............: maestro0

Summary:
Disk at hardware path 0/4/1/1.0.0 : Software configuration error


Description of Error:

The device is in a condition where it requires action on the part of the
device driver or a human operator.

Probable Cause / Recommended Action:

The device has been reset by a Bus Device Reset message, a hard reset
condition, or a power-on reset.

If this is the case, no action is necessary.

Alternatively, a removable medium has been loaded or replaced.

If this is the case, no action is necessary.

Alternatively, the mode parameters, microcode, or inquiry data for the
device have been changed.

If this is the case, no action is necessary.

Alternatively, the installed version of the device driver does not match
that of the installed version of HP-UX. Install the correct version of the
driver.

Additional Event Data:
System IP Address...: 157.100.92.86
Event Id............: 0x46e08c2800000002
Monitor Version.....: B.01.01
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_disk_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x46e08c2800000001
Additional System Data:
System Model Number.............: 9000/800/rp3410
OS Version......................: B.11.11
STM Version.....................: A.47.00
EMS Version.....................: A.04.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100091

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...: 0/4/1/1.0.0
Device Class...........: Disk
Inquiry Vendor ID......: HP 36.4G
Inquiry Product ID.....: MAP3367NC
Firmware Version.......: HPC6
Serial Number..........: KS049228 0431

Product/Device Identification Information:

Logger ID.........: sdisk
Product Identifier: SCSI Disk
Product Qualifier.: HP36.4GMAP3367NC
SCSI Target ID....: 0x00
SCSI LUN..........: 0x00

I/O Log Event Data:

Driver Status Code..................: 0x0000000B
Length of Logged Hardware Status....: 36 bytes.
Offset to Logged Manager Information: 40 bytes.
Length of Logged Manager Information: 34 bytes.

Hardware Status:

Raw H/W Status:
0x0000: 00 00 00 02 70 00 06 00 00 00 00 28 00 00 00 00
0x0010: 29 02 00 00 00 00 00 2A 00 67 06 01 00 00 00 00
0x0020: 00 00 00 00

SCSI Status...: CHECK CONDITION (0x02)
Indicates that a contingent allegiance condition has occurred. Any
error, exception, or abnormal condition that causes sense data to be
set will produce the CHECK CONDITION status.

SCSI Sense Data:

Undecoded Sense Data:
0x0000: 70 00 06 00 00 00 00 28 00 00 00 00 29 02 00 00
0x0010: 00 00 00 2A 00 67 06 01 00 00 00 00 00 00 00 00

SCSI Sense Data Fields:
Error Code : 0x70
Segment Number : 0x00
Bit Fields:
Filemark : 0
End-of-Medium : 0
Incorrect Length Indicator : 0
Sense Key : 0x06
Information Field Valid : FALSE
Information Field : 0x00000000
Additional Sense Length : 40
Command Specific : 0x00000000
Additional Sense Code : 0x29
Additional Sense Qualifier : 0x02
Field Replaceable Unit : 0x00
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x00 0x00 0x00

Sense Key 0x06, UNIT ATTENTION, indicates that the target has been
reset by a BUS DEVICE RESET message, a hard reset condition, or by a
power-on reset. If not a reset, then one of the following may have
occurred.
1. A removable medium may have been changed.
2. The mode parameters in effect for this initiator have been
changed by another initiator.
3. The version or level of microcode has been changed.
4. Tagged commands queued for this initiator were cleared by
another initiator.
5. INQUIRY data has been changed.
6. The mode parameters in effect for this initiator have been
restored from non-volatile memory.
7. A change in the condition of a synchronized spindle.
8. Any other event that requires the attention of the initiator.

The combination of Additional Sense Code and Sense Qualifier (0x2902)
indicates: SCSI bus reset occurred.

SCSI Command Data Block:

Command Data Block Contents:
0x0000: 2A 00 00 00 05 70 00 00 04 00

Command Data Block Fields (10-byte fmt):
Command Operation Code...(0x2A)..: WRITE
Logical Unit Number..............: 0
DPO Bit..........................: 0
FUA Bit..........................: 0
Relative Address Bit.............: 0
Logical Block Address............: 1392 (0x00000570)
Transfer Length..................: 4 (0x0004)

Manager-Specific Data Fields:
Request ID.............: 0x0507910B
Data Residue...........: 0x00000800
CDB status.............: 0x00000002
Sense Status...........: 0x00000000
Bus ID.................: 0x05
Target ID..............: 0x00
LUN ID.................: 0x00
Sense Data Length......: 0x20
Q Tag..................: 0x76
Retry Count............: 0


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

[Sandman!]

See if there are any lbolt errors in the syslog and post them here viz.,

# grep lbolt /var/adm/syslog/syslog.log

[Ed D]

Hi,

I had a similar problem with a 3440 and a scsi attached DAT72 tape drive. It would work intermitently, it would mostly work with tar commands but had trouble with ignite recovery commands. Went through a lot with HP - replaced drive, re-installed drivers and patches. Turned out to be a scsi cable, we replaced the external cable with and internal type one and it now works perfectly.
Might be worth trying different cable or different type cable.
Ed