Users Guide

Workaround A fix for this issue is available at rhn.redhat.com.

DRAC 4 Virtual Media Reset May Cause System Instability

Description Using the default ide driver may cause the system to lock up when a Dell Remote Access

Controller (DRAC) 4 reset occurs.

Workaround Use the ide-scsi driver to control the virtual media on systems using DRAC 4. To do so, pass the

following parameter to the kernel command line:

hdX=ide-scsi

where X is the virtual media device letter. You can find the virtual media letter by reading the /

proc/ide/hdX/model files until you locate the value for VIRTUALCDROM DRIVE.

While using the ide-scsi driver, the operating system takes the virtual media offline when a

DRAC reset occurs. The device can be brought online in the usual manner for SCSI devices, by

typing the following commands in a console:

echo "scsi remove-single-device Y 0 0 0" > /proc/scsi/scsi

echo "scsi add-single-device Y 0 0 0" > /proc/scsi/scsi

Where Y is the SCSI host number of the virtual media, which can be found by reading the /proc/

scsi/scsi file and finding the line Host:scsiY that corresponds to the virtual media.

If you have installed the operating system using the

Dell Systems Build and Update Utility

media, this workaround will already be installed on your system.

Unlike DRAC 4, a kernel panic does not occur while resetting or rebooting a system using

DRAC 5.

Input Output Errors Occur When A Fiber Channel Card Is Connected Without A LUN

Description When a Fiber Channel adapter is installed on a system attached to a storage area network

(SAN) without a logical unit number (LUN) assigned to the adapter, the following error

message is displayed:

end_request: I/O error, dev sdg, sector 2097024

Buffer I/O error on device sdg, logical block 0

end_request: I/O error, dev sdg, sector 0

Workaround Configure a LUN for the adapter.

Network Channel Bonding May Cause Call Trace Messages

Description If a network channel bond is configured on a Red Hat Enterprise Linux 5 system a call trace

message may appear in /var/log/messages involving the kernel symbols rtmsg_ifinfo,

rtnetlink_event, and notifier_call_chain.

Workaround You can ignore the messages as channel bonding works as expected.