Users Guide
Table Of Contents
- Dell Update Packages User's Guide
- Getting Started
- What’s new in this release
- DUP event viewer
- Zip pack elimination
- Slot information for hard drive
- Dependency
- Supported Operating Systems
- Prerequisites
- Prerequisites And Features For Systems Running Linux
- Prerequisites and Features for Systems Running Windows
- Downloading DUPs
- Downloading DUPs through Repository Manager
- Installing Device Drivers
- Installation Order of DUPs
- Best practices for using DUPs
- Other Documents You May Need
- Contacting Dell
- Using Dell Update Packages
- Update and Rollback in Lifecycle Controller Enabled Server
- Command Line Interface Reference
- Linux Troubleshooting
- Known Issues
- Diagnostic Tasks Will Not Run While a DUP Reboot is Pending
- Abnormal Termination of a DUP
- Error While Loading Shared Libraries
- Insufficient Free Physical Memory to Load the BIOS Image
- Kernel Panic While Running Storage Controller Firmware Update Packages
- Loss of Functionality While Renaming Linux DUPs
- DUPs Fail on 64-bit Red Hat Enterprise Linux Operating System
- DUP Update of Firmware Might Fail While Running in the UEFI Mode
- Messages
- DUP Message Logs
- Known Issues
- Troubleshooting for Systems Running Windows
- Trusted Platform Module and BitLocker Support
- Microsoft Windows Server 2008 User Account Control
- Frequently Asked Questions
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.
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: <Model Name> System(s)
supported by this package: <Model Name>
Select a compatible DUP, and try the update again.
24 Linux Troubleshooting