From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description of problem: File "/usr/bin/anaconda", line 633m in ? intf.run (id, dispatch, configFileData) File "/usr/lib/anaconda/text.py", line 427, in run dispatch,gotoNext() ........ File "/usr/lib/anaconda/fsset.py", line 984, in badblocksEntry val = (long(l[0]) * 100) / long(l[1]) Value Error: invalid literal for long(): 267840 267841 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Nothing special, just selecting scan for bad blocks at partitioning. Hard disk does have bad sectors, and check couldn't get pass them. Actual Results: Unhandled exception. Expected Results: It should have scanned bad blocks, and marked them. Nothing special. Additional info: harddisk: Old seagate ~500mb with few bad sectors.
Created attachment 56905 [details] anaconda crashed on the checking for bad sectors
I have had the exact same problem. Installed RHL 7.3 on a brand new system including out of the box HDD. Once I removed the "check for bad blocks", installed as before it worked fine. After install i used: badblocks /dev/hda6 and it found three bad blocks. Here is the anacron output: 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 mainloop () File "/usr/lib/python1.5/site-packages/gtk.py", line 2676, in mainloop _gtk.gtk_main() File "/usr/lib/anaconda/gui.py", line 529, in handleRenderCallback self.currentWindow.renderCallback() File "/usr/lib/anaconda/iw/progress_gui.py", line 135, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 417, in nextClicked self.dispatch.gotoNext() File "/usr/lib/anaconda/dispatch.py", line 144, in gotoNext self.moveStep() 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 thefsset.checkBadblocks(instPath) File "/usr/lib/anaconda/fsset.py", line 1007, in checkBadblocks self.badblocksEntry(entry, chroot) File "/usr/lib/anaconda/fsset.py", line 984, in badblocksEntry entry.fsystem.badblocksDevice(entry, self.progressWindow, chroot) File "/usr/lib/anaconda/fsset.py", line 210, in badblocksDevice l = string.split(num, '/') TypeError: argument 1: expected read-only character buffer, int found
*** Bug 65169 has been marked as a duplicate of this bug. ***
*** Bug 65162 has been marked as a duplicate of this bug. ***
*** Bug 65151 has been marked as a duplicate of this bug. ***
*** Bug 65013 has been marked as a duplicate of this bug. ***
*** Bug 64992 has been marked as a duplicate of this bug. ***
This error occurs when the badblocks command detects bad blocks on the system. The traceback occurred because the output from the badblocks command has changed, fooling our parser. If you get this traceback it means you have bad blocks on the drive it was testing. In the future an error dialog will be presented saying bad blocks have been detected.
*** This bug has been marked as a duplicate of 66181 ***
Wait a minute. Does the fact that this bug is closed mean nothing is going to be fixed? I can't install RedHat 7.3 because of this bug. I have several bad blocks in my hard disk, but that shouldn't mean the hard disk is unusable. That's the whole point of scanning for bad blocks -- so they can be marked as "do not use." Heck, DOS was able to handle the bad blocks. Are you saying this is too complicated for RedHat? I would very much appreciate this bug being fixed. I'd like to install 7.3. But till this bug is fixed, I can't.
*** Bug 67478 has been marked as a duplicate of this bug. ***
Time tracking values updated