- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: hardware path failed on VA7100
HPE EVA Storage
1748036
Members
4662
Online
108757
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
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
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
тАО05-22-2009 05:28 AM
тАО05-22-2009 05:28 AM
hardware path failed on VA7100
hardware path 0/7/0/0 is showing failed, and we cannot communicate with the array. while we await response from HP hardware support, should I not expect the other path - 0/4/0/0 to be used? since is not, is there a way I can force the system to try HW path 0/4/0/0?
(we tried booting after the failure and the OS is complaining of pvlink failures.....
<31 0x041100> <31 0x041200> <31 0x041300> <31 0x041400> <31 0x042100> <31 0x0422
00> <31 0x042700>
LVM: VG 64 0x030000: PVLink 31 0x041200 Failed! The PV is not accessible.
LVM: VG 64 0x030000: PVLink 31 0x041300 Failed! The PV is not accessible.
LVM: VG 64 0x030000: PVLink 31 0x041400 Failed! The PV is not accessible.
LVM: VG 64 0x030000: PVLink 31 0x042100 Failed! The PV is not accessible.
LVM: VG 64 0x030000: PVLink 31 0x042200 Failed! The PV is not accessible.
LVM: VG 64 0x030000: PVLinLVM: VG 64 0x020000: Lost quorum.
This may block configuration changes and I/Os. In order to reestablish quorum at
least 2 of the following PVs (represented by current link) must become availabl
e:
<31 0x040600> <31 0x040700> <31 0x041000> <31 0x042000>
LVM: VG 64 0x020000: PVLink 31 0x040700 Failed! The PV is not accessible.
LVM: VG 64 0x020000: PVLink 31 0x041000 Failed! The PV is not accessible.
LVM: VG 64 0x020000: PVLink 31 0x042000 Failed! The PV is not accessible.)
(we tried booting after the failure and the OS is complaining of pvlink failures.....
<31 0x041100> <31 0x041200> <31 0x041300> <31 0x041400> <31 0x042100> <31 0x0422
00> <31 0x042700>
LVM: VG 64 0x030000: PVLink 31 0x041200 Failed! The PV is not accessible.
LVM: VG 64 0x030000: PVLink 31 0x041300 Failed! The PV is not accessible.
LVM: VG 64 0x030000: PVLink 31 0x041400 Failed! The PV is not accessible.
LVM: VG 64 0x030000: PVLink 31 0x042100 Failed! The PV is not accessible.
LVM: VG 64 0x030000: PVLink 31 0x042200 Failed! The PV is not accessible.
LVM: VG 64 0x030000: PVLinLVM: VG 64 0x020000: Lost quorum.
This may block configuration changes and I/Os. In order to reestablish quorum at
least 2 of the following PVs (represented by current link) must become availabl
e:
<31 0x040600> <31 0x040700> <31 0x041000> <31 0x042000>
LVM: VG 64 0x020000: PVLink 31 0x040700 Failed! The PV is not accessible.
LVM: VG 64 0x020000: PVLink 31 0x041000 Failed! The PV is not accessible.
LVM: VG 64 0x020000: PVLink 31 0x042000 Failed! The PV is not accessible.)
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 06:02 AM
тАО05-22-2009 06:02 AM
Re: hardware path failed on VA7100
> should I not expect the other path - 0/4/0/0 to be used?
Yes, assuming that the second path had been configured in the volume group(s) and was available. What does the configuration look like?
Yes, assuming that the second path had been configured in the volume group(s) and was available. What does the configuration look like?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 09:46 AM
тАО05-22-2009 09:46 AM
Re: hardware path failed on VA7100
Our configuration looks like this:
icgswa1:/etc # strings lvmtab
/dev/vg00
/dev/dsk/c2t2d0
/dev/dsk/c1t2d0
/dev/vgbck
/dev/dsk/c4t1d1
/dev/dsk/c4t1d2
/dev/dsk/c4t1d3
/dev/dsk/c4t1d4
/dev/dsk/c4t2d1
/dev/dsk/c4t2d2
/dev/dsk/c6t1d1
/dev/dsk/c6t1d2
/dev/dsk/c6t1d3
/dev/dsk/c6t1d4
/dev/dsk/c6t2d1
/dev/dsk/c6t2d2
/dev/dsk/c6t2d7
/dev/dsk/c4t2d7
/dev/vgicgs
/dev/dsk/c4t0d1
/dev/dsk/c4t0d2
/dev/dsk/c4t0d3
/dev/dsk/c4t0d4
/dev/dsk/c4t0d5
/dev/dsk/c4t1d6
/dev/dsk/c4t1d7
/dev/dsk/c6t0d1
/dev/dsk/c6t0d2
/dev/dsk/c6t0d3
/dev/dsk/c6t0d4
/dev/dsk/c6t0d5
/dev/dsk/c6t1d6
/dev/dsk/c6t1d7
/dev/dsk/c4t2d4
/dev/dsk/c4t2d5
/dev/dsk/c6t2d4
/dev/dsk/c6t2d5
/dev/dsk/c4t1d5
/dev/dsk/c6t1d5
/dev/dsk/c4t2d3
/dev/dsk/c6t2d3
/dev/vgrams
/dev/dsk/c4t0d6
/dev/dsk/c4t0d7
/dev/dsk/c4t1d0
/dev/dsk/c4t2d0
/dev/dsk/c6t0d6
/dev/dsk/c6t0d7
/dev/dsk/c6t1d0
/dev/dsk/c6t2d0
/dev/vgapps
/dev/dsk/c6t2d6
/dev/dsk/c4t2d6
icgswa1:/etc # strings lvmtab
/dev/vg00
/dev/dsk/c2t2d0
/dev/dsk/c1t2d0
/dev/vgbck
/dev/dsk/c4t1d1
/dev/dsk/c4t1d2
/dev/dsk/c4t1d3
/dev/dsk/c4t1d4
/dev/dsk/c4t2d1
/dev/dsk/c4t2d2
/dev/dsk/c6t1d1
/dev/dsk/c6t1d2
/dev/dsk/c6t1d3
/dev/dsk/c6t1d4
/dev/dsk/c6t2d1
/dev/dsk/c6t2d2
/dev/dsk/c6t2d7
/dev/dsk/c4t2d7
/dev/vgicgs
/dev/dsk/c4t0d1
/dev/dsk/c4t0d2
/dev/dsk/c4t0d3
/dev/dsk/c4t0d4
/dev/dsk/c4t0d5
/dev/dsk/c4t1d6
/dev/dsk/c4t1d7
/dev/dsk/c6t0d1
/dev/dsk/c6t0d2
/dev/dsk/c6t0d3
/dev/dsk/c6t0d4
/dev/dsk/c6t0d5
/dev/dsk/c6t1d6
/dev/dsk/c6t1d7
/dev/dsk/c4t2d4
/dev/dsk/c4t2d5
/dev/dsk/c6t2d4
/dev/dsk/c6t2d5
/dev/dsk/c4t1d5
/dev/dsk/c6t1d5
/dev/dsk/c4t2d3
/dev/dsk/c6t2d3
/dev/vgrams
/dev/dsk/c4t0d6
/dev/dsk/c4t0d7
/dev/dsk/c4t1d0
/dev/dsk/c4t2d0
/dev/dsk/c6t0d6
/dev/dsk/c6t0d7
/dev/dsk/c6t1d0
/dev/dsk/c6t2d0
/dev/vgapps
/dev/dsk/c6t2d6
/dev/dsk/c4t2d6
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 12:49 PM
тАО05-22-2009 12:49 PM
Re: hardware path failed on VA7100
What does the vgdisplay output show at the bottom of the listing where the PVs are? Do the PV devices show up as primary and alternate and are they available? Is it possible the alternate path had also failed before the primary path.
Also check with ioscan.
Also check with ioscan.
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