Bug 111243
Summary: | DiskDruid messes mount points - partitions mappings when going back in installer | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Aleksander Adamowski <bugs-redhat> |
Component: | installer | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
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: | 2004-04-16 21:48:45 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
Aleksander Adamowski
2003-12-01 10:04:40 UTC
Does this still happen with Fedora Core 1? I seem to remember fixing it there... Nope, I've just tested with Fedora Core 1 installer. Fedora installer does exactly the same thing: Initially places filesystems in order "/boot", "/usr", "/"; When I go to GRUB boot menu editor (where I see root device on hda3), then go back to disk druid and force "/" to be a primary partition, the order changes to "/boot", "/", "/usr". But on the GRUB menu editor root is still visible as hda3, not hda2. When I go further and start package installation, I can see that the filesystems were mounted in old order (hda1 -> "/boot", hda2 -> "/usr", hda3 -> "/"), and the sizes use the new order (hda1 -> 256, hda2 -> 1024, hda3 -> 4096). So in short the problem is: Disk Druid has reordered size specifications, but not mount points after I had clicked "Force primary partition". Which leaves me with filesystems having different sizes and order than I've specified in Disk Druid. BTW, I've passed the exam anyway :) But the score was only 88%... Fixed in CVS |