Kickstart Insufficient

Support
1

Problem:

I am provisioning bare metal server and I am encountering this issue kickstart insufficient on anaconda prompt my hard drives are good and

I have partition defined correctly as it works for another model of hardware in my kickstart

image
image1920×933 126 KB

Unaware what can be causing this issue

2

It says no usable disks. Several possible issues. RAID controller or iSCSI not loaded, bad disk assignation, or bad partition template. Start it using a live media and look for disks and note down them (/dev/sda or /dev/nmvme…)

3

How do I make iSCSI load earlier i encountered that issue but was able to pass it by using the IP address instead of foreman URL

4

Are you using a diskless server? If not, probably you are missing a DUD driver. What model of server are you trying to install ? For me I require injecting drivers in Dell R620, as an example, because their controllers are not enabled anymore in vanilla kernel from enterprise linux derivatives
It’d be nice if you can describe a bit about your hardware
Usually kernel parameter for a missing driver (example Megaraid and a 8.5 kernel) will be inst.dd=https://elrepo.org/linux/dud/el8/x86_64/dd-megaraid_sas-07.717.02.00-1.el8_5.elrepo.iso

5

we are using a local hard drive once it get’s PXE boot.

My kickstart work for a similar POS model IBM 4900745 but not for this specific model which is a POS iBM 4800743 machine and it works with other model which is similar to it .

we don’t have iSCSI configured though and I’m new to foreman as well we are moving to OL 8 from Centos

6

Try to boot that machine using a normal media from OL8. If it does not recognize disks you are sure it’s related to additional drivers

7

I am able to see the disk in bios but during provisioning my POS is not able to see any disk

image

It’s not even showing the partition

8

check your ks.cfg,
it will be great if you can show your partition part

9

zerombr
clearpart --all --initlabel

part /boot --fstype="xfs" --ondisk=sda --size=1024
part pv.01 --fstype="lvmpv" --ondisk=sda --size=1024 --grow

volgroup vg_sda --pesize=4096 pv.01
logvol swap --fstype=“swap” --size=4096 --name=lv_swap --vgname=vg_sda
logvol / --fstype=“xfs” --percent=100 --name=lv_root --vgname=vg_sda

This is my kickstart partition which works for another similar model of POS machine but not for another model

If i provision this model with CentOS 7 it does detect the disk but not with OL8.5

10

Do AlmaLinux 8.10 or 9.4 show the disk in lsblk? Those two versions have some hardware re-enabled out-of-the-box.

Does lspci -nn show anything listed as removed in Chapter 11. Hardware enablement | Red Hat Product Documentation ?

dmesg | grep -i 'hardware is detected'?

11

for my ks.cfg, I did not need to specify the disk, I just use below, if your OS did not detect the disk, you may do a disk rescan and check the dmesg. It looks like the disk cannot be detected by the OS.

clearpart --all --initlabel

part /boot/efi --fstype efi --size=512 --label=EFIFS
part /boot --fstype xfs --size=1024 --label=BOOTFS --asprimary
part pv.01 --size=100 --grow

### Create a logical volume management (LVM) group.
volgroup vg0 --pesize=4096 pv.01

### Create logical volumes.
logvol / --fstype swap --name=swap --vgname=vg0 --size 2048
logvol / --fstype xfs --name=root --vgname=vg0 --size=25600
logvol /var --fstype xfs --name=var --vgname=vg0 --size=4096 --grow