Users Guide
Table 8. Possible Outcomes for PowerEdge systems (continued)
Scenarios Outcomes
DSU 1.5 RPM (sourced from linux.dell.com) on a 10th
generation of PowerEdge system pointing to the newest
Linux Repository that no longer has 10G content.
Platform not supported message is displayed.
DSU 1.4 RPM on a 10th generation of PowerEdge system
pointing to an older Linux Repository that still has 10G
content.
All commands work as usual.
DSU 1.4 DUP (sourced from downloads.dell.com) pointing to
catalog.xml file that no longer has 10G content.
There may be two possible outcomes:
● If the DUP doesn’t support 10G platform, then DSU is not
installed.
● If DUP supports 10G platform, DSU is installed. When dsu
command is invoked Platform not supported message is
displayed.
I am running DSU 1.4 DUP and pointing at a legacy
catalog.xml that has 10G content.
There may be two possible outcome:
● If the DUP doesn’t support 10G platform, then DSU is not
installed.
● If DUP supports 10G platform, DSU is installed. dsu
command works as usual.
On Ubuntu operating system, I see a message “genisoimage: command not found. Please install genisoimage to
create bootable iso”. What am I supposed to do?
To troubleshoot the issue, execute the following command: sudo apt-get install genisoimage. By executing the
command, you are installing the genisoimage to generate the ISO.
On Linux operating system, I see a message “mkisofs: command not found. Please install mkisofs to create bootable
iso”. What am I supposed to do?
To troubleshoot the issue, execute the following command: yum install mkisofs on RHEL operating systems and zypper
install mkisofs on SLES operating systems.
On Microsoft Windows operating system, when I execute the command “dsu”, I see a message “dsu is not
recognized as an internal or external command, operable program or batch file”. What am I supposed to do?
To troubleshoot the issue, you must add the dsu install path to environmental variable by executing following command with
administrator privileges: setx PATH=%PATH%;C:\Dell\Dell System Update.
There are few components that are listed when I execute the command dsu —i or dsu /i. However, I am not able
to view these components in the comparison report. Why do I see the difference?
Though the components are listed after executing the command, there may be no updates available for certain components in
the catalog. You may view the components in the comparison report if an update is available for that particular component in
the catalog.
I get a warning message saying “Inventory collector returned with partial failure”. How do I get more information
about the potential issue?
Check the IC log to get more information regarding the failure. You can find the log file in C:\ProgramData\Dell
\UpdatePackage\log on Microsoft Windows operating systems and /var/log/dell/ on Linux operating systems.
I see a message saying “Failed to parse config file” with exit code 17. What should I do to troubleshoot and resolve
the issue?
The config file may not be filled correctly. Refer the configuration schema information in the dsuconfig.xml section in Using
DSU bootable ISO topic.
I see a message “unable to get the inventory collector path from catalog”. What should I do to troubleshoot and
resolve the issue?
For more information on the inventory collector path, check the catalog file.
Sample inventory collector data from catalog.xml:
● WIN64: <InventoryComponent schemaVersion="2.0" releaseID="WF06C"
hashMD5="0dbe6b18f0ebf247ea317c51c7257ff4" path="FOLDER04054889M/1/
76
Frequently asked questions