- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: message from dmesg
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
09-15-2003 12:38 AM
09-15-2003 12:38 AM
message from dmesg
i think they can be very dangerous
anyone can help me ?
what do they mean ?
thanks in advance
Fab
Major 09/15/03 02:17:54 pemihp03 UX10/dmesg OS LVM LVM: Path (device 0x1f039000) to PV 13 in VG 8 Failed!
Major 09/15/03 02:17:54 pemihp03 UX10/dmesg OS LVM LVM: Path (device 0x1f019300) to PV 16 in VG 8 Failed!
Major 09/15/03 02:17:54 pemihp03 UX10/dmesg OS LVM LVM: Path (device 0x1f039100) to PV 14 in VG 8 Failed!
Major 09/15/03 02:17:54 pemihp03 UX10/dmesg OS LVM LVM: Path (device 0x1f005400) to PV 0 in VG 8 Failed!
Major 09/15/03 02:17:54 pemihp03 UX10/dmesg OS LVM LVM: Path (device 0x1f005500) to PV 1 in VG 8 Failed!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2003 12:47 AM
09-15-2003 12:47 AM
Re: message from dmesg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2003 01:05 AM
09-15-2003 01:05 AM
Re: message from dmesg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2003 01:05 AM
09-15-2003 01:05 AM
Re: message from dmesg
Could you check the ioscan output
and look for all the devices with the
state as "NO_HW".
Is it a Direct attached storage or thru
SAN switch?
Regards
Fenil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2003 03:32 AM
09-15-2003 03:32 AM
Re: message from dmesg
If connected by fiber, you may get additional info from this command:
fcmsutil /dev/td0
replace td0 by the actual address of the card.
A physical inspection of the fiber card itself for lights, connections and such is warranted, because the hardware folks will ask you that anyway. Also a look at the lights on the fabric switch and the console for the disk array would be very helpful.
It is possible that the disk admin(hopefully not yourself) has changed zoning or ownership on the disks, or the fabric switch itself has failed. It depends how you are connected.
Depending on whats actually on those disks, I'd be wary of whether production is going to be normal today.
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
09-15-2003 03:58 AM
09-15-2003 03:58 AM
Re: message from dmesg
or a storage device fault (can be checked if you have more LUNs from this storage used ).
"ioscan -fn" to see state (NO_HW,CLAIMED,UNKNOWN).Seek "scsi" errors in syslog.log , if found could also lead to physicall / logical scsi errors (ie termination,cable,bad set scsi id).
Usually most storage arrays provide specific commands to check storage state.
Zeev