Owner's Manual

forwarding") when running the GUI.
* If tapeware is installed, the Dell Online Diagnostics application
may fail to start. If that happens, please delete the softlink
entry /lib/libstdc++-libc6.2-2.so.3 and restart the Dell Online
Diagnostics application to make it work. Please check with the
Tapeware support team for fix to this issue.
* ICH7R IDE controllers are not supported. Running tests on this
controller or the devices connected to it may cause
unexpected behavior.
* When you run a SCSI Communication test, on a channel that has an
LTO3 tape drive connected to it and perform a backup
simultaneously using 'tar commands', the backup operation may fail.
Ensure that backup or restore operations are not in progress
before running the SCSI Communication test.
* When the Yosemite backup software is installed on a system that
has a tape changer, SCSI Communication tests and tape tests may
fail. Ensure that the Yosemite backup software service is
stopped before running these tests.
* The Tape Self Test writes to and advances the tape media during
execution. Manual erase operations using the Linux command
"mt -f /dev/stX erase", if executed immediately after the
Tape Self Test execution, will fail with an I/O error.
To avoid this error condition always rewind the tape media after
running the Tape Self Test.
* When a non-root user uses "su" to become superuser (root), some
tests may not work in the CLI, when the pediags command is run.
Users should use "su -" to become the super user to run the pediags
command.
* On Red Hat Enterprise Linux version 4, when SELinux
(Security Enhanced Linux) is enabled and you run network diagnostics
on console - some warning messages appear
indicating a violation of policy.
* On SuSE Enterprise Server 10, with ArpArmor enabled and when you run
network diagnostics on console - some warning messages appear
indicating a violation of policy.
* Multiple USB devices, when connected to a deep hierarchy
of bus powered USB Hubs, cause the Linux USB device driver
sub-system to become unresponsive.
This prevents Online Diagnostics from launching
in the GUI mode. Perform the following corrective measures
if you are faced with this error situation:
* Disconnect the top-level hub connected to the system,
* Connect external power supply if supported, to this hub
* Disconnect all the devices from the hub
* Reconnect the hub to the server
* Reconnect the devices on server ports (if available) and to other
higher level hub ports having external power supply,