Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When multiple disks are used for a volume group anaconda provides the following errors:
GUI & Text installs produce:
Unable to allocate requested partition scheme
Output of /tmp/anaconda.log (relevant lines):
is_valid* all return true
is_valid_stage1_device(sda) = true
stage1 device cannot be of type lvmvg
stage1 device cannot be of type lvmlv
Version-Release number of selected component (if applicable):
RHEL-7.0
RHEL-7.1
RHEL-7.2
How reproducible:
When multiple volumes are combined into one volume group the error can be produced.
Steps to Reproduce:
The disk configuration used can be found under the 'additional info' section.
The disk(s) are partitioned as follows:
c0:
|- d0
|- p0 (sda)
|- p1 (sdb)
|- d1
|- p0 (sdc)
|- p1 (sdd)
Actual results:
Errors about partition scheme
Expected results:
The same kickstart disk partitions work in RHEL-6.5, 6.6 & 6.7.
Additional info:
# Zero the MBR
zerombr
# Clear out partitions for sda
clearpart --all --initlabel --drives=sda
# Create a /boot partition on sda of 500MB
part /boot --size=500 --fstype="ext4" --ondisk=sda
# Create an LVM partition of 172337MB on sda
part pv.root --size=172337 --ondisk=sda --grow --asprimary
# Create the root volume group
volgroup rootvg --pesize=4096 pv.root
# Create a memory partition of 31962MB
logvol swap --fstype="swap" --name="swaplv" --vgname="rootvg" --size=31962
# Create logical volume for the / mount point
logvol / --fstype="ext4" --name="rootlv" --vgname="rootvg" --size=102400
# Create logical volume for the /var mount point
logvol /var --fstype="ext4" --name="varlv" --vgname="rootvg" --size=40960
# Create logical volume for the /export/home mount point
logvol /export/home --fstype="ext4" --name="homelv" --vgname="rootvg" --size=10240
# Create logical volume for the /tmp mount point
logvol /tmp --fstype="ext4" --name="tmplv" --vgname="rootvg" --size=2048
# Create new physical volume on sdb as pv.optapp.1
part pv.optapp.1 --size=78741 --grow --ondisk=sdb
# Create new physical volume on sdc as pv.optapp.2
part pv.optapp.2 --size=100352 --grow --ondisk=sdc
# Create new physical volume on sdd as pv.optapp.3
part pv.optapp.3 --size=100352 --grow --ondisk=sdd
# Create new physical volume on sde as pv.optapp.4
part pv.optapp.4 --size=78741 --grow --ondisk=sde
# Create a new volume group with all the physical volumes
volgroup optappvg pv.optapp.1 pv.optapp.2 pv.optapp.3 pv.optapp.4 --pesize=4096
# Create a new logical volume for /opt/app mount point
logvol /opt/app --fstype="ext4" --name="optapplv" --vgname="optappvg" --size=268639
I have attached the logs as requested. If necessary I can provide the kickstart script used but the attachment titled 'Included disk partitioning' is the output of that tool.
FYI: If I modify the /tmp/ks-diskconfig file which is used to create the LVM & physical partitions to comment out the following I do not receive errors:
I am accommodating for the ext4 overhead per disk by %2 of the total bytes prior to the values shown below.
# Create new physical volume on sdb as pv.optapp.1
#part pv.optapp.1 --size=78741 --grow --ondisk=sdb
# Create new physical volume on sdc as pv.optapp.2
#part pv.optapp.2 --size=100352 --grow --ondisk=sdc
# Create new physical volume on sdd as pv.optapp.3
#part pv.optapp.3 --size=100352 --grow --ondisk=sdd
# Create new physical volume on sde as pv.optapp.4
#part pv.optapp.4 --size=78741 --grow --ondisk=sde
# Create a new volume group with all the physical volumes
#volgroup optappvg pv.optapp.1 pv.optapp.2 pv.optapp.3 pv.optapp.4 --pesize=4096
# Create a new logical volume for /opt/app mount point
#logvol /opt/app --fstype="ext4" --name="optapplv" --vgname="optappvg" --size=268639
20:28:29,361 ERR anaconda: storage configuration failed: The following problem occurred on line 35 of the kickstart file:
Specified unpartitioned disk sdb in partition command
Perhaps you forgot to add sdb to the clearpart drive list?
Ok you can close this out. Where version 6.5, 6.6 & 6.7 allow the originally attached ks-diskconfig version 7.x for multiple disks do require the following modification:
# Worked for 6.5, 6.6 & 6.7
clearpart --all --initlabel --drives=sda
# Required for > 7.x
clearpart --all --initlabel --drives=sda,sdb,sdc,sdd,sde
Thanks, looks like this bug was filed in error.
Description of problem: When multiple disks are used for a volume group anaconda provides the following errors: GUI & Text installs produce: Unable to allocate requested partition scheme Output of /tmp/anaconda.log (relevant lines): is_valid* all return true is_valid_stage1_device(sda) = true stage1 device cannot be of type lvmvg stage1 device cannot be of type lvmlv Version-Release number of selected component (if applicable): RHEL-7.0 RHEL-7.1 RHEL-7.2 How reproducible: When multiple volumes are combined into one volume group the error can be produced. Steps to Reproduce: The disk configuration used can be found under the 'additional info' section. The disk(s) are partitioned as follows: c0: |- d0 |- p0 (sda) |- p1 (sdb) |- d1 |- p0 (sdc) |- p1 (sdd) Actual results: Errors about partition scheme Expected results: The same kickstart disk partitions work in RHEL-6.5, 6.6 & 6.7. Additional info: # Zero the MBR zerombr # Clear out partitions for sda clearpart --all --initlabel --drives=sda # Create a /boot partition on sda of 500MB part /boot --size=500 --fstype="ext4" --ondisk=sda # Create an LVM partition of 172337MB on sda part pv.root --size=172337 --ondisk=sda --grow --asprimary # Create the root volume group volgroup rootvg --pesize=4096 pv.root # Create a memory partition of 31962MB logvol swap --fstype="swap" --name="swaplv" --vgname="rootvg" --size=31962 # Create logical volume for the / mount point logvol / --fstype="ext4" --name="rootlv" --vgname="rootvg" --size=102400 # Create logical volume for the /var mount point logvol /var --fstype="ext4" --name="varlv" --vgname="rootvg" --size=40960 # Create logical volume for the /export/home mount point logvol /export/home --fstype="ext4" --name="homelv" --vgname="rootvg" --size=10240 # Create logical volume for the /tmp mount point logvol /tmp --fstype="ext4" --name="tmplv" --vgname="rootvg" --size=2048 # Create new physical volume on sdb as pv.optapp.1 part pv.optapp.1 --size=78741 --grow --ondisk=sdb # Create new physical volume on sdc as pv.optapp.2 part pv.optapp.2 --size=100352 --grow --ondisk=sdc # Create new physical volume on sdd as pv.optapp.3 part pv.optapp.3 --size=100352 --grow --ondisk=sdd # Create new physical volume on sde as pv.optapp.4 part pv.optapp.4 --size=78741 --grow --ondisk=sde # Create a new volume group with all the physical volumes volgroup optappvg pv.optapp.1 pv.optapp.2 pv.optapp.3 pv.optapp.4 --pesize=4096 # Create a new logical volume for /opt/app mount point logvol /opt/app --fstype="ext4" --name="optapplv" --vgname="optappvg" --size=268639