Bug 7563 - installer upgrade doesn't recognize existing linux partitions
installer upgrade doesn't recognize existing linux partitions
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Depends On:
  Show dependency treegraph
Reported: 1999-12-03 14:13 EST by rzdroj
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-15 15:16:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description rzdroj 1999-12-03 14:13:27 EST
Using 6.1 installer and booting from boot-RHEA-1999:044.img and
updates-RHEA-1999:045.img on a Gateway GP6-450, the installer does not
recognize any existing linux partitions when I try to upgrade. The
partitions are recognized for a new install. This occurs when the existing
system is either 6.0 or 6.1. The problem did not occur when installing on a
Gateway Solo 9100 laptop.
Comment 1 Jay Turner 1999-12-06 08:24:59 EST
Please send me a copy of your /etc/fstab as well as output from "fdisk -l

There are known bugs in the installer with being able to see into an Win98
extended partition (partition of type "f")  The workaround is to change the
partition to type "5" for the duration of the upgrade and then change it back
after the upgrade is complete.  We are also planning on releasing a new errata
image here shortly which will include this as a fix.

------- Email Received From  Ron Z <rzdroj@mail.lm.com> 12/06/99 13:52 -------
Comment 2 Jay Turner 2000-02-09 09:46:59 EST
This problem is a result of the type 85 linux extended partition that you have.
The installer is not able to see inside that partition, and hence is telling you
that it cannot find anything to upgrade.  This code should be in installer in
the next release.
Comment 3 Jay Turner 2000-02-15 15:16:59 EST
Will be resolved in the next cut of the beta.

Note You need to log in before you can comment on or make changes to this bug.