Dell E1711 Error
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 Server Error Posted by Z_Z on 3 Mar 2008 2:36 Hello, We dell poweredge 2950 error codes lost connectivity to a PE2950 earlier today and when we arrived at the data centre the front-panel dell poweredge 2950 e1000 failsafe LCD was orange and saying the following: "E1420 CPU Bus PERR". I power cycled the machine and it came back up with no problems and currently SEEMS
E1624 Ps Redundancy
to be running fine. When I loaded up Dell Server Administrator it shows everything with green check marks and doesnt report any issues. When I look at the log section it shows that there was a critical error (red x) and reports a
Dell 2950 E1422 Cpu Machine Chk
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 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. dell poweredge 2950 e1410 system fatal 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 posts before they are publicly available. Posted by snapohead on 7 Mar 2008 4:16 Yes, it's a parity error with the CPU bus. Although, I'm not sure what would cause this. It may well be a one off (hopefully). The config is written to both the disks and controller, so swapping to an identical system will work.You'll need to import the config from the disks though, as it
Variable??? Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] 2950s work fine. I have had the parity error for over a year with no noticable problems. It is working fine. I did have to
Dell Poweredge 1950 Error Codes
make some IRQ changes to clean up the system. I did these on my i1911 3 errs chk log Dell 1750 test machine, but have made the same changes on my production machine. The changes basically redue the IRQ load from e1614 other cards, like the RAID card, which will reduce the bus's capacity for processing all of the TDM IRQs. It also allocates just one CPU full time for all of the TDM IRQs. The changes http://en.community.dell.com/support-forums/servers/f/956/t/18903018 are below: ref: FYI on zttool output on SMP system --- Results after 56 passes --- Best: 100.000000 -- Worst: 99.987793 -- Average: 99.999564 Only 2 were 99.987793, the 54 others were all 100.000000. I got this by making the changes below on my dual proc Dell 1750. setpci -v -s 01:08.1 LATENCY_TIMER=8 setpci -v -s 00:0f.1 LATENCY_TIMER=8 setpci -v -s 01:04.0 LATENCY_TIMER=8 setpci -v -s 01:02.0 LATENCY_TIMER=8 setpci -v -s 00:0f.2 http://lists.digium.com/pipermail/asterisk-users/2007-November/199883.html LATENCY_TIMER=8 setpci -v -s 01:04.0 LATENCY_TIMER=8 (these are USB, SCSI HW RAID driver, Ethernet, Video, etc. I did not alter ZAP cards, nor any bridges or buses) echo 1 > /proc/irq/17/smp_affinity (Ethernet) echo 1 > /proc/irq/18/smp_affinity (SCSI HW RAID Driver) echo 2 > /proc/irq/20/smp_affinity (TDM) echo 2 > /proc/irq/24/smp_affinity (TE411P) I also turned of the startup of irqbalance. The setpci changes did the most work concerning reaching 100% in zttest. Irqbalance was causing the the processor handling the interrupts of the zap cards to change very often. This would impose a delay during the change and cause the zttest numbers to drop/be inconsistent. Because I turned irqbalance off, the irqs are processed round robin style, which is also not good. Therefore, I hard coded the processor affinity for the zap cards to one proc and all other high load irqs to the other proc. If you have more than 2 procs, you can spread them out even more. If you do not turn off irqbalance, the affinity changes will be overwritten by it. I made these changes on a live system without issue. I set these changes in /etc/rc.d/rc.local to reset them after reboots. -- -- Steven http://www.glimasoutheast.org "Brian Hutchinson"
Favorite Rating: Interpreting the error codes displayed on the system LCD screen of the https://www.novell.com/support/kb/doc.php?id=7921054 Forge applianceThis document (7921054) is provided subject to the disclaimer at https://www.manualowl.com/m/Dell/PowerEdge-2950/Manual/189142?page=23 the end of this document. Environment Forge 1.0 and higher Situation The following articleprovides definitions of the error codes displayed on PlateSpin Forge appliance system LCD screen. The error codes and their definitions are separated into categoriesdepending on the source of the error.Cable dell poweredge and Board Presence - Message Code: "x1Axx" Message Code Message String Message Priority Message Comments Minimum Action Required to Remove Message from LCD System Phase When Event Can Occur? E1A10 PDBPwrCable High PDB power cable to the planar is missing or bad and system will not power on. Failing device is reseated/replaced/repaired. Pre-Post E1A11 dell poweredge 2950 PCIRsrConfig High PCI risers are not configured correctly; some invalid configurations prevent system power on. Failing device is reseated/replaced/repaired. Pre-Post E1A12 PCIRsrMissing High One or all of the PCI risers is missing. This prevents system power on. Failing device is reseated/replaced/repaired. Pre-Post E1A14 SAS Cable A Low SAS cable A is missing or bad. Failing device is reseated/replaced/repaired. Any E1A15 SAS Cable B Low SAS cable B is missing or bad. Failing device is reseated/replaced/repaired. Any E1A16 SAS Cable FB Low Flex bay SAS cable is missing or bad. Failing device is reseated/replaced/repaired. Any E1A17 PwrCable FB Low Flex bay power cable is missing or bad. Failing device is reseated/replaced/repaired. Any E1A18 PDBCtrl Cable High PDB control cable to the planar is missing or bad and system will not power on. Failing device is reseated/replaced/repaired. Any Temperature - Message Code: "x11xx" Message Code Message String Message Priority Message Comments Minimum Action Required to Remove Message from LCD System Phase When
Add to My Manuals! Save this manual to your list of manuals Page 23 highlightsTable 1-6. Code E1711 LCD Status Messages (continued) Text Causes Corrective Actions Remove and reseat the PCI expansion cards. If the problem persists, see "Troubleshooting Expansion Cards" on page 127. Reinstall the expansion-card cage. See "Expansion-Card Cage" on page 78. If the problem persists, the riser card or system board is faulty. See "Getting Help" on page 147. Remove and reseat the PCI expansion cards. If the problem persists, see "Troubleshooting Expansion Cards" on page 127. PCI PERR B## D## The system BIOS has reported a F## PCI parity error on a component PCI PERR Slot # that resides in PCI configuration space at bus ##, device ##, function ##. The system BIOS has reported a PCI parity error on a component that resides in the specified PCI slot. PCI SERR B## D## The system BIOS has reported a F## PCI system error on a component PCI SERR Slot # that resides in PCI configuration space at bus ##, device ##, function ##. E1712 Reinstall the expansion-card cage. The system BIOS has reported a See "Expansion-Card Cage" on PCI system error on a component page 78. that resides in the specified slot. If the problem persists, the riser card or system board is faulty. See "Getting Help" on page 147. E1714 Unknown Err The system BIOS has determined See "Getting Help" on page 147. that there has been an error in the system, but is unable to determine its origin. The system BIOS has reported a PCIe fatal error on a component that resides in PCI configuration space at bus ##, device ##, function ##. The system BIOS has reported a PCIe fatal error on a component that resides in the specified slot. Remove and reseat the PCI expansion cards. If the problem persists, see "Troubleshooting Expansion Cards" on page 127. Reinstall the expansion-card cage. See "Expansion-Card Cage" on page 78. If the problem persists, the riser card or system board is faulty. See "Getting Help" on page 147. See "Troubleshooting a Hard Drive" on page 124. E171F PCIE Fatal Err B##