- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- What's this critical error message mean?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2004 08:18 PM
05-23-2004 08:18 PM
What's this critical error message mean?
Notification Time: Sun May 23 15:27:04 2004
L2000_cn sent Event Monitor notification information:
/storage/events/disks/default/0_7_0_1.9.0 is >= 3.
Its current value is CRITICAL(5).
Event data from monitor:
Event Time : Sun May 23 15:27:04 2004
Hostname : L2000_cn IP Address : 10.56.10.71
Event Id : 0x0040b0524800000000 Monitor : disk_em
Event # : 100091 Event Class : I/O
Severity : CRITICAL
Disk at hardware path 0/7/0/1.9.0 : Software configuration error
Associated OS error log entry id(s):
0x40b0524800000000
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100091
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.
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 Identification Information:
Logger ID.........: sdisk
Product Identifier: SCSI Disk
Product Qualifier.: SEAGATEST136403LC
SCSI Target ID....: 0x09
SCSI LUN..........: 0x00
I/O Log Event Data:
Driver Status Code..................: 0x0000007E
Length of Logged Hardware Status....: 22 bytes.
Offset to Logged Manager Information: 24 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 0A 00 00 00 00
0x0010: 29 02 02 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 0A 00 00 00 00 29 02 02 00
0x0010: 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 : 10
Command Specific : 0x00000000
Additional Sense Code : 0x29
Additional Sense Qualifier : 0x02
Field Replaceable Unit : 0x02
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.
SCSI Command Data Block:
Command Data Block Contents:
0x0000: 2A 00 00 6F 3A 90 00 00 10 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............: 7289488 (0x006F3A90)
Transfer Length..................: 16 (0x0010)
Manager-Specific Data Fields:
Request ID.............: 0x05C46668
Data Residue...........: 0x00002000
CDB status.............: 0x00000002
Sense Status...........: 0x00000000
Bus ID.................: 0x05
Target ID..............: 0x09
LUN ID.................: 0x00
Sense Data Length......: 0x12
Q Tag..................: 0x73
Retry Count............: 0
>---------- End Event Monitoring Service Event Notification ----------<
In the syslog contents I find the following message:
May 23 15:26:59 L2000_cn vmunix: SCSI: Resetting SCSI -- lbolt: 196686456, bus:
5
May 23 15:26:59 L2000_cn vmunix: SCSI: Reset detected -- lbolt: 196686456, bus:
5
and from May 1 this message shows several times each day.
But my application on the disk array is ok now
The attachment is the syslog file.
So I want to know what's the matter.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2004 08:38 PM
05-23-2004 08:38 PM
Re: What's this critical error message mean?
Check this hardware path. 0/7/0/1.9.0
# ioscan -fnkCdisk
# diskinfo /dev/rdsk/cxtydz
Is it still available ?
Regards,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2004 08:53 PM
05-23-2004 08:53 PM
Re: What's this critical error message mean?
This means the SCSI bus is constantly resetting as its being upset by "Disk at hardware path 0/7/0/1.9.0 : Software configuration error" as Robert suggested start checking the disk.
If you type lbolt in the search box at the top of the page you will find lots of threads to similar problems
:-) John.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2004 09:41 PM
05-23-2004 09:41 PM
Re: What's this critical error message mean?
# ioscan -fnkCdisk
disk 6 0/7/0/1.9.0 sdisk CLAIMED DEVICE SEAGATE ST136403LC
/dev/dsk/c5t9d0 /dev/rdsk/c5t9d0
# diskinfo /dev/rdsk/cxtydz
diskinfo /dev/rdsk/c5t9d0
SCSI describe of /dev/rdsk/c5t9d0:
vendor: SEAGATE
product id: ST136403LC
type: direct access
size: 35566480 Kbytes
bytes per sector: 512
Is the disk ok?
And I find another disk /dev/dsk/c5t8d0 has the same problem.
This server use SCSI line connected to Disk Array.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2004 09:45 PM
05-23-2004 09:45 PM
Re: What's this critical error message mean?
it is probably a scsi reset since the disk is now claimed. do this to confirm condition of disks:
# dd if=dev/rdsk/c5t9d0 of=/dev/null bs=256
break the above command after about 5 minutes, check if the input and output are the same. if same, it should be alright. do this for the other disk as well
regards.