Bug 37271 - Anaconda crashes with a backtrace after selecting upgrade
Anaconda crashes with a backtrace after selecting upgrade
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Brent Fox
Brock Organ
Yes This was part of a raid 1 system....
Depends On:
  Show dependency treegraph
Reported: 2001-04-23 16:55 EDT by Tom Diehl
Modified: 2007-04-18 12:32 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-04-24 14:04:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Backtrace from the install (10.57 KB, text/plain)
2001-04-24 07:19 EDT, Tom Diehl
no flags Details
fdisk -l output (1.16 KB, text/plain)
2001-04-24 12:52 EDT, Tom Diehl
no flags Details

  None (edit)
Description Tom Diehl 2001-04-23 16:55:13 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.

Reproducible: Always
Steps to Reproduce:
1.Start anaconda with "text" at the lilo prompt
2.select us keymap, then 101 key keyboard
3.Select upgrade

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
Comment 1 Brent Fox 2001-04-23 23:33:01 EDT
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.
Comment 2 Tom Diehl 2001-04-24 07:19:40 EDT
Created attachment 16205 [details]
Backtrace from the install
Comment 3 Brent Fox 2001-04-24 12:08:44 EDT
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.
Comment 4 Tom Diehl 2001-04-24 12:52:40 EDT
Created attachment 16245 [details]
fdisk -l output
Comment 5 Tom Diehl 2001-04-24 12:58:13 EDT
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.
Comment 6 Brent Fox 2001-04-24 14:04:50 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.