How to repair iDRAC7 after bad firmware update

Hi.

The BIOS version is already 2.7.0 (which you do not list.) and I am quite certain the iDRAC version was 2.63.60.62 (which you also do not list) before the botched update. I have multiple R320's that I keep all on the same version, that is how I know the previous iDRAC firmware version.

The only updated available to the other R320's through the lifecycle controller appears to be 2.63.60.62 (which is already installed). Do bad things happen when you flash the same version of the firmware over itself?

Do you have any tips for how to successfully flash the iDRAC firmware version 2.65.65.65? The lifecycle controller is unavailable as is the iDRAC interface. I need another way to force an update on the broken system.

Thanks,
Frnot

Hi @DiegoLopez 

I'm disappointed to hear it, but I guess there isn't anything to do about it at this point.

I truly do believe the issue is a bug on Dell's part, as I applied the same update on another system with the same hardware configuration and all the same firmware versions. That machine is still happily running. I guess these are the risks you take when you run enterprise hardware without any warranty.

Edit: I forgot to ask, if I get a new motherboard, will I be able to transfer my iDRAC7 enterprise license to the new board?

Thanks for your help,
Frnot

Before you run off and buy anything, have you tried the SD recovery method? If that isn't something you're familiar with, you can review the linked article.

https://dell.to/3dqwEWF

I forgot to mention in the OP, but yes, I have tried flashing the firmware with an SD card. The light on the back of the server doesn't flash like it is in recovery mode. If I recall, it doesn't light up anymore at all.

The only method I haven't tried is flashing it via console. However, I'm not sure how one would go about that. If you think it would be worth trying, I will look into it some more.

Thanks for your suggestion

do a search on serve the home for "Dell R715 iDRAC6 flash repair" and then look for a link with the text :

iDrac6 Recovery Through TFTP and Serial

it will show you how to use putty and tftp to fix your system.  this just worked for me

The manufacturer is generally responsible for a defect discovered after the product has been placed on the market.
This is a latent (hidden) addiction to this Dell product.
Many have this problem after updating the BIOS, etc. They know the problem and ignore their consumers.
Dell, honestly, must replace the card (or rewrite the ROM) even after the warranty, as the problem is hidden until the update (provided by Dell) or mysterious reboot.
For Dell the cost would be small considering that it would reuse motherboards and just rewrite, but it would be very respectful to the consumer.

Hi @Vacari,

Could PM me your case number or service tag of the system, I'll check if I can reach out any of the support services to help you. 

Hi Joey C,
I appreciate your contact and willingness to help. The service tag is .
Have a nice day!

Hello @Vacari,

Thank you for the Service Tag information. But please, make sure to edit your message and delete the Service Tag information as this should not be public. Do you remember from which iDRAC/BIOS firmware version were you updating from? Was it a very old one? I have seen this happening in the past, it used to happen when updating from a old version to the newest one.

I am afraid I see your system is a PowerEdge T320 out of warranty since 2016. It is not possible to replace the motherboard for this system with the expired warranty. But there are a bunch of this you can try.

First, the Drain Power option: How do I Reset and Drain Power of my Dell PowerEdge Server?

Then you can try to reset the iDRAC: How to reset the internal Dell Remote Access Controller (iDRAC) on a PowerEdge server? 

And of course, the iDRAC Recovery Procedure with firmimg.d7 

You can also try to clear the NVRAM if you are able to identify the jumper and shifting its position (this operation can be different depending on the PowerEdge server).

If none of this possibilities help you to solve the problem, then I am sorry, the only option left is to replace the motherboard.

Regards.

Are you saying you should upgrade one version newer at a time and if the BIOS was updated before the next iDrac update you should update the BIOS first then the idrac etc?

So for example:

March 1 - Bios update

March 2 - iDrac update

You would update the BIOS then if all ok update idrac?  And only update one incremental version at a time?

So you wouldnt want to go from idrac 2.41 to 2.65 etc without updating a BIOS thats two versions out of date basically?

IF BIOS and iDRAC FW on the server is very old then it is recommended to perform staged update instead of directly directly updating latest FW from an old FW.

If there are multiple component of the server which have old firmware level, it is recommended to perform stage update of all components in parallel rather than updating one component to latest by stage update then moving to another component.

Hello,

Unfortunately, I'm not seeing any earlier downloads available. What version is your Lifecycle Controller, though? Depending on what version it is, updating that may fix the problem. If it is below 1.4.2, try the update below and see if it helps.

https://dell.to/39YihZp;

Do you have any of the versions prior to 1.46? mine is on 1.30 and it still says no compatible components when updating  to 1.46 from 1.30