I use two RPi3 as clients and initially I detected the clients have issues to mount the root partition. I detected nfs 4.1 was used which was refused by the nfs server. When I updated the cmdline to use nfs 3 the clients booted. Then I detected I missed your comment to use pxe-add-bm for Trixie. When I used this add script nfs version 3 was used and the clients boot without any issue. Any reason you keep pxe-add ?I would suggest you test the scripts contained in pxe-boot.zip on a clean Trixie installation to see if they satisfy your needs (use pxe-add-bw instead of pxe-add on Bookworm and Trixie). I just tested them here with Trixie, using a Raspberry Pi 5 as the server and a Raspberry Pi 4 as a client.
On thing I noticed: The clients reboot two times until they are ready to be used. The image I provided in pxe-add was a Trixie lite image which completed the initial reboots of a fresh installed RaspbianOS already. I have no idea why additional two reboots happen.
Next I detected /pxe-boot was not mounted on the client. Fortunately I already setup a dnsmasq proxy server by hand and had the same issue: For some reasons the client is able to mount /pxe-root but fails with /pxe-boot. Solution: Install nfs-common in the client image or much better, install nfs-common in the image which will be used by the clients in pxe-add.
But other than that it was easy to setup the dnsmas proxy. Your script works perfect
Would be great if you could add the capability to use the root filesystem of the clients on a different system than the dnsmasq server. That way a more powerful nfs server, e.g. a NAS, can provide the client root filesystem.Statistics: Posted by framp — Fri Dec 12, 2025 9:13 pm