RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 483170 [details]
Kickstart used

Description of problem:

When trying to install RHEL6 on a virtual machine (Virtual Box) with 4x 8GB hard drives, (or even tried on a physical machine with 4x 750GB drives)
using following scheme:
sda:
 256MB for raid1 for /boot
 [8GB-256M] for raid10 for LVM vgname=vgrp
sdb
 256MB for raid1 for /boot
 [8GB-256M] for raid10 for LVM vgname=vgrp
sdc
 256MB for raid1 for /boot
 [8GB-256M] for raid10 for LVM vgname=vgrp
sdd
 256MB for raid1 for /boot
 [8GB-256M] for raid10 for LVM vgname=vgrp
vgrp
 300MB swap
 the rest of the space for / ext4

It fails with Not enough free space for logical volume.

Tried with RHEL 6.0 and SL 6.0

part --size=1 --grow is really not good syntax to use.  You need to give a minimum --size= that will actually work to hold data, not just use the smallest number you can think of.

FYI, with RHEL6.3 at least this issue has been addressed.  not sure when between 6.0 and 6.3, but with 6.3 it is worked as expected now.

As for "just use the smallest number you can think of", please see the RHEL documents on the subject:

https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Installation_Guide/s1-kickstart2-options.html

https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-options.html


from those Install guide docs you will see this:
part raid.11 --size=1 --grow --ondisk=sda  
part raid.12 --size=1 --grow --ondisk=sdb  
part raid.13 --size=1 --grow --ondisk=sdc

so the "size=1" is actually in the examples on how to do the RAID setup in kickstart.  and it makes it the simplest approach to do a consistent raid setup on varying hardware.