Bug 73883 - Software RAID not working with kickstart
Summary: Software RAID not working with kickstart
Status: CLOSED DUPLICATE of bug 73884
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
(Show other bugs)
Version: 7.2
Hardware: All Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2002-09-12 21:34 UTC by John Airey
Modified: 2017-05-18 09:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-09-12 21:34:33 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description John Airey 2002-09-12 21:34:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; T312461)

Description of problem:
The anaconda installer does not create the correct size software RAID partitions

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

How reproducible:

Steps to Reproduce:
1. Install Red Hat Linux 7.2 with software raid partitions
2. Create ks.cfg file from anaconda-ks.cfg file and boot disk
3. Boot system

Actual Results:  An error appears that the system cannot install onto disks 
with size "None". The installation fails.

Expected Results:  There should have been no error and the correct RAID 
partitions created and the installation completed.

Additional info:

The problem is caused by the installer writing an incorrect anaconda-ks.cfg. 
Here's an example:

clearpart --linux
#part raid.2 --noformat --onpart hda2
#part raid.5 --noformat --onpart hdc2
#part swap --onpart hda3
#part swap --onpart hdc3
#raid / --fstype ext3 --level=RAID1 raid.2 raid.5

The solution is for software RAID partitions to be represented by start and end 
cylinders, since specifying size may lead to software RAID partitions being 
placed differently on the disk.  For the above example:

#clearpart --linux
#part raid.2 --noformat --start=2 --end=1001 --ondisk=hda
#part raid.5 --noformat --start=2 --end=1001 --ondisk=hdc
#part swap --start=1002 --end=1023 --ondisk=hda
#part swap --start=1002 --end=1023 --ondisk=hdc
#raid / --fstype ext3 --level=RAID1 raid.2 raid.5

This is also a problem with Red Hat 7.3

Comment 1 Michael Fulbright 2002-09-13 18:38:40 UTC

*** This bug has been marked as a duplicate of 73884 ***

Comment 2 John Airey 2002-09-14 10:53:03 UTC
Excuse me, but how can bug 73884 be a duplicate of this one? You can only 
register a bug against a single version of RedHat, but I've seen this bug on 
versions 7.2 and 7.3. Therefore I registered it twice, deliberately.

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