- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Disk failures MSA20 upgrading to SmartStart 8.3 Fr...
Disk Enclosures
1748051
Members
4803
Online
108758
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
тАО01-06-2010 06:21 AM
тАО01-06-2010 06:21 AM
Disk failures MSA20 upgrading to SmartStart 8.3 Frimware 8.6
Hi,
We are experiencing issues with our MSA20 storage enclosures which are connected externally to ProLiant DL 380 G5 servers using 6400 Smart Array Controllers for SCSI connectivity only (Arrays managed by controller module in the MSA20 itself).
Everything has been configured and running fine for a couple of years in some cases. When updating to SmartStart 8.30 and Firmware 8.6 the arrays on the MSA20 experience disk failures and in some cases the server will fail to boot with the MSA20 connected to the 6400 Smart Array Controller. If we try to replace a failed disk the array is lost.
I have found the following Advisory which seems to match our situation, however this advisory was published a year before SmartStart 8.30 and Firmware 8.6 were released:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=125&prodSeriesId=420469&prodTypeId=12169&objectID=c01232270
Has anyone else come across disk failure on MSA20 when upgrading to SmartStart 8.30 and Firmware 8.6?
Can anyone reccommend what steps we should take to prevent this from happening again? i.e. what is the safest SmartStart and Firmware versions for our configuration or should we switch to using dedicated SCSI controllers?
Any help would be greatly appreciated.
Thanks,
Brian
We are experiencing issues with our MSA20 storage enclosures which are connected externally to ProLiant DL 380 G5 servers using 6400 Smart Array Controllers for SCSI connectivity only (Arrays managed by controller module in the MSA20 itself).
Everything has been configured and running fine for a couple of years in some cases. When updating to SmartStart 8.30 and Firmware 8.6 the arrays on the MSA20 experience disk failures and in some cases the server will fail to boot with the MSA20 connected to the 6400 Smart Array Controller. If we try to replace a failed disk the array is lost.
I have found the following Advisory which seems to match our situation, however this advisory was published a year before SmartStart 8.30 and Firmware 8.6 were released:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=125&prodSeriesId=420469&prodTypeId=12169&objectID=c01232270
Has anyone else come across disk failure on MSA20 when upgrading to SmartStart 8.30 and Firmware 8.6?
Can anyone reccommend what steps we should take to prevent this from happening again? i.e. what is the safest SmartStart and Firmware versions for our configuration or should we switch to using dedicated SCSI controllers?
Any help would be greatly appreciated.
Thanks,
Brian
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2010 05:02 PM
тАО02-08-2010 05:02 PM
Re: Disk failures MSA20 upgrading to SmartStart 8.3 Frimware 8.6
We just had an interesting experience, perhaps it can shed some light.
Similar setup, MSA20, 380G5, Storage Server 2003. We've been updating this roughly between 1-60 days after firmware/driver updates come out per maintenance windows. Firmware 8.6 was installed fine.
Just today the server hung/locked up, with no connectivity via RDP/KVM/iLO. We hard reset the server/MSA20, and when it came up we had drive failure after drive failure reported in the MSA. Eventually every drive was marked as bad. We ran diagnostics, then HP had us power down, pull the disk controller module in the G5, put it back in, and everything came back as if nothing wrong had *ever* occurred. (Server is acting normally and all the shares are accessible.) Still testing now, but it's rather scary. I don't know why a re-seating of this device would bring about this condition.
Similar setup, MSA20, 380G5, Storage Server 2003. We've been updating this roughly between 1-60 days after firmware/driver updates come out per maintenance windows. Firmware 8.6 was installed fine.
Just today the server hung/locked up, with no connectivity via RDP/KVM/iLO. We hard reset the server/MSA20, and when it came up we had drive failure after drive failure reported in the MSA. Eventually every drive was marked as bad. We ran diagnostics, then HP had us power down, pull the disk controller module in the G5, put it back in, and everything came back as if nothing wrong had *ever* occurred. (Server is acting normally and all the shares are accessible.) Still testing now, but it's rather scary. I don't know why a re-seating of this device would bring about this condition.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2010 11:08 AM
тАО02-23-2010 11:08 AM
Re: Disk failures MSA20 upgrading to SmartStart 8.3 Frimware 8.6
Hello,
we have the same issue. DL380 + MSA20 + SA6400.
It crashed when running hpsum_hwdiscovery.exe. After a reboot of the MSA20 everythings works fine. This configuration was running fine for 3 years, but after upgrading to SmartStart 8.30 this error occured.
I have no suggestion to solve this problem.
Joerg
we have the same issue. DL380 + MSA20 + SA6400.
It crashed when running hpsum_hwdiscovery.exe. After a reboot of the MSA20 everythings works fine. This configuration was running fine for 3 years, but after upgrading to SmartStart 8.30 this error occured.
I have no suggestion to solve this problem.
Joerg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2010 02:05 AM
тАО03-03-2010 02:05 AM
Re: Disk failures MSA20 upgrading to SmartStart 8.3 Frimware 8.6
Hi, same issue, what was your old version of Smartstart and firmware that was working?
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