Red Hat Bugzilla – Bug 52361
Roswell2 kickstart now stomps on Windows installation
Last modified: 2005-10-31 17:00:50 EST
Description of Problem:
Starting with Roswell2 the kickstart installer removes my Windows 2000
installation which resided on the first partition of my hard drive.
The partitioning section of my kickstart file is:
clearpart --linux --drives=hda
part /boot --fstype ext3 --size=50 --ondisk=hda
part / --fstype ext3 --size=1100 --grow --ondisk=hda
part swap --size=880 --grow --maxsize=1760 --ondisk=hda
This worked just fine on Roswell #1.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Win2k on first partition
2. Use kickstart to install Linux on the rest of the drive.
katzj, have you seen any behavior like this? I don't think this code changed
between Roswell 1 and Roswell 2.
Its because zerombr is ONLY supposed to remove the mbr if it is BAD.
Read the RH 5.0 installer code.
It seems to do more than mess with the mbr (unless the mbr also has something to
do with the partition table that I'm not aware of) --- the fat32 partition is
completely removed. I'm hesitant to reproduce this again since it takes so
damned long to install Windows 2000, but I think that there was a message on the
console where partition information is reported that may have said something
about not liking one of the partitions just before it created the linux
partitions. Could it be that the partition table is misread?
Yes, the fact that this happens is a bug... I've got a patch which I'm testing
at the moment
Fixed in CVS
Is there somewhere a bootnet.img with the new fixes that I could use to test things?
Unfortunately, the files which were changed have diverged a little bit too much
to easily create an updates disk with the fix without having to basically redo
the diff against the older tree.