Red Hat Bugzilla – Bug 64562
Installer dies when installing on drive with unconfigured raid partitions
Last modified: 2007-04-18 12:42:28 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.1 (X11; Linux i586; U;) Gecko/20020417
Description of problem:
While attempting fresh install on a SCSI based system (w/ aic7899 onboard),
anaconda dies while preparing the filesystem for install. I partition my drives
using fdisk as follows:
and then assign them as follows:
/dev/sda1 type=83 /boot ext3 format=yes
/dev/sda2 type=82 Linux swap
/dev/sda3 type=83 / ext3 format=yes
on both configs while leaving sda4 and/or sda5 alone.
I then select my packages and begin install but anaconda dies either shortly
after or during the formats of /dev/sda1-3
I have 2 anacdumps for each config.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. fdisk configure partitions as shown above
2. assign mount points as shown above
3. start installation of packages
Actual Results: Anacond dumped and requests reboot (dumps attached)
Expected Results: Installation should have proceeded to completeness.
Created attachment 56584 [details]
Anaconda dump from install of simple_config1
Created attachment 56585 [details]
Anaconda dump from install of simple_config2
Why is there just one partition of type 0xfd?
There is only one partition of type 0xfd in order to show the problem in the
simplest form. We first discovered the problem while setting up 6 drives. Each
drive had 6 partitions of type 0xfd, but we didn't configure them in Anaconda
because we have our own benchmarking scripts to do that afterwards. I tested
several variations and they all died if you had an unconfigured 0xfd partition.
I finally set all the partitions to typ 0x83 then after the install, changed
them all back to 0xfd. I would like it to work the first way though.
Ok thank you I understand now. I will forward this issue to a developer.
Can you try using the update disk available at
http://people.redhat.com/~katzj/73raid.img? If you put that on a separate
floppy and boot with 'linux updates', inserting the disk when prompted, it
should fix the problem.
*** This bug has been marked as a duplicate of 64734 ***