Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 65551

Summary: Unassigned RAID (type 0xfd) partitions cause traceback
Product: [Retired] Red Hat Linux Reporter: Heinz Deinhart <linux_rhbugz>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-06-04 15:28:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda generated dump none

Description Heinz Deinhart 2002-05-27 14:47:55 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (X11; U; Linux 2.4.18-3 i586)

Description of problem:
after selecting packages the installer dies with an exception (see dump)

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. take new compaq DL380
2. insert 2 9G SCSI drives and one 18G and one IDE CDROM
3. try to make install with root on raid partition

more details in anaconda dump
	

Additional info:
Comment 1 Heinz Deinhart 2002-05-27 14:48:58 UTC 
Created attachment 58666 [details]
anaconda generated dump
Comment 2 Heinz Deinhart 2002-05-27 16:08:42 UTC 
Found out more details:

This happens when you assign some raid partitions (type 0xfd) with fdisk and
then
do not assign all of them in the installer. Those unassigned will not be
formatted, and then the installer crashes when trying to start them up.

The reason i did not assign all of them is: it does not seem possible
to create a RAID 1 on top of a RAID 0 device.
Comment 3 Michael Fulbright 2002-06-04 15:28:43 UTC 
Assigning to an engineer.
Comment 4 Jeremy Katz 2002-06-04 15:52:33 UTC 
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 ***
Comment 5 Michael Fulbright 2002-12-20 17:38:25 UTC 
Time tracking values updated