Red Hat Bugzilla – Bug 37271
Anaconda crashes with a backtrace after selecting upgrade
Last modified: 2007-04-18 12:32:48 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.3-ac3-1 i586)
When doing a text upgrade anaconda crashes with a backtrace. Doing a
graphical upgrade the machine just hangs. I saved the backtrace from the
text install but I am not sure how to submit it to Bugzilla. I would prefer
not to copy it by hand.
Steps to Reproduce:
1.Start anaconda with "text" at the lilo prompt
2.select us keymap, then 101 key keyboard
Actual Results: anaconda barfs and asks for a disk to copy the backtrace
Expected Results: Perform normal upgrade to completion
This is a stock RH 6.2 system with all applicable upgrades. The system is a
P3-600 with 1 20 Gig IBM drive and 256 Megs of memory
I know it's kind of a pain to enter it by hand, but without it, we don't really
have a way to debug it.
Created attachment 16205 [details]
Backtrace from the install
Oh, it looks like you have some partitions on your system that used to be RAID
partitions...does this sound correct? I have seen this bug before...the
installer is having trouble reading partition on hda5. Can you tell me what
your existing partition table looks like? Just run /sbin/fdisk -l /dev/hda as
root and post the output here.
Created attachment 16245 [details]
fdisk -l output
Yes it was part of a raid 1 installation. It was not stable so I broke it down.
The partitions are still marked as raid autostart. There is only 1 disk in the
machine. I do not see why it should matter to anaconda unless it is broken. It
does not seem to matter to anything else. :-). Oh well if you think it will help
I could change the partition type. FWIW hda5 is the root partition. I do not
have any of the md partitions in the fstab, they are all hdax.
In this scenario, the installer sees a RAID partition which has been orphaned.
That is, the installer cannot find the other RAID partitions that it is looking
for in order to upgrade. Yes, this is a problem, but there's not much we can do
since there's no way of knowing where the other partitions have gone or how many
there were. What you need to do is run fdisk and wipe that partition (or just
change the type) and things will work fine. Please reopen this bug if this
doesn't solve the problem.