ProLiant Servers (ML,DL,SL)
1755377
Members
5037
Online
108832
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
тАО07-16-2006 07:08 AM
тАО07-16-2006 07:08 AM
cpqasm2
I am getting the following description from a warning in the event logs: "Memory module #3 has exceeded its threshold of correctable errors. Subsequent correctable memory errors will continue to be corrected, but memory error reporting will cease until the system is rebooted." My system has rebooted the last three nights in a row and this is the only thing that I see in the event logs. Can someone please tell me what this means.
Thanks.
Thanks.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-16-2006 07:00 PM
тАО07-16-2006 07:00 PM
Re: cpqasm2
Jarret,
several components in a system have their thresholds, for memory modules in particular, their is a hard coded threshold by the manufacturer that, when crossed, is believed to be the time to alert the user that it's now time to replace the component in order to avoid unplanned downtime in the (near) future.
So if the module 3 has experienced to many correctable bit errors (because some chips on the SIMM/DIMM have a problem, then their is a chance that in the future you'll see crashes on your machine as the number of bit errors can grown and at some point in time become a double bit error which the system can not tolerate (or data corrutpion occurs) and it will then generate a crash and the system will go down immediately.
What probably happens here is that the module generates so many errors that you get the same message again after a reboot because the threshold is reached again so rapidly.
I'd make sure that module 3 gets replaced.
HTH
Kris
several components in a system have their thresholds, for memory modules in particular, their is a hard coded threshold by the manufacturer that, when crossed, is believed to be the time to alert the user that it's now time to replace the component in order to avoid unplanned downtime in the (near) future.
So if the module 3 has experienced to many correctable bit errors (because some chips on the SIMM/DIMM have a problem, then their is a chance that in the future you'll see crashes on your machine as the number of bit errors can grown and at some point in time become a double bit error which the system can not tolerate (or data corrutpion occurs) and it will then generate a crash and the system will go down immediately.
What probably happens here is that the module generates so many errors that you get the same message again after a reboot because the threshold is reached again so rapidly.
I'd make sure that module 3 gets replaced.
HTH
Kris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-17-2006 01:20 AM
тАО07-17-2006 01:20 AM
Re: cpqasm2
Agreed, swap module 3 but make sure you know which is module 3 before switching off and opening up the server. It's not always obvious. Take a look at the 'Maintenance and Service Guide' for your specific model. That should show you how the memory boards are laid out. A little planning is often a good investment.
The sheep tell me what I need to know
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