Bug 22701
Summary: | Disk Druid fails -- installer dies | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Chris Runge <crunge> |
Component: | anaconda | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | Florence Beta-3 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-01-16 18:01:14 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
Chris Runge
2000-12-21 23:07:28 UTC
(I don't think the oops is related to that; when I chased it a few days ago it was some bug in the xor module; mostly harmless.) Please give the output of 'fdisk -l' for the original partitioning of the system before trying installation, as well as a list of the partitions in that list which you removed before trying to create the '/boot' partition. same problem if I start with just a FAT32 partition before the install. here is the output of fdisk from florence beta 1 during the install: Command (m for help): p Disk /tmp/hda: 16 heads, 63 sectors, 26377 cylinders Units = cylinders of 1008 * 512 bytes Device Boot Start End Blocks Id System /tmp/hda1 * 1 12495 6297448+ b Win95 FAT32 Partition 1 does not end on cylinder boundary: phys=(783, 254, 63) should be (783, 15, 63) For comparison purposes, here is the output of fdisk under RHL 7: 255 hears, 63 sectors, 1655 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /tmp/hda1 * 1 784 6297448+ b Win95 FAT32 Nothing was changed between the time I got the output for each -- I assume something is funny in the new kernel such that it is detecting the hard disk differently This defect is considered MUST-FIX for Florence Gold release FWIW, still an issue in beta 2 I think I have this fixed, although I'm unclear about the original bug post. If this was a GUI install then there is no way to proceed if '/' or '/boot' are currently unallocated. In the TUI install there is no way to proceed in this case w/o saying 'Yes' to a warning dialog, in which case its expected to fail anyways. you are correct about the 2.4 kernel vs 2.2 kernel reporting the same drive geometry two different ways ... (that is another bug) ... For this type of install, disk druid will not create a /boot partition above the 1024 cylinder limit. To perform an install in the case that needs a /boot above 1024 cylinder, it is necessary to create the /boot partition in fdisk where desired, and then assign a /boot mount point to the newly created partition ... this DOES allow the install to procede, although a warning dialog is provided since not all hardware that says it is able to boot above 1024 cyl actually does ... thanks for your report! |