- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- error in syslog 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
тАО02-01-2011 08:53 PM
тАО02-01-2011 08:53 PM
LVM: Recovered Path (device 0x1f070100) to PV 0 in VG 1.
Feb 1 19:58:39 dr1 vmunix: LVM: Path (device 0x1f070100) to PV 0 in VG 1 Failed!
Feb 1 19:58:39 dr1 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050100) is POWERFAILED
Feb 1 22:08:20 dr1 vmunix: LVM: Recovered Path (device 0x1f070100) to PV 0 in VG 1.
Feb 1 22:08:54 dr1 vmunix: LVM: Path (device 0x1f070100) to PV 0 in VG 1 Failed!
Feb 1 22:08:54 dr1 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050100) is POWERFAILED
Feb 1 23:18:30 dr1 vmunix: LVM: Recovered Path (device 0x1f070100) to PV 0 in VG 1.
Feb 1 23:19:04 dr1 vmunix: LVM: Path (device 0x1f070100) to PV 0 in VG 1 Failed!
Feb 1 23:19:04 dr1 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050100) is POWERFAILED
Feb 2 03:38:51 dr1 vmunix: LVM: Recovered Path (device 0x1f070100) to PV 0 in VG 1.
Feb 2 03:39:24 dr1 vmunix: LVM: Path (device 0x1f070100) to PV 0 in VG 1 Failed!
Feb 2 03:39:24 dr1 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050100) is POWERFAILED
Feb 2 04:18:57 dr1 vmunix: LVM: Recovered Path (device 0x1f070100) to PV 0 in VG 1.
Feb 2 04:19:31 dr1 vmunix: LVM: Path (device 0x1f070100) to PV 0 in VG 1 Failed!
Feb 2 04:19:31 dr1 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050100) is POWERFAILED
Feb 2 04:29:01 dr1 vmunix: LVM: Recovered Path (device 0x1f070100) to PV 0 in VG 1.
Feb 2 04:29:35 dr1 vmunix: LVM: Path (device 0x1f070100) to PV 0 in VG 1 Failed!
Feb 2 04:29:35 dr1 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050100) is POWERFAILED
Feb 2 07:59:23 dr1 vmunix: LVM: Recovered Path (device 0x1f070100) to PV 0 in VG 1.
Feb 2 07:59:57 dr1 vmunix: LVM: Path (device 0x1f070100) to PV 0 in VG 1 Failed!
Feb 2 07:59:57 dr1 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050100) is POWERFAILED
Feb 2 08:00:02 dr1 vmunix: LVM: Recovered Path (device 0x1f050100) to PV 0 in VG 1.
Feb 2 08:00:02 dr1 vmunix: LVM: Restored PV 0 to VG 1
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2011 10:05 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2011 10:06 PM
тАО02-01-2011 10:06 PM
Re: error in syslog message
# vgdisplay -v
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2011 10:12 PM
тАО02-01-2011 10:12 PM
Re: error in syslog message
>>Feb 2 07:59:57 dr1 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050100) is POWERFAILED
Looks one of the PV path has power failed
Check for registrar.log under /etc/opt/resmon/log/ for HW alerts.
Yes send vgdisplay -v vg01 , you will see alternate links there.
Thanks
Manix
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-02-2011 08:47 PM
тАО02-02-2011 08:47 PM
Re: error in syslog message
It seems that the connectivity between the Server and the storage was having some issue.
Do you face any issue with any of your filesystem? if not then you have alternate links available.
Can you check for any UNCLAIMED status in ioscan -fnCdisk output?
Kindly post the vgdisplay -v vg01 out put.
Thanks
Mohammad Sanaullah
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-02-2011 10:10 PM
тАО02-02-2011 10:10 PM
Re: error in syslog message
Please check
1) the status of the disk /dev/dsk/c5t0d1 using ioscan -fnC disk
2)diskinfo /dev/rdsk/c5t0d1
3)vgdisplay -v vg_name
4)Check event.log (/var/opt/resmon/log/event.log)for any hardware error.
Regards,
George
I am an HPE Employee. .
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2011 04:11 AM
тАО02-04-2011 04:11 AM
Re: error in syslog message
and vgdisplay -v
regards
MC