Bug 184284 - Software RAID5 error
Summary: Software RAID5 error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-07 20:35 UTC by Chris Elsmore
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version: fc5
Clone Of:
Environment:
Last Closed: 2006-03-21 16:18:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
anaconda.log and syslog from failed install (10.81 KB, application/x-zip)
2006-03-07 20:35 UTC, Chris Elsmore
no flags Details

Description Chris Elsmore 2006-03-07 20:35:07 UTC
Description of problem:

When using 3 SATA harddisks on a Chaintech ZNF3-250, and creating a RAID5
software array, the FC5T3 install encounters a error, with the message: "The
system has encountered a serious error and install cannot continue. It is
nessasary to restart your computer."

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

FC5T3

How reproducible:

Easily, by following below steps.

Steps to Reproduce:
1. Run FC5T3 install.
2. Setup a Software RAID5 with 3 disks.
3. Install falls over when it starts installing.
  
Actual results:

Install encounters error, and cannot continue.

Expected results:

Install to create software RAID5 array, and carry out installation.

Additional info:

Ananconda.log and syslog are included.

Comment 1 Chris Elsmore 2006-03-07 20:35:07 UTC
Created attachment 125775 [details]
anaconda.log and syslog from failed install

Comment 2 Jeremy Katz 2006-03-07 22:25:08 UTC
It looks like the kernel threw out the device as not being sane for creating a
RAID and mdadm didn't error.

Is this reproducible for you?

Comment 3 Chris Jones 2006-03-08 00:13:46 UTC
Yes

Comment 4 Sitsofe Wheeler 2006-03-08 08:16:08 UTC
The problem happens every time the RAID5 is newly configured during the Fedora
install. In order to work around the problem it is possible to use an Ubuntu
installation CD to configure the RAID5 setup and create the md device. You can
then reboot to the Fedora install and so long as you do not change the RAID
device (formatting is OK) anaconda does not error.

Comment 5 Chris Elsmore 2006-03-08 13:48:24 UTC
Yes, the bug is reproducible.

Comment 6 Chris Lumens 2006-03-09 16:31:47 UTC
This should be fixed in rawhide today by a new mdadm package.

Comment 7 Chris Jones 2006-03-21 15:58:35 UTC
This apears to have been fixed in the final FC5 installer


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