You appear to want to copy an 80MB install image to the root filesystem in
order to do the install. If the disk doesn't have that much space the
install crashes and leaves the system in a difficult to recover state.
When the crash occurred it displayed an error box with buttons to save to
floppy and to scroll the display, but the user interface is frozen at this
point, so the display is useless.
I switched to VT1 and copied the following Python dump by hand:
File /var/tmp/anaconda-7.0//usr/lib/anaconda/iw/progress_gui.pu, Line 19 in
File /var/tmp/anaconda-7.0//usr/lib/anaconda/iw/ToDo.py Line 1451 in
DoInstall self.method.systemMounted(self.fstab, self.instPath,
File /var/tmp/anaconda-7.0//usr/lib/anaconda/iw/image.py Line 40 in
SystemMounted (self.progresswindow,_("Copying File"),
File /var/tmp/anaconda-7.0//usr/lib/anaconda/iw/util.py Line 144, in
Also the error message appeared as:
OSError: [Errno 28] No Space Left on Device
At this point my only choice was to reboot. This left the file systems
dirty. My next install it told me I needed to go into Linux to fsck. I did
that. Linux didn't come up cleanly because the root was full, so the mount
table couldn't be written during statup and therefore df couldn't work.
Also the rpm database appears to have been converted at this point, so rpm
no longer works on the system.
First, check that there is space for the install image before installing
Second, if possible allow that image to go on another partition on the
system. My root is only 128MB, so even when I freed enough space to get the
install on it it needed more space to do the actuall install and it failed
This defect is considered MUST-FIX for Winston Gold-release
I think this is fixed now - ewt?
RC-1 does not fix the problem. Now the installer decides that the file system
be installed on /home, but fails the space check on /home because the filesystem
doesn't exist. When I looked in the debugger I saw that the variable fsystem was
set to "/home". Interestingly
enough /home is not the file system with the most space on my system.
Did you use the RC1 update disk?
No I used straight RC1. I will try again with RC2.
This problem definitely occured w/o the updates disk. Reopen if RC2 still