- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Monitor event notification mail message
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
Discussions
Discussions
Forums
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
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
тАО01-11-2012 11:12 PM
тАО01-11-2012 11:12 PM
Hello,
I received a mail message on my HP-UX B.10.20 (see below).
Please let me know what exactly does it say? and what should I do in order to solve the issue.
From root Wed Jan 11 12:31:43 GMT 2012
Received: (from root@localhost) by hmb5.sol8.com (8.9.3 (PHNE_18979)/8.7.1) id MAA00874; Wed, 11 Jan 2012 12:31:43 GMT
Date: Wed, 11 Jan 2012 12:31:43 GMT
Message-Id: <201201111231.MAA00874@hmb5.sol8.com>
To: root
From: root@hmb5
Subject: hmb5: Event Monitor Notification
Content-Length: 4889
Status: RO
>------------ Event Monitoring Service Event Notification ------------<
Notification Time: Wed Jan 11 12:31:42 2012
hmb5 sent Event Monitor notification information:
/storage/events/disks/default/10_0_15_1.6.0 is >= 3.
Its current value is CRITICAL(5).
Event data from monitor:
Event Time : Wed Jan 11 12:31:41 2012
Hostname : hmb5
Event Id : 0x004f0d812d00000000 Monitor : disk_em
Event # : 100037 Event Class : I/O
Severity : CRITICAL
Disk at hardware path 10/0/15/1.6.0 : Media failure
Associated OS error log entry id(s):
0x4f0d812b00000000
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100037
Description of Error:
The device was unsuccessful in reading or writing data for the current I/O
request due to an error on the medium. The data could not be recovered.
Probable Cause / Recommended Action:
Reformatting the medium may fix the problem.
Alternatively, the medium in the device is flawed. If the medium is
removable, replace the medium with a fresh one.
Alternatively, if the medium is not removable, the device has experienced
a hardware failure. Repair or replace the device, as necessary.
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.: QUANTUMAtlas4-9LVD
SCSI Target ID....: 0x06
SCSI LUN..........: 0x00
I/O Log Event Information:
Driver Status Code..................: 0x0000007C
Length of Logged Hardware Status....: 22 bytes.
Offset to Logged Manager Information: 24 bytes.
Length of Logged Manager Information: 44 bytes.
Hardware Status:
Raw H/W Status:
0x0000: 00 00 00 02 F0 00 03 00 8E 80 60 0A 08 8A 18 5A
0x0010: 11 00 00 80 00 2E
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: F0 00 03 00 8E 80 60 0A 08 8A 18 5A 11 00 00 80
0x0010: 00 2E
SCSI Sense Data Fields:
Error Code : 0x70
Segment Number : 0x00
Bit Fields:
Filemark : 0
End-of-Medium : 0
Incorrect Length Indicator : 0
Sense Key : 0x03
Information Field Valid : TRUE
Information Field : 0x008E8060
Additional Sense Length : 10
Command Specific : 0x088A185A
Additional Sense Code : 0x11
Additional Sense Qualifier : 0x00
Field Replaceable Unit : 0x00
Sense Key Specific Data Valid : FALSE
Sense Key Specific Data : 0x80 0x00 0x2E
Sense Key 0x03, MEDIUM ERROR, indicates that the command terminated
with a nonrecovered error condition that was probably caused by a
flaw in the medium or an error in the recorded data. This sense key
may also be returned if the device is unable to distinguish between a
flaw in the medium and a specific hardware failure (sense key 0x04).
For the RECOVERED ERROR, HARDWARE ERROR, or MEDIUM ERROR Sense Key,
the Sense Key Specific data indicates that 46 retries were attempted.
The combination of Additional Sense Code and Sense Qualifier (0x1100)
indicates: Unrecovered read error.
SCSI Command Data Block:
Command Data Block Contents:
0x0000: 28 00 00 8E 80 60 00 00 02 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............: 9338976 (0x008E8060)
Transfer Length..................: 2 (0x0002)
Manager-Specific Data Fields:
Data Residue...........: 0x00000400
Sense Status...........: 0x00000000
Request ID.............: 0x036749EE
Additional IO Status : 0x00000000
Target ID..............: 0x06
LUN ID.................: 0x00
Sense Data Length......: 0x12
Q Tag..................: 0x7A
Retry Count............: 0
>---------- End Event Monitoring Service Event Notification ----------<
BR,
Yali
Solved! Go to Solution.
- Tags:
- EMS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2012 11:21 PM
тАО01-11-2012 11:21 PM
Re: Monitor event notification mail message
The message says the disk at
10/0/15/1.6.0
is bad and needs replacement ASAP.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2012 03:20 AM
тАО01-18-2012 03:20 AM
Re: Monitor event notification mail message
Thanks for the reply.
I have a spear DISK how can I replace the bad disk with it? I might need the information inside.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2012 05:08 AM
тАО01-18-2012 05:08 AM
Re: Monitor event notification mail message
You need a disk with the same interface (size may be larger) for replacement.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2012 05:12 AM
тАО01-18-2012 05:12 AM
Re: Monitor event notification mail message
No, its not mirrored by LVM.
Yes, I have the same disk interface.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2012 05:16 AM
тАО01-18-2012 05:16 AM
Re: Monitor event notification mail message
This may help, but it is written for newer OS releases than 10.20:
When_Good_Disks_Go_Bad_WP
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01911837/c01911837.pdf
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-18-2012 01:04 PM
тАО01-18-2012 01:04 PM
SolutionYou'll need to get a complete backup immediately. Unfortunately, the unrecoverable disk error may cause your backup program to abort partway through the task. All you can do is to continue with additional backup runs that skip the file or directory that has the bad spot on disk. If the data is important, do not do anything more until you get a a complete set of backups.
Have you ever run the command make_tape_recovery (Ignite backup)? If not, your backups (tar or fbackup) will not be useable if this disk is your boot disk. When you replace the disk, there will be no way to put anything back on the disk until you install HP-UX. For this task, you need an Ignite backup, or the Core CDROM disc. Once HP-UX is running, you can restore your data on the new disk.
If this disk is not part of vg00, then you must un-mount the lvols that are on the bad disk, then deactivate the volume group and vgexport the vg. Replace the disk and then recreate the vg and lvol(s) and mount them. Now you can restore the data to the mount points.
Bill Hassell, sysadmin