SCSI lbolt errors

[MikeL_4]

I am receiving SCSI lbolt errors in syslog.log:

Dec 8 10:53:22 odcign1 vmunix: SCSI: -- lbolt: 960015433, dev: 1f048000
Dec 8 10:53:22 odcign1 vmunix: lbolt_at_timeout: 0, lbolt_at_start: 0
Dec 8 10:53:23 odcign1 vmunix: SCSI: Resetting SCSI -- lbolt: 960015533, bus: 4 path: 0/4/1/0
Dec 8 10:53:23 odcign1 vmunix: SCSI: Reset detected -- lbolt: 960015533, bus: 4 path: 0/4/1/0

and associated EMS messages:

Event Monitor notification information:

/storage/events/disks/default/0_4_1_0.10.0 is >= 3.
Its current value is MAJORWARNING(3).



Event data from monitor:

Event Time..........: Sat Dec 6 17:04:09 2008
Severity............: MAJORWARNING
Monitor.............: disk_em
Event #.............: 100091
System..............: odcign1

Summary:
Disk at hardware path 0/4/1/0.10.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...: 155.90.142.32
Event Id............: 0x493af6d900000004
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):
0x493af6d800000003
Additional System Data:
System Model Number.............: 9000/800/rp3410
OS Version......................: B.11.11
STM Version.....................: A.59.00
EMS Version.....................: A.04.20
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/0.10.0
Device Class...........: Disk
Inquiry Vendor ID......: ModusLnk
Inquiry Product ID.....: MXJ3147SC800600X
Firmware Version.......: HPB2
Serial Number..........: ML00019855

Product/Device Identification Information:

Logger ID.........: sdisk
Product Identifier: SCSI Disk
Product Qualifier.: ModusLnkMXJ3147SC800600X
SCSI Target ID....: 0x0A
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 0A 28 00 99 01 80 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 0A 28 00 99 01 80 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: 28 00 10 A2 74 00 00 01 F0 00

Command Data Block Fields (10-byte fmt):
Command Operation Code...(0x28)..: READ
Logical Unit Number..............: 0
DPO Bit..........................: 0
FUA Bit..........................: 0
Relative Address Bit.............: 0
Logical Block Address............: 279081984 (0x10A27400)
Transfer Length..................: 496 (0x01F0)

Manager-Specific Data Fields:
Request ID.............: 0x04EE3874
Data Residue...........: 0x0003E000
CDB status.............: 0x00000002
Sense Status...........: 0x00000000
Bus ID.................: 0x04
Target ID..............: 0x0A
LUN ID.................: 0x00
Sense Data Length......: 0x20
Q Tag..................: 0x7E
Retry Count............: 1


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

[john123]

A good reference here..

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=219110

[Steven E. Protter · Accepted solution]

Shalom,

Two sources of these kind of message.

Benign: Recent replacement or pull on a hot swap disk. dmesg - will clear it as will a boot.

Problem: Actual disk or scsi controller failure.

The second cause requires correction, usually replacement of the disk in question.

http://docs.hp.com/en/5992-3385/ch04s08.html

http://docs.hp.com/en/5992-3385/ch04s08.html#lvm.trouble.nmnb

SEP

[MikeL_4]

Thanks