This post is more than 5 years old

1 Rookie

 • 

7 Posts

53565

September 15th, 2015 16:00

R410 red light blinking

I can't find any description in the hardware manual for a red light blinking on the display panel on the front (there's no error message) and a red led blinking below the NIC card on the back of the server.  It's out of warranty so I'm hoping this is a minor problem.  

Community Manager

 • 

9.6K Posts

 • 

43.1K Points

September 15th, 2015 19:00

Try updating the system bios and clearing the logs and we will see if the errors return.

Community Manager

 • 

9.6K Posts

 • 

43.1K Points

September 15th, 2015 18:00

Hi,

An amber light indicates some error. Do you have Server administrator installed so we can look at the logs and see what the error is. It could be as simple as the logs being full.

1 Rookie

 • 

7 Posts

September 15th, 2015 18:00

No, I don't see Server Administrator installed.  Do you mean Server Manager?

Community Manager

 • 

9.6K Posts

 • 

43.1K Points

September 15th, 2015 18:00

1 Rookie

 • 

7 Posts

September 15th, 2015 18:00

What should I do next?

Community Manager

 • 

9.6K Posts

 • 

43.1K Points

September 15th, 2015 18:00

Once you have it installed, run it and go to the system object on the left and then to the logs tab. The system event logs should show whatever error is causing the amber light.

1 Rookie

 • 

7 Posts

September 15th, 2015 18:00

Ok, I'm installing it now.

1 Rookie

 • 

7 Posts

September 15th, 2015 19:00

Under System health, all 3 dimms show the error: 

Single bit warning error rate exceeded Single-bit failure error rate exceeded.

 

1 Rookie

 • 

7 Posts

September 15th, 2015 19:00

I cleared the logs and rebooted.  The errors no longer appear.  yeah!  thanks for your help!

11 Legend

 • 

16.3K Posts

September 15th, 2015 22:00

The errors may return. The SBE log/counter resets after every reboot. So, say it takes two weeks to reach the maximum number of SBE's ... rebooting will clear the error for two weeks - as long it takes to reach that limit again. It could be less than a second or several weeks or even months to reach that limit; pay close attention to the timeframe for future troubleshooting.

Updating the system firmware is the most important piece of preventative and diagnostic maintenance you can do, but if it returns, reseat the DIMM's in question. You should then note which DIMM's the error returns for. Swap the DIMM's to different slots to see if the error follows the slot or the DIMM to make sure you don't have a slot/bank/channel issue and that it is indeed faulty memory.

No Events found!

Top