- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- DL385 G7 controller issue
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
Forums
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
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
03-15-2011 11:53 AM
03-15-2011 11:53 AM
DL385 G7 controller issue
Hello,
I've been reading up on an issue I'm having at my customer site regarding the p410i raid controller. I ran across an issue with the 380 G7 on the IT Resource Center site, but wanted to double check to see I was running the right track troubleshooting the 385.
The issue:
At bootup I get an error message for the controller locking up 1719 0x13 and 1797 0x13.
Current solution:
Upgrade p410i controller firmware from 3.5 to 3.66.
If this is still failing, swap out the 1GB FWBC for another 1GB or a 512GB FWBC
OS: ESX 4.1
Thoughts and concerns:
I am going to move off my virtual servers to the other VM server while I do the upgrade to reduce the risk of anything going wrong with this upgrade. The issue hasn't been reported for long, from what I understand it has just started within a few days. Is there anything else I should/could look at or would this be the viable fix? Nothing else has a fully answered question.
Thanks,
Josh