As I already wrote I had trouble to use my Synology. As @ronr suggested I switched to mount a local attached disk instead. Everything worked fine. So I have to find out what causes my Synology to create issues. Looks like it's some nfs authorization issue and nfs 3.0 vs nfs 4.1 issue I have to fix.
@ronr I used a RPi3 first to test PXE Boot and everything worked fine with your scripts. I then added a RPi1 but this one doesn't boot. journalctl shows
Do you have any idea why this PXE Boot fails?
@ronr I used a RPi3 first to test PXE Boot and everything worked fine with your scripts. I then added a RPi1 but this one doesn't boot. journalctl shows
Code:
Dec 27 21:34:45 raspberrypi-trixie-dhcptest dnsmasq-tftp[954]: file /pxe-images/pxe-boot/1cd6a6c9/start.elf not found for 192.168.0.100Dec 27 21:34:45 raspberrypi-trixie-dhcptest dnsmasq-tftp[954]: file /pxe-images/pxe-boot/autoboot.txt not found for 192.168.0.100Dec 27 21:34:45 raspberrypi-trixie-dhcptest dnsmasq-tftp[954]: file /pxe-images/pxe-boot/config.txt not found for 192.168.0.100Dec 27 21:34:45 raspberrypi-trixie-dhcptest dnsmasq-tftp[954]: file /pxe-images/pxe-boot/recovery.elf not found for 192.168.0.100Dec 27 21:34:45 raspberrypi-trixie-dhcptest dnsmasq-tftp[954]: file /pxe-images/pxe-boot/start.elf not found for 192.168.0.100Dec 27 21:34:45 raspberrypi-trixie-dhcptest dnsmasq-tftp[954]: file /pxe-images/pxe-boot/fixup.dat not found for 192.168.0.100Statistics: Posted by framp — Sat Dec 27, 2025 9:06 pm