- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- ProLiant DL160 Gen8 - Drive Array Controller Failu...
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
07-19-2021 07:37 AM
07-19-2021 07:37 AM
ProLiant DL160 Gen8 - Drive Array Controller Failure
I recently found on my ProLiant DL160 Gen8 a critical error.
From the Integrated Management Log:
Severity: Critical
Class: Drive array
Count: 2
Description: Drive Array Controller Failure (Slot 2)
From the System Information - Health Summary - Storage:
Controller Status: Failed
Model: Smart Array P420 Controller
Firmware Version: 8.00
Controller Type: HPE Smart Array
Cache Module Status: OK
I tried to look for some help and I found this SUPPORT COMMUNICATION - CUSTOMER ADVISORY on HPE Support site: https://support.hpe.com/hpesc/public/docDisplay?docId=a00029265en_us
Anyone had this error? Do you think I must proceed with upgrade the adapter firmware to a new version?
I'm trying to install the HPE Smart Storage Administrator (HPE SSA) on the server to look what it says but from the ILO I can see that my two physical drives are on this controller witha a RAID 1 / RAID 1+0.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2021 08:15 PM
07-19-2021 08:15 PM
Re: ProLiant DL160 Gen8 - Drive Array Controller Failure
Hello Frenky-77,
In my openion, the firmware update on controller(as mentioned in the advisory) should fix this issue.
Note: "While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2021 11:26 PM
07-19-2021 11:26 PM
Re: ProLiant DL160 Gen8 - Drive Array Controller Failure
After a first reboot the failure error was cleaned but I updated the firmware to the 8.32C version, it's very easy.
Now it's ok but I want to wait some days...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2021 05:39 PM
07-20-2021 05:39 PM
Re: ProLiant DL160 Gen8 - Drive Array Controller Failure
Hello,
Yes, please do update the firmware as suggested in the advisry and monitor the server.
Thanks.
If you feel this was helpful please click the KUDOS! thumb below and accept the solution.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2021 11:19 PM
07-20-2021 11:19 PM
Re: ProLiant DL160 Gen8 - Drive Array Controller Failure
I'm monitoring the server but it seems to be ok now...