- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: SCSI Disk Errors
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
тАО05-22-2006 08:01 AM
тАО05-22-2006 08:01 AM
May 14 15:39:08 ignite1 vmunix: msgcnt 1 vxfs: mesg 038: vx_dataioerr - /dev/vgi
gn1/ignitelv file system file data read error in block 7399426
May 19 10:42:40 ignite1 vmunix: msgcnt 13 vxfs: mesg 008: vx_direrr: vx_readdir2
_1 - /var/opt/ignite file system dir inode 103811 block 6422535 dirent inode 0 e
rror 5
When we started doing our weekly Ignite make recoveries this past weekend they all failed due to not being able to write to the Volume.
Is there a way in the Event Monitor to trap these errors so that we receive them in our Event Monitor EMail's ??
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2006 09:17 AM
тАО05-22-2006 09:17 AM
SolutionYou should be able to configure EMS with SAM to trap the issues and notify via email.
You have a bad sector on your disk and probably have block relocation set to enabled.
I'd get a good backup, id the disk with cstm,xstm or mstm and replace the disk.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2006 04:30 PM
тАО05-22-2006 04:30 PM
Re: SCSI Disk Errors
Try /etc/opt/resmon/lbin/monconfig to configure receiving EMS alerts
rgds,
Ajit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-23-2006 05:50 AM
тАО05-23-2006 05:50 AM
Re: SCSI Disk Errors
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-24-2006 10:09 PM
тАО05-24-2006 10:09 PM
Re: SCSI Disk Errors
You do NOT configure the EMS HW monitors using SAM (SEP please note! I think you've stated this before; it's not true.).
The disk monitor, disk_em, does not monitor virtual disk arrays (XP, VA, etc.), so if that's what you have, that would explain why no EMS event was generated.
If these are directly attached SCSI disks, then you need to check you have a current version of the OnlineDiags (running 'cstm' will show the version you have installed, including the patch level).
Note also that the monitors do not generate an EMS event for every single low-level failure; there are thresholds set so that the events are only generated when the number of failures indicates a likely real problem. Hardware is resilient to a certain degree, and one or two recoverable errors are acceptable.
I notice you've closed the thread; did you find the answer?
Andrew