Bug 89100 - Installer/Disk Druid create wrong partition types on dual-boot system
Summary: Installer/Disk Druid create wrong partition types on dual-boot system
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: parted
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-17 16:59 UTC by Bob Jones
Modified: 2007-04-18 16:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-06-25 19:05:11 UTC

Attachments (Terms of Use)

Description Bob Jones 2003-04-17 16:59:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
When installing RH9 on a dual-boot machine (PIII 1.2Ghz, 256Mb, 20Gb HD)
previously partitioned thusly:
/dev/hda1   10Gb   /dosc  -  Windows 2000/XP Pro partition (fat32)
/dev/hda2   8.5Gb  /      -  Linux partition (ext3)
/dev/hda3   530Mb  <swap> -  Linux swap partition

having fdisk partition types of:
hda1 - c
hda2 - 83
hda3 - 82

from prior installation of RH7.3 and using BootMagic to control OS boot options.
 When installing RH9, there was no option to run fdisk .. only automatically
partition and use Disk Druid.    I ran Disk Druid as I did not want to lose
information on the fat32 partition since its vital for work and to restore user
accounts in Linux.  After several days of trying to figure out what was wrong
and what was keeping BootMagic from properly booting into Windows (hda1), I
booted into RH9 from boot floppy and ran fdisk.  I noticed at this point that
the partition types had been changed to:

hda1 - 1c (hidden fat32)
hda2 - 93 (Amoeba)
hda3 - 82 (Linux Swap)

Only after changing the partition types for hda1 and hda2 back to original and
installing GRUB into the MBR was I able to restore the dual-boot nature of this

I do not think its an outright problem with BootMagic sine bootmagic worked
beautifully with RH7.3.  Instead, I believe that there might have been a
partition information communication problem between BM and RH installer.  Adding
the option to use fdisk to manually partition the drives back into the installer
would be a good idea to this user.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.see description

Actual Results:  see description

Expected Results:  see description

Additional info:

see description

Comment 1 Michael Fulbright 2003-04-22 15:55:06 UTC
This is most likely an issue with parted.

Comment 2 Jeremy Katz 2004-06-25 19:05:11 UTC
This doesn't appear to be a problem for me with newer releases.

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