Bug 143778 - Installer anaconda crash assert heads <256 fails on disk partitioning
Summary: Installer anaconda crash assert heads <256 fails on disk partitioning
Keywords:
Status: CLOSED DUPLICATE of bug 138419
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 3
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-27 16:03 UTC by Mark Carter
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:07:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dump file generated during failed install (728.26 KB, text/plain)
2004-12-27 16:05 UTC, Mark Carter
no flags Details

Description Mark Carter 2004-12-27 16:03:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
The core 3 installation CDs worked for a 30 GB disk, but seem to fail
with an 80 GB disk.  Errors occur with "ignore" or "continue" as early
as the keyboard select screen.  The final error occurs when disk is
ready to be formatted (no formatting takes place):
File
"/usr/src/build/475969-i386/install//usr/lib/anaconda/partedUtils.py",
line 715, in savePartitions
    disk.commit()
error: Bug: Assertion (heads < 256) at disk_dos.c:486 in function
probe_partition_for_geom() failed.

Full dump attached.

Version-Release number of selected component (if applicable):
Core 3 standard

How reproducible:
Always

Steps to Reproduce:
1.Attempt to install on hdb 80 GB disk
2.
3.
    

Actual Results:  Install fails

Expected Results:  Installation of FC3

Additional info:

Dump attached.

Comment 1 Mark Carter 2004-12-27 16:05:59 UTC
Created attachment 109139 [details]
dump file generated during failed install

Comment 2 Jeremy Katz 2004-12-27 18:27:09 UTC

*** This bug has been marked as a duplicate of 138419 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:07:48 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.