Hello

You should take the system down to minimum to POST. These are the minimum items required to POST:

System board
Risers
Processor (CPU1) with Heatsink
Power Supply
One stick of memory in dual in-line memory module (DIMM) slot A1
Control Panel with cable

If the issue persists with only those items in the system then swap what parts you can. Swap the DIMM in A1 with another DIMM, swap the CPU if you can, and test with the other PSU installed. Also, you can test the PSU in a different slot.

If the problem still persists then you will need to start replacing parts if you do not have spares to test with.

Thanks

Daniel,

Thank you for your suggestions.  I will try these out and let you know how I get on.

Anup.

Hello Daniel,

I tried your suggestions i.e. took the system down to basic configuration as per your list above with no success.  Same errors appeared i.e. E122E and E1000

I tried switching out DIMM and swapped CPUs and PSU.

On a hunch, I started to work in reverse and took out Riser 2 - the error E1A12 PCI Riser not detected came up but not E122E or E1000.

Installed a new Riser 2 card and the E122E and E1000 reappeared.

Installed a new Motherboard, new Riser 1 card and new Riser 2 card and the E122E and E1000 came up.

Uninstalled the new Riser 2 card and the E122E and E1000 disappeared only the E1A12 Riser not detected came up.

Any suggestions you have would be appreciated.

Is there any way to stop the system looking for Riser 2 as we do not have any Expansion cards in Riser 2 and do not see any need for them in the future?

Thank you.

On a hunch, I started to work in reverse and took out Riser 2 - the error E1A12 PCI Riser not detected came up but not E122E or E1000. Installed a new Riser 2 card and the E122E and E1000 reappeared. Installed a new Motherboard, new Riser 1 card and new Riser 2 card and the E122E and E1000 came up. Uninstalled the new Riser 2 card and the E122E and E1000 disappeared only the E1A12 Riser not detected came up.

That doesn't point to a riser issue. When the system is going through it's check list of startup it goes in a particular order. If you don't have a riser installed then it will not make it to the point of reporting any other errors. It will just stop at that point.

Is there any way to stop the system looking for Riser 2 as we do not have any Expansion cards in Riser 2 and do not see any need for them in the future?

No, and I doubt riser 2 is the issue.

Based on what you have swapped/replaced I would lean toward this being a system board issue. The system board contains many components. On older systems voltage regulator modules and power distribution boards are separate components. On most of our newer systems they are built into the system board, so replacing the system board will replace a lot of the power subsystem components.

I would just make sure you that you followed the list correctly before replacing the system board. Make sure you disconnected HDDs, USB devices, etc.

Thanks

The R710 has been in constant use since we got it last year.  We were notified of an extended power outtage, so shut servers down for most of the weeken.  The server came on, I had logged into it, and saw that the virtual servers running in Hyper-V on it were started.  At that point, I left to turn on remaining equipment in the IDF's and came back about 35 minutes later to find that server was off and it refused to come back on.   I am getting the error E1000 error contact support.... Following the little button messages, the system seems to be indicating a 3.3Volt Perc battery.  I ordered one, but I am very concerned, after reading above messages, something else could be wrong.  Until I opened it to try to reseat RISER cards, it had not been opened, reseating cards has had no effect.  The battery 0NU209, is rechargable, so I had hoped leaving the server plugged into power, might recharge it; however, as the gentleman above mentions, the power supply lights are green, there is an orange light on the back, but pressing the button gets it turn off.  I am very interested to learn what the outcome was here... and what to expect.  is the TAG.

Hi encountered the same problem on my R710. I finally concluded after many manoeuvers (like the ones u did above) that it was a  battery somewhere (BIOS, Regulator board, mother board???) that was discharged. I connected the both power units of my R710 to power and I left the server connected during a week (7 days). Curiously, the 7th day it started working when I powered it up. The server is still running fine until today. However, I cannot tell you which battery inside the server was discharged.

did you ever get this resolved, i have the same issue.

PSUs have been replaced, i am now debating a mainboard replacement.

Don't know what happened, after I released the remaining power, (like other guys said press the power button without connecting power cable. I tried couple of times, but didn't work). after my last try, I just simple went through the setting from LCD without changing anything, then press the power on button, it worked! Seems R710 server needs sort of reset setting from LCD for this error, not 100% sure, but it worked for me.  

The LCD board was my problem. Fortunately I have two of these servers and was able to diagnose by component swapping. Once the LCD was disconnected the server comes on via detection of ac power once I disconnect and reconnect the power supply. I am running the server without the LCD while I seek a replacement. 

Important to note that if you shutdown the server via means of a normal Windows shutdown, then you will not be able to power it on again without removing the CMOS battery since the "AC restore power" feature will not have been initialized due to a normal shutdown procedure..

I solved this issue by replace the batteries CMOS and the big one...

Removed all dimms except A1 and B1 for the two processors...
Removed all the Harddisks
Removed all the Powerunits...

then put back the powerunits and power on the system...

E1000 is gone but the E122E stays as error !

Shut down the power again en put the harddisks on 0 and 1 back and turned on the system again...

System is booting.... without any errors...  it's just vague

............ and just after one hour working...... pats, boem quit..... again E1000 and E122E... WT

Hello everyone, anyone! Happy 2020!

My R710 was displaying the same error reported in this thread. I Googled for hours trying to find a solution for the errors "E1000 failsafe voltage error & E122E Onboard Regulator Failed" and did not find anything that worked for me!

My Server has 8 Sticks of RAM and somehow for an unknown reason, one of the sticks was not completely sitting all the way in. 

I figured out after removing all but two sticks of RAM (left A1 and B1) plugged, restarted my server and booted correctly. After reinstalling all the RAM carefully and making sure the sticks were sitting completely in, the server restarted with no errors.

I hope this information is helpful to someone encountering this issue.

Also, sorry for my grammar errors. English is not my first language and was not translated by Google.  

~Viper85

was this the cmos battery?

CMOS battery(System battery) is a small battery used on the server to save BIOS settings. You can refer page 80 (connector 11) for location of this battery and page 142 for details on removing CMOS battery on below link for R710. I am not sure which server you have

https://downloads.dell.com/manuals/all-products/esuprt_ser_stor_net/esuprt_poweredge/poweredge-r710_owner%27s%20manual_en-us.pdf 

https://downloads.dell.com/manuals/all-products/esuprt_ser_stor_net/esuprt_poweredge/poweredge-r710_owner%27s%20manual_en-us.pdf 

I know this thread is old, but wanted to share our experience since my searching landed on this page.  For us, it turned out to be a faulty hard drive.  Once we isolated it, we tried it in multiple servers and it immediately shut them down with the same error codes.