Bug 139126
Summary: | Assertion (heads > 0) at disk_dos.c:485 in function probe_partition_for_geom() failed. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nathan G. Grennan <redhat-bugzilla> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | kashif_ali2000, nobody+pnasrat, rmorriso |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:06:59 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nathan G. Grennan
2004-11-13 00:58:56 UTC
Same bug on my system. Primary drive (hda) is a Samsung SP1203N, also installed in system are Maxtor 6Y120L0 (hdc) and Maxtor 6Y160L0 (hdd). 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 http://rhlinux.redhat.com/anaconda/updatedisks.html) *** 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, 138419. 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. |