Bug 8811 - Installer partition manager fails on my wd drive
Summary: Installer partition manager fails on my wd drive
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.1
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-01-24 23:05 UTC by chad
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-02-16 19:40:37 UTC
Embargoed:


Attachments (Terms of Use)

Description chad 2000-01-24 23:05:38 UTC
I have a 17 G Western Digital drive (one of the 7200 ata/66 capable
drives) it's the 3rd one in my system, on the secondary ata/33 controller
as master with my cdrom the slave, on the abit bp6 dual mobo.  The other
two drives are a half gig, and a 5 gig, which has windows 98se installed.
I had previously had win2k rc3 installed on the 17G drive, running ntfs
the whole drive.  When entering the partition manager, I see it as a type
0x84 partition, it allows me to delete it, but when I try to add a new
partition on that drive, it gives me an 'Unknown Error' disallowing me
from completing the action. Any ideas here?

chad

trying to netinstall rh 6.1

Comment 1 Jay Turner 2000-02-07 13:52:59 UTC
Partition type 0x84 is "OS/2 Hidden C:" which is not a partition type that I
have an experience with, but I would have to assume that it is not very common
:-)  Anyway, there is a chance that Disk Druid just does not know how to deal
with clearing partitions of this type.  My suggestion is the following.  Run the
install in expert mode (type "linux expert" at the boot prompt) and use fdisk to
delete that partition.  Then try the installation again and see what happens.
My guess is that you will not have any problems from that point.  Please post
followup information if this workaround does indeed work.

Comment 2 Jay Turner 2000-02-16 19:40:59 UTC
Issue is resolved in next cut of the install code available in beta.


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