Dell Update Packages Version 7 4 Users Manual 7.4 User's Guide

2014-11-13

: Dell Dell-Update-Packages-Version-7-4-Users-Manual-117486 dell-update-packages-version-7-4-users-manual-117486 dell pdf

Open the PDF directly: View PDF .
Page Count: 50

Download
Open PDF In Browser	View PDF

Dell Update Packages Version 7.4
User's Guide

Notes, Cautions, and Warnings
NOTE: A NOTE indicates important information that helps you make better use of your computer.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you
how to avoid the problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

Copyright © 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and
intellectual property laws. Dell™ and the Dell logo are trademarks of Dell Inc. in the United States and/or other
jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
2013 - 12
Rev. A00

Contents
1 Getting Started...........................................................................................................7
What’s New in This Release...................................................................................................................7
Dependency...........................................................................................................................................7
Hard Disk Driver Firmware Update....................................................................................................... 8
Supported Operating Systems.............................................................................................................. 8
Prerequisites.......................................................................................................................................... 8
Prerequisites And Features For Systems Running Linux...................................................................... 8
Dell-Qualified and Dell-Enabled Packages.................................................................................... 9
OpenIPMI Requirements................................................................................................................. 9
Prerequisites and Features for Systems Running Windows.................................................................9
Downloading DUPs............................................................................................................................. 10
Installing Device Drivers......................................................................................................................10
Interactive Mode............................................................................................................................10
Non-Interactive Mode...................................................................................................................10
Installation Order of DUPs...................................................................................................................11
Important Tips to Remember for Using DUPs....................................................................................11
Other Documents You May Need.......................................................................................................11
Contacting Dell....................................................................................................................................12

2 Using Dell Update Packages.................................................................................13
Updating Packages Component and System Compatibility..............................................................13
Executing DUPs in Linux Environment............................................................................................... 13
Interactive Mode............................................................................................................................ 13
Non-Interactive Mode................................................................................................................... 13
Verifying the Digital Signature.......................................................................................................14
Executing DUPs On Systems Running Windows............................................................................... 15
Verifying the Digital Signature On Systems Running Windows................................................... 15
Compatibility Concerns.......................................................................................................................15
Effects of Applying the Updates on a Running System......................................................................16
System Reboot Required...............................................................................................................16
Saving Console Output for Linux..................................................................................................16
Delivering DUPs to the Systems......................................................................................................... 16
Updating Multiple Systems............................................................................................................16
Remote Terminal Sessions............................................................................................................ 17
Stand-Alone Systems and Firewalls.............................................................................................. 17
Confirming the Update........................................................................................................................17

3 Performing BIOS and Firmware Updates Using Dell Linux Online
Repository.................................................................................................................... 19
Setting Up or Bootstrapping the Repository......................................................................................20
Creating a Local Mirror................................................................................................................. 20
Installing Firmware Tools....................................................................................................................20
Downloading Applicable Firmware.................................................................................................... 20
Inventory Installed Firmware.............................................................................................................. 20
Updating BIOS and Firmware............................................................................................................. 20
Updating BIOS and Firmware Using CLI....................................................................................... 21
Automatically Update Firmware..........................................................................................................21
Viewing Log Information.....................................................................................................................21

4 Update and Rollback in Lifecycle Controller Enabled Server..................... 23
Update in Lifecycle Controller............................................................................................................23
Rollback in Lifecycle Controller..........................................................................................................23

5 Command Line Interface Reference..................................................................25
Linux CLI Options................................................................................................................................25
Windows CLI Options......................................................................................................................... 27
Exit Codes for CLI............................................................................................................................... 28

6 Linux Troubleshooting.......................................................................................... 31
Known Issues....................................................................................................................................... 31
Diagnostic Tasks Will Not Run While a DUP Reboot is Pending..................................................31
Abnormal Termination of a DUP...................................................................................................31
Mellanox Inventory Collector is Failing.........................................................................................31
Error While Loading Shared Libraries............................................................................................31
Insufficient Free Physical Memory to Load the BIOS Image........................................................31
Kernel Panic While Running Storage Controller Firmware Update Packages............................ 32
Loss of Functionality While Renaming Linux DUPs..................................................................... 32
Yum Repository Management Software Caches Incorrect Repository Metadata...................... 32
DUPs Fail on 64-bit Red Hat Enterprise Linux Operating System...............................................32
DUP Update of Firmware Might Fail While Running in the UEFI Mode.......................................32
Messages............................................................................................................................................. 33
DUP Message Logs..............................................................................................................................39
Message Location..........................................................................................................................39
Messages Log Files........................................................................................................................ 39

7 Troubleshooting for Systems Running Windows........................................... 41
Known Issues....................................................................................................................................... 41
Inventory Failure............................................................................................................................ 41

Messages..............................................................................................................................................41
DUP Message Logs..............................................................................................................................43
Message Location..........................................................................................................................43
Messages Log Files........................................................................................................................44

8 Trusted Platform Module and BitLocker Support..........................................45
9 Microsoft Windows Server 2008 User Account Control..............................47
UAC Restrictions When Running DUPs Remotely.............................................................................48

10 Frequently Asked Questions..............................................................................49

Getting Started

A Dell Update Package (DUP) is a self-contained executable in a standard package format that updates a
single software element on the system.
DUPs are available for the following software components:
•

System BIOS

•

System firmware, also known as the Embedded Systems Management (ESM) firmware

•

Network firmware and drivers

•

Remote Access Controller (RAC) firmware

•

RAID controller firmware and device drivers

•

Software RAID 3.0 (S110) driver

•

Hard Disk Drive

•

Lifecycle Controller

•

Dell Diagnostics and Driver Pack

•

Backplane

•

Tape drives

•

Enclosures

Using DUPs, you can update a wide range of system components simultaneously and apply scripts to
similar sets of Dell systems to bring the system components to the same version levels.
You can use DUPs to:
•

Apply an individual update to a system by using an interactive command line interface (CLI).

•

Install device drivers in interactive and non-interactive modes.

•

Execute multiple updates on the system by using a script comprised of non‑interactive commands
that you write using the CLI feature.

•

Leverage the scheduling of your operating system and software distribution utilities to apply updates
remotely to any number of systems.

What’s New in This Release
The new features for this release include:
•

Support for a new feature, dependency. For more information, see Dependency.

Added support for the following cards:
•

Mellanox ConnectX-3 Dual Port 40 GbE QSFP + Ethernet Adapter.

•

Mellanox ConnectX-3 Dual Port 10 GbE DA/SFP + Ethernet Adapter.

Dependency
DUP supports the following dependencies:

•

Soft Dependencies: The requirements that must be completed for enabling certain features of the
updates are soft dependencies. The required dependent updates must be completed before updating.
(For example, restart the system if required for getting the full features of the dependencies.)

•

Hard dependencies: The requirements that must be completed before an update are hard
dependencies. The hard dependencies must be met for enabling an update.

Hard Disk Driver Firmware Update
The feature hard disk driver supports online firmware updates when connected to a S110 controller. The
hard disk driver online firmware updates also supports when connected to a H200, H300, SAS 5, SAS 6,
PERC 5, PERC 6, H7xx and H8xx servers.

Supported Operating Systems
For Windows:
•

Microsoft Windows Server 2012 R2

•

Microsoft Windows Server 2012, Essentials, Enterprise, datacenter and Foundation x64 Editions

•

Microsoft Windows Server 2008 R2 Foundation, Standard, Enterprise, and data center and web x64
Editions with SP2

•

Microsoft Windows Server 2008 SP2 Foundation, Standard, Enterprise, and data center and web x86
and x64 Editions with SP2

For Linux:
•

SUSE Linux Enterprise Server 10 SP4 (32 and 64 - bit)

•

SUSE Linux Enterprise Server 11 SP3 (32 and 64 - bit)

•

Red Hat Enterprise Linux 5 update 9 (32 and 64 - bit)

•

Red Hat Enterprise Linux 6 update 5 (64 - bit)

•

VMware ESX 4.1 U3

•

Citrix XenServer 6.2

For detailed information on various Dell systems and operating systems on which SUU is supported, see
the Dell Systems Software Support Matrix at dell.com/openmanagemanuals.

Prerequisites
Before you install and use DUPs, ensure that:
•

The system and operating system is supported by DUPs. See Supported Operating Systems for more
information.

•

You have administrator privileges.

Prerequisites And Features For Systems Running Linux
This section lists all the prerequisites and features for systems running the Linux operating system.

Dell-Qualified and Dell-Enabled Packages
Before installing DUPs, read the information provided online and in the download package. Ensure that
the updates you selected are both necessary and appropriate for the system. You may also need to
complete some or all of the following:
•

Add executable privileges to the package filename. Type the following command: chmod +x
packagename.bin.

•

Verify that the package meets the prerequisites for performing an update. To perform the check,
type: ./packagename.bin -c.

•

Utilize one of the following methodologies for performing the updates. The first method is called the
Single update method. In this method, Run the DUP from the command line in interactive mode to
perform the update. The other method is called the Script method. Use this method if you want to run
one or more updates from a script in non-interactive mode.

OpenIPMI Requirements
Certain DUPs may require the latest OpenIPMI Linux device drivers to be installed on the system. If you
are prompted during installation to obtain the latest drivers, see dell.com/support/manuals or download
the latest drivers from the Linux support site.
NOTE: For dependencies and information on running DUPs in the Dell‑provided embedded Linux
environment and in a customized embedded Linux environment and for information on the
required files and tools, see the Dell OpenManage Deployment Toolkit User's Guide at dell.com/
support/manuals.
NOTE: The required minimum kernel version is 2.6.9-42.

Prerequisites and Features for Systems Running Windows
Before installing DUPs, read the information provided online and in the download package. Ensure that
the updates you selected are both necessary and appropriate for the system. You may also need to
complete some or all of the following steps:
NOTE: Run the DUP Check option on the target system and ensure that the system meets the
prerequisites for performing an update.
To run the check from the CLI, type: packagename.exe /c /s.
To run the check from the GUI:
1.
2.

Double-click the .exe file for the DUP you downloaded.
Read the information about the update in the GUI’s scrolling text window.
You can view the log results after running the check option from either the CLI or the GUI. The
default path for the older version prior to DUP 7.2 framework is %SystemDrive%\dell\updatepackage
\log.
The paths of the log files from 7.2 DUP framework are:
Windows Server 2003: %SystemDrive%\Documents and Settings\All Users\Application Data\Dell
\UpdatePackage\log
Windows Server 2008 and Windows Server 2012: %SystemDrive%\Program Data\Dell
\UpdatePackage\log.

Determine that the target system meets compatibility requirements.

For more information, see the Dell OpenManage Legacy Compatibility Guide, the Dell Systems
Software Support Matrix, and Other Documents You May Need.
4.

Create a directory structure for performing the updates.

Determine a methodology for performing the updates. The first method is Single update method. In
this method, Run DUP from the command line in interactive mode to perform the update. The other
method is Script method. Use this method if you want to run one or more updates from a script in
non-interactive mode.
NOTE: DUPs for Windows can also be found in the repository on the Dell Server Updates DVD that
contains the updated BIOS, drivers, and firmware components for Dell systems.

Downloading DUPs
You can download DUPs from support.dell.com.
NOTE: DUPs are also available in the repository folder in the Dell OpenManage Server Update Utility
DVD, along with the Catalog.xml (that contains information about both Windows and Linux DUPs)
and DellSoftwareBundleReport.html files.
To download DUPs from support.dell.com:
1.

Go to support.dell.com and select Support for Work.

Type the Service Tag and click submit.

Select Drivers and Downloads.

Select the operating system, category, and the update importance.
The list of applicable updates are displayed.

Click Download.

To complete downloading the file, follow the instructions on the screen.
NOTE: You can also download a different file format from the File Title column by selecting a file
format for the DUP and clicking it. In case you want to download more than one file type, you must
do it one at a time.
NOTE: You can also download a DUP or group of DUPs using Dell Repository Manager. See the Dell
Repository Manager User's Guide for more information.

Installing Device Drivers
DUPs update BIOS, firmware, drivers, and applications. If a device driver is not present in the system,
DUPs allow you to perform fresh installation of the driver. You can install the driver provided the
supported hardware is present.

Interactive Mode
In an interactive mode, if a fresh installation is applicable, DUP displays a message to install the driver
along with the version of the package. Click Yes to install the package. Installation results are logged in
the DUP Message Logs.

Non-Interactive Mode
When a fresh installation is applicable, executing DUPs with the /s switch installs the driver.
For example, packagename.exe /s and packagename.exe /s /r performs fresh installation of driver DUPs.

NOTE: Not all driver DUPs support fresh installation. See the Dell Update Packages for Microsoft
Windows Operating Systems readme file for the list of drivers that do not support fresh installation.

Installation Order of DUPs
If you are installing multiple DUPs, install the updates that require a reboot at the end. For recommended
installation order see the following table.
Table 1. Update Packages: Recommended Installation Order

Installation Order

System Software Components

Device driver

Device firmware

ESM firmware

LifeCycle Controller

BIOS
NOTE: If you have updated the BIOS, power supply firmware, PERC firmware, SAS expander
firmware, PCIe SSD firmware, Intel, QLogic and Broadcom firmware the changes to the
components take effect only after you reboot the system.
NOTE: For a single reboot, you must install the ESM firmware update before the BIOS update.

Important Tips to Remember for Using DUPs
•

Prepare repair disks before you perform any updates.

•

Download the currently installed version of drivers, BIOS, and firmware, so that you have a backup
plan in case of any issues.

•

Make sure that you have a backup of operating system files or system configuration files stored on a
system other than the one you are updating.

•

Make sure that the updates are planned for and performed by the system administrator who knows
which applications could be affected.

•

Before updating all systems, perform the upgrade on one nonessential system to test the update.

•

Do not run other applications while executing DUPs.

•

On a Microsoft Hyper-V virtual machine, while updating the host operating system components,
ensure that the guest operating systems are not running.

•

Do not shut down the system while an update is in progress.

•

Make sure that the system reboots without power interruption after performing a BIOS update.

•

Do not close any terminal console windows used for performing the DUP CLI execution, while DUP
executions are in progress.

Other Documents You May Need
To access other documents go to dell.com/support/manuals and select the product or use the direct
link on the Dell Systems Management Tools and Documentation DVD.
•

Dell OpenManage Legacy Compatibility Guide

NOTE: You do not need to install Dell OpenManage Server Administrator on the system to run
DUPs.
•

Dell OpenManage Server Update Utility User's Guide

•

Dell OpenManage Deployment Toolkit (DTK) User's Guide

•

Dell OpenManage IT Assistant User’s Guide

•

Dell Systems Software Support Matrix

•

Glossary

•

Dell Repository Manager Users Guide

•

Man page for DKMS from linux.dell.com/dkms/manpage.html

Contacting Dell
NOTE: If you do not have an active Internet connection, you can find contact information on your
purchase invoice, packing slip, bill, or Dell product catalog.
Dell provides several online and telephone-based support and service options. Availability varies by
country and product, and some services may not be available in your area. To contact Dell for sales,
technical support, or customer service issues:
1.

Visit dell.com/support

Select your support category.

Verify your country or region in the Choose a Country/Region drop-down menu at the top of page.

Select the appropriate service or support link based on your need.

Using Dell Update Packages

Dell provides a number of aids to help you determine whether or not the system requires an update. You
can download DUP from dell.com/support/manuals. For more information, see Downloading DUPs .
NOTE: DUPs currently does not support every device type. DUPs will be available on additional
devices in future releases.

Updating Packages Component and System
Compatibility
You can run the DUP and read the summary information. This information is provided to help you
determine whether the update is appropriate for the system and specific environment.

Executing DUPs in Linux Environment
You can run DUPs from the console in two modes:
•

interactive

•

non‑interactive

Interactive Mode
In the interactive mode, you issue a command, and the interface prompts you for permission to continue
executing the command. When you execute a package in this mode, it first displays a scrollable view of
the release notes for the package. You may view these notes before continuing with the execution of the
package.
DUP may be executed from a local console attached to the target system or from an administrator’s
workstation by using a remote shell, such as ssh. Once a package has been delivered to the target
system, administrators can execute the package by performing the following:
•

Type ./packagename.bin from the working directory.
NOTE: Where packagename is the model and component‑specific name of the package

•

Ensure that the .bin file has the appropriate permissions set and that a user account with root
privileges to executes the update.

•

The progress and status is displayed to the console (stdout) and log its activity to /var/log/messages.

Non-Interactive Mode
Non‑interactive mode is essential when executing a script for applying DUPs to multiple systems. When
applying DUPs to multiple systems, you cannot answer yes or no during script execution.
•

Type ‑q for non‑interactive mode.

•

‑f for force.

•

‑r for reboot if a reboot is required for the type of update being performed.

In the following command example, the command applies a BIOS DUP without any user confirmation,
forces the execution in the case of a downgrade from a more recent BIOS version, and reboots the
system after the DUP is applied. This command is executed provided the DUP satisfies all the system and
version requirements.
./PE2850-ESM_FRMW_LX_R92394.bin -q -f -r
For more information on the command line interface (CLI), see Command Line Interface Reference.

Verifying the Digital Signature
A digital signature is used to authenticate the identity of the signer of an Update Package and to certify
that the original content is unchanged. Digital signature of DUPs provide a reliable and trustful method of
authentication.
Verifying the digital signature ensures that the original Update Package was received correctly and that
the content has not been modified since it was signed.
NOTE: Verifying the digital signature is applicable for systems running Windows and Linux.

Verifying the Digital Signature on Systems Running Linux
If you do not already have it installed on your system, you must install the Gnu Privacy Guard (GPG) to
verify a Linux DUP digital signature. To use the standard verification procedure, perform the following
steps:
1.

Get the Dell Linux public GnuPG key, if you do not already have it. You can download it by navigating
to lists.us.dell.com and clicking the Dell Public GPG key link.

Import the public key to the gpg trust database by running the following command: gpg --import

NOTE: You must have a private key to complete the process.

To avoid a distrusted-key warning, validate the public key by its fingerprint before you use it.
a) Type the following command: gpg --edit-key 23B66A9D
b) In the GPG key editor, type fpr. The following message appears: pub 1024D/23B66A9D
2001-04-16 Dell, Inc. (Product Group) Primary
key fingerprint: 4172 E2CE 955A 1776 A5E6 1BB7 CA77 951D 23B6 6A9D. If the
fingerprint of the imported key is the same as the key owner's, you have a correct copy of the
key. You can verify the key's owner in person, over the phone, or by any other means that
guarantees that you are communicating with the key's true owner.
c) While still in the key editor, type sign.
d) Answer the list of trust-validation questions that appear and create a passphrase to use as the
secret key. You must import and validate the public key only once.

Obtain the Linux DUP and its associated signature file from dell.com/support/manuals/downloads.
NOTE: Each Linux DUP has a separate signature file, which is displayed along with the DUP. You
need both the DUP and its associated signature file for verification. By default, the signature file
is named the same as the DUP filename with a sign extension.

Verify the DUP using the following command: gpg --verify .

Executing DUPs On Systems Running Windows
To run DUPs from the interactive graphical user interface (GUI), perform the following steps. This
procedure applies to all Update Packages.
1.

Execute the DUP by double-clicking the filename from within Windows Explorer.

Read the update information displayed in the DUP window.

Check the DUP inventory report for Package version and installed versions of component.

Click Install to install the DUP.

Reboot the system, if necessary.

To execute DUPs from the command line interface (CLI), see Command Line Interface Reference.

Verifying the Digital Signature On Systems Running Windows
To verify the Update Package’s digital signature:
1.

Start Windows Explorer and locate the Update Package whose digital signature you want to verify.

Right-click the filename.

Click Properties in the pop-up menu.

In the Properties window, click the Digital Signatures tab. If this tab is not displayed, the Update
Package is not signed.

Select the signature from the signature list, and click Details.
The Digital Signature Details window appears.
NOTE: The signature is not verified until you click Details.

Read the digital signature information to verify that the digital signature is OK.

Click OK to close the window.

Compatibility Concerns
DUPs are designed to confirm that all prerequisites are satisfied before applying the update to the system.
Each DUP checks to ensure the following:
•

The logged-on user has root privileges.

•

DUP to be applied in the command is compatible with the target system and the operating system
running on a system.

•

The device associated with the DUP is present on the system.

•

The minimum required versions of related system software are running on the system.

DUPs are designed with built-in error handling capabilities to ensure that the preceding requirements are
validated. If the conditions are not met, no update occurs. DUPs also check for dependencies between
BIOS and certain ESM packages. The application design allows you to create groups of DUPs and apply
them to a wide range of systems. Additionally, if you only want to verify that a given package can be
applied to the system, you can invoke the package by using the following CLI command:
./Packagename.bin ‑c for Linux
packagename.exe /c /s for Windows

This command executes the dependency rules within the DUP, issues any warnings, exits without
applying the update to the system, and writes the results to the console. You can also use the DUP to set
an exit code to perform decisions within the scripts.

Effects of Applying the Updates on a Running System
This section describes all the effects of applying the updates on a running system.

System Reboot Required
Certain packages, such as those that update the system BIOS, require a reboot for the new software to
take effect. After you apply an update that requires a reboot, you must restart the system to complete the
update.
You have the option of choosing to defer the reboot until another time as long as you do not turn off the
system. This feature is primarily intended to allow you to apply any number of updates together and
perform the system reboot after the last update has been applied. If this process is interrupted, for
example, through a power interruption, you must repeat the updates. Therefore, it is recommended that
you schedule updates for a time when the reboot can take place immediately after you apply the last
update.

Saving Console Output for Linux
As the DUPs are executed, messages are printed to the console. To redirect console output, use the
following syntax with interactive commands:
./packagename.bin|tee -a logname.lo
The |tee specifies the output from the DUP to be sent to both the console and to a log file. The ‑a switch
ensures that the output is appended to a file, protecting any previous log file output from being
overwritten.

Delivering DUPs to the Systems
The DUP application does not provide scheduling and delivery of the packages to multiple systems. You
must rely on third‑party or native operating system applications to accomplish script execution and
distribution on multiple systems.

Updating Multiple Systems
For large environments that consists of multiple systems, remote software distribution applications
provide the best solution. Many of these tools can effectively leverage the DUP and provide the
convenience of installing and updating a variety of software, such as operating systems and applications,
in a heterogeneous environment.
Network file shares also are an effective method of making DUP accessible in a distributed environment.
When a DUP begins execution, it first copies the contents of the package to a temporary location on the
local drive of the system. This process ensures that the update can be completed even if the connection
to the network share is lost for any reason.

Remote Terminal Sessions
In today's highly distributed environment, it is common for IT organizations to use remote access
solutions, such as Microsoft Terminal Services, to gain access to their remote systems. You may use this
type of solution to run DUPs.
NOTE: If the terminal session is disconnected during a NIC driver update, you will need to reconnect and verify that the update has completed successfully.

Stand-Alone Systems and Firewalls
For systems that are not connected to the Internet or that have firewall which block user downloads, you
need to download DUP from dell.com/support by using a system that has Internet access, such as
desktop or portable computer. You can make DUP available to the system by copying them onto
removable media that the system supports.

Confirming the Update
To ensure that the DUPs were applied to the system, review the console output that was generated
during execution. For detailed information about the messages, see Linux Troubleshooting.
If you want to revert to a previous (older) version of the software after updating to a newer version, you
must download the appropriate DUP from dell.com/support/manuals and install it.
For Systems Running Linux:
To install the previous version from a script, use -q (unattended) mode. In addition, you must use the CLI
-f option, which forces the downgrade.
NOTE: If the system loses power during the update process, you must perform the updates again.
NOTE: DUPs for Linux can also be found in the repository on the Dell OpenManage Server Update
Utility DVD that contains the updated BIOS, and firmware components for Dell systems. For more
information, see the Dell OpenManage Server Update Utility User's Guide available at dell.com/
support/manuals.
For Systems Running Windows:
To install the earlier version from a script, use the /s (unattended) mode. In addition, you must use the
CLI /f option, which forces the downgrade. You are prompted to ensure that you want to install an earlier
version.

Performing BIOS and Firmware Updates
Using Dell Linux Online Repository

You can update the system to the latest version or to a specific version of the BIOS and firmware available
in the Dell Linux online repository. The updates are available in the RPM Package Manager (RPM) format.
RPM is a standard package format for software updates specific to Linux operating systems. You can
inventory the system, scan the repository for matching firmware with newer version using repository
management software such as Yellowdog Updater, Modified yum, rug, and zypper. The repository
management software supports the following operating systems:
•

yum: Red Hat Enterprise Linux 5.9 (x86 and x86_64), Red Hat Enterprise Linux 6.5 (x86_64)

•

Rug: SUSE Linux Enterprise Server 10 SP4 (x86_64)

•

Zypper: SUSE Linux Enterprise Server 11 SP3 (x86_64)

Yum supports Integrated Dell Remote Access Controller (iDRAC) Service Module. The Integrated Dell
Remote Access Controller (iDRAC) Service Module is a lightweight optional software application that can
be installed on Dell 12G and later server. The iDRAC Service Module complements iDRAC interfaces –
Graphical User Interface (GUI), RACADM CLI and Web Service Management (WSMAN) with additional
monitoring data. You can configure the features on the supported operating system depending on the
features to be installed and the unique integration needs in a work environment. The services provided by
the iDRAC Service Module are:
•

Displaying operating system information

•

Replication of log in Lifecycle Controller into operating system

•

Automatic System Recovery
NOTE: By default, Yellowdog Updater, Modified (yum), VMware Update Manager (VUM) and Citrix
XenServer supplemental pack are enabled on iDRAC service module.

•

iDRAC Service Module is supported on all 12G servers (64-bit operating system) with iDRAC version
later than 1.50.50.

Firmware-tools are used to update BIOS and firmware on the system. With firmware-tools, the RPMbased BIOS and firmware updates are available along with the packages containing the tools to install
those updates. Using a repository management software, you can easily update the BIOS and firmware to
the latest or specific versions on the system.
The latest BIOS and firmware updates are available at the Dell OM Linux Repository website at
linux.dell.com/repo/hardware/latest/.
To update BIOS and firmware for the system:
•

Setup or bootstrap the repository.

•

Install firmware-tools.

•

Download applicable firmware.

•

Update BIOS and firmware.

Setting Up or Bootstrapping the Repository
To setup or bootstrap the Dell Linux online repository, run the following command at the command
prompt:
•

wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash | bash

•

The system is configured to access the Dell Linux online repository using supported repository
management software. The Dell GPG keys and libsmbios (BIOS library) are also installed.

Creating a Local Mirror
To create a local mirror of the Dell Linux online repository, use the following command:
rsync://linux.dell.com/repo/hardware
NOTE: The Dell Linux repository contains .htaccess files. To enable Apache system to recognize
these, you must allow overrides for the directory that contains the Dell Linux repository.

Installing Firmware Tools
Depending on the repository management software you are using, run one of the following commands
to install firmware-tools:
•

For yum: yum install dell_ft_install

•

For rug: rug install dell_ft_install

•

For zypper: zypper install dell_ft_install

Downloading Applicable Firmware
Depending on the repository management software you are using, run one of the following commands
to download applicable firmware:
•

For yum: yum install $(bootstrap_firmware)

•

•

For zypper: zypper install $(bootstrap_firmware)

Bootstrap firmware is a process where the latest BIOS or firmware update RPMs for the system are
downloaded from the repository, along with the utilities necessary to inventory and apply updates on the
system.

Inventory Installed Firmware
You can also inventory the system for the list of existing versions of BIOS and firmware using the
inventory_firmware CLI command.

Updating BIOS and Firmware
After you have installed the firmware-tools and downloaded the applicable BIOS and firmware updates,
you can update the BIOS and firmware on the system using the CLI or the GUI.

Updating BIOS and Firmware Using CLI
1.

Run update_firmware to inventory the system and scan the repository for new versions of the
components.
This command provides information about the existing versions of components on the system and
the list of component versions that are available to be installed.

Run update_firmware --yes to install all applicable BIOS and firmware updates on the system.

Once the devices are updated, the execution success message is displayed.

Automatically Update Firmware
By default, installing a BIOS or firmware RPM does not apply the update to the hardware. The update is
manually applied using the update_firmware command. However, you can automatically update the
hardware during RPM installation by configuring the /etc/firmware/firmware.conf file.
To automatically install BIOS and firmware updates, ensure that rpm_mode is set to auto in the
firmware.conf file as shown:
[main]
# Automatically install BIOS updates when an RPM BIOS Update file is installed
# values: 'auto', 'manual'
# default: 'manual'
rpm_mode=auto

Viewing Log Information
The log information is stored in the firmware-updates.log file located at /var/log/ folder.

Update and Rollback in Lifecycle
Controller Enabled Server

Dell Lifecycle Controller Enabled Server is an embedded configuration utility that enables systems and
storage management tasks from an embedded environment throughout the life cycle of a system..
Residing on an embedded flash memory card, Lifecycle Controller is similar to a BIOS utility in that it can
be started during the boot sequence and can function independently of an installed operating system.
Using Lifecycle Controller, you can quickly identify, download, and apply system updates without
searching the Dell Support website. You can also configure the system BIOS and system devices (such as
NIC, RAID, and iDRAC), deploy an operating system, and run diagnostics to validate the system and the
attached hardware.
NOTE: Certain platforms or systems may not support the full set of features provided by Lifecycle
Controller.

Update in Lifecycle Controller
You can update the system BIOS, iDRAC firmware, power supply firmware, RAID firmware, and NIC
firmware. Use the wizard to display a list of available updates for the system Platform Update
You can define a location to search for available updates from the following options:
•

The Dell File Transfer Protocol (FTP) system (ftp.dell.com). You can use a proxy system to access
ftp.dell.com.

•

A USB device. When accessing updates from a local USB device, the USB device must be plugged in
before selecting the Platform Update option in Lifecycle Controller. For more information on
updating the platform, see the Dell Lifecycle controller User Guide available at dell.com/support/
manuals.

After you select the updates you want to apply, Lifecycle Controller downloads and applies the updates. If
you decide to update any device in Lifecycle Controller, the update package of the corresponding device
is downloaded. After successfully downloading, verifying, and extracting the DUPs, the corresponding
devices are updated. If the update fails, error messages are displayed.

Rollback in Lifecycle Controller
You can update any component, for example BIOS, in both Lifecycle Controller and the operating system
environment. After the update is successful in the operating system environment using DUPs, you can
enter Lifecycle Controller and revert the component to the version that was previously installed before
the update occurred.
Lifecycle Controller supports platform firmware rollback to the previous version. If the operating system
has a non–functioning application because of a BIOS or firmware flash, reboot to Lifecycle Controller
and roll back to the previous version.

NOTE: Only BIOS and firmware can be rolled back. The Lifecycle Controller application, the Dell
Diagnostics application, and drivers required for operating system installation cannot be rolled back
to an earlier version.
If you have updated the BIOS or firmware of the system only once, the rollback feature offers the option
of reverting to the factory-installed BIOS or firmware images. If you have updated the BIOS or firmware
to multiple versions, the factory-installed images are overwritten and you cannot revert to them.
NOTE: Rollback is not supported in the operating system environment. To enable rollback, ensure
that you boot into Lifecycle Controller.

Command Line Interface Reference

You can display information about the CLI options by typing the DUP name and either -h or --help at a
command line prompt.
The console displays all of the command line options and provides help for each choice.

Linux CLI Options
For a list of CLI options for systems running Linux, a description of each option, and the command syntax
see the following table:
Table 2. Linux CLI Options: Usage

CLI Option

CLI Task Description

(no option; run command
without options)
Run commands in an interactive
mode.

Apply the DUP in an interactive
./packagename.bin
mode; the DUP interacts with the
user if it is valid.

-h or --help

Display command line options
and help information.
The --help option executes
before all other -- options.

Help option

Command Syntax

./packagename.bin -h
./packagename.bin --help

NOTE: This option exits after
displaying the requested
information; no DUP
verification or updates
occur.
-c
Check option
-f
Force option

Determine if the update can be
applied to the target system.

./packagename.bin -c

Force a downgrade or update to
an older version. The ‑q option is
required when using the ‑f
option.

./packagename.bin -q ‑f

NOTE: Before downgrading
the software to a previous
version, refer to the
documentation of the
previous version.
--list
List package contents option

Display all files that are contained ./packagename.bin --list
in the DUP.

CLI Option

CLI Task Description

Command Syntax

NOTE: This option exits after
displaying the requested
information; no DUP
verification or updates
occur.
-q
Run command in non-interactive
mode
-r
Reboot option

Execute the DUP silently without
user intervention.

./packagename.bin -q

Reboot the system, if required,
after performing the update. The
reboot does not occur:

./packagename.bin -r ‑q

•
•

If the DUP fails or is not
applicable to the target
system.
If the DUP does not require
the target system to be
rebooted.
NOTE: The -q option is
required with this option.

--rebuild
Rebuild option
-v,--version
Display version option

Automatically rebuild a DUP to
support Linux operating system
kernels in addition to the
supported kernels.

./packagename.bin --rebuild

Display the version, fixes,
./packagename.bin -v
enhancements, and release date; ./packagename.bin --version
lists systems to which the DUP
can be applied.
NOTE: This option exits after
displaying the requested
information; no DUP
verification or updates
occur.

--extract

Extract all files contained in the
DUP to the path you specify. If
the directory specified in the path
does not exist, it is created.
If the path contains spaces, use
quotation marks around the
value.
NOTE: This option exits after
extracting the requested
files; no DUP verification or
updates occur.

./packagename.bin --extract /
update
./packagename.bin --extract "/
update files"

Windows CLI Options
For a list of the CLI options for systems running Windows, a description of each option, and the
command syntax see the following table.
NOTE: DUPs for Microsoft Windows operating systems cannot display output at the command line
because they are Windows GUI applications. All output information is written to a log file. For
information on log files, see DUP Message Logs.
Table 3. Windows CLI Options: Usage

CLI Option

CLI Task Description

Command Syntax

/? or /h
Help option

Displays command line options
and help information.

packagename.exe /?

Determines if the update can be
packagename.exe /s /c /l=c:
applied to the target system.
\pkg.log
The /s option is required with this
option.
Options /f, /e, and /r are not valid
with this option.
When you click Install in the
graphical user interface (GUI)
mode, the same checking process
is performed.

Check option

/e=
Extract option

/f
Force option

packagename.exe /h

Extracts all files contained in the
packagename.exe /s /e=c:\update
DUP to the path you specify. If the packagename.exe /s /e="c:
directory specified in the path
\update files"
does not exist, it is created.
If the path contains spaces, use
quotation marks around the
value.
The /s option is required with this
option.
Options /f, /c, and /r are not valid
with this option.
Allows downgrade of the software packagename.exe /s /f /l=c:
to a previous (older) version.
\pkg.log
The /s option is required with this
option.
Options /e and /c are not valid
with this option.
NOTE: Before downgrading
the software to a previous
version, see the
documentation for the
previous version.

/l=
Log option

Appends logged messages to a
specified ASCII file; creates a new
file if one does not exist.

packagename.exe /s /l=c:\pkg.log
packagename.exe /s /l="c:\Update
Log\pkg.log"

CLI Option

CLI Task Description

Command Syntax

NOTE: If the file name
contains spaces, use
quotation marks around the
value.
The /s option is required with this
option.
/r
Reboot option

Reboots the system, if required,
after performing the update. The
reboot does not occur:
•
•

packagename.exe /s /r /l=c:
\pkg.log

If the DUP fails or is not
applicable to the target system.
If the DUP does not require a
reboot.

The /s option is required with this
option.
Options /e and /c are not valid
with this option.
/s
Silent option

Executes the update silently
packagename.exe /s /l=c:\pkg.log
without user intervention. When /s
is not specified, the DUP is
launched in GUI (interactive)
mode.
The /s option is required when
using the /e, /f, /c, /l, and /u
options.
NOTE: Using the /s option
causes all output to be
written to log files.

/u=
Unicode Log option

Appends logged messages to a
packagename.exe /s /u=c:\pkg.log
specified Unicode file; creates a
packagename.exe /s /u="c:
new file if one does not exist. If the \Update Log\pkg.log"
file name contains spaces, use
quotation marks around the
value.
The /s option is required with this
option.

Exit Codes for CLI
Exit codes help you determine and analyze the execution results after you run DUPs.
After running DUPs, see the exit codes described in the following table.
Table 4. Exit Codes

Value

Message Name

Display Name

Description

SUCCESSFUL

Success

The update was successful.

UNSUCCESSFUL
(FAILURE)

Unsuccessful

An error occurred during the update process;
the update was not successful.

Value

Message Name

Display Name

Description

REBOOT_REQUIRED

Reboot required

You must restart the system to apply the
updates.

DEP_SOFT_ERROR

Soft dependency error Some possible explanations are:
•
•

You attempted to update to the installed
version of the software.
You tried to downgrade to a previous
version of the software.

To avoid receiving this error, provide the /f
option.
4

DEP_HARD_ERROR

Hard dependency
error

The required prerequisite software was not
found on the system. The update was
unsuccessful because the system did not
meet BIOS, driver, or firmware prerequisites
for the update to be applied, or because no
supported device was found on the target
system.

QUAL_HARD_ERROR

Qualification error

The DUP is not applicable to the system.
Some possible explanations are:
•
•
•

The operating system is not supported by
the DUP.
The system is not supported by the DUP.
The DUP is not compatible with the
devices found in your system.

A QUAL_HARD_ERROR cannot be suppressed
by using the /f switch.
6

REBOOTING_SYSTEM Rebooting system

The system is being rebooted.

RPM_VERIFY_FAILED

The Linux DUP framework uses RPM
verification to ensure the security of all DUP
dependent Linux utilities. If security is
compromised, the framework displays a
message and an RPM Verify Legend, and then
exits with exit code 9.
RPM produces output only if there is a
verification failure. The format of the output
is:
.SM5DLUGT 'utility name'

RPM verification has
failed

For example, if the fmt command is
compromised, the framework displays the
message:
rpm verify
failed: .M...... /usr/bin/fmt
RPM Verify Output Legend:
.‑ Verification test passed
S‑ File Size differs
M‑ Mode differs (includes permissions and file
type)
5‑ MD5 sum differs

Value

Message Name

Display Name

Description
D‑ Device major/minor number mismatch
L‑ ReadLink(2) path mismatch
U‑ User ownership differs
G‑ Group ownership differs
T‑ mTime differs

UPDATE_SUCCESSFU Update is successful.
L_SOFT_DEPEDENCY Soft Dependencies
_NOT_MET
are not met.

The applied update is successful. The soft
dependencies, which enable all the features of
the updated software are not met. Apply the
dependent updates for getting the full
features.

REBOOT_REQUIRED_ Update is successful.
SOFT_DEPENDENCY_ Reboot is required.
Soft Dependencies
NOT_MET
are not met.

The update is successful. Reboot is required
to complete the update. The soft
dependencies, which enable all the features of
the updated software are not met. Apply the
dependent updates after reboot for getting
the full features.

Linux Troubleshooting

This section describes possible troubleshooting steps related to Linux Operating System.

Known Issues
The issues listed below are known issues and corrective actions for Dell Update Packages (DUPs) for
Linux operating systems. Also see the corresponding Readme for Linux at dell.com/support/manuals.
NOTE: The Readme file, which is available at dell.com/support/manuals, provides the latest
information regarding known issues.

Diagnostic Tasks Will Not Run While a DUP Reboot is Pending
If you try to run a diagnostic task and there are pending updates, the diagnostic task fails.
To resolve this, complete all pending updates, reboot the system and then run a diagnostic task.

Abnormal Termination of a DUP
A DUP may stop abruptly due to a power outage or abnormal termination.
To resolve this:
1.

Remove the lock file from the lock folder.

Type the command: rm -f /var/lock/.spsetup.

Run the DUP again to reapply the update.

Mellanox Inventory Collector is Failing
If you run the Mellanox Inventory Collector after running the Broadcom Inventory Collector, then
Mellanox Inventory Collector fails.
To resolve, run the Mellanox Inventory Collector prior to Broadcom Inventory Collector or install
Mellanox Ethernet drivers.

Error While Loading Shared Libraries
The following error may be displayed when you load shared libraries. Error while loading shared
libraries: libstdc++.so.5: Cannot open shared object file: No such file or directory.
To install the compatibility libraries, using the following command: RPM -ih compat-libstdc+
+-33-3.2.3-47.3.i386.rpm.

Insufficient Free Physical Memory to Load the BIOS Image
BIOS updates require enough free physical memory to load the entire BIOS image into the physical
memory. If there is insufficient free physical memory available on the system to load the BIOS image, the

DUP for the BIOS may fail. To resolve this, the BIOS can be updated using the Diskette method, run the
DUP after adding more memory or immediately after a reboot.

Kernel Panic While Running Storage Controller Firmware Update Packages
Linux systems running one or more applications that interact with SCSI devices in certain ways are known
to cause a kernel panic situation.
To resolve this, stop the Dell OpenManage Server Administrator and Dell OpenManage Server
Administrator Storage Management Service before running the storage controller firmware DUPs.

Loss of Functionality While Renaming Linux DUPs
Linux DUPs can be executed even if they are renamed, but some functionality is lost. Renamed Linux
DUPs with extensions that are in the Linux MIME (Multimedia Internet Message Extensions) database
could fail to execute from various X‑Windows desktops, for example GNOME. In this case the desktop
issues a file open error message indicating that the DUP cannot be opened. This occurs if a DUP with an
uppercase .BIN extension is renamed to a lowercase .bin extension. The .bin extension has an entry in
the Linux MIME database which leads to the file open error.

Yum Repository Management Software Caches Incorrect Repository
Metadata
To resolve this
Run the yum clean all command to remove old metadata and retry updating the firmware.

DUPs Fail on 64-bit Red Hat Enterprise Linux Operating System
If DUPs fail to run on a 64-bit Red Hat Enterprise Linux operating system, manually install the following
RPMs:
•

compat-libstdc++-33.i686

•

libstdc++-4.4.4-5.el6.i686

•

libxml2.i686
NOTE: The RPMs are available on the Red Hat Enterprise Linux 6.3 x64 media.

DUP Update of Firmware Might Fail While Running in the UEFI Mode
When Red Hat Enterprise Linux 6 or SLES 11 is installed and booted in a UEFI environment, flashing
firmware using DUP might fail after DUP reboots the system.
DUP relies on a warm reset to enable firmware flashing. In the UEFI mode, the kernel by default performs
a cold reset.
Boot the system with the reboot=k kernel command line option to enable the firmware flashing
procedure to complete successfully. You could add this to /etc/grub.conf to be persistent across
reboots.
NOTE: Using the reboot=w option as documented in the Linux Kernel documentation might cause
a Kernel Panic to occur on Red Hat Enterprise Linux 6 while the system shuts down.

Messages
For descriptions and solutions to messages that you may receive when running DUPs, see the following
table:
Table 5. Update Packages Message Information

Message

Description/Solution

This Update Package is not compatible
with your
system Your system:
System(s) supported by this package:

Select a compatible DUP, and try the update
again.

This Update Package cannot be executed
under the current
operating system.

DUPs supports Linux operating systems and
kernels supported by the -- rebuild option.

This Update Package is not compatible
with any of
the devices detected in your system.

Select a compatible DUP for the device(s) you
want to update, and try again.

The prerequisite software version for
this update
was not found.
Software application name:
Current version:
Required version:

The DUP you selected cannot be installed
because a prerequisite requirement was not met.
Install the appropriate prerequisite software
version, and try the update again.

You must use the -f option to continue
with the
update in the non‑interactive mode.

The version of this DUP is either older than or the
same as the version installed. To apply the DUP,
you must force execution.

The software to be updated was not
found. Install
the following software, and then retry
the update. Software name:
Required version:

The system does not contain the software that
matches the DUP.

The version of this Update Package is
newer than
the currently installed version.
Software application name:
Package version: Installed
version:

This message confirms the version of the
currently installed software before the update is
performed.
(Using the interactive mode) Type Y or N when
prompted to continue.
(Using the CLI) Specify the -f option.

The version of this Update Package is
older than
the currently installed version.
Software application name:
Package version: Installed
version:

The DUP you selected cannot be installed
because a newer version of the software already
exists on the system. To install the older version:
(Using the interactive mode) Type Y or N when
prompted to continue.
(Using the CLI) Specify the -f option.

The version of this Update Package is
the same
as the currently installed version.
Software application name:

The DUP you selected cannot be installed
because the same version of the software already
exists on the system.
(Using the interactive mode) Type Y or N when
prompted to continue.

Message

Description/Solution

Package version:
Installed version:

(Using the CLI) Specify the -f option.

This package is not compatible with
the version
of Server Agent on your system. You
must upgrade to Server Administrator
before running this package.

Use an alternative update method from dell.com/
support/manuals.

This update package requires an
OpenIPMI driver.
Currently no OpenIPMI driver is
installed on the system.

The DUP you selected cannot be installed
because you do not have the OpenIPMI driver
installed on the system.

In order to assist in the ,
you can download and install a version
of the OpenIPMI driver that meets
the minimum version requirement from
dell.com/support/manuals. The minimum
version required is .

Download and install the minimum required
OpenIPMI driver from dell.com/support/manuals.

This Update Package requires a newer
version of
the OpenIPMI driver than is currently
installed on the system, which is
version .

The OpenIPMI driver that is currently installed on
the system does not meet the minimum version
requirements of the selected DUP.

Kernel source for the running kernel
is not installed,
and the currently installed OpenIPMI
driver RPM was installed without the
kernel source for the running kernel.
In order to install OpenIPMI driver
modules for the running kernel that
meet the minimum version requirement,
you must install kernel source for the
running kernel, and then use DKMS (see
man page for dkms) to install and
build OpenIPMI driver modules for the
running kernel. To install kernel
source for the running kernel, install
the RPM that is applicable
to the running kernel.

Install the kernel source for the running kernel,
and then use the Dynamic Kernel Module Support
(DKMS) framework to install and build the
OpenIPMI driver modules for the running kernel.
You must install the kernel source by installing
the .rpm file required by the kernel.
For information on using DKMS, see the man page
for DKMS from linux.dell.com/dkms/
manpage.html.

You must reboot the system for the
update to take
effect.

If you shut down or power off the system after
performing an update, you will lose the update.
After performing a BIOS update, do not power off
the system. Reboot the system for the update to
take effect.

An Update Package is already running.
Wait until
it is complete before proceeding with
another update.

You can run only one DUP at a time.

WARNING: DO NOT STOP THIS PROCESS OR
INSTALL OTHER
DELL PRODUCTS WHILE UPDATE

Do not interrupt DUP execution.

Message

Description/Solution

IS IN PROGRESS. THESE ACTIONS MAY
CAUSE YOUR SYSTEM TO BECOME UNSTABLE.
Cannot find utilities on the system to
execute package.

The package must have certain utilities to
execute.

Make sure the following utilities are
in the path:

The utilities named must be in the path
mentioned in the message.

File already exists.

The package is attempting to overwrite an existing
file.

Rebuilding package to
support kernel
version "kernel.x". This process may
take several minutes to complete...

The DUP application is rebuilding the package to
support a different kernel version.

No specific kernel version specified!
Building
support for current kernel...

Unable to determine current system kernel. The
DUP application attempts to rebuild the package.

Cannot create directory /extract
directory. Please ensure that there is
enough space.

Extracting the package to this path requires more
disk space than available.

Cannot create temporary file "filename"

The package cannot create the temporary file for
a technical reason, such as lack of disk space,
permissions, or an existing file.

Unable to create Temp Files. Please
ensure that
there is enough space in the tmp
folder.

The package cannot create temporary files due to
lack of space in the tmp folder.

Archive cannot be extracted. Please
ensure that
there is enough space in the tmp
folder.

Insufficient space for extracting the archive.

Please provide a directory name to
extract to.

Provide a directory name for the extracted files.

ROOT directory cannot be used for
extraction.

Create a directory for the extracted files.

Successfully extracted to "/extractdir"

The package contents were extracted to the
directory you designated.

Cannot find utilities on the system to
extract package. Make sure the
following utilities are on the path:

Locate the listed utilities and add their directory to
the specified path.

Rebuilding Package Failed - Error
creating driver
support directory.

The package could not be rebuilt because the
support directory could not be created.

Message

Description/Solution

Rebuilding Package Failed - Error
copying kernel
modules.

The package could not be rebuilt because the
kernel modules could not be copied.

Rebuilding Package Failed - Error recreating archive.

The package could not be rebuilt because the
archive could not be recreated.

Rebuilding Package Failed Uninstallation of driver was
unsuccessful.

The package could not be rebuilt because the
driver could not be uninstalled.

Package has been rebuilt successfully.

The package rebuild was successful.

Rebuilding Package Failed - Error
creating output package.

Make sure that the directory from which the
package rebuild option is being executed is
writable.

Rebuilding Package Failed - Error
creating wrapper files.

The required wrapper files could not be created.

Output package:

Specifies the name of the output package.

Package execution requires 'root' user
privileges.

Successfully extracted to
.

The package is being extracted to the target
directory.

Rebuilding package packagename.bin to
support ’uname
-r’.

DUP is rebuilding the packages to support the
running kernel.

This process may take several minutes
to complete.

Wait for the process to complete.

Rebuilding Package Failed - Unable to
extract
package contents.

Unable to extract the contents of the package.

Rebuilding Package Failed - Server
Administrator
device driver (HAPI) is already
installed on the system.Package can be
rebuilt only on a system that does not
have Server Administrator device
driver (HAPI) installed.

Packages cannot be rebuilt on a system that has
the HAPI device driver installed.

Unable to Install Dell Instrumentation
Driver (HAPI).

The package cannot install the HAPI driver.

Rebuilding Package Failed - RPM
Installation failed
with error code=

Provides the RPM error code that prevented the
package from being rebuilt.

packagename.bin: Rebuilding Package
failed - Unable
to extract package contents.

Make sure that there is enough space in the /tmp
directory.

Message

Description/Solution

packagename.bin: Rebuilding Package Kernel is already
supported by this package.

You do not have to rebuild this package because
you have already customized the package for the
kernel. You will only receive this message if you
have previously used the --rebuild option and
then ran the rebuilt package.

packagename.bin: Rebuilding Package
Failed - RPM Installation failed with
error code=

Check the LSB Compliant RPM error return codes
to determine the exact reason for failure.

packagename.bin: Rebuilding Package
Failed - Error creating driver support
directory.