Red Hat Bugzilla – Bug 31717
Boot partition in kickstart is not allocated < 1024 if on RAID
Last modified: 2007-03-26 23:42:15 EDT
It (still...) seems to be impossible to auto-install a RAID1 system.
I include "part raid.xx --size yy --ondisk sda/b" and then "raid /zz
--level1 --device mdX raid.xx raid.yy". Then everything works, *except*
that /boot, being the smallest partition, appears at the end of the disks
(sda9/sdb9 as md0 in my case) and lilo won't work because of the too large
Trying to "help" a bit with specifying "--asprimary" for the "part"
statements that later becomes the /boot volume. Now it doesn't work at
all: on VC3 these messages appear:
Failed to allocate 'raid.01': Allocation succeeded
Failed to allocate 'raid.02': Allocation succeeded
and Anaconda gives me the "Disk Setup" main window to do it myself :-(.
Looking into a related issue at the moment, will see if same case.
Please attach your ks.cfg as an attachment please.
This defect considered MUST-FIX (Show-stopper) for Florence Gold
Created attachment 12666 [details]
ks.cfg file that causes the "Disk Setup" screen to appear
Leaving out the --asprimary flags in the previously attached ks.cfg file causes
the system to install, but putting /boot at an unreachable place (at the end of
Still leaves problem that if the boot partition is on RAID, it is not marked to
be put < 1024 cylinders. This code is in the GUI disk druid, but not the python
code for kickstart. Deferring for now because of lateness in cycle, and there is
Does this mean --asprimary (and --onprimary 1 as well?) now works?
This should be fixed in Enigma