Red Hat Bugzilla – Bug 67478
Value Error: invalid literal for long()
Last modified: 2007-04-18 12:43:40 EDT
Description of Problem:
During installation while checking for bad blocks, the "Value Error: invalid
literal for long(): 2943872" message appears, ending the installation.
Version-Release number of selected component (if applicable):
Red Hat Linux 7.3
Ask to (repartition and) check for bad blocks on the hard drive. This error has
occurred on both a laptop and a workstation installation
Steps to Reproduce:
1. Request check for bad blocks
Error and Termination of installation
Discovery of bad blocks, marking them as unusable if found, then continuation of
Additional Information: The following is the error messaged was saved in
"anacdump.txt" -- there's more info in the file if you want it.
Traceback (innermost last):
File "/usr/bin/anaconda", line 633, in ?
intf.run(id, dispatch, configFileData)
File "/usr/lib/anaconda/gui.py", line 353, in run
self.icw.run (self.runres, configFileData)
File "/usr/lib/anaconda/gui.py", line 814, 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/iw/progress_gui.py", line 135, in renderCallback
File "/usr/lib/anaconda/gui.py", line 417, in nextClicked
File "/usr/lib/anaconda/dispatch.py", line 144, in gotoNext
File "/usr/lib/anaconda/dispatch.py", line 209, in moveStep
rc = apply(func, self.bindArgs(args))
File "/usr/lib/anaconda/packages.py", line 375, in turnOnFilesystems
File "/usr/lib/anaconda/fsset.py", line 1007, in checkBadblocks
File "/usr/lib/anaconda/fsset.py", line 984, in badblocksEntry
entry.fsystem.badblocksDevice(entry, self.progressWindow, chroot)
File "/usr/lib/anaconda/fsset.py", line 211, in badblocksDevice
val = (long(l) * 100) / long(l)
ValueError: invalid literal for long(): 2943872
Created attachment 62644 [details]
Error msg and values saved by installer
The bad blocks check discovered bad blocks, and there is a bug in the reporting
of this fact.
We've fixed this reporting error in CVS.
Basically your drive has problems and the bad blocks check uncovered them.
*** This bug has been marked as a duplicate of 64711 ***