Bug 70742 - Anaconda Crash: invalid literal for LONG() during installation
Anaconda Crash: invalid literal for LONG() during installation
Status: CLOSED DUPLICATE of bug 66181
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-08-04 13:55 EDT by Need Real Name
Modified: 2007-04-18 12:45 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-04 13:55:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-08-04 13:55:18 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)

Description of problem:
When reinstalling RH7.3 on a machine I previously had problems installing RH 
on, in fact ive installed the same distribution from the same installation 
disks on this machine 3 times now... the machine hangs after selecting packages.

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

How reproducible:

Steps to Reproduce:
1.Select packages
2.When Anaconda starts configuring it crashes

Actual Results:  An unhandled exception occurs.
Traceback (innermost last)
File "/usr/bin/anaconda", line 633, in ?

File "/usr/lib/anaconda/gui.py",line 353, in run

File "/usr/lib/python1.5/site-packages/gtk.py",
line 2676, in mainloop

File "/usr/lib/anaconda/gui.py" line 529
in handleRenderCallBack
File "/usr/lib/anaconda/fsset.py", line 211,
in badblock device

ValueError: Invalid literal for long(): 361428

Expected Results:  Installation should have proceeded as usual.

Additional info:

I believe the problem might be a new Memorex Thirty-two max CDR that I am using 
to read the installation disks from.

Is there anyway besides swapping the CD drive to remedy this situation?
Comment 1 Michael Fulbright 2002-08-05 11:33:48 EDT
The bad blocks check found bad blocks on the drive being tested - the installer
crashes because it did not handle that exception correctly.

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

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