Users Guide

Message Description/Solution
special, or consequential damages suffered
during or after package customization and
execution.
Attempt to update BIOS or firmware to the
same
version. Update was unnecessary and not
applied.
Re-application of BIOS or firmware DUP serves no purpose.
Inventory operation exceeded specified
timeout.
Inventory operations have time-out limits as defined in the
package’s PIEConfig.xml file. Time‑out durations are in
seconds. If an operation times out, the remainder of the
package update is cancelled.
Execution operation exceeded specified
timeout.
Execution update operations have time‑out limits as defined in
the package. Time-out durations are in seconds. If an operation
times out, the remainder of the package update is cancelled.
/var/lock directory must exist.
Create this system directory to make sure that package
updates do not execute concurrently.
Unable to build a device driver for the
running
kernel because it is not supported on your
system.
Select a compatible DUP and try again.
The Intel IMB driver is currently loaded.
Please unload
the driver before executing.
Unload the Intel IMB driver before installing the selected DUP.
Warning: The shell less command is not
available.
When viewing Release Notes, press space to
continue viewing notes, q to continue DUP
processing.
Continue to view the release notes, or install the less
command from operating system media, and re-execute the
package interactively.
Press 'q' to exit DUP
(--version).
Press 'q' to continue with DUP execution
(dup dup execution).
The Linux DUP framework uses the Linux utility, less, to display
the release notes relevant to the specific firmware or driver
release managed by the DUP. When viewing release notes,
DUP prompts when executed with the below options:
--version: Press 'q' to exit DUP (--version)
All other DUP execution: Press 'q' to continue with DUP
execution.
Warning: Screen widths of less than <numeric
value> can distort the information view.
To optionally correct this, answer < No > to stop package
execution. Increase the width of the terminal window to the
required size and then re-execute the package interactively.
DUP Message Logs
Logging occurs when you run a command for a DUP. The logs maintain information about all update activities. DUPs write to the
Messages log. If you install the same package more than once on the same system, the log is appended. The messages files
directory contain messages about a wide range of events on the system. Therefore, you must scan through the log file to find the
messages that are relevant to DUPs.
28