Owner's Manual
Table Of Contents
- User’s Guide
- Getting Started With Dell Update Packages
- Using Dell Update Packages
- Performing BIOS and Firmware Updates Using Dell Linux Online Repository
- Update and Rollback in Unified Server Configurator - Lifecycle Controller Enabled
- 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
- Yum and Up2date Repository Management Software Caches Incorrect Repository Metadata
- Use Dell Linux Repository with yum and Red Hat Enterprise Linux Version 4
- 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
- Windows Troubleshooting and FAQs
- Index

42 Linux Troubleshooting
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.
Therefore, it is recommended that you stop Dell OpenManage Server
Administrator and Dell OpenManage Server Administrator Storage
Management Service before running 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 one having a lowercase
".bin" extension. The ".bin" extension has
an entry in the Linux MIME database which leads to the file open error.
NOTE: The readme.txt file, which is available at support.dell.com/manuals,
provides the latest information regarding known issues.
Yum and Up2date Repository Management Software Caches Incorrect
Repository Metadata
For yum, run the yum clean all command to remove old metadata and
retry updating the firmware.
For up2date, run rm -f /var/spool/up2date/* to remove old
metadata. You can also remove all the files under /var/spool/up2date/ at any
time and up2date will automatically download the required updates.
Use Dell Linux Repository with yum and Red Hat Enterprise Linux
Version 4
If you do not have Red Hat Network (RHN) configured, and need to use the
Dell yum repository with Red Hat Enterprise Linux version 4 and up2date,
you must disable RHN. Open the /etc/sysconfig/rhn/sources file and comment
the following line:
up2date default