Bug 46288

Summary: Kickstart will not create /boot raid partition
Product: [Retired] Red Hat Linux Reporter: Kevin Keegan <kevin>
Component: anacondaAssignee: Brent Fox <bfox>
Status: CLOSED NOTABUG QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
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: 2001-07-13 15:34:13 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:

Description Kevin Keegan 2001-06-27 17:00:17 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)

Description of problem:
When using kickstart to configure a raid system, partitions are created in 
in descending size order, making the boot partition unusable (past 1024 
cyl. limit).  The order of the partitions in the ks.cfg file is irrelevant.

How reproducible:
Always

Steps to Reproduce:
1. Use ks.cfg sample below
2.
3.
	

Actual Results:  System will not boot

Additional info:


keyboard "us"
zerombr yes
clearpart --all
part raid.01 --size 25 --ondisk hda
part raid.02 --size 3500 --ondisk hda
part raid.03 --size 500 --ondisk hda
part /mnt/dos1 --size 250 --type=6 --ondisk hda
part swap --size 300 --ondisk hda
part raid.04 --size 1000 --grow --ondisk hda

part raid.11 --size 25 --ondisk hdb
part raid.12 --size 3500 --ondisk hdb
part raid.13 --size 500 --ondisk hdb
part /mnt/dos2 --size 250 --type=6 --ondisk hdb
part swap --size 300 --ondisk hdb
part raid.14 --size 1000 --grow --ondisk hdb

raid /boot --level 1 --device md0 raid.01 raid.11
raid / --level 1 --device md1 raid.02 raid.12
raid /var --level 1 --device md2 raid.03 raid.13
raid /home --level 1 --device md3 raid.04 raid.14
install
Comment 1 Brent Fox 2001-06-29 23:02:12 UTC 
I think you may be able to force raid.01 and raid.11 to be the first primary
partition on the drive.  From the Red Hat Linux 7.0 Reference Guide, you can use
the kickstart option:

--onprimary <N>
    Forces the partition to be created on primary partition <N> or fail. <N> can
be 1 through 4.

So, I think if you say:
part raid.01 --size 25 --ondisk hda  --onprimary 1
part raid.11 --size 25 --ondisk hdb  --onprimary 1

Then that will force both partitions to be hda1 and hdb1, repectively.  In
theory, this should avoid the 1024 cylinder limit problem.  Does this help?
Comment 2 Brent Fox 2001-07-13 15:34:09 UTC 
Closing due to inactivity. Please reopen if you have more information.