Bug 6987 - Install fails with /RedHat on ntfs or extended fat partitons
Summary: Install fails with /RedHat on ntfs or extended fat partitons
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.1
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jay Turner
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-11-13 11:47 UTC by gcollins
Modified: 2015-01-07 23:39 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 1999-11-16 13:19:48 UTC
Embargoed:


Attachments (Terms of Use)

Description gcollins 1999-11-13 11:47:36 UTC
The install disks (xxx-RHEA-1999-044/045) cannot load /RedHat from either a
NTFS (on a primary partition) or fat (on an extended partition). At the
prompt for the location of /RedHat, neither partition appears as a choice.
Even if the update disk does resolve the problem, it doesn't help because
the installer won't prompt for the update disk until AFTER it's located
/RedHat!

By copying /RedHat to my existing linux root partition, I was able to get
the update disk loaded. I then tried backing up to the screen where you
select the location of /RedHat, but the install program aborted at that
point.

At the least, the installer should support loading /RedHat from a fat
filesystem on an extended partition...

Comment 1 Jay Turner 1999-11-16 13:19:59 UTC
The installer was never meant to recognize source files on an NTFS partition, so
that is not really a bug.  We know that there are problems with the extended
partitions, and it actually related to extended partitions of type "f" as
opposed to the usual type "5"  We are going to be putting together another
update which will fix this problem, but until then the easiest workaround is to
change the type of the extended partition from type "f" to type "5", upgrade
your system, and then change the partition type back to "f".

*** This bug has been marked as a duplicate of 6482 ***


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