User's Manual

30 Known Issues and FAQs
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 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.
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.
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.
A5_bk0.book Page 30 Friday, February 25, 2011 2:47 PM