Red Hat Bugzilla – Bug 36604
Anaconda failure... First time user attempt
Last modified: 2007-04-18 12:32:43 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; Win 9x 4.90)
After creation of the "Loopback File System", some type of 'critical
failure' occured. I was informed to report this bug to bugzilla
Steps to Reproduce:
1. Reboot machine
2. follow installation menu
3. choose 1000 (mb) partition (for partitionless installation with
4. Wait while system installs itself. Will crash with anaconda file
dump every time.
Actual Results: system crashes with anaconda file dump "anacdump.txt"
Expected Results: should have progressed to use floppy to create boot
disk for partitionless installation under Windows ME.
I have absolutely NO idea what all of this means. I'd hate to think that
this OS is incompatible with my hardware... Any ideas? Following text is
the ACTUAL anacdump.txt file saved to my floppy disk by the system.
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
rc = apply (step(), step)
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/text.py", line 507, in
if todo.doInstall ():
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 1466, in
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/fstab.py", line 664, in
File "/usr/lib/anaconda/isys.py", line 116, in umount
mountCount[what] = mountCount - 1
TypeError: bad operand type(s) for -
Local variables in innermost frame:
This is a dupe of bug #19523. Please look at it for more details. Your options
are to use the installer updates disk (see bug #19523) or download Red Hat Linux
7.1, which does not have this problem.
*** This bug has been marked as a duplicate of 19523 ***