- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Degradation in performance before disk array accel...
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-04-2011 11:39 PM
07-04-2011 11:39 PM
Degradation in performance before disk array accelerator battery charge error reported
Hi
recently we had a HP ProLiant DL360 G5 on CentOS 4.9 that ran into a "POST Error: 1794-Drive Array - Array Accelerator Battery Charge Low". Looking at performance stats before the error I can see that IO wait was peaking at 12% where as now its at 3% and can also see increased disk utilisation before the issue too.
Is there any explanation of why an issue with the battery charge leading up to the failure might have caused the increased load, disk util etc?
Does anyone know the specific behaviour of the write cache based on the status of the battery e.g. charge <75% then no write cache, or is it more comlpex than that?
Thanks
Jason
- Tags:
- battery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2011 05:13 PM
07-05-2011 05:13 PM
Re: Degradation in performance before disk array accelerator battery charge error reported
Shalom,
Battery being low can lead to erratic performance on the RAID card. It is very important to act on these warnings and replace that battery when the warning is received.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-06-2011 12:21 AM
07-06-2011 12:21 AM
Re: Degradation in performance before disk array accelerator battery charge error reported
Hi Steven,
thank you very much for your feedback. So I understand correctly are you saying a battery with low charge but still above the 75% threshold (ie 100-76%) can still affect performance?
This is the key fact that I am trying to understand. We definitely saw issues on the servers when the charge dipped below 75%. But before the event we so no errors and exrta load on the box. That extra load didnt cause a performance issue but it was noticeable and so far unexplained. It could just be down to our application (in this case tomcat) slowly eating up resource over time but I am also out of interest pursuing the possibility of the battery being a contributing factor.
Thanks again
Jason