- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- dmesg -> got error .
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
тАО11-26-2008 08:32 PM
тАО11-26-2008 08:32 PM
dmesg -> got error .
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2008 08:39 PM
тАО11-26-2008 08:39 PM
Re: dmesg -> got error .
Did you check your /var/adm/syslog/syslog.log ?
Is there any error over there at syslog.log
Suraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2008 08:41 PM
тАО11-26-2008 08:41 PM
Re: dmesg -> got error .
Nov 26 21:58:17 camrac01 uvservd[17350]: stdout = $AgentGUID=2E7F2CD5A9FBD5EA93C554102099D980;AgentStatus=1;
Nov 26 22:07:56 camrac01 vmunix: DIAGNOSTIC SYSTEM WARNING:
Nov 26 22:07:56 camrac01 vmunix: The diagnostic logging facility has started receiving excessive
Nov 26 22:07:56 camrac01 vmunix: errors from the I/O subsystem. I/O error entries will be lost
Nov 26 22:07:56 camrac01 vmunix: until the cause of the excessive I/O logging is corrected.
Nov 26 22:07:56 camrac01 vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
Nov 26 22:07:56 camrac01 vmunix: in stm to start it.
Nov 26 22:07:56 camrac01 vmunix: If the diaglogd daemon is active, use the logtool utility in stm
Nov 26 22:07:56 camrac01 vmunix: to determine which I/O subsystem is logging excessive errors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2008 11:45 PM
тАО11-26-2008 11:45 PM
Re: dmesg -> got error .
Look at "ioscan -fnC disk" and check for lines with "NO_HW" in it.
Alterbatively, run "vgsdisplay" (without options) and see what warnings/errors it returns about missing physical volumes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2008 11:50 PM
тАО11-26-2008 11:50 PM
Re: dmesg -> got error .
Thanx for the reply..
but i already check on both command earlier. No such error/NO_HW or unclaimed disk. Everything looks OK.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2008 11:52 PM
тАО11-26-2008 11:52 PM
Re: dmesg -> got error .
check the HBA card(s).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2008 11:57 PM
тАО11-26-2008 11:57 PM
Re: dmesg -> got error .
Thanks for the idea..
BTW, please refer below...looks like no problem
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
fc 0 0/3/2/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
/dev/td0
fc 1 0/4/2/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
/dev/td1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2008 02:57 AM
тАО11-27-2008 02:57 AM
Re: dmesg -> got error .
if its SAN/FC based, it could be a problem with the SAN, FC card or cables.
may be latest patch set may solve this.
you may apply latest hwenabler path bundles.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2008 03:02 AM
тАО11-27-2008 03:02 AM
Re: dmesg -> got error .
I am not an stm-specialist. I opened stm myself to look at this logtool.
Maybe you just should do what the error messages says : run stm (having an X-Display works more comfortable) and query your hardware from there to see what device is giving you these IO errors. STM is a default software as part of on-line diagnostics.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2008 04:55 AM
тАО11-28-2008 04:55 AM
Re: dmesg -> got error .
Jozef