Kickstart failure

https://forums.almalinux.org/t/kickstart-failure/2808

jmr

sej7278 Aug 2023 Not really the issue. The issue is: after a successful install, the parameters in the anaconda kickstart file DO NOT WORK in a kickstart file

sej7278 Aug 2023 ksvalidator is useless.

i wouldn’t really expect /root/anaconda-ks.cfg to work 100% for new installs, you need to put some work into it usually, as they’re parsed and rearranged and all sorts. even if you do a kickstart install, the anaconda version ends up different to the original.

did you try my suggestion of not specifying the size of / ? i’m thinking the disk sizes aren’t identical even if they are virtual ssd vs nvme (probably 512b vs 4kb sector size issue).

quartsize Aug 2023 If you open a shell in the installer environment, what are the full errors in the .log files in /tmp, particularly in storage.log?

azardo Aug 2023 Here’s mine:

For legacy bios: clearpart –all –initlabel partition /boot –asprimary –fstype ext4 –size=512 –maxsize=512 partition / –asprimary –fstype=ext4 –size=1024 –grow

For EFI: clearpart –all –initlabel partition /boot/efi –asprimary –fstype=efi –size=512 –maxsize=512 partition / –asprimary –fstype=ext4 –size=1024 –grow

For xfs I think you only have to modify “fstype”. 512 for /boot for me is sufficient, because I don’t have more than 3 kernels, but you can increase it as you need.

sej7278 Aug 2023 yeah could be as simple as /boot/efi is missing, which has to be vfat, can’t be xfs

part /boot –fstype xfs –size=512 –fsoptions=”nodev,nosuid,noexec” part /boot/efi –fstype vfat –size=512 –fsoptions=”umask=0077,fmask=0077,uid=0,gid=0,shortname=winnt” you could use reqpart, see docs:

Fedora Docs

[f36] Kickstart Syntax Reference Learn more about Fedora Linux, the Fedora Project & the Fedora Community.