Description of problem:
Upgrading a Dell Inspiron 8100 laptop from Red Hat 9.
About 70% of the way through the transfer of the system image from
the CD to my hard disk, I get an error message to the effect that
the copy could not be completed and that I am "probably out of disk
space." Since I know that I have at least 700MB on the / partition
(more than the size of the iso image), I dismiss the error and try
clicking next to begin the upgrade again. This is where the
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. select upgrade
2. select update boot loader
3. click begin upgrade
4. error message "probably out of disk space" during transfer of
system image to disk, click ok to dismiss
5. click next to begin upgrade again
Actual Results: crash
Expected Results: I would expect a message about how much disk
space is needed and how much is available if a full disk is indeed
the problem. Also, the "next" button should be disabled if an error
has occurred and it is not really possible to continue
There is a message on virtual console 2:
"-/bin/sh: relocation error: -/bin/sh: symbol version GLIBC_2.0 not
defined in file libc.so.6 with link time reference"
If I drop into the python debug shell after the exception and try to
exec anything in a shell with a command like:
I get the same error. If I boot from the cd in recovery mode, I do
not get shell errors.
The traceback says:
File "/usr/lib/anaconda/packages.py", line 669, in doPreInstall
f = open(instPath + "/etc/mtab", "w+")
IOError: [Errno 2] No such file or directory:
There is a comment in the source at that line about problems with
Created attachment 95843 [details]
anaconda error dump
Have same problem when updating from Fedora test3 on one machine.
Having ~2.5 GB of free disc space, the same fails appeared couple
time. Not possible to proceed. On other machine works without problem.
Does booting with 'linux allowcddma' help at all?
Yes, allowcddma gets me past the point where failure occurred
before, and installation now appears to be proceeding normally.
Also, the shell is now available and functioning on tty2.
Created attachment 95908 [details]
save of log crash
Have same problem when updating from RH9 on one machine Dell Precision
with option allowcddma the installation process works correctly in the
machine dell precision 330.
*** This bug has been marked as a duplicate of 109462 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.