User's Manual

Configuring and Using Virtual Media 157
Why do error messages like the
following display on the console
when Red Hat Enterprise Linux
boots a Dell server with a DRAC
4 present?
... other console
startup messages ...
Apr 16 14:48:27
localhost kernel:
hde: VIRTUALFLOPPY
DRIVE, ATAPI FLOPPY
drive
Apr 16 14:48:27
localhost kernel:
hdf: VIRTUALCDROM
DRIVE, ATAPI CD/DVD-
ROM drive
Apr 16 14:48:27
localhost kernel:
ide0 at 0x1f0-
0x1f7,0x3f6 on irq 14
Apr 16 14:48:27
localhost kernel:
ide-floppy: hde: I/O
error, pc = 23, key =
2, asc = 3a, ascq = 0
Apr 16 14:48:27
localhost kernel:
ide-floppy: Can't
get floppy
parameters
... other console
startup messages ...
The Red Hat Enterprise Linux IDE driver writes
all error responses that it receives to the console
log for diagnostic purposes. However, in this case,
the messages are not indications of any real errors
and should be ignored.
The reason these error responses are generated is
because a Virtual Media client is not connected to
the DRAC 4 management board while the system
is being booted, but the Red Hat Enterprise Linux
IDE driver is requesting information regarding the
Virtual floppy media size. This information is not
available until a Virtual Media client connects its
floppy device to the DRAC 4.
The error response, in this case, (key=2, asc=3a)
from the DRAC 4 hardware indicates "media not
present."
Table 7-2. Using Virtual Media: Frequently Asked Questions
(continued)
Question Answer