As soon as I upgrade the firmware, I can ssh to the devices.
Does anyone know how and why the RUT955 get this state?
Can I fix this state by some way, without updating firmware?
Please note that I have a script which try to update the firmware if needed. When the RUT955 is in this state, it doesn’t work (because no ssh connection) but maybe the devices get this state because a previous firmware update failed?
If you get to this page each and every single time you reboot the router, it looks like your device is stuck in the Bootloader state. More information can be found here: Bootloader menu - Teltonika Networks Wiki
If what I said applies to you, then we consider this to be a hardware-related issue that can only be resolved by either replacing or repairing the device; This process is usually done either by us, or by the reseller/distributor that you’ve purchased the device from, though your device looks to be old, so warranty is most likely due.
Thanks for the reply. I understand the device can be stuck in Bootloader state, but it does not seem to be a hardware issue, because uploading and installing the new firmware fix the issue.
Could it be caused by an error (a reboot or something like this) when calling “sysupgrade [FIRMWARE_BIN_FILE]“?
In the case that it works fine, it seems like your device then accidentally got into a bootloader state somehow, although getting into it usually requires very specific steps to be made.
As for how you would usually resolve this, is you would either:
Continue with the process (so upgrade the firmware, though this will reset the device)
Unplug the power from the device, and plug it back in; This should cancel the bootloader state.
Please also ensure that your physical reset button on your device isn’t broken or clicked in, as unplugging the cable, plugging it back in could cause the device to go into the bootloader state again if the reset button is pressed-in
Yes 1. (upgrade the firmware) fix it but 2. (unplug/replug power) no.
Anyway, this requires a human action to be fixed.
Now the question is more, how can I prevent it. Could it be caused by a reboot when trying an automatic firmware update using the ‘sysupgrade‘ command?