Bug 7200
Summary: | disk druid partition allocation failure, reason undefined | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | bill.cooksey |
Component: | installer | Assignee: | Jay Turner <jturner> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | srevivo |
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: | 1999-11-22 15:00:38 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
bill.cooksey
1999-11-21 14:17:28 UTC
Disk Druid is trying to be "smart" and only allow the /boot partition to be placed on /dev/hda, as this is the only drive that most BIOSes can boot. Anyway, the workaround for this problem is that you will want to install in "expert" mode (type "expert" at the boot prompt) and then create the partitions in fdisk. You will then be able to tell the system which partition to use for /boot and the other partitions, without having to worry about the installer second-guessing you. |