Hi,

Can you try to do a racreset and then run the update again? https://dell.to/2VceAJb

That did not help. I tried a manual reset through the CLI as well as checking the "Reset idrac" box in the GUI of the Update Firmware screen. Same error.

I was able to update the iDRAC manually through the iDRAC GUI. When I re-check the compliance on the baseline, I do not see the updated iDRAC version on this M640.

We had the same problem, I think we went from R640 F/W 3.15 to 4.0.

OME gave us an RED008 on install, in the end we had to unpack the F/W and manually upload the native firmimgFIT.d9 file.

I thought it was an issue with the jump from 3.15 to 4.0, interesting to see others with the same issue.

You would have to manually kick off an Inventory Job for that Service Tag if you manually apply an update (or wait for a scheduled Inventory Job to run)

@Silver-mox @ut_fleet thank you both very much for the responses. After I manually updated the inventory on the blade I updated to 3.36.36.36, re-ran the compliance check, I saw this version in the baseline. Furthermore, I was able to upgrade to 4.0 from OME. So I suppose I'll need to create another catalog/baseline with version 3.3x for any of our servers that'll need that intermediary jump to get to 4.0. 

Not sure if you guys are using Dell Repository Manager, but if you have any tips on creating a repo with older versions of FW, that'd be great. Thanks again for the help here

We are not using the Repository Manager, but it's something I've been wanting to look into.

That said, it would be really, really nice if Dell's own software knew when a device needed an intermediate update to be successful, and just took care of that for us *hint hint*

I'm having an issue updating iDRAC firmware on M640's in OMEnterprise from 3.2x or below to 4.0. The resolution I've found is to update the iDRAC to 3.3x first, and then update to 4.0 through OME, which works.

Question is - how can I create a repository in Dell Repository Manager with iDRAC version 3.34.34.34???

Hi Guys,

We use dells repo manager and it works fine, it allows us to create offline local monthly repos (monthly snap shots of updates), so we can roll backwards or forwards when required.

Its only a shame that it needs to be installed on a windows server. I've asked our account manager a few times to recommend baking it and licence manager into the next version of OME appliance however that might be a reach too far..

Unsure if this helps, but I've noticed that I get a more successful patch deployment if I complete the none reboots updates first, usually the OS and firmware updates, then roll out the BIOS and NIC updates after that normally require a restart.. ok its two passes but seems to work well when OME is playing nicely.

HTH