Red Hat Bugzilla – Bug 28142
after 18032 error
Last modified: 2007-04-18 12:31:32 EDT
After downloading the update to fix bug 18032 I am now getting this error
at the same point in the process:
Traceback (innermost last):
File "/usr/bin/anaconda", line 438, in ?
intf.run(todo, test = test)
"/var/tmp/anaconda-7.0.1//usr/lib/anaconda/gui.py", line 336, in run
line 678, in run
"/usr/lib/python1.5/site-packages/gtk.py", line 2554, in mainloop
File "/usr/lib/python1.5/site-packages/gtk.py", line 125,
ret = apply(self.func, a)
"/var/tmp/anaconda-7.0.1//usr/lib/anaconda/gui.py", line 428, in
self.setScreen (self.currentScreen, self.nextClicked)
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/gui.py", line 466, in
new_screen = screen.getScreen ()
133, in getScreen
avail = apply(isys.spaceAvailable,
File "/usr/lib/anaconda/isys.py", line
10, in spaceAvailable
mount(device, "/mnt/space", fstype = fsystem)
File "/usr/lib/anaconda/isys.py", line 99, in mount
_isys.mount(fstype, device, location, readOnly)
SystemError: (22, 'Invalid
Local variables in innermost frame:
Make sure you boot the installer with the line
and enter the update disk when prompted.
I have made the boot update disk and am using the linux upgrades command.
I was told that the installation that I am choosing may be causing my problem.
I was attempting to install this as a partitionless install on a 3 Gig FAT32 partition.
I was told that there are two problems with this:
1. FAT32 only supports 2.0 GIG partitions and that I need to partition down to that size
(don't ask why it seems to work now for windows, but I believe them)
2. The speed penalty this will cause my 200MHz Cyrix chip is going to be unsatisfactory.
I will relook my installation - I am thinking that I'll try to move stuff around on the hard drive and make a linux partition
(stuff is spread out all over the place). I've been reading the manual and believe it or not I now know how to do it
in linux - but not yet in windows.
I'll try it tonight or tomorrow and get back to you with the results.
Closing due to inactivity. Please reopen if you have additional information to add.