Back to Contents Page

Known Issues and Frequently Asked Questions

Dell™ OpenManage™ Server Update Utility User's Guide

  Known Issues

  Frequently Asked Questions

Known Issues

The following are some known issues with Dell™ OpenManage™ Server Update Utility (SUU).

Enabling Operating System Devices

SUU does not inventory or update devices that are disabled in the operating system, though these devices may be displayed in the Comparison Report. To update the disabled devices, make the appropriate changes in the operating system and restart SUU.

Linux Systems Require the Library

On Linux systems, is required to run SUU. Your system will have this library if you have installed SUSE® Linux Enterprise Server (SP3) or current versions of Red Hat® Enterprise Linux® on your system. If your system does not have this library and you are running a supported version of Red Hat Enterprise Linux or SUSE Linux Enterprise Server on your system, install the compat-libstdc++ RPM from or from the Red Hat CD (for Red Hat customers), or the SUSE Linux Enterprise Server CD (for SUSE Linux customers).

Running Linux Updates

SUU uses the Dell Update Packages (DUP) to update various system components. During a Linux update, the DUP creates the /var/lock/.spsetup file using the Linux lockfile utility. This file is created when one of the following conditions occur:

If one of these conditions occur, a /var/lock/.spsetup file is created rather than deleted, causing SUU to report a successful update and prompt the user to reboot the system. When you run SUU again and run the Comparison Report, the comparison procedure reports no change in device status.

If this situation occurs and you are not running an update, delete the /var/lock/.spsetup file before running another update.

Running SUU and DUP on a Red Hat Enterprise Linux (Version 4) System

If you have installed the Red Hat Enterprise Linux (version 4) operating system using the Red Hat operating system CDs, the native Redundant Array of Independent Disks (RAID) driver included with the operating system prevents DUP from running on your system. To fix this issue, install the updated RAID driver available on the Dell Systems Management Tools and Documentation DVD or download the driver from the Dell Support website at

Running SUU With the Progress Option

When running SUU with the -p (progress) option, the SUU current instance log location is reported rather than the SUU update log location.

Updating Multiple Devices

When updating multiple, identical devices on the same system, SUU applies the update to all instances of all devices. For example, if your system is configured with three controllers running firmware/driver versions 1.1, 1.2, and 1.3, and the repository contains version 1.2, the update applies firmware version 1.2 to all devices.

Updating PERC Firmware

If you have multiple PowerEdge Expandable RAID Controller (PERC) cards installed on a system, you may need to run the SUU update more than once to update the firmware of all PERC cards. This procedure ensures that all PERC cards are updated if one or more cards failed to update during the initial SUU update.

Updating PERC 3/Di Firmware

SUU may fail to update Adaptec PERC firmware to version 2.7 or 2.8 in some cases. It may not be possible to flash some ROMB controllers to version 2.8 firmware by using DUPs. If this issue arises, you must reflash the ROMB firmware using a bootable floppy diskette.

NOTICE: If SUU fails to update Adaptec PERC firmware, you will also be unable to downgrade to version 2.7 if you upgrade to 2.8.

PERC update packages may fail if other activities, such as a consistency check or background initialization (BGI) are running on the controller. Ensure that such activities are not in progress before running the update package.

Verifying NIC Teaming Software Compatibility

If an NIC teaming application is installed on the system, SUU updates the NIC base driver only if the driver is compatible with the teaming application. To verify compatibility, run DUP for the NIC and view the resulting messages.

Restarting the System Inventory in the Same Session

SUU does not allow you to restart the system inventory in the same session if there is insufficient space in the var or tmp folder.

In Linux, if the space is not enough in the var or tmp folder, SUU displays the following error message:

Not enough space available in /var or /tmp folder. Please make sure you have atleast 100MB.

Ensure that you have sufficient space in the var or tmp folder and restart SUU to start the system inventory.

Running SUU From a Network Location

Deleting the Temporary Folder

When you run SUU from a network location, JRE creates temporary files in the <%systemdrive%>\Documents and Settings\<%user%>\Local Settings\Temp\hsperfdata_<%user%> directory in Microsoft Windows or in the /var folder in Linux. You need to manually delete these temporary files.

Updating the H661 Firmware

If your CERC ATA RAID controllers are configured with the H661 firmware, SUU cannot update the firmware to the latest version. To update the firmware, use the -force option to manually apply the DUP with the latest firmware version.

Using the Remote Access Controller Virtual Media

Do not use the Virtual Media to run SUU remotely on a system. This procedure breaks the Virtual Media connection, causing the SUU update procedure to fail.

Using Special Characters in the SUU Directory Name

SUU fails if you run it from a directory that contains special characters such as ", :, /, \, $, and so on.

For example, when a USB DVD-ROM or USB disk is attached to the SUSE Linux Enterprise Server operating system, it may by default, mount to a directory name that contains special characters. For example, /media/USB:1:2/

It is recommended to use a directory name without any special characters while running SUU.

Running RAC DUP Packages

If you launch SUU when a Remote Access Controller (RAC) DUP package (RAC 4/P or RAC 4/i) is running, execution of the DUP package may fail. To resolve this issue, run SUU only after the RAC DUP package has completed execution.

Frequently Asked Questions

The following are frequently asked questions concerning the SUU.

Why do I get a pop-up dialog box saying, "There is no disk in the drive. Please insert a disk into drive"?

The Dell Server Updates DVD was ejected from the DVD drive while SUU was running. SUU requires the DVD to be present during execution.

When I run suu -c on a Linux system, I get an error saying, "Problem executing Inventory Collector." What causes this error and how can I fix it?

The Inventory Collector subcomponent of SUU requires the shared library to be installed on the system. Install the compat-libstdc++ RPM from or from the Red Hat CD if you are running a supported version of Red Hat Enterprise Linux on your system or from the SUSE Linux Enterprise Server CD if you are running SUSE Linux Enterprise Server on your system.

Why do I get a pop-up box titled "Unsafe Removal of Device"?

A part of the SUU update requires updating the backplane firmware. If the operating system queries the backplane during a flash update and the backplane does not respond, the operating system receives an indication that the device was removed unsafely. After the backplane firmware is updated, you may see a screen indicating that a new device was added.

When using the SUU GUI to perform an update, a message is displayed asking me to see the User's Guide for information on possible causes of why a server object is not displayed in the tree.

To perform updates, you must be running SUU on a supported system and must have the correct user access privileges. For Microsoft® Windows® you must have administrator privileges and for Linux you must have root privileges. For a list of supported servers and operating systems, see the Dell Systems Software Support Matrix on the Dell Support website at or on the Dell Systems Management Tools and Documentation DVD.

When I run SUU, why do I not see the Comparison Report? Why can I not update my system?

SUU requires that Windows users have local administrator privileges. To obtain local administrator privileges, users must either belong to the local administrators group or use the local administrator account. On Linux systems, only root (user id 0) users can see the Comparison Report and perform updates.

I get a "Prerequisites not met" error. What should I do?

Run a Prerequisites check and install the recommended items. See the Prerequisites section for more information.

Why do I get a message saying, "Inventory operation exceeded specified time-out" when I try to run a Dell Update Package at the same time as SUU?

Running SUU and a separate DUP concurrently may cause unexpected behavior. SUU runs DUPs in the background. Therefore, you do not need to run the DUPs. Either run SUU or the DUP; do not run both at the same time.

I cannot start SUU. The "Another instance of SUU is already running" message is displayed even though no other instance of SUU is running on the system.

To ensure that no other instance of SUU is running on the system:

On systems running Windows operating systems, open the Windows Task Manager, click the Applications tab, and find out if SUU is running.

On systems running Linux operating systems, open a terminal and type the ps -eaf | grep suu command to find out if SUU is running.

If SUU is running, close the application, and restart SUU.

If no other instance of SUU is running, then SUU may have encountered an abrupt shutdown for some reason. This results in the creation of lock files. To delete these lock files on systems running a Windows operating system, navigate to the <%systemdrive%>\dell\suu directory and delete the suu.lck file.

To delete the lock files on systems running a Linux operating system, run the following commands:

chattr -i suu.lck

rm -f suu.lck

This removes the lock file from the log directory located at /var/log/dell/suu by default.

I cannot start Server Administrator after updating using SUU.

Sometimes, after updating Server Administrator using SUU, some of the Service Administrator services may not run. Restart your system and start Server Administrator.

I cannot update BIOS versions using SUU.

For systems with a TCG 1.2 compliant Trusted Platform Module (TPM) chip, BIOS updates using SUU and DUPs fail if all of the following are true:

For details about the failure, see the log files at <%systemdrive%>:\dell\suu (on Microsoft Windows) and /var/log/dell/suu (on Linux systems).

To successfully update BIOS on such systems, perform the following steps:

  1. Disable Microsoft Windows BitLocker Drive Encryption feature. For information on disabling this feature, see the Microsoft documentation at

  2. Restart SUU and update BIOS.

  3. Restart your system.

  4. Re-enable the Windows BitLocker Drive Encryption feature. For information on enabling this feature, see the Microsoft documentation at

For details about TPM, see Trusted Platform Module (TPM) and BitLocker Support.

I cannot run SUU, the "SUU Logging System has failed: There is not enough space on the disk" message is displayed.

While running SUU, ensure that the log directory specified at <%systemdrive%>\dell\suu (on Windows operating systems) and /var/log/dell/suu (on Linux operating systems) contains at least 10MB of free space.

You can also specify a different directory to save the log files. See the SUU command line options for more details.

Back to Contents Page