Can no longer PXE boot LE 13

I PXE boot one of my machines Radka X4 (Intel n100) and I recently updated it and and it fails to load. Going back in the nigthlies PXI boots appears to have stopped working for me with the Dec 6. I can't see all the FAILED services on boot but it hangs at Reache dtarget kodi.target and freezes Any suggestion how I might diagnose this?

I did trying renaming my system based storage though and it doesn't recreate it instead I get an error during boot

writer can't create directory '/storage/the number': Read onlyfile system

Error in mount_storage: mount command could not mount 172.16.3.4:/mnt/media/storage/same number

Quote from mglae

Assuming you are using Generic (GBM) this is usually caused by kodi crashing. If ssh is enabled login should still be possible. With adding systemd.debug_shell to the kernel command line a debug shell can be reached at console 3 with Alt-F3 as long kodi is not running.

If you are using the overlay parameter the message is caused by this mkdir. Please check the access rights of 172.16.3.4:/mnt/media/storage

Yes it is Generic. If I drop KERNEL/SYSTEM back to the LE 12 or LE `13 before Dec 6th the mkdir works so what access right would have changed?

Thanks though I now can drop to the shell with ALT-F3 and can see that when it works mount has

172.16.3.4:/mnt/media/storage/1002b58608ea on /storage type nfs (rw,noatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=172.16.3.4,mountvers=3,mountproto=tcp,local_lock=all,addr=172.16.3.4)

and in the newest version the line is the same but that rw turns to ro but I can see existing files.

Ok remounting rw does work which allows me to start Kod and I have this log now https://paste.libreelec.tv/clever-wolf.log so maybe related to

Dec 17 19:59:29.015980 172.16.3.29 kernel: Kernel command line: root=/dev/ram0 rdinit=/init usbcore.autosuspend=-1 BOOT_IMAGE=/KERNEL ip=dhcp boot=NFS=172.16.3.4:/srv/tftp disk=NFS=172.16.3.4:/mnt/media/storage overlay systemd.debug_shell
Dec 17 19:59:29.015991 172.16.3.29 kernel: Unknown kernel command line parameters "overlay BOOT_IMAGE=/KERNEL boot=NFS=172.16.3.4:/srv/tftp disk=NFS=172.16.3.4:/mnt/media/storage", will be passed to user space.

I looked for a tmpfiles.d that might be missed but I don't see anything around Dec 6.

I am pretty sure the change has something to do with nfs4. I can't specify disk=NFS4 as a kernel parameter as far as I can tell but I have been able to use /flash/mount-storage-sh to manually mount /storage

OVERLAY_DIR=$(cat /sys/class/net/eth0/address | tr -d :)
mount  -t nfs4 172.16.3.4:/mnt/media/storage/$OVERLAY_DIR /storage -o rw,noatime

It seems like the busybox mount that is used at this early stage before the full mount.nfs etc is available is not good at working with nfs versions

OK, I did try vers=3 from the command line and that failed but I will try the other options

mount -t nfs 172.16.3.4:/mnt/media/storage/$OVERLAY_DIR /storage -o rw,noatime,vers=3

Martin

Quote from mglae

To mount a nfs4 server use e.g. disk=NFS=172.16.3.4:/mnt/media/storage,vers=4.2

As a test you may even try with disk=NFS=172.16.3.4:/mnt/media/storage,vers=3 to see if there is any issue in the LE parsing code.

So trying the test it works with vers=4.2 but fails with vers=3 Here is the working log FWIW https://paste.libreelec.tv/flowing-mullet.log

Thanks both of you.