- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- which VA generating syslog POWERFAILED messages
Disk Enclosures
1752815
Members
5778
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
07-17-2004 08:12 AM
07-17-2004 08:12 AM
I have two VA7400's and one of them is generating the following messages to my syslog. How can I determine which VA is generating the message, please.
Jul 17 13:48:18 erptest vmunix: LVM: Recovered Path (device 0x1f194600) to PV 1 in VG 7.
Jul 17 13:45:01 erptest : su : + tty?? root-oramaint
Jul 17 13:48:18 erptest above message repeats 2 times
Jul 17 13:48:18 erptest vmunix: LVM: Recovered Path (device 0x1f195000) to PV 3 in VG 7.
Jul 17 13:48:32 erptest vmunix: LVM: vg[7]: pvnum=1 (dev_t=0x1f194600) is POWERFAILED
Jul 17 13:48:32 erptest vmunix: LVM: vg[7]: pvnum=3 (dev_t=0x1f195000) is POWERFAILED
Jul 17 13:48:55 erptest vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000439f0800), from raw device 0x1f195000 (with p
riority: 0, and current flags: 0xc0) to raw device 0x1f175000 (with priority: 1, and current flags: 0x0).
Jul 17 13:48:56 erptest vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000439e4800), from raw device 0x1f194600 (with p
riority: 0, and current flags: 0xc0) to raw device 0x1f174600 (with priority: 1, and current flags: 0x0).
Jul 17 13:48:57 erptest vmunix: LVM: Restored PV 1 to VG 7.
Jul 17 13:48:57 erptest vmunix: LVM: Restored PV 3 to VG 7.
Jul 17 13:49:06 erptest vmunix: LVM: Recovered Path (device 0x1f194600) to PV 1 in VG 7.
Jul 17 13:49:06 erptest vmunix: LVM: Recovered Path (device 0x1f195000) to PV 3 in VG 7.
Jul 17 13:49:06 erptest vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000439f0800), from raw device 0x1f175000 (with p
riority: 1, and current flags: 0x0) to raw device 0x1f195000 (with priority: 0, and current flags: 0x80).
Jul 17 13:49:06 erptest vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000439e4800), from raw device 0x1f174600 (with p
riority: 1, and current flags: 0x0) to raw device 0x1f194600 (with priority: 0, and current flags: 0x0).
Jul 17 13:50:01 erptest : su : + tty?? root-oramaint
Jul 17 13:55:00 erptest : su : + tty?? root-oramaint
Jul 17 14:10:00 erptest : su : + tty?? root-oramaint
Jul 17 14:11:57 erptest above message repeats 4 times
Jul 17 14:15:00 erptest : su : + tty?? root-oramaint
Jul 17 14:17:16 erptest vmunix: LVM: Recovered Path (device 0x1f193400) to PV 1 in VG 5.
Jul 17 14:17:20 erptest vmunix: LVM: Restored PV 1 to VG 5.
Jul 17 14:20:02 erptest : su : + tty?? root-oramaint
Jul 17 14:31:29 erptest named[651]: NSTATS 1090092689 1089649888 Unknown=8 A=2510 NS=1 SOA=1477 PTR=167 33=4080 ANY=4
Jul 17 14:31:29 erptest named[651]: XSTATS 1090092689 1089649888 RR=4879 RNXD=390 RFwdR=4514 RDupR=2 RFail=0 RFErr=0 RErr=0 RAXFR=0
RLame=0 ROpts=0 SSysQ=106 SAns=3868 SFwdQ=4592 SDupQ=392 SErr=0 RQ=8247 RIQ=0 RFwdQ=4592 RDupQ=680 RTCP=7 SFwdR=4514 SFail=2 SFErr=0
SNaAns=2331 SNXD=276
Jul 17 14:30:01 erptest : su : + tty?? root-oramaint
Jul 17 14:31:57 erptest above message repeats 2 times
Jul 17 14:35:01 erptest : su : + tty?? root-oramaint
Jul 17 14:35:03 erptest monitor.sh: CHECK_POINT
Jul 17 14:40:00 erptest : su : + tty?? root-oramaint
Jul 17 14:48:53 erptest vmunix: LVM: Recovered Path (device 0x1f193600) to PV 3 in VG 5.
Jul 17 14:45:00 erptest : su : + tty?? root-oramaint
Jul 17 14:49:08 erptest vmunix: LVM: Restored PV 3 to VG 5.
Jul 17 14:50:00 erptest : su : + tty?? root-oramaint
Jul 17 14:55:00 erptest : su : + tty?? root-oramaint
Jul 17 15:10:00 erptest : su : + tty?? root-oramaint
Jul 17 15:11:57 erptest above message repeats 4 times
Jul 17 15:15:00 erptest : su : + tty?? root-oramaint
#
Jul 17 13:48:18 erptest vmunix: LVM: Recovered Path (device 0x1f194600) to PV 1 in VG 7.
Jul 17 13:45:01 erptest : su : + tty?? root-oramaint
Jul 17 13:48:18 erptest above message repeats 2 times
Jul 17 13:48:18 erptest vmunix: LVM: Recovered Path (device 0x1f195000) to PV 3 in VG 7.
Jul 17 13:48:32 erptest vmunix: LVM: vg[7]: pvnum=1 (dev_t=0x1f194600) is POWERFAILED
Jul 17 13:48:32 erptest vmunix: LVM: vg[7]: pvnum=3 (dev_t=0x1f195000) is POWERFAILED
Jul 17 13:48:55 erptest vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000439f0800), from raw device 0x1f195000 (with p
riority: 0, and current flags: 0xc0) to raw device 0x1f175000 (with priority: 1, and current flags: 0x0).
Jul 17 13:48:56 erptest vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000439e4800), from raw device 0x1f194600 (with p
riority: 0, and current flags: 0xc0) to raw device 0x1f174600 (with priority: 1, and current flags: 0x0).
Jul 17 13:48:57 erptest vmunix: LVM: Restored PV 1 to VG 7.
Jul 17 13:48:57 erptest vmunix: LVM: Restored PV 3 to VG 7.
Jul 17 13:49:06 erptest vmunix: LVM: Recovered Path (device 0x1f194600) to PV 1 in VG 7.
Jul 17 13:49:06 erptest vmunix: LVM: Recovered Path (device 0x1f195000) to PV 3 in VG 7.
Jul 17 13:49:06 erptest vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000439f0800), from raw device 0x1f175000 (with p
riority: 1, and current flags: 0x0) to raw device 0x1f195000 (with priority: 0, and current flags: 0x80).
Jul 17 13:49:06 erptest vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000439e4800), from raw device 0x1f174600 (with p
riority: 1, and current flags: 0x0) to raw device 0x1f194600 (with priority: 0, and current flags: 0x0).
Jul 17 13:50:01 erptest : su : + tty?? root-oramaint
Jul 17 13:55:00 erptest : su : + tty?? root-oramaint
Jul 17 14:10:00 erptest : su : + tty?? root-oramaint
Jul 17 14:11:57 erptest above message repeats 4 times
Jul 17 14:15:00 erptest : su : + tty?? root-oramaint
Jul 17 14:17:16 erptest vmunix: LVM: Recovered Path (device 0x1f193400) to PV 1 in VG 5.
Jul 17 14:17:20 erptest vmunix: LVM: Restored PV 1 to VG 5.
Jul 17 14:20:02 erptest : su : + tty?? root-oramaint
Jul 17 14:31:29 erptest named[651]: NSTATS 1090092689 1089649888 Unknown=8 A=2510 NS=1 SOA=1477 PTR=167 33=4080 ANY=4
Jul 17 14:31:29 erptest named[651]: XSTATS 1090092689 1089649888 RR=4879 RNXD=390 RFwdR=4514 RDupR=2 RFail=0 RFErr=0 RErr=0 RAXFR=0
RLame=0 ROpts=0 SSysQ=106 SAns=3868 SFwdQ=4592 SDupQ=392 SErr=0 RQ=8247 RIQ=0 RFwdQ=4592 RDupQ=680 RTCP=7 SFwdR=4514 SFail=2 SFErr=0
SNaAns=2331 SNXD=276
Jul 17 14:30:01 erptest : su : + tty?? root-oramaint
Jul 17 14:31:57 erptest above message repeats 2 times
Jul 17 14:35:01 erptest : su : + tty?? root-oramaint
Jul 17 14:35:03 erptest monitor.sh: CHECK_POINT
Jul 17 14:40:00 erptest : su : + tty?? root-oramaint
Jul 17 14:48:53 erptest vmunix: LVM: Recovered Path (device 0x1f193600) to PV 3 in VG 5.
Jul 17 14:45:00 erptest : su : + tty?? root-oramaint
Jul 17 14:49:08 erptest vmunix: LVM: Restored PV 3 to VG 5.
Jul 17 14:50:00 erptest : su : + tty?? root-oramaint
Jul 17 14:55:00 erptest : su : + tty?? root-oramaint
Jul 17 15:10:00 erptest : su : + tty?? root-oramaint
Jul 17 15:11:57 erptest above message repeats 4 times
Jul 17 15:15:00 erptest : su : + tty?? root-oramaint
#
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2004 11:43 PM
07-18-2004 11:43 PM
Solution
Pat,
how do you know it is only one of the VAs?
You can decipher the device files:
the message says
device 0x1f195000 is PV3 in VG 7
so find the vg with a group file with minor number 7:
ll /dev/vg*/group | grep 0x070000
then see what is the third disk in that vg.
strings /etc/lvmtab | more
that device should match 0x1f195000
Anyway, for the VA and other disk arrays you should set the timeout value for LVM disks higher than the default, i.e. e.g. for LUN 5 run pvchange -t 180 /dev/dsk/c#t0d5
use this command for all VA disk devices.
Regards,
Bernhard
how do you know it is only one of the VAs?
You can decipher the device files:
the message says
device 0x1f195000 is PV3 in VG 7
so find the vg with a group file with minor number 7:
ll /dev/vg*/group | grep 0x070000
then see what is the third disk in that vg.
strings /etc/lvmtab | more
that device should match 0x1f195000
Anyway, for the VA and other disk arrays you should set the timeout value for LVM disks higher than the default, i.e. e.g. for LUN 5 run pvchange -t 180 /dev/dsk/c#t0d5
use this command for all VA disk devices.
Regards,
Bernhard
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP