TechCenter Blogs

How to resolve package errors when updating firmware via WSMAN in iDRAC with Lifecycle Controller


TechCenter is a community for IT professionals that focuses on Data Center and End User Computing best practices. Here you can learn about and share knowledge about Dell products and solutions.

How to resolve package errors when updating firmware via WSMAN in iDRAC with Lifecycle Controller

Upon initiating a firmware update via WSMAN, you are provided a Job class instance. The first thing that happens is the download of the update package. After some time, you might see the Job that looks like this:

       <n1:Message>Package verification failed.</n1:Message>

In case you wonder what this is all about, iDRAC with Lifecycle Controller in Dell PowerEdge servers allows you to update system firmware remotely using the WSMAN interface. If you are not familiar with this yet, I recommend reading this whitepaper

Here, we'll talk about errors you might encounter and what you can do to resolve them. Specifically when you see status as 'Failed'.

If you see one of the following in the Job Message:

  • Package extraction failed.   (ID=RED008)
  • Package verification failed.   (ID=RED007)

More likely, you have provided the incorrect package file format. Notice when you download a firmware update, you have a choice of "Format". One of them is "Update Package for Microsoft Windows" with file having EXE suffix. This is what you want.  There are many file types with EXE suffix so make sure you pick the right one. Also, you might see a 32-bit version and a 64-bit version. You can use either version.

11th generation servers:

Only in 11th generation servers such as R710, you may get "Package verification failed" error message when updating any firmware if the iDRAC version in the system is older than 1.85 (or older than 3.35 on modular servers). To resolve, first update iDRAC to 1.85 (or 3.35 on modular). Reboot will occur and after the update Job goes to completion, you should be able to update other components to the latest.

If you see one of the following in the Job Message:

  • The package is not applicable on this system.    (ID=RED017)
  • The package specified does not match the target.   (ID=RED013)

More likely, you have provided the incorrect package for the component you are trying to update. It can be confusing especially when there are more than one model for a component such as NICs and RAID controllers. To resolve, simply trace back and verify that you picked the correct (a) system model and (b) component type/model when choosing the update package for the component you're trying to update.





To post a comment login or create an account

Comment Reminder

Unrelated comments or requests for service will be unpublished. Please post your technical questions in the Support Forums or for direct assistance contact Dell Customer Service or Dell Technical Support.. All comments must adhere to the Dell Community Terms of Use.

  • This post is very helpful, especially for users who are not too familiar with the various error messages and how to make the appropriate corrections to successfully update their firmware.  There are many Job Status error messages that are generated due to incorrect information provided.  Oftentimes, this incorrect information is due to a mere oversight.  For instance, if you see the "Dell Update Package download failed. (ID=RED006)" Job Message error, then the user either provided the incorrect IP address for the management station or provided the incorrect InstanceID.

  • iDRAC8 V2.20.20.20

    I noticed another reason getting the error "RED008".

    I get this error using "racadm  update -f localFile" if I am also logged in via GUI.

    If I first logoff from GUI and restart the "racadm update -f loaclFile" all works fine.

    BTW: Does anyone know how to upload a firmwareupdate vie wsman/winrm from a local file?