PXE Boot - oom-killer

General Help
, ,
1

Hello there,

Just purchased a second hand HP Probook 6465 with 16GB memory, ... and apparently the bios is locked with a password, only allowing boot from internal Hard disk and network boot.
So ... i set up the old network boot, using tftp (via dnsmasq) ... as a matter of fact i found the instructions here (How To Install ZorinOS 16 Over LAN)
I tried it with zorin os Core 17.1 and 17.2 ... it all works until oom-kill decides the memory is overused and wget is killed at 33% of copying the Iso file over.

Is there any way to disable oom in the kernel or use another kernel? or should i go back to Zorin 16.2? Haven't tried that one yet ..

2

You should be able to disable oom through systemd as described here:
How do I disable the systemd OOM process killer in Ubuntu 22.04? - Ask Ubuntu

Essentially it boils down to this:

systemctl disable --now systemd-oomd

Then you should see something similar to this:

Removed /etc/systemd/system/multi-user.target.wants/systemd-oomd.service.
Removed /etc/systemd/system/dbus-org.freedesktop.oom1.service.

Then you can confirm if it's disabled via this:

systemctl is-enabled systemd-oomd

Going through the link may be beneficial, if it tried to restart itself. But I would wager those commands may be enough to get you through the install without worry too much about it. Although I haven't tried a network install in quite some time, so I could be wrong on that one.

I believe that you can just uninstall it with this also, unless it has changed recently:

sudo apt remove systemd-oomd
3

I haven't tested with Zorin OS 17 but I doubt that the ISO is what's causing the issue here... Try disabling OOM killer and see what happens, although so soon into the download it might be indication that something else is going on.

What machine are you using as the server? It could be that you need a more efficient server other than Python's, which might be struggling with larger files.
I'll have to try it out over the weekend and see if I can come up with something... but I'll likely won't have too much time to play with this the next few weeks or so :frowning:

4

See if the password issue gets resolved with this:

Or the risky method: