- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: MSA1000 error #259
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
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
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-09-2009 07:09 AM
тАО03-09-2009 07:09 AM
MSA1000 error #259
#259 The current arrary controller had an unexpected arrary accelerator battery voltage drop which may have resulted in a corrupted data in its cache.
Any suggestions?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-09-2009 10:36 AM
тАО03-09-2009 10:36 AM
Re: MSA1000 error #259
is it working with the write cache disabled and hence the performance is degraded pls?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2009 08:06 AM
тАО03-10-2009 08:06 AM
Re: MSA1000 error #259
Batteries are disabled
Module #1 is fully charged and turned off
Module #2 is fully charged and turned off
Why does it say that if the ACU says is enabled?
How do I turn them on?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2009 08:37 AM
тАО03-10-2009 08:37 AM
Re: MSA1000 error #259
(can be checked via the
show globals command
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2009 08:53 AM
тАО03-10-2009 08:53 AM
Re: MSA1000 error #259
Global Parameters:
System Name: SGA075201L
Rebuild Priority: high
Expand Priority: high
Surface Delay: 3.0 seconds
Total Cache: 512MB
50% Read Cache: 256MB
50% Write Cache: 256MB
Temperature:
No temperature sensor support.
FIBRE BAY: 44 Celsius, 111 Fahrenheit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-10-2009 09:19 AM
тАО03-10-2009 09:19 AM
Re: MSA1000 error #259
Total Cache: 512MB
50% Read Cache: 256MB
50% Write Cache: 256MB
means that there seems no problem with batteries, because the the controller cache moudule is temporarily disabled e.g. when the controller is powered on, if they are discharged the internal circuitry automaticaly recharges them. The controller functions properly at that time, although withoout the performance advantage of the controller cache module. When the batteries are charged to 90 percent of their capacity, the controller cache module is automaticaly enabled.
Now in your situation there seems are 2 information which seems to be contradictory:
a) that during the power off there was a drop in the cache battery, therefore it could be that the data in cache are corrupted and
b) that there is no unflushed data in cache
Resume
Run the ADU (array diagnostic utility) check it and send it also to HP support with the issue description for the possible root cause analysis to come onsite and e.g. reinsert/replace the batteries