Red Hat Bugzilla – Bug 140464
kickstart installation waits for user-interaction
Last modified: 2007-11-30 17:07:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
I have a system with an HBA and a local scsi disk. The HBA shows up
as sda, sdb, and sdc. The local scsi disk is sdd. When I do an
installation, during the partitionobjinit phase, I get a dialog box
with the message "Error opening /dev/sdd: No such device or address"
with two choices (Retry, Cancel).
Selecting Cancel will allow me to proceed. But I have found no way to
automate this selection in a kickstart file, allowing me to completely
install the machine in an unattended fashion.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install on a machine like mine (Dell 2650, with HBA & Local disk)
2. see screen (click & continue)
Well, one question would be why the disk can't be read as that seems
like something that should be fixed :)
For RHEL4, we've added an 'ignoredisk' directive which should work for
this case. Assigning to Paul to assess the feasibility of a backport
for a RHEL3 update.
Created attachment 107301 [details]
This should be sufficient.
Commited on tarroon branch for U5
I can't find any doncumentation on usage for this in the RHEL 4 docs or package
I am assuming the syntax for omiting one device is:
Where <disk-name> = hda or sdx (with no device path)
and I am assuming the syntax for omiting mulitple devices is is a comma
seperated list, like this:
Is this correct? I want to file an RFE for docs and enter this into the
I promise whatever ends up in the knowledgebase and docs will have better
grammer and spelling than the above passage
Okay, the syntax appears to be:
Confirmed trough testing.
Let me know if there are any caveats.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.