PXE boot broken or changed in 12.0.2?

RetroLarry · January 25, 2025 at 12:28 PM

The LE in our living room is booting KERNEL and SYSTEM from SSD but is mounting its HOME by NFS. This is still working after the update.
start by syslinux is
LABEL LibreElec
   MENU LABEL LibreElec
   LINUX /KERNEL
   INITRD /intel-ucode.img
   APPEND ip=:::::eth0:dhcp boot=/dev/sda1 disk=NFS=192.168.0.3:/srv/nfs4/pxe/libreelec mitigations=off overlay quiet

Every other room in our house is running a diskless LE setup for years. They're booting as documentated in https://wiki.libreelec.tv/configuration/network-boot
Yesterday I've updated KERNEL and SYSTEM on the (PXE) server and now none of the boxes are correctly booting up anymore.
iPXE start in detail is
kernel http://${next-server}/pxe/linux/libreelecx64
imgargs libreelecx64 ip=:::::eth0:dhcp boot=NFS=${next-server}:/srv/nfs4/pxe/libreelec disk=NFS=${next-server}:/srv/nfs4/pxe/libreelec overlay quiet

When they/one of them is booting up I can see that it is mounting its HOME - or tyring to do so...boot doesn't continue and no file in HOME is touched.

Jan 25 12:33:31 debianpve rpc.mountd[1457]: authenticated mount request from 192.168.2.11:950 for /srv/nfs4/pxe/libreelec (/srv/nfs4/pxe)
Jan 25 12:33:31 debianpve rpc.mountd[1457]: authenticated mount request from 192.168.2.11:857 for /srv/nfs4/pxe/libreelec (/srv/nfs4/pxe)
Jan 25 12:33:31 debianpve rpc.mountd[1457]: authenticated mount request from 192.168.2.11:816 for /srv/nfs4/pxe/libreelec/00012e00800e (/srv/nfs4/pxe)

Now I'm a little confused and looking for help...

**mglae** · January 25, 2025 at 12:57 PM

Add the required NFSV4 parameter, e.g. ,vers=4.2. The wiki was updated recently.

I'm still surprised that it was working before without, as reported in this thread too.

RetroLarry · January 25, 2025 at 1:43 PM

Quote from mglae

Add the required NFSV4 parameter, e.g. ,vers=4.2. The wiki was updated recently.
I'm still surprised that it was working before without, as reported in this thread too.

Thanks, but doesn't work. Tried with 3, 4 and 4.2 for "vers", added to boot= and/or disk=
Server setup is providing a working NFSv3 and v´4.2 for daily use, so this should be out of question.

What I'm still wondering about is the (new) message as shown in pic#1:
mkdir: can’t create directory ’/storage/00012e00500E”: Read-only file system
Sounds like HOME was found and mounted, but is read-only.

**mglae** · January 25, 2025 at 6:35 PM

That is exactly the error message of the other thread, therefore I expected the same solution.

boot= can be RO but disk= must be RW. Main change at this point is kernel update from 6.6.46 to 6.6.71but I have no idea what differs in detail.

RetroLarry · January 26, 2025 at 5:11 AM

And that's the weird thing to me... Assuming that KERNEL and SYSTEM is getting bootstrapped correctly, why is the same disk= instruction working when SYSTEM is coming from local (ie SSD), but not working when SYSTEM is coming from NFS?

However, I setup two "important" diskless LE boxes (they're all NUC like and having a SD slot) to boot from a syslinux'd SD, containing KERNEL and SYSTEM and still mounting their HOME from NFS. Also fast and reliable working like iPXE only, so I can live with that.

I'll leave that issue opened for more experiments and comments, if any.

auld1 · February 4, 2025 at 4:41 PM

I was facing this issue as well after upgrading my diskless PXE media PC, just dropped the images and saw a hanging black screen, after some boot messages read-only filesystem. Found this thread and did some research.

My debian NFS server (12/bookworm) had a (probably debian default)

RPCMOUNTDOPTS="--manage-gids"
in /etc/default/nfs-kernel-server

Removing that manage-gids (some server side permission handling according to the man pages) and adding ,vers=4.2 to the kernel boot and disk parameters as suggested above succeeded and LE 12.0.2 started up as expected.