Cpu 1 Bus Parity Error Detected
Contents |
Sign in Critical Server Error Servers Information and ideas on Dell PowerEdge rack, tower and blade server solutions. Get this RSS feed Home Forums Server Media Gallery 94 Replies 3 Subscribers Postedover 8 years ago Critical a parity error was detected on device raidport0 Server Error Posted by Z_Z on 3 Mar 2008 2:36 Hello, We lost connectivity to
A Parity Error Was Detected On Device Ide Iastor0
a PE2950 earlier today and when we arrived at the data centre the front-panel LCD was orange and saying the following: "E1420 CPU what is parity error Bus PERR". I power cycled the machine and it came back up with no problems and currently SEEMS to be running fine. When I loaded up Dell Server Administrator it shows everything with green check marks and doesnt parity error cisco report any issues. When I look at the log section it shows that there was a critical error (red x) and reports a similar error to the front panel LCD. My question now is:1) What is the error? Is it something I should be worried about?2) Why is the front panel LCD still amber showing that error when the server administrator is reporting no issues? Please advise, thanks Like 0 Reply You have posted to a
Parity Error Fix
forum that requires a moderator to approve posts before they are publicly available. Posted by snapohead on 4 Mar 2008 4:51 Clearing the logs will change the LCD to blue and remove the error. But I suspect the error may appear again at a later stage. Were there any errors indicating a particular CPU? If not, it may require a replacement MB at some stage.See how it runs, and if the problems persist then log a call with Dell. Like 0 Reply You have posted to a forum that requires a moderator to approve posts before they are publicly available. Posted by Z_Z on 4 Mar 2008 14:06 Hi Snapohead, Thanks for your reply. Do you know what that error actually means? What is PERR? Some sort of pairty error? The strange thing is that the server has been working perfectly fine since the incident. Not sure what could have caused it. I'm worried because its an important server. I'm using PERC raid controller (RAID1 on sys drives, RAID10 on data drives) - if I pull those drives and put them into an identical PE2950 will the raid still work? (does the info get written to the RAID drives or does the controller have to move with them?) Thanks Like 0 Reply You have posted to a forum that requires a moderator to approve
7200 Series RoutersTroubleshoot and AlertsTroubleshooting TechNotes Cisco 7200 Parity Error Fault Tree Download Print Available Languages Download Options PDF (49.3 KB) View with Adobe Reader system returned to rom by processor memory parity error at pc on a variety of devices Updated:Apr 13, 2009 Document ID:12763 Contents Introduction parity error detected in vram Prerequisites Requirements Components Used Conventions Network Processing Engine (NPE) Parity Error Fault Tree Analysis NPE Parity Error Detection
Parity Error Checking
and Messages Parity Errors in the NPE-300 NPE-400 Parity/ECC Detection Parity Errors in the C7200 Router Solutions Related Information Introduction This document explains the steps to troubleshoot and isolate which part http://en.community.dell.com/support-forums/servers/f/956/t/18903018 or component of a Cisco 7200 is failing when you identify a variety of parity error messages. We recommend that you read Troubleshooting Router Crashes and Processor Memory Parity Errors (PMPEs) before you proceed with this document. Note:The information in this document is based on the Cisco 7200 Series Routers. Prerequisites Requirements There are no specific prerequisites for this document. Components Used http://www.cisco.com/c/en/us/support/docs/routers/7200-series-routers/12763-c7200-faulttree.html This document is not restricted to specific software and hardware versions. The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you work in a live network, ensure that you understand the potential impact of any command before you use it. Conventions For more information on document conventions, refer to the Cisco Technical Tips Conventions. Network Processing Engine (NPE) Parity Error Fault Tree Analysis This diagram describes the steps to determine which part or component of a Cisco 7200 is failing when you identify a variety of parity error messages. Note:Capture and record the show tech-support output and console logs, and collect all crashinfo files during parity error events. NPE Parity Error Detection and Messages This section contains block diagrams of the NPE and where these systems detect parity errors. You can find a description of each type of error message below. Parity Errors in the NPE-300 The NPE-300 uses parity checking in shared memory (SDRAM), PCI Bus, and the CPU's external interf
provides status messages to signify when its physical system is operating well or when needs some attention. The LCD lights blue to indicate a normal operating condition, and lights amber to indicate an http://www.admon.org/hardwares/dell-pe2950-lcd-message-explained/ error condition. The LCD scrolls a message that includes a status code followed by descriptive text. The following section lists the LCD status messages that can occur and the probable cause for each message. The LCD messages refer to events recorded in the System Event Log (SEL). For information on the SEL and configuring system management settings, see the systems management documentation. NOTE: If parity error your system fails to boot, press the System ID button for at least five seconds until an error code appears on the LCD. Record the code, then check it here or see Getting Help on Dell.com. The following lines will should each error in a two-line mode, the first line indicates the appeared Error code and Text, and the second line is a case parity error detected explaination. N/A - SYSTEM NAME Causes: A 62-character string that can be defined by the user in the System Setup program. The SYSTEM NAME displays under the following conditions: * The system is powered on. * The power is off and active POST errors are displayed. E1000 - FAILSAFE, Call Support Causes: SORRY E1114 - Temp Ambient Causes: Ambient system temperature is out of acceptable range. E1116 - Temp Memory Causes: Memory has exceeded acceptable temperature and has been disabled to prevent damage to the components. E12nn - xx PwrGd Causes: Specified voltage regulator has failed. E1210 - CMOS Batt Causes: CMOS battery is missing, or the voltage is out of acceptable range. E1211 - ROMB Batt Causes: RAID battery is either missing, bad, or unable to recharge due to thermal issues. E1229 - CPU # VCORE Causes: Processor # VCORE voltage regulator has failed. E1310 - RPM Fan ## Causes: RPM of specified cooling fan is out of acceptable operating range. E1313 - Fan Redundancy Causes: The system is no longer fan-redundant. Another fan failure will put the system at risk of over-heating. E1410 - CPU # IERR Cau