Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 6666 - Cannot Install RedHat From DOS Fat Extended Partitions
Summary: Cannot Install RedHat From DOS Fat Extended Partitions
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-02 23:01 UTC by samuel
Modified: 2015-01-07 23:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-11-30 14:44:04 UTC


Attachments (Terms of Use)

Description samuel 1999-11-02 23:01:47 UTC
In 6.0 Everything Is Fine.


In 6.1 The Kernal Does see my Fat(16) Extended Partitions as
<Hda5><HDA6><HDA7>
But the Installer does Not let me Chosse HDA7 as Source for
Redhat Files.

It Only sees: HDA1  HDA2  HDD1
I have downloaded the Updated image from your WebSite and it
is Worst.. Now It Only Sees : HDA1 HDD1


Therefore i cannot Install REDHAT 6.1 :-(

The 6.0 Boot disk does Work but an error occurs when it
tries to load the base/stage2.img

HELP!!

Comment 1 Jay Turner 1999-11-03 12:54:59 UTC
Send me a copy of your /etc/fstab as well as the output from "fdisk
-l"  There are several known issues which moght be causing the
problems you are seeing, and seeing these two piecees of data will
help us get you back on the right path.

Comment 2 Jay Turner 1999-11-30 14:44:59 UTC
There are a couple of known bugs with the installer that you might be seeing.
The installer is not currently able to see into Win95 extended partitions of
type "f", and I am betting this is the bug you are seeing.  We should be
releasing an update here in the coming days which will fix this.  I would
recommend that you download and make use of the updated boot images and see if
that solves your problem.


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