Hi,
I set up my existing MOX with the “Turris MOX network boot” package installed. I also have 2 more Power WIFI MOX devices that I would like to boot over the network from my preexisting MOX. However when I remove the SD card from the Power WIFI devices, they do not boot up properly. The log on the existing MOX shows that the designated APs attempt to boot over the network:
Jun 11 08:29:58 turris dnsmasq-dhcp[3482]: DHCPDISCOVER(br-lan) d8:58:d7:00:cf:1a
Jun 11 08:29:58 turris dnsmasq-dhcp[3482]: DHCPOFFER(br-lan) 192.168.1.156 d8:58:d7:00:cf:1a
Jun 11 08:29:58 turris dnsmasq-dhcp[3482]: DHCPREQUEST(br-lan) 192.168.1.156 d8:58:d7:00:cf:1a
Jun 11 08:29:58 turris dnsmasq-dhcp[3482]: DHCPACK(br-lan) 192.168.1.156 d8:58:d7:00:cf:1a
Jun 11 08:29:58 turris dnsmasq-tftp[3482]: file /srv/tftp/C0A8019C.img not found
Jun 11 08:29:58 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/01-d8-58-d7-00-cf-1a not found
Jun 11 08:29:58 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0A8019C not found
Jun 11 08:29:58 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0A8019 not found
Jun 11 08:29:58 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0A801 not found
Jun 11 08:29:58 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0A80 not found
Jun 11 08:29:58 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0A8 not found
Jun 11 08:29:58 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0A not found
Jun 11 08:29:58 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0 not found
Jun 11 08:29:58 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C not found
Jun 11 08:29:58 turris dnsmasq-tftp[3482]: sent /srv/tftp/pxelinux.cfg/default-arm-mvebu-turris_mox to 192.168.1.156
Jun 11 06:29:58 turris dhcp_host_domain_ng.py: DHCP update hostname [MOX-DG,192.168.1.156]
Jun 11 06:29:58 turris dhcp_host_domain_ng.py: Refresh kresd leases
Jun 11 06:30:00 turris crond[770]: (root) CMD (/usr/bin/notifier)
Jun 11 06:30:00 turris crond[769]: (root) CMDOUT (There is no message to send.)
Jun 11 06:30:00 turris crond[769]: (root) CMDEND (/usr/bin/notifier)
Jun 11 08:30:05 turris dnsmasq-tftp[3482]: sent /srv/tftp/turris-netboot/mox to 192.168.1.156
Jun 11 06:30:06 turris odhcpd[1927]: Failed to send to ff02::1%guest_turris@br-guest-turris (Address not available)
Jun 11 08:30:21 turris dnsmasq-dhcp[3482]: DHCPDISCOVER(br-lan) d8:58:d7:00:cf:1a
Jun 11 08:30:21 turris dnsmasq-dhcp[3482]: DHCPOFFER(br-lan) 192.168.1.156 d8:58:d7:00:cf:1a
Jun 11 08:30:21 turris dnsmasq-dhcp[3482]: DHCPREQUEST(br-lan) 192.168.1.156 d8:58:d7:00:cf:1a
Jun 11 08:30:21 turris dnsmasq-dhcp[3482]: DHCPACK(br-lan) 192.168.1.156 d8:58:d7:00:cf:1a
Jun 11 08:30:21 turris dnsmasq-tftp[3482]: file /srv/tftp/C0A8019C.img not found
Jun 11 08:30:21 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/01-d8-58-d7-00-cf-1a not found
Jun 11 08:30:21 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0A8019C not found
Jun 11 08:30:21 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0A8019 not found
Jun 11 08:30:21 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0A801 not found
Jun 11 08:30:21 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0A80 not found
Jun 11 08:30:21 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0A8 not found
Jun 11 08:30:21 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0A not found
Jun 11 08:30:21 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C0 not found
Jun 11 08:30:21 turris dnsmasq-tftp[3482]: file /srv/tftp/pxelinux.cfg/C not found
Jun 11 08:30:21 turris dnsmasq-tftp[3482]: sent /srv/tftp/pxelinux.cfg/default-arm-mvebu-turris_mox to 192.168.1.156
Jun 11 06:30:21 turris dhcp_host_domain_ng.py: DHCP update hostname [MOX-DG,192.168.1.156]
Jun 11 06:30:21 turris dhcp_host_domain_ng.py: Refresh kresd leases
This however seems to fail which causes the to reboot with the same result.
I already ran the netboot-manager regen:
root@turris:~# netboot-manager regen
Regenerating configuration...
Signing kernels...
The problem however persists and the devices never show up in reforis or through netboot-manager list. Any advice on other troubleshooting steps to try?
Regards,
Michael