Description of problem: Kickstart using LVM partitioning with LUKS does not accept the --grow option How reproducible: Always Steps to Reproduce: 1. Kickstart using LUKS and LVM with a partition using --grow Actual results: "Kickstart insufficient" "('device cannot be smaller than 16 MiB', 'luks5' Expected results: Partition is created exactly as when not using LUKS Additional info: logvol /opt --name=lv_opt --vgname=vg_rocsoft --size=1 --grow --fsoptions="nodev" --encrypted --cipher=aes-cbc-essiv:sha256 --passphrase=xxxxxx
Matt, try using "... --size=32 --grow ...", it works for me. The installer behavior is a bit confusing to me. With "--size=1 --grow" and enough free space in the VG - for example 1 GiB, I would expect the installer to create the partitioning with 1 GiB LV/LUKS device and not failing with 'device cannot be smaller than 16 MiB'. Reassigning to blivet and attach installation logs from an installation with the following partitioning: bootloader --location=mbr zerombr clearpart --all --initlabel part /boot --asprimary --size=500 --label=boot part pv.01 --size=18000 volgroup SNAKEVG pv.01 logvol / --size=10000 --name=SNAKEROOT --vgname=SNAKEVG logvol /opt --size=1 --grow --name=SNAKEOPT --vgname=SNAKEVG --encrypted --passphrase XYZ
Confirmed the expected behavior with --size=32 --grow
This has been a quirk of '--size XX --grow' for years. The size needs to be larger than the minimum size of the partition is being created. So for / it needs to be big enough to hold the installed packages, and as the error says, in this case it has to be at least 16 MiB.
(In reply to Brian Lane from comment #4) > This has been a quirk of '--size XX --grow' for years. The size needs to be > larger than the minimum size of the partition is being created. So for / it > needs to be big enough to hold the installed packages, and as the error > says, in this case it has to be at least 16 MiB. Note that I only see the error when using --encrypted, otherwise it works fine with --size=1