Bug 100800 - RedHat 9 CD-ROM install fails with anaconda python error.
Summary: RedHat 9 CD-ROM install fails with anaconda python error.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 9
Hardware: i686
OS: Linux
high
high
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-07-25 16:59 UTC by Tom Browder
Modified: 2005-10-31 22:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-07-29 16:41:47 UTC
Embargoed:

Attachments (Terms of Use)
Error dump produced by anaconda during an attempted RedHat 9 install. (38.81 KB, text/plain)
2003-07-25 17:01 UTC, Tom Browder 		no flags Details
A further dump from a different PC on the other side of the Atlantic (40.62 KB, text/plain)
2003-07-27 09:28 UTC, Tim Greening-Jackson 		no flags Details
View All

Description Tom Browder 2003-07-25 16:59:24 UTC 
Description of problem:

Unable to install RedHat 9 on a pristine IBM IDE disk (or after creating a 
complete, standard Linux filesystem with /boot, and swap partitions).

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

RedHat 9

How reproducible:

Attempt to install from CD-ROM (which checks good).

Steps to Reproduce:
1.
2.
3.
    
Actual results:


Expected results:


Additional info:

See attached error text from anaconda error dump.
Comment 1 Tom Browder 2003-07-25 17:01:14 UTC 
Created attachment 93153 [details]
Error dump produced by anaconda during an attempted RedHat 9 install.
Comment 2 Tim Greening-Jackson 2003-07-27 09:28:31 UTC 
Created attachment 93177 [details]
A further dump from a different PC on the other side of the Atlantic

This is a dump of the same bug experienced on a generic PC: AMD 1800 processor,
IDE hard drive with existing RedHat 8.0 and Win 2000 partitions, Raytheon 9000
graphics card, UK keyboard
Comment 3 Michael Fulbright 2003-07-29 16:41:47 UTC 
This is a problem with the lvmtools being confused by data on your drive when it
scans for existing lvm.  This issue is addressed in our development version.
Note You need to log in before you can comment on or make changes to this bug.