Red Hat Bugzilla – Bug 139126
Assertion (heads > 0) at disk_dos.c:485 in function probe_partition_for_geom() failed.
Last modified: 2007-11-30 17:10:54 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Description of problem:
Assertion (heads > 0) at disk_dos.c:485 in function
Assertion (sectors > 63) at disk_dos.c:490 in function
It is a Samsung SP1213N 120gb. It has 255 heads, 63 sectors, and 14596
cylinders as reported by the kernel used during installation. fdisk
reports now problems.
Selecting Ignore for both errors would cause the installer to crash.
Selecting Cancel repeatedly, and in more than one location during the
install would allow it to go on.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot disc 1
2. Press Enter at the boot: prompt
3. Skip cd check
4. Click Next
5. Click Next
6. Click Next
Actual Results: Assertion (heads > 0) at disk_dos.c:485 in function
Expected Results: No error
Same bug on my system. Primary drive (hda) is a Samsung SP1203N,
also installed in system are Maxtor 6Y120L0 (hdc) and Maxtor 6Y160L0
By pressing cancel enough times you can progress through Anaconda up
to the actual point of installation of packages, at which time it
dies a fatal death in one of the .py scripts. If I get some time I
will go through the process again and make note of what/where exactly.
The install finished properly by clicking cancel enough in my case.
Can you try the update image at
http://people.redhat.com/~katzj/fc3-part-upd.img and see if that helps?
(Instructions for using an update disk are available at
*** This bug has been marked as a duplicate of 138419 ***
That update image had the effect of changing the line number in
disk_dos.c. Nothing else. I'll follow up in the other bug thread,
i have the same problem plz tell what can i do so that i can easily install
fedora core 3.plz tell me any body
Hey the comment#3 solution work fine for me... Thank a lot
I encountered this error on a HP Proliant DL360 G3.
The update image solved the problem for me.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.