Discussion:
`inst.ks` hides installation source on an ISO?
Brian C. Lane
2021-03-29 18:47:43 UTC
Permalink
Good Morning!
Duck Duck Go searches haven't helped me, and this problem feels like it
has an obvious answer if I put the question in front of the right person.
I'm adding a kickstart reference to an ISO. When I do, Anaconda (I
think) can't find the Installation Source. If I drop the "inst.ks" the
Installation Source is autodetected. So, an unmodified entry in
Assuming you are trying to install from the DVD via kickstart, does the
kickstart have 'cdrom' in it instead of 'url'?

https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#cdrom

Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
Young, Gregory
2021-04-05 16:50:46 UTC
Permalink
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=hd:LABEL=CentOS\x207\x20x86_64:/ks.cfg inst.sshd inst.graphical inst.noninteractive inst.noshell net.ifnames=0 selinux=0 rhgb quiet vga=792 modprobe.blacklist=floppy consoleblank=0 biosdevname=0 rdblacklist=nouveau nouveau.modeset=0

And this is the genisoimage command:

genisoimage \
-input-charset default \
-U \
-r \
-v \
-T \
-J \
-joliet-long \
-V "CentOS 7 x86_64" \
-volset "CentOS 7 x86_64" \
-A "CentOS 7 x86_64" \
-b "isolinux/isolinux.bin" \
-c "isolinux/boot.cat" \
-no-emul-boot \
-boot-load-size 4 \
-boot-info-table \
-eltorito-alt-boot \
-e "images/efiboot.img" \
-no-emul-boot \
-o "${SCRIPT_DIR}/disk.iso" \
"${BUILDDIR}/"


Greg

From: kickstart-list-***@redhat.com <kickstart-list-***@redhat.com> on behalf of David Barr <***@dafydd.com>
Date: Saturday, March 27, 2021 at 17:26
To: kickstart-***@redhat.com <kickstart-***@redhat.com>
Subject: `inst.ks` hides installation source on an ISO?
Good Morning!

Duck Duck Go searches haven't helped me, and this problem feels like it has an obvious answer if I put the question in front of the right person.

I'm adding a kickstart reference to an ISO. When I do, Anaconda (I think) can't find the Installation Source. If I drop the "inst.ks" the Installation Source is autodetected. So, an unmodified entry in isolinux/isolinux.cfg looks like this:

```
label linux
menu label ^Install CentOS Linux 8
kernel vmlinuz
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS-8-3-2011-x86_64-dvd quiet
```

This will autodetect the Installation Source. If I add a kickstart reference:

```
label linux
menu label ^Install CentOS Linux 8
kernel vmlinuz
append initrd=initrd.img inst.stag2=hd:LABEL=CentOS-8-3-2011-x86_64-dvd quiet inst.ks=hd:LABEL=CentOS-8-3-2011-x86_64-dvd
```

No Installation Source is found, but any `repo` entries in the kickstart file will be listed as "Additional Repositories." This is true for any variety of inst.ks reference. ("inst.ks=hd:/dev/sdb", "inst.ks=hd:/dev/sdb:/ks.cfg", etc.)

Am I not seeing a kickstart entry that specifies the Installation Source? Do I have to add another `append` argument that specifies the Installation Source? What am I missing?

Thanks!
David

Previous problems and solutions:

- https://unix.stackexchange.com/questions/640232/verified-good-mkisofs-for-centos-8/640786
- https://unix.stackexchange.com/questions/641277/centos-8-custom-iso-adding-ks-cdrom-ks-cfg-hangs-the-installer/641278

--

David/dafydd

PGP Public Key<https://keys.openpgp.org/vks/v1/by-fingerprint/042BC7A61817FD78AC85DD4ACC0B3F78FDDBD9AC>

“The hardest thing in the world<https://quoteinvestigator.com/2014/11/27/always-done/> is to change the minds of people who keep saying, ‘But we’ve always done it this way.’ These are days of fast changes and if we don’t change with them, we can get hurt or lost.” -- Admiral Grace Hopper
David Barr
2021-04-07 03:32:36 UTC
Permalink
Hi, Greg,

My scripted ISO creation process is at

https://github.com/dafydd2277/systemAdmin/tree/main/kickstart/centos8

It includes executing `blkid` on the exemplar ISO, and storing that
volume label in a variable to add to `mkisofs -V...`

I've run into so many challenges with kickstart on CentOS 8 that I have
three issues in that GitHub repository for keeping track. I've turned
two of those issues into bugs at bugzilla.redhat.com.

Thanks!
David
From your description, I suspect when you generated the iso, you
didn’t label it, or you gave it a different label than
“CentOS-8-3-2011-x86_64-dvd”. Also be careful of spaces in the label
 
append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64
inst.ks=hd:LABEL=CentOS\x207\x20x86_64:/ks.cfg inst.sshd
inst.graphical inst.noninteractive inst.noshell net.ifnames=0
selinux=0 rhgb quiet vga=792 modprobe.blacklist=floppy consoleblank=0
biosdevname=0 rdblacklist=nouveau nouveau.modeset=0
 
 
genisoimage \
    -input-charset default \
    -U \
    -r \
    -v \
    -T \
    -J \
    -joliet-long \
    -V "CentOS 7 x86_64"\
    -volset "CentOS 7 x86_64"\
    -A "CentOS 7 x86_64"\
    -b "isolinux/isolinux.bin"\
    -c "isolinux/boot.cat"\
    -no-emul-boot \
    -boot-load-size 4 \
    -boot-info-table \
    -eltorito-alt-boot \
    -e "images/efiboot.img"\
    -no-emul-boot \
    -o "${SCRIPT_DIR}/disk.iso"\
    "${BUILDDIR}/"
 
 
Greg
 
*Date: *Saturday, March 27, 2021 at 17:26
*Subject: *`inst.ks` hides installation source on an ISO?
Good Morning!
Duck Duck Go searches haven't helped me, and this problem feels like
it has an obvious answer if I put the question in front of the right
person.
I'm adding a kickstart reference to an ISO. When I do, Anaconda (I
think) can't find the Installation Source. If I drop the "inst.ks" the
Installation Source is autodetected. So, an unmodified entry in
```
label linux
  menu label ^Install CentOS Linux 8
  kernel vmlinuz
  append initrd=initrd.img
inst.stage2=hd:LABEL=CentOS-8-3-2011-x86_64-dvd quiet
```
```
label linux
  menu label ^Install CentOS Linux 8
  kernel vmlinuz
  append initrd=initrd.img 
inst.stag2=hd:LABEL=CentOS-8-3-2011-x86_64-dvd quiet
inst.ks=hd:LABEL=CentOS-8-3-2011-x86_64-dvd
```
No Installation Source is found, but any `repo` entries in the
kickstart file will be listed as "Additional Repositories." This is
true for any variety of inst.ks reference. ("inst.ks=hd:/dev/sdb",
"inst.ks=hd:/dev/sdb:/ks.cfg", etc.)
Am I not seeing a kickstart entry that specifies the Installation
Source? Do I have to add another `append` argument that specifies the
Installation Source? What am I missing?
Thanks!
David
-
https://unix.stackexchange.com/questions/640232/verified-good-mkisofs-for-centos-8/640786
<https://unix.stackexchange.com/questions/640232/verified-good-mkisofs-for-centos-8/640786>
-
https://unix.stackexchange.com/questions/641277/centos-8-custom-iso-adding-ks-cdrom-ks-cfg-hangs-the-installer/641278
<https://unix.stackexchange.com/questions/641277/centos-8-custom-iso-adding-ks-cdrom-ks-cfg-hangs-the-installer/641278>
--
David/dafydd
PGP Public Key
<https://keys.openpgp.org/vks/v1/by-fingerprint/042BC7A61817FD78AC85DD4ACC0B3F78FDDBD9AC>
“The hardest thing in the world
<https://quoteinvestigator.com/2014/11/27/always-done/> is to change
the minds of people who keep saying, ‘But we’ve always done it this
way.’ These are days of fast changes and if we don’t change with them,
we can get hurt or lost.” -- Admiral Grace Hopper
_______________________________________________
Kickstart-list mailing list
https://listman.redhat.com/mailman/listinfo/kickstart-list
--
David/dafydd

PGP Public Key
<https://keys.openpgp.org/vks/v1/by-fingerprint/042BC7A61817FD78AC85DD4ACC0B3F78FDDBD9AC>

“The hardest thing in the world
<https://quoteinvestigator.com/2014/11/27/always-done/> is to change the
minds of people who keep saying, ‘But we’ve always done it this way.’
These are days of fast changes and if we don’t change with them, we can
get hurt or lost.” -- Admiral Grace Hopper
Loading...