Red Hat Bugzilla – Bug 55425
Insatller stops during upgrade, Unhandled exception
Last modified: 2007-04-18 12:37:54 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.3) Gecko/20010801
Description of problem:
After most ( maybe all) of the packages had been installed, a dialong
appeared stating that an Unhandeled Exception had occurred and to post the
info in the window here. After having it dump the info to floppy, clicking
ok aborted the install and shutdown the system
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Burn 7.2 cds from ISOs
2.try to upgrade from 7.1
Actual Results: Unhandeld Exception
Expected Results: Continued install
Created attachment 35801 [details]
dump from anaconda
RH 7.1 system hosed by upgrade attempt. Attempt to perform full re-install gets
At any point in the install, did you switch to VC2 and go into the /mnt/sysimage
no I didn't do any console switching. But I can try again and do that if it will
gain useful info.
No, don't do that. :) When people do that, and don't leave the /mnt/sysimage
directory, the kernel will be unable to unmount the hard drive from the
filesystem because it is in use.
Some process is still holding a file that prevent the device from being
unmounted, but I don't know what it is without really having access to the
machine in order to look around in /proc. We have heard reports of this before,
but have not been able to reproduce it in house.
Did the upgrade leave your system in a usable state?
No, Linux won't boot. It would only go to LI
I'm running dual boot right now, so my system is useable.
There was an dialog midway through the process stating that it could not read a
certain RPM. (seems odd since this was a just unwrapped cd-r) After a couple of
tries it either worked or skipped it. Could this file still be open?
Ok, I re-burned the first CD, and it installed fine. Must have been a burning
glitch. However the ysytem still does not boot. I keep getting severe errors
during the disk scanning phase that freeses the system. Some form of kernel OOPS
Weird. Did you check the md5sums of the ISOs before you burned them? You are
seeing some pretty strange stuff.
I did not check the isos but i have fixed the problem. By booting with the
noathlon flag then upgrading the kernel. I looked about and seems some other
people with thunderbird chips ahve the same problem. now booting fine.
Ok. Yes, there seems to be some Thunderbird weirdness. My Athlon is
pre-Thunderbird, so I haven't seen it. I'm closing this bug since you have
found a workaround.