Hi PhilPennock, miska
I had the same problem - default-arm-mvebu-turris_mox
was empty and similar situation, custom configuration for TFTP and /srv is symlink to SSD.
I read this script https://gitlab.labs.nic.cz/turris/turris-netboot/blob/master/manage.sh (regen part).
I tried run netboot-manager regen
, but without success.
The script check key ~/.ssh/reg_key.pub
and if it does not exist, tries to create it. In my case, key wasn’t created (I don’t known why, but time is expensive for experiments). I created the key manually by ssh-keygen -t ed25519 -f ~/.ssh/reg_key -N "" -C "registration_key
. After, I tried to re-run netboot-manager regen
, but default-arm-mvebu-turris_mox
was stay empty. I removed it and re-runed netboot-manager regen
. Change! Script “said”: can’t create /srv/tftp/pxelinux.cfg/default-arm-mvebu-turris_mox: Permission denied.
Steps for help (for my case):
- check permission on
/srv/tftp/pxelinux.cfg/
- I set 777 - remove
default-arm-mvebu-turris_mox
- run
netboot-manager regen
- check size of
default-arm-mvebu-turris_mox
4.1 if is empty, try to generate registration key and go back to step 2
4.2 if is empty, I don’t known why - turn on your MOX and wait for some seconds
- run
netboot-manager list-incoming
5.1 if you see serial number, you’r win
5.2. runnetboot-manager accept <serial>
Question for miska:
- Before MOX I use TFTP for booting “rescue OS” with “incompatible” configuration
- What’s right access/owner for
/srv/tftp/pxelinux.cfg
and/srv/tftp/turris-netboot
?
My English is bad, I known