Bug 163911
Summary: | kickstart probes block devices it shouldn't and halts automated install process | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Axel Thimm <axel.thimm> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED NOTABUG | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-07-26 04:10:50 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Axel Thimm
2005-07-21 21:31:21 UTC
It looks like FC4 does not trigger the bug because it doesn't see the SAN devices at anaconda time. What makes it even worse is that the non-faulty paths are now carrying a gpt table. Now anaconda needs 4 (!) prompts during kickstart time for *each* device. E.g. for 5 devices on the SAN the kickstart process gets interrupted 20 times. Is there a way to communicate to anaconda not to look at any other block devices other than those given for the installation? There's an ignoredisk directive to ignore specific disks. Thanks, I found the syntax as ignoredisk --drives=<drive1>,<drive2>,... where <driveN> is one of sda,sdb,...,hda,... etc. But it only works if --initlabel (in clearpart) is not used. If it is used, then initAll is set which reenables probing for all disks in DiskSet.skippedDisks. Should I open a new bug for this one? |