
When I physically went to the server, it was at the BIOS start screen stating “Error Communicating with iDrac. I then, remotely, told the system to reboot it shut down and never came back up.

The system used the Windows iDrac Updater, which stated the update had competed successfully. After upgrading everything, iDrac still was not working, after a few days of messing with it, I found out through piecing together several sites how to force the iDrac in recovery mode to do a TFTP repair, writing a new image to it.

I thought it might have been because I upgrade the iDrac from an old version to the latest, without components like the BIOS or NIC, that the iDrac communicates with, being upgraded as well. This week I had a Dell PowerEdge R510’s iDrac completely die on me I attempted repairs with several utilities that Dell gives out on their site and all of them ended with failure.
