Description of problem:
trying to use a usb key to boot PC and start installer and using hard disk
method fails with anaconda traceback
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. dd of diskboot.img on usb key
2. setup iso dvd image on not to be upgraded partition
3. choose to upgrade using hard disk method
anaconda traceback in harddrive.py line 100 in mountDirectory
proceeding of upgrade
At first during initial phase of the gui part I get the message
The installer has tried to mount image #1, but cannot find it on the hard disk
I choose to continue. In console I see the message
INFO path to valid iso with the path name of the correct iso file previously
I created a directory on the partition to be chosen for installation (not part
of the running FC6 system) where I only put the iso.
After configuration of grub advanced option and choosing to install to boot
sector of root partition I get the exception.
I'm going to attach screen dumps of gui message and console message.
Created attachment 153316 [details]
gui screenshot of traceback
Created attachment 153317 [details]
console message screenshot
I just realized after two days thinking before posting bug that actually the
partition used for hard disk method upgrade, is in /etc/fstab of the system to
be upgraded, too, even if not a "system" partition (such as / or /usr).
I'm going to check if this can be the problem, omittingit from /etc/fstab and
In any case if this is the problem, probably would have to be taken in
consideration, not giving instead a traceback...
Nothing changes. Same error.
Anaconda finds correct partition to upgrade (/dev/sda3), as before, but as soon
as I click next after setting the root partition as target for grub install, it
Through the messages in console I find one, don't know exactly when, but some
steps before exception, telling
error opening device /tmp/disk: errno 6 no such file or directory.
I'm gong to attach screen dump of mounted partitions at exception point and
output of bt command after choosing to debug the python exception (I don't know
how to debug python, I simply tried emulating somethng done in the past with C...)
Created attachment 153322 [details]
directories mounted at exception time
Created attachment 153324 [details]
output of bt command after choosing to debug exception
Sorry, I don't quite follow your additional info in comment #1. Can you explain
exactly what steps you are taking? Also, if you could attach a screenshot of
tty3 when the exception happens, that would also be helpful. Thanks.
Closing due to inactivity; please reopen if you have further information to add
to this report