Jump to content

KRD 2018 + PXE

Recommended Posts

I use a fairly simple PXE server: I decompress the iso image in subfolder, adds a menu entry.
I can then boot a machine on the LAN to perform a installation, make material diagnosis, or... disinfection...

I seem to be missing knowledge. KRD 2018 cannot finish to start for the two following reasons:

  1. it can't find data/krd.iso
  2. it can't mount sda and sda1-6

The only thing I have is a mini-shell (already not bad).
Precision: I do not use NFS for the moment since useless with what's in place. I'll use it if I have no other solution.

After many unsuccessful tests, the menu entry was returned as found in krd/boot/grub/x86_64-efi/cfg/kav_menu.cfg :

linux krd/boot/grub/k-x86_64 net.ifnames=0 lang=en dostartx (isoloop=krd.iso)
initrd krd/boot/grub/initrd.xz

It's a syntax for GRUB, not for PXElinux...

Do you know of any arguments to give to the kernel that might to succeed? Or maybe some documentation?


a few remarks @K :
1. it would be very nice to have easily an azerty map, (or even better, azerty and bepo) in KRD/xfce B)
2. It would be nice if the giants would stop making us train AI..
   Please stop using captcha, recaptcha or any other tools their resembling. I'm sure you can be more inventive...
   If I work for a company's AI, shouldn't I be paid for this?

Best regards and thanks you for your attention.

Share this post

Link to post

It is not just only a matter of the right pxelinux arguments, it also requires of an additional INITRD_N24.1.GZ

See what Serva does for PXE booting KRD 2018 here:


Share this post

Link to post

(sorry, can't post answer since few days due to javascript/ckeditor issue)

It has worked on 1st try with :

    KERNEL        krd2018/boot/grub/k-x86_64
    APPEND initrd=krd2018/boot/grub/initrd.xz,krd2018/boot/grub/INITRD_N24.1.GZ net.ifnames=0 dostartx dodhcp netboot=http://[IP-address]/krd2018/data/* loadsrm=000-core.srm,001-xorg.srm,002-xfce.srm,003-kl.srm,004-krt.srm,005-bases.srm

Many thanks for this useful link!

Share this post

Link to post

you have to coy the whole content of the distribution ISO under your TFTP_ROOT/krd2018/

did you do that?

Share this post

Link to post


two things can be useful :

- say "hello" or something else… :)

- provide informations about what you want to do, how and -shortly- describe the environment

I encountered the same issue as you. Using Serva's initrd solved it because it does what

a classic initrd doesn't: lauch the .srm files.


Share this post

Link to post


this is my very first post here in this forum.
i have a tiny project, where is setup a PXE server to let PCs pxe boot into several different Linux Live systems.

now i tried to get the free Kaspersky Rescue Disk to PXE boot, but i run into two problems.

  1. on the ISO file there are only SHA512 files, but the init-script is looking for md5 files only and has only md5sum checks.
    i changed the init script by replacing all "md5" to "sha512" and "MD5" to "SHA512" what fixed the first issue.
  2. when i run into the problem, that when the system successfuly booted up via PXE, it doesn't resolv networknames properly, because of a missing /etc/resolv.conf file.
    also that i could fix by customizing the init-script.

but why there are those issues?
and can it be fixed on the kaspersky site, so i don't have to create ma own init script inside the initrd.xz file?

here the link to my project: RPi-PXE-Server

here the patch i did to fix the issues of the init-script (relativ to the krd.iso from 2018-12-21): init.patch

please fix that issue on kaspersky site... thank you.

Edited by beta-tester

Share this post

Link to post

forgot to tell the PXE menu entry to boot up free Kaspersky Rescue Disk:

LABEL kaspersky-rescue-x86
    MENU LABEL Kaspersky Rescue CD
    KERNEL http://pxe-server/nfs/kaspersky-rescue-x86/boot/grub/k-x86_64
    INITRD http://pxe-server/nfs/kaspersky-rescue-x86/boot/grub/initrd.xz,http://pxe-server/nfs/kaspersky-rescue-x86-initrd.xz
    APPEND netboot=nfs:// ro dostartx --
        Boot to Kaspersky Rescue CD



my customized initrd.xz is, that overlays the original broken init-script.

Edited by beta-tester

Share this post

Link to post

oh, and the kaspersky-rescue-x86.iso (krd.iso) is just mounted via an entry in /etc/fstab:

/srv/iso/kaspersky-rescue-x86.iso  /srv/nfs/kaspersky-rescue-x86  auto  ro,nofail,auto,loop  0  10

and nfs-exported via an entry in /etc/exports:

/srv/nfs/kaspersky-rescue-x86  *(ro,async,no_subtree_check,root_squash,mp,fsid=345e2088-04f8-11e9-91c7-e716ee7b802a)


Share this post

Link to post

Предлагаю вам аж 3 варианта загрузки по сети(PXE), но для начала нужно скачать образ KRD2018 и распаковать в папку kaspersky. Затем  скачать файлик INITRD_N24.1.GZ  в облаке https://yadi.sk/d/j9JEtqwdk2VY3A и положить в kaspersky/boot/grub, а так же создать md5 файла kernel.dat в той же папке что и данный файл, что бы получилось kernel.dat.md5. Это можно сделать в Total Commander или другой программе.

После этого создайте NFS шару на серваке с именем kaspersky, в которой лежат распакованные файлы из диска.

1. Загрузчик SYSLINUX

LABEL * Kaspersky Rrescue CD 2018
KERNEL kaspersky/boot/grub/k-x86_64
INITRD kaspersky/boot/grub/initrd.xz,kaspersky/boot/grub/INITRD_N24.1.GZ
APPEND netboot=nfs:// ro net.ifnames=0 lang=ru dostartx --

2. Загрузчик GRUB2

menuentry " 11. Kaspersky Rescue Disk 2018 (x64)" {
linux /syslinux/kaspersky/boot/grub/k-x86_64 netboot=nfs:// ro  net.ifnames=0 lang=ru dostartx --
initrd /syslinux/kaspersky/boot/grub/initrd.xz /syslinux/kaspersky/boot/grub/INITRD_N24.1.GZ

3. Загрузчик iPXE

set server_ip
set nfs_path /kaspersky
kernel nfs://${server_ip}${nfs_path}/boot/grub/k-x86_64        || read void
initrd nfs://${server_ip}${nfs_path}/boot/grub/initrd.xz       || read void
initrd nfs://${server_ip}${nfs_path}/boot/grub/INITRD_N24.1.GZ || read void
imgargs k-x86_64 initrd=initrd.xz initrd=INITRD_N24.1.GZ netboot=nfs://${nfs_path} ro net.ifnames=0 lang=ru dostartx --


ps: Сорри, что написал не па ангельску)

Edited by Маггер-Мясник

Share this post

Link to post

  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.