HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Disk issue in Syslog!
Operating System - HP-UX
1837159
Members
2651
Online
110112
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
Forums
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
06-18-2007 09:58 PM
06-18-2007 09:58 PM
Disk issue in Syslog!
HI,
I am getting following error in syslog:
Jun 17 01:45:01 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000043752000), from raw device 0x1f090600 (with priority: 0, and current flags: 0x40) to raw device 0x1f050600 (with priority: 1, and current flags: 0x0).
Jun 17 01:45:02 vmunix: LVM: VG 64 0x030000: PVLink 31 0x090600 Failed! The PV is still accessible.
Jun 18 01:49:45 vmunix: This may block configuration changes and I/Os. In order to reestablish quorum at least 1 of the following PVs (represented by current link) must become available:
Jun 18 01:49:45 vmunix: LVM: VG 64 0x030000: PVLink 31 0x050600 Failed! until the cause of the excessive I/O logging is corrected.
Jun 18 01:49:45 vmunix: The PV is not accessible.
Jun 18 10:04:47 vmunix: LVM: VG 64 0x030000: PVLink 31 0x050600 Recovered.
Jun 19 01:50:17 vmunix: This may block configuration changes and I/Os. In order to reestablish quorum at least 1 of the following PVs (represented by current link) must become available:
Jun 19 01:50:17 vmunix: LVM: VG 64 0x030000: PVLink 31 0x050600 Failed! The PV is not accessible.
Can any one advice please
I am getting following error in syslog:
Jun 17 01:45:01 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000043752000), from raw device 0x1f090600 (with priority: 0, and current flags: 0x40) to raw device 0x1f050600 (with priority: 1, and current flags: 0x0).
Jun 17 01:45:02 vmunix: LVM: VG 64 0x030000: PVLink 31 0x090600 Failed! The PV is still accessible.
Jun 18 01:49:45 vmunix: This may block configuration changes and I/Os. In order to reestablish quorum at least 1 of the following PVs (represented by current link) must become available:
Jun 18 01:49:45 vmunix: LVM: VG 64 0x030000: PVLink 31 0x050600 Failed! until the cause of the excessive I/O logging is corrected.
Jun 18 01:49:45 vmunix: The PV is not accessible.
Jun 18 10:04:47 vmunix: LVM: VG 64 0x030000: PVLink 31 0x050600 Recovered.
Jun 19 01:50:17 vmunix: This may block configuration changes and I/Os. In order to reestablish quorum at least 1 of the following PVs (represented by current link) must become available:
Jun 19 01:50:17 vmunix: LVM: VG 64 0x030000: PVLink 31 0x050600 Failed! The PV is not accessible.
Can any one advice please
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2007 12:26 AM
06-19-2007 12:26 AM
Re: Disk issue in Syslog!
Hi Ganti
if it started on it's own without you running any commands or making changes might be a failed disk in the LUN
gather the log and open a hw case with HP
if it started on it's own without you running any commands or making changes might be a failed disk in the LUN
gather the log and open a hw case with HP
The tongue weighs practically nothing, but so few people can hold it
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP