Description of problem: Im a first time linux user insatlling fedora core 3. I use a intel p4 1.7Ghz 256 ram, 2 harddisks ( a 20G and a 80G). First and foremost errors start occuring at the beginning of the installation when selecting the keyboard layout and then hitting next generates the error, "Assertion (heads>256) at disk_doc.c: 486 in function probe_partition_for_geom() failed" After my first failed attempt at installation, in any subsequent installations the above message is followed by the messages "Attempt to read sectors 2-3 outside of partition on /dev/hdb" & "Attempt to read sectors 0-7 outside of partition on /dev/hdb". I just hit ignore for all the prompts. Well i'll give you the layout on the drives. The 20 gig drive has windows xp with a ntfs file system. I used partition magic to free up 10 gigs (approx) for use with linux. 80 gig drive is OS free and is formatted in the vfat file system (for some reason their is 2 megs of unallocted space). Using disk druid in linux, i set up a root partition for linux with size 8582 megs and a swap partition with (510 megs). Note all this is on hda and I do nothing to hdb (80 gig drive). I pretty much select default settings for all other install options, except i use the advanced boot features and not use the MBR of hda because I heard windows sometimes has problems with this. I periodically (when clicking 'next' to move to the upcoming screen) gwt the error messages I mentioned earlier occuring again, till finally I reach the final install stage, where i am informed that I need 2 fedora cds (even though my friend gave me 4??) and i ok the install. Upon doing this I get a rerun of the error message mentioned earlier and im given the option to save a log onto didk and post on the website. thx for the help, excuse my noobness if i missed anything. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 111325 [details] This is the post installation dump of my failed installation
*** This bug has been marked as a duplicate of 138419 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.