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): RHEL4 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 argument" With an option "--asprimary=1" - ignored and it becomes /dev/sdb2 instead of /dev/sdb1 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:
https://www.redhat.com/archives/kickstart-list/2000-November/msg00075.html Similar bug was reported 2000. I tried to follow the advice and use --onprimary but this option is unknown
--asprimary doesn't take an argument. It just says to make this partition a primary, not a specific primary partition.
(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?