From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Description of problem:
After FC4 install, geometry on a 124 gb IBM HD wa changed from
16383,16,63 to 59131,16,255
This causes subsequent attempts to install XP Home to crash.
ISO files were verified with sha1sum, burned and verified with Nero.
All disks fail the Linux disk scan on 4 differenr machines.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.Boot XP distriution disk
3. Try to partition HD from XP installer
Actual Results: Hard drive geom changed, Win XO installer crashes
Expected Results: Expected normal installation and XP cpmpatibility
as with FC3 Release install.
How many drives are in the machine, what interface are they connected to, and
what model numbers are they?
Drive is IBM Deskstar IC35L120AVVA07-0
Motherboaed ABIT KR7A-RAID AMD 1900 1.5gb ram
One HD Primaty master
DVD R/W Seconday master
I have not been able to restore the original geometry.
The sfdisk procedure does not work.
BTW All ISO files passed sha1sum
Discs burned and verified with Nero
Discs (CD and two copies of DVD iso) failed mediacheck
on four different machines
I was able to make the HD reusable by repeatedly applying sfdisk
anf fdisk with the special DOS command.
59131,16,255 isn't a valid CHS geometry. I am not aware of any
programs that would display such a number. Where did you get the number from?
This is what FC4 test1 changed it to,
according to sfdisk.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
Fedora Core 3 and Fedora Core 4 are no longer supported. If you could retest
this issue on a current release or on the latest development / test version, we
would appreciate that. Otherwise, this bug will be marked as CANTFIX one month
from now. Thanks for your help and for your patience.
Fedora Core 4 is not maintained anymore.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.