I have a RUT240 currently running RUT2_R_00.07.01.6.
The device is experiencing persistent JFFS2 errors and I/O errors, including:
Header CRC failed
Node CRC ffffffff
read_cache_page() returned error: -5
Error garbage collecting node
I/O error when reading files under /etc/
I tried upgrading to the official RUT240 firmware RUT2_R_00.07.06.21, but the upgrade did not complete. After reboot, the device is still on 00.07.01.6.
The firmware file has been verified with MD5 and can be read normally, but sysupgrade -T returns an I/O error.
Could you please advise what I should perform next?
Thanks. I haven’t tried the bootloader recovery yet because I’m not physically at the router’s location.
Is there any way to perform the bootloader firmware recovery remotely, for example through RMS, SSH/CLI, or another remote method? Or does entering the bootloader menu always require physical access to the reset button and power cycle?
If physical access is required, is there any alternative remote recovery procedure you would recommend for this situation?
Already tried by always failed have error like this:
root@Teltonika-RUT240:~# sysupgrade -F /tmp/RUT2_R_00.07.06.21_WEBUI.bin
Tue Sep 1 07:04:23 UTC 2026 upgrade: RUT2_R_00.07.06.21
sh: out of range
OK
OK
sh: : unknown operand
sh: : unknown operand
sh: : unknown operand
sh: out of range
sh: out of range
sh: out of range
sha256sum: can't read '/etc/strongswan.conf': I/O error
sha256sum: can't read '/etc/ipsec.conf': I/O error
sha256sum: can't read '/etc/ipsec.secrets': I/O error
Tue Sep 1 07:04:39 UTC 2026 upgrade: Saving config files...
Failed to create the configuration backup.
Could you please try updating the firmware through the WebUI? Instead of updating directly to the latest version, we recommend doing the upgrade in two steps.
As a first step, please update the device to 00.07.04.5. This may help by reducing the firmware version gap and allowing for a smoother upgrade process.
Please also note that the issue according to your error messages you been provided could potentially indicate a problem with the device’s storage memory.
Once you have tried the update, please let us know if the issue persists so we can investigate further.