Bug 190142
Summary: | Fedora installation alters partition table of other hard drives | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Victor <veejunk1> |
Component: | parted | Assignee: | Joel Andres Granados <jgranado> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | clausen, triage, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | bzcl34nup | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-04-18 11:00:57 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: | |||
Attachments: |
Description
Victor
2006-04-27 23:22:52 UTC
Created attachment 128324 [details]
The initial state of both drives partition tables before each linux installation.
Created attachment 128325 [details]
FC4_4.txt – The state of the partitions after installing FC4
Created attachment 128326 [details]
Ubu.txt – The state of the partitions after installing Ubuntu 5.1
Just FYI for comparison purposes.
Does this still occur with Fedora Core 5? Sorry for the delay - it took me a while to get a copy of FC5 and then my previous reply appears to have been lost. Yes, the same problem still occurs with FC5. Install: I didn't specify the drive geometry. I performed a minimal install, deselecting all packages and did NOT install GRUB to any partition. At partitioning screen I left the 1.5Gb drive (/dev/hdd) selected and deselected the 160Gb (/dev/hdg) & selected custom. I told it to use existing ext2 partition for root and NOT to reformat it. Same for swap. After the install I didn't even run Linux. Result: the 160Gb drive was modified - all EPBRs in the extended partition had Head/Sector changed from 0,1 to 254,63. I don't understand why the CHS values are being changed at all as I gather that Linux only uses LBA and doesnt even use CHS. This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks. This is still a bug with FC5 (comment 5). I've changed the version in the bug header. I'm unable to try it with FC6 at the moment. I'll try to test it on FC7 as soon as I can. Thanks for the interest. Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers Tested this on current Rawhide and did not see the behavior. You can either deselect the drive from the initial drive list in the gui install. or you can --ignoredisk in the kickstart. |