- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- MSA500 HA Linux multipath can't see one path
Disk Enclosures
1752815
Members
6197
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
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-22-2009 05:05 AM
06-22-2009 05:05 AM
MSA500 HA Linux multipath can't see one path
Hi,
We have two identical systems, one can only see one path of a multi path
md: autorun ...
md: considering cciss/c1d0p1 ...
md: adding cciss/c1d0p1 ...
md: created md0
md: bind
md: running:
md: cciss/c1d0p1's event counter: 0000012a
The other can see both paths
md: considering cciss/c0d1p1 ...
md: adding cciss/c0d1p1 ...
md: adding cciss/c1d0p1 ...
md: created md0
md: bind
md: bind
md: running:
md: cciss/c0d1p1's event counter: 00000552
md: cciss/c1d0p1's event counter: 00000552
Linux SCSI driver can see both paths on boot up
SCSI subsystem driver Revision: 1.00
HP CISS Driver (v 2.4.54.RH1)
cciss: Device 0x46 has been found at bus 4 dev 3 func 0
blocks= 142253280 block_size= 512
heads= 255, sectors= 32, cylinders= 17433 RAID 1(0+1)
blocks= 142261440 block_size= 512
heads= 255, sectors= 32, cylinders= 17434 RAID 1(0+1)
blocks= 142261440 block_size= 512
heads= 255, sectors= 32, cylinders= 17434 RAID 1(0+1)
blocks= 142261440 block_size= 512
heads= 255, sectors= 32, cylinders= 17434 RAID 1(0+1)
blk: queue c04fefa0, I/O limit 4294967295Mb (mask 0xffffffffffffffff)
Partition check:
cciss/c0d0: p1 p2 p3
cciss/c0d1: p1
cciss/c0d2: p1
cciss/c0d3: p1 p2
cciss: Device 0x46 has been found at bus 10 dev 1 func 0
blocks= 142261440 block_size= 512
heads= 255, sectors= 32, cylinders= 17434 RAID 1(0+1)
blocks= 142261440 block_size= 512
heads= 255, sectors= 32, cylinders= 17434 RAID 1(0+1)
blocks= 142261440 block_size= 512
heads= 255, sectors= 32, cylinders= 17434 RAID 1(0+1)
blk: queue c04ff070, I/O limit 4294967295Mb (mask 0xffffffffffffffff)
cciss/c1d0: p1
cciss/c1d1: p1
cciss/c1d2: p1 p2
So Linux can see both paths but miltipath cannot.
Any ideas ?
Thanks
john
We have two identical systems, one can only see one path of a multi path
md: autorun ...
md: considering cciss/c1d0p1 ...
md: adding cciss/c1d0p1 ...
md: created md0
md: bind
md: running:
md: cciss/c1d0p1's event counter: 0000012a
The other can see both paths
md: considering cciss/c0d1p1 ...
md: adding cciss/c0d1p1 ...
md: adding cciss/c1d0p1 ...
md: created md0
md: bind
md: bind
md: running:
md: cciss/c0d1p1's event counter: 00000552
md: cciss/c1d0p1's event counter: 00000552
Linux SCSI driver can see both paths on boot up
SCSI subsystem driver Revision: 1.00
HP CISS Driver (v 2.4.54.RH1)
cciss: Device 0x46 has been found at bus 4 dev 3 func 0
blocks= 142253280 block_size= 512
heads= 255, sectors= 32, cylinders= 17433 RAID 1(0+1)
blocks= 142261440 block_size= 512
heads= 255, sectors= 32, cylinders= 17434 RAID 1(0+1)
blocks= 142261440 block_size= 512
heads= 255, sectors= 32, cylinders= 17434 RAID 1(0+1)
blocks= 142261440 block_size= 512
heads= 255, sectors= 32, cylinders= 17434 RAID 1(0+1)
blk: queue c04fefa0, I/O limit 4294967295Mb (mask 0xffffffffffffffff)
Partition check:
cciss/c0d0: p1 p2 p3
cciss/c0d1: p1
cciss/c0d2: p1
cciss/c0d3: p1 p2
cciss: Device 0x46 has been found at bus 10 dev 1 func 0
blocks= 142261440 block_size= 512
heads= 255, sectors= 32, cylinders= 17434 RAID 1(0+1)
blocks= 142261440 block_size= 512
heads= 255, sectors= 32, cylinders= 17434 RAID 1(0+1)
blocks= 142261440 block_size= 512
heads= 255, sectors= 32, cylinders= 17434 RAID 1(0+1)
blk: queue c04ff070, I/O limit 4294967295Mb (mask 0xffffffffffffffff)
cciss/c1d0: p1
cciss/c1d1: p1
cciss/c1d2: p1 p2
So Linux can see both paths but miltipath cannot.
Any ideas ?
Thanks
john
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2009 01:03 PM
07-13-2009 01:03 PM
Re: MSA500 HA Linux multipath can't see one path
During array controller upgrade activities, somehow, we lost one path of the redundant multipath paths to the disk array, the path via the onboard controller on each POP.
The activation/deactivation of multipath paths is independent of each server, so it was a coincidence that both serverss had the same problem, or the action which caused the path to be deactivated was common to both serverss.
The deactivated path did not appear at boot time and did not appear when you ran the multipath checks. So it did not appear as deactivated, it just did not appear at all.
If you physically disconnect the working path and you try to run on the deactivated path only, you got a kernel panic error, which is effectively a crash. This is not a lot of help when trying to problem solve.
To clear. If you physically disconnect the working path and then try
Path deactivated, onboard physically disconnected - Server boots
Path deactivated, onboard physically connected - Server crashes
Path activated, onboard physically disconnected - Server boots
Path activated, onboard physically connected - Server boots
So this is bizarre. If the path is deactivated and the cable is disconnected, the server boots. If the path is deactivated and the cable is connected, the server crashes. So leaving a deactivated path connected will cause a server crash (assuming the other cable is disconnected). This is not right in any sense.
It is clear that the firmware/drivers for multipath have some issues, and the fact that they caused a kernel panic crash rather than just reporting an error has made this look like a hardware problem. And this put us on a path of finding a hardware problem which did not exist.
Finally the other confusing thing for me is, if one path was deactivated and stayed deactivated during each boot, where is the activation/deactivation stored. It is not stored in any config file. I have asked Red Hat to tell me. If there was a config file I could at least have looked there and seen that the path had been deactivated.
The activation/deactivation of multipath paths is independent of each server, so it was a coincidence that both serverss had the same problem, or the action which caused the path to be deactivated was common to both serverss.
The deactivated path did not appear at boot time and did not appear when you ran the multipath checks. So it did not appear as deactivated, it just did not appear at all.
If you physically disconnect the working path and you try to run on the deactivated path only, you got a kernel panic error, which is effectively a crash. This is not a lot of help when trying to problem solve.
To clear. If you physically disconnect the working path and then try
Path deactivated, onboard physically disconnected - Server boots
Path deactivated, onboard physically connected - Server crashes
Path activated, onboard physically disconnected - Server boots
Path activated, onboard physically connected - Server boots
So this is bizarre. If the path is deactivated and the cable is disconnected, the server boots. If the path is deactivated and the cable is connected, the server crashes. So leaving a deactivated path connected will cause a server crash (assuming the other cable is disconnected). This is not right in any sense.
It is clear that the firmware/drivers for multipath have some issues, and the fact that they caused a kernel panic crash rather than just reporting an error has made this look like a hardware problem. And this put us on a path of finding a hardware problem which did not exist.
Finally the other confusing thing for me is, if one path was deactivated and stayed deactivated during each boot, where is the activation/deactivation stored. It is not stored in any config file. I have asked Red Hat to tell me. If there was a config file I could at least have looked there and seen that the path had been deactivated.
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