Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 160791 - Kickstart ignores --asprimary 1 option
Summary: Kickstart ignores --asprimary 1 option
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: anaconda
Version: 4.0
Hardware: powerpc
OS: Linux
Target Milestone: ---
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2005-06-17 10:11 UTC by Tomas Baublys
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-06-17 15:44:45 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Tomas Baublys 2005-06-17 10:11:35 UTC
Description of problem:
Unable to setup the right partitioning order (same for both disks) in order to
use SW Raid on Power. There is a kickstart option "--asprimary N" which is
ignored if the setting "--asprimary=1" or produces "partition command requires
one anonymous argument" error if set like this: "--asprimary 1" 

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

How reproducible:
Every kickstart installation with partitioning below

Steps to Reproduce:
1. Use a system with 2 disks
2. Use following partitioning section in the ks.cfg:

bootloader --location=partition --append="console=hvc0 rhgb quiet"
clearpart --all --initlabel --drives=sda,sdb
# First prepboot partition
part prepboot --fstype "PPC PReP Boot" --size=4 --ondisk=sda --asprimary
#This partition will become Prepboot in the postinstall, needs to be 1.
partition on the disk
part /prep2 --fstype "vfat" --size=4 --ondisk=sdb --asprimary=1
# Second partition for kernel and yaboot.conf
part /boot --fstype "ext3" --size=100 --ondisk=sda --asprimary
# Copy on the second disk
part /boot1 --fstype "ext3" --size=100 --ondisk=sdb --asprimary
# All the space left is used for raid1 and LVM
part raid.01 --size=0 --grow --ondisk=sda
part raid.02 --size=0 --grow --ondisk=sdb
raid pv.3 --level=1 --device=md0 --fstype "physical volume (LVM)" raid.01 raid.02
volgroup volgrp01 --pesize=4096 pv.3
logvol / --fstype ext3 --size=2000 --name=rootlv --vgname=volgrp01
logvol /usr --fstype ext3 --size=1000 --name=usrlv --vgname=volgrp01
logvol /opt --fstype ext3 --size=1000 --name=optlv --vgname=volgrp01
logvol /var --fstype ext3 --size=512 --name=varlv --vgname=volgrp01
logvol /home --fstype ext3 --size=512 --name=homelv --vgname=volgrp01
logvol /tmp --fstype ext3 --size=512 --name=tmplv --vgname=volgrp01
logvol swap --fstype swap --size=512 --name=swap --vgname=volgrp01

Actual results:
With an option "--asprimary 1" - error "partition command requires one anonymous
With an option "--asprimary=1" - ignored and it becomes /dev/sdb2 instead of
Setting Prepboot2 to prepboot (what it will become later) reboot fails

Expected results:
setting "--asprimary=1" should set it to be the first partition on the disk

Additional info:

Comment 1 Tomas Baublys 2005-06-17 10:29:50 UTC
Similar bug was reported 2000.
I tried to follow the advice and use --onprimary but this option is unknown

Comment 2 Jeremy Katz 2005-06-17 15:44:45 UTC
--asprimary doesn't take an argument.  It just says to make this partition a
primary, not a specific primary partition.

Comment 3 Tomas Baublys 2005-06-17 15:56:22 UTC
(In reply to comment #2)
> --asprimary doesn't take an argument.  It just says to make this partition a
> primary, not a specific primary partition.

Is there any other option to set the partition number? Or at least to guarantee
the partitions are created in the order they are set?

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