error during installation from Hard Disk giving following message: Traceback (innermost last): File "/usr/bin/anaconda.real", line 438, in ? intf.run(todo, test = test) File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/text.py", line 1030, in run File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/textw/packages_text.py", line 33, in __call__ File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 539, in getCompsList File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/harddrive.py", line 43, in readComps File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/comps.py", line 459, in __init__ File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/comps.py", line 428, in readCompsFile File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/comps.py", line 101, in __getitem__ KeyError: indexhtml Local variables in innermost frame: self: <comps.HeaderList instance at 8234710> item: indexhtml ToDo object: (itodo ToDo p1 (dp2 S'method' p3 (iharddrive HardDriveInstallMethod p4 (dp5 S'fstype' p6 S'vfat' p7 sS'isMounted' p8 I1 sS'fnames' p9 (dp10 <failed>
*** Bug 17979 has been marked as a duplicate of this bug. ***
*** Bug 18059 has been marked as a duplicate of this bug. ***
*** Bug 17994 has been marked as a duplicate of this bug. ***
*** Bug 18121 has been marked as a duplicate of this bug. ***
Your indexhtml file may be corrupted - try comparing it to a version on a different mirror than where you got your current version to see if something is wrong. Hard drive installs have been tested and we have not seen this issue.
I received the same error during my install. I got my indexhtml file off the redhat ftp site. I replaced it, and all the other packages, after I first received the error, and still no luck.
I also originally downloaded indexhtml from the redhat site. Downloading indexhtml from 2 or 3 other sites and running cksum, I find that the indexhtml I have from redhat is the same as the one on the mirrors.
I believe I have a solve. I redownloaded RH7 with a RH6.1 install, and met with success. I suspect that forcing the FTP client into binary/image mode (TYPE I) for all files would solve it. I'll investigate further.
*** Bug 18154 has been marked as a duplicate of this bug. ***
Please retry downloading the image and make sure to use BINARY mode with your ftp client.
*** Bug 17920 has been marked as a duplicate of this bug. ***
*** Bug 17881 has been marked as a duplicate of this bug. ***
*** Bug 17754 has been marked as a duplicate of this bug. ***
*** Bug 16895 has been marked as a duplicate of this bug. ***
*** Bug 18280 has been marked as a duplicate of this bug. ***
*** Bug 18392 has been marked as a duplicate of this bug. ***
*** Bug 18325 has been marked as a duplicate of this bug. ***
*** Bug 18189 has been marked as a duplicate of this bug. ***
*** Bug 18482 has been marked as a duplicate of this bug. ***
*** Bug 18293 has been marked as a duplicate of this bug. ***
*** Bug 18242 has been marked as a duplicate of this bug. ***
*** Bug 18646 has been marked as a duplicate of this bug. ***
*** Bug 18641 has been marked as a duplicate of this bug. ***
*** Bug 18640 has been marked as a duplicate of this bug. ***
*** Bug 18487 has been marked as a duplicate of this bug. ***
*** Bug 18564 has been marked as a duplicate of this bug. ***
*** Bug 18730 has been marked as a duplicate of this bug. ***
Released errata RHBA-2000:084-02, which has a clearer dialog message when this problem occurs to help diagnose it better.
Traceback (innermost last): File "/usr/bin/anaconda", line 438, in ? intf.run(todo, test = test) File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/text.py", line 1030, in run rc = apply (step[1](), step[2]) File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/text.py", line 507, in __call__ if todo.doInstall (): File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 1480, in doInstall if self.method.systemMounted (self.fstab, self.instPath, self.hdList.selected()): File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/image.py", line 46, in systemMounted self.loopbackFile = mntPoint + fstab.filesystemSpace(mntPoint)[0][0] + \ File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/fstab.py", line 258, in filesystemSpace space.append((mntpoint, isys.fsSpaceAvailable(topMount + '/' + mntpoint))) File "/usr/lib/anaconda/isys.py", line 16, in fsSpaceAvailable return _isys.devSpaceFree(fsystem) SystemError: (2, 'No existe el fichero o el directorio') Local variables in innermost frame: fsystem: /mnt/sysimage//C ToDo object: (itodo ToDo p1 (dp2 S'method' p3 (iimage CdromInstallMethod p4 (dp5 S'progressWindow' p6 <failed> Local variables in innermost frame:
*** Bug 18763 has been marked as a duplicate of this bug. ***
*** Bug 18870 has been marked as a duplicate of this bug. ***
*** Bug 18895 has been marked as a duplicate of this bug. ***
*** Bug 18947 has been marked as a duplicate of this bug. ***
*** Bug 19071 has been marked as a duplicate of this bug. ***
*** Bug 19091 has been marked as a duplicate of this bug. ***
*** Bug 19125 has been marked as a duplicate of this bug. ***
*** Bug 19226 has been marked as a duplicate of this bug. ***
*** Bug 19304 has been marked as a duplicate of this bug. ***
*** Bug 19353 has been marked as a duplicate of this bug. ***
*** Bug 19377 has been marked as a duplicate of this bug. ***
I have tried all these fixes and I am still getting the same error message during the install. Does the update patch file have to be the same name? that is the only thing I can think of. I also tried to go back and re-install my previous RH6.2 (that was working great) and now I get the same error message trying to do this. Any Suggestions????
It happens to me even after I use the update img.
*** Bug 19095 has been marked as a duplicate of this bug. ***
I receive this bug while i try to mount my Windows disk during the instalation, but later when I resign with this option - error was not appear. I dont know but try this !
The installation is still not working after applying the bug fix RHBA-2000:084- 04: the installer is asking for the update disk, is reading the update, but fails at the same point as before, with the same error message. Is there a fix for this bug after all ?
I experience the same installation errors after the update. If this fix truly recognizes corrupt installation files during installation, then wouldn't I at least get a different error message. This still appears to be a widespread problem for anyone who has downloaded an image and is performing a hard drive installation.
OK let's try this (I do it - and it works): 1. Format your linux native or delete your native and create a new (with Partition Magic etc.) 2. During the instalation do not mount your Windows partition (or others - you can do it later in file : fstab) And that's all - but I dont guarantee success in all events. Try this - maybe it will be works.
*** Bug 19500 has been marked as a duplicate of this bug. ***
*** Bug 19547 has been marked as a duplicate of this bug. ***
*** Bug 19643 has been marked as a duplicate of this bug. ***
*** Bug 19645 has been marked as a duplicate of this bug. ***
*** Bug 19651 has been marked as a duplicate of this bug. ***
*** Bug 19728 has been marked as a duplicate of this bug. ***
*** Bug 19843 has been marked as a duplicate of this bug. ***
*** Bug 19845 has been marked as a duplicate of this bug. ***
*** Bug 19891 has been marked as a duplicate of this bug. ***
*** Bug 19943 has been marked as a duplicate of this bug. ***
*** Bug 19948 has been marked as a duplicate of this bug. ***
*** Bug 20276 has been marked as a duplicate of this bug. ***
*** Bug 20266 has been marked as a duplicate of this bug. ***
*** Bug 20217 has been marked as a duplicate of this bug. ***
*** Bug 20149 has been marked as a duplicate of this bug. ***
*** Bug 20133 has been marked as a duplicate of this bug. ***
*** Bug 20328 has been marked as a duplicate of this bug. ***
*** Bug 20350 has been marked as a duplicate of this bug. ***
*** Bug 20363 has been marked as a duplicate of this bug. ***
*** Bug 20436 has been marked as a duplicate of this bug. ***
*** Bug 20456 has been marked as a duplicate of this bug. ***
*** Bug 20125 has been marked as a duplicate of this bug. ***
*** Bug 19094 has been marked as a duplicate of this bug. ***
*** Bug 20664 has been marked as a duplicate of this bug. ***
*** Bug 20680 has been marked as a duplicate of this bug. ***
*** Bug 20671 has been marked as a duplicate of this bug. ***
*** Bug 20523 has been marked as a duplicate of this bug. ***
*** Bug 20156 has been marked as a duplicate of this bug. ***
I tried the update but the exact same error occurs. I also downloaded boot.img again. Well isn't this nice. The morons at redhat have posted a update that does not fix the problem and he status of this ticket is marked closed! IDIOTS!!!! hahahah I deleted slackware so I could install this crap!
*** Bug 20902 has been marked as a duplicate of this bug. ***
*** Bug 20894 has been marked as a duplicate of this bug. ***
*** Bug 20891 has been marked as a duplicate of this bug. ***
*** Bug 20825 has been marked as a duplicate of this bug. ***
*** Bug 20886 has been marked as a duplicate of this bug. ***
*** Bug 21358 has been marked as a duplicate of this bug. ***
*** Bug 21400 has been marked as a duplicate of this bug. ***
*** Bug 21332 has been marked as a duplicate of this bug. ***
*** Bug 21330 has been marked as a duplicate of this bug. ***
*** Bug 21324 has been marked as a duplicate of this bug. ***
What should I do if my redHat7 files are on a ext2 file system? I have to mount this drive,no other choice. There is not enough free space to copy RedHat7 on my existing linux partition. What should I do... Is there a real fix that will allow me to install from a ext2 file system? Come on msf stop to write "marked as a duplicate of this bug" and try to give to users a real fix. Thx redHat team.
Status Closed? I cannot download the anaconda fix, but IE5.5 reports it cannot find the server and CuteFTP reports it can't connect. Even so, the 'fix' would only clarify my problem at most. I have tried the solution suggested by msf of downloading with type set to binary (I) an have downloaded ALL the RPMS/base files again, and I still get the same error. As for not mounting my windows partition; I have no linux partition to put Redhat on, so I must point to one of my windows partitions to install. I had exactly the same error when I tried to install Redhat6.2. Can this be reopened and a solution found please.
Traceback (innermost last): File "/usr/bin/anaconda", line 438, in ? .... downloaded 7.0 fr/boot.img and RPMS on ftp.free.fr/mirrors/ for a hard drive install or upgrade from 6.1 I 'll try update-disk-20001009.img thanks
Yes I agree I have also done what suggested and no help. What kinda of suggestion is "Released errata RHBA-2000:084-02, which has a clearer dialog message when this problem occurs to help diagnose it better." Then closing the bug?? This isn't a viable solution
OK, add me to the list. I too, couldn't get the "fix" to work. I have tried to install from the CD, boot from disc, install boot "linux updates etc"...still getting the same araconda error messages. The araconda PATCH/fix DOESN'T WORK. Now, do I totally uninstall WinMe, and then attempt to reinstall, than partition the drive again, theN attempt to reinstall linux again....please tell me if this is going to work, before I go thru all this trouble? My eyeballs are falling out of my head after 8 hours of screwing around with this. Should I just trash WinMe , install Linux and say screw it? But I wanted a dual booting computer !!!!!! I sure as heck have plenty of drive space. This is a brand new computer! {{{{grrrr}}}} help Patti Patti
The Errata does not work. Binary downloading in FTP doesn't work. This is not the same bug as the "windows" partition problem. Why is this bug closed?
The fix doesn't work, i can't afford downloading again with a 44.000 bps connection, and, anyway, many guys here say it won't work with re-download either. It is rather irritating to see that this bug is marked as CLOSED, specially if you consider the large amount of people it has affected. Please note that this is not a marginal problem you can ignore: one of the installation methods is disabled, and all you say is 'this fix will help you make a better diagnose'. ?do i have to be a master programmer in order to instal an OS?. ?what's the use of bugzilla, then?
*** Bug 23537 has been marked as a duplicate of this bug. ***
*** Bug 23534 has been marked as a duplicate of this bug. ***
I go through package selection and all that fine; I get the "Loopback: creating loopback filesystem on /dev/hdb5..." window; it does its thing and eventually goes away, replaced by a "Formatting: formatting / filesystem" window, which lasts about 5-10 seconds or so, give or take...before I get a popup with the contents attached below. I can go no farther, and the install fails and I'm done. Now, before you go and hit Ctrl-V and paste what seems to have become the standard, no-fault reply, read on. I've read almost everything there is to read about this; I've tried the update img. No dice. You've mentioned corrupt HD install files over and over again. Well, I'm doing an FTP install, and have tried a variety of mirrors. Still no dice. I've remade all the boot disks, drivers disk, and updates disk several times. Carefully, methodically. Still no dice. And I'm apparently not the only one who still can't overcome the problem, despite no small amount of trying. My suggestion is that there really IS something more going on here than bad/corrupt FTP'ing. The update isn't working for everyone. Something ELSE is happening. Now, what is it? Please, toss this around with your folks a bit more. Thanks for your time. -agf ============ Traceback (innermost last): File "/usr/bin/anaconda.real", line 438, in ? intf.run(todo, test = test) File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/text.py", line 1030, in run File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/text.py", line 507, in __call__ File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 1466, in doInstall File "fstab.py", line 666, in makeFilesystems File "/usr/lib/anaconda/isys.py", line 116, in umount mountCount[what] = mountCount - 1 TypeError: bad operand type(s) for - ===========
Oh oh oh!!! Can I join the list too, please???? Same problem here. Tried everything, nothing works. Maybe Linux isn't as good as Windows NT anyway...... ;o) (maybe that will convince them to fix it)
tried doing a linux ks=floppy and found this problem used the update image and problem is STILL THERE!
Damn, this is such crap. At least it's possible to INSTALL windows98. Linux used to be known for stability and quick bugfixes, but now it seems they think more about getting quick cash here at RedHat. They release a system not thoroughly tested and then refuse to fix the bugs, now how fucked up is that?!? Ah, i have the same problem if you didn't already figure that one out: can't install, now i get a little different error message with the update disk, but that's it.
Apparently I have the same problem. The installation stopped 5 or 10 sec after the message of formating the disk. I tried the official RH7 box, ftp and buring CD, or ft installation. I also called and tried the update disks, using several methods. The RH7 is apparently a piece of junk. I then gave up this shity RH7 and downloaded Corel Linux 1.2 and burned the CD. The whole installation was so automatic and I did not have any problem with it. Apparently the people in Redhat need to work harder on this.
*** Bug 18136 has been marked as a duplicate of this bug. ***
I tried the fix and it does not work. why can't REDHAT put the correct fix out there to download. I bought the box set and I am not getting good telephone support. I am not very happy with this.
*** Bug 33480 has been marked as a duplicate of this bug. ***
*** Bug 34315 has been marked as a duplicate of this bug. ***
*** Bug 34229 has been marked as a duplicate of this bug. ***
*** Bug 35074 has been marked as a duplicate of this bug. ***
*** Bug 35804 has been marked as a duplicate of this bug. ***
I have to join the queue as well... the update patch doesn't work at all and the same error message is returned each time, I have downloaded the RPMS several times over now (in forced BINARY mode) and it makes no difference....
*** Bug 35893 has been marked as a duplicate of this bug. ***
*** Bug 35895 has been marked as a duplicate of this bug. ***
From feedback I see here, it seems that the errata we released does not fix this problem. Reopening bug.
*** Bug 36063 has been marked as a duplicate of this bug. ***
*** Bug 35176 has been marked as a duplicate of this bug. ***
We have changed the hard drive installation method to only install from the cd iso images stored on the hard drive. This will make checking the md5sum of the isos very easy, so the user can verify that nothing went wrong during the download. No matter what kind of error checking we try to put it, we can't account for a corrupted download, which I believe is the source of the problem. Resolving as 'Current Release' since 7.1 was released yesterday.
*** Bug 36686 has been marked as a duplicate of this bug. ***
*** Bug 23271 has been marked as a duplicate of this bug. ***
*** Bug 33168 has been marked as a duplicate of this bug. ***
*** Bug 37635 has been marked as a duplicate of this bug. ***
*** Bug 46459 has been marked as a duplicate of this bug. ***
*** Bug 19945 has been marked as a duplicate of this bug. ***
Created attachment 24510 [details] I tried the fix and it does not work. why can't REDHAT put the correct fix out there to download
*** Bug 51264 has been marked as a duplicate of this bug. ***
*** Bug 52949 has been marked as a duplicate of this bug. ***
Created attachment 37342 [details] This is an error while installing
I have so many times tried to install RH 7 on our machine at work a gateway model e-4200 and keep getting the anaconda error. I have tried so many red hat help forums but nobody seems to have a handle on it. RH salesperson suggestion is to call in for help pay $30 for the service ( since my warranty has expired ). I might as well purchase red hat 7.2 but what for, i am afraid i may not be able to install it on our machine. The other suggestion is that the CDs may be corrupted. Thanks alot, don't you guys test this stuff? Here is the text of what happens. Running anaconda-.... could not find platform independent libraries<prefix> could not find platform dependent libraries <exec_prefix> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>] 'import exceptions' failed; use -v for traceback Warning! Falling back to string-based exceptions 'Import site' failed; use -v for traceback Traceback (innermost last): File '/usr/bin/anaconda", line 3, in ? import sys,os, signal Import Error: No module named os Install exited abnormally.
I had the same problem (install exited abnormally -- received signal 11) and after I checked my RAM and removed the faulty one the installation went smoothly.