- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: MSA1000 Failed Redundancy Path Error
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
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
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
04-03-2010 04:43 AM
04-03-2010 04:43 AM
MSA1000 Failed Redundancy Path Error
In an attempt to resolve the 776 error, I completely powered down all servers that are attached to the SAN, powered down the MSA1000 and finally powered down the additional MSA30. I let the MSA1000/MSA30 sit for about 10 minutes after powering down the servers to make sure all cache information had been flushed. I reseated all drives and cables. Next, I powered up the MSA30 and then the MSA1000 and waited for 10 minutes to make sure all of the drives initialized and that the controllers were completely up. Next, I powered up one server and verified that all of the arrays were operational and that the array that needed rebuilding had indeed started the rebuild process. I next powered up the remaining three servers. After about six hours of rebuilding, the array is now back in the "Ready for Recovery" status and no drives are showing failed in either the MSA1000 or the MSA30. I have not done a visual inspection, but when I looked previous after this issue arose, I would find that drive 13 was offline. I have replaced this drive three times....
I "inherited" support of this MSA1000, so I was not fully aware of the hardware configuration until I began this process. Since the second controller does not have a 2/8 switch, should the controller be disabled or removed? Could it cause problems with array rebuilds?
Any ideas as to what my next steps should be with regards to the array that needs rebuilding? I have a case open with HP, the tech gave me the above shutdown/reseat steps above, but I wanted some input from those "in the field" who may have run into this issue. Could old firmware on the MSA1000 cause the rebuild issue?
Thanks in advance for your assistance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2010 05:12 AM
04-05-2010 05:12 AM
Re: MSA1000 Failed Redundancy Path Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2010 05:01 AM
04-06-2010 05:01 AM
Re: MSA1000 Failed Redundancy Path Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2010 02:46 AM
07-08-2010 02:46 AM
Re: MSA1000 Failed Redundancy Path Error
We are having a similar issue with an array rebuild. Can you tell me what the resolution to your issue was?