Suspicious error messages when restoring backup on RUT241

Networking Solutions
1

On a RUT241 with firmware version RUT2M_R_00.07.18.3 I get the following suspicious error messages when restoring a backup from the command line:

root@RUT241:/tmp# sysupgrade -r /tmp/backup.tar.gz
Thu Dec 11 15:21:14 UTC 2025 upgrade: Restoring config files...
Warning: Path does not exist: /etc/certificates/tpm2
Warning: Path does not exist: /etc/package_restore.txt

The error messages do not appear with firmware version RUT2M_R_00.07.17.5.

2

Hello, DonDiego,

Question - was the backup originally made on the 7.17.5 firmware version and is now being uploaded onto a device with the 7.18.3 firmware?

Additionally, these error messages can be safely ignored.

Regards,
M.

4

It is not possible to create backups with the firmware version you mention, see:

5

Hi,

Can you please try sysupgrade -b /tmp/backup-name.tar.gz instead of the command you were using?

Regards,
M.

6 
BusyBox v1.34.1 (2025-10-28 06:59:39 UTC) built-in shell (ash)

     ____        _    ___  ____
    |  _ \ _   _| |_ / _ \/ ___|
    | |_) | | | | __| | | \___ \
    |  _ <| |_| | |_| |_| |___) |
    |_| \_\\__,_|\__|\___/|____/
-------------------------------------
     Teltonika RUT2M series 2025
-------------------------------------
   Device:     RUT241
   Kernel:     5.15.186
   Firmware:   RUT2M_R_00.07.18.3
   Build:      ec1ef51550e
   Build date: 2025-10-28 07:44:31
-------------------------------------
root@RUT241:~# sysupgrade -b /tmp/backup-name.tar.gz
Fri Dec 12 12:14:37 UTC 2025 upgrade: Saving config files...

root@RUT241:~# sysupgrade -r /tmp/backup-name.tar.gz
Fri Dec 12 12:15:13 UTC 2025 upgrade: Restoring config files...
Warning: Path does not exist: /etc/certificates/tpm2
Warning: Path does not exist: /etc/package_restore.txt

This is directly after a factory reset.

7

Looks like generating the file worked fine, did it also apply the configuration from the backup?

Regards,
M.

8

Yes. After a factory reset:

BusyBox v1.34.1 (2025-10-28 06:59:39 UTC) built-in shell (ash)

     ____        _    ___  ____
    |  _ \ _   _| |_ / _ \/ ___|
    | |_) | | | | __| | | \___ \
    |  _ <| |_| | |_| |_| |___) |
    |_| \_\\__,_|\__|\___/|____/
-------------------------------------
     Teltonika RUT2M series 2025
-------------------------------------
   Device:     RUT241
   Kernel:     5.15.186
   Firmware:   RUT2M_R_00.07.18.3
   Build:      ec1ef51550e
   Build date: 2025-10-28 07:44:31
-------------------------------------
root@RUT241:~# sysupgrade -b /tmp/backup-name.tar.gz
Fri Dec 12 12:47:48 UTC 2025 upgrade: Saving config files...

root@RUT241:~# sed -i -e s/RUT241/NUT241/g /etc/config/system
root@RUT241:~# grep 241 /etc/config/system
	option device_code 'NUT24101XXXX'
	option devicename 'NUT241'
	option hostname 'NUT241'
root@RUT241:~# sysupgrade -r /tmp/backup-name.tar.gz
Fri Dec 12 12:48:39 UTC 2025 upgrade: Restoring config files...
Warning: Path does not exist: /etc/certificates/tpm2
Warning: Path does not exist: /etc/package_restore.txt

root@RUT241:~# grep 241 /etc/config/system
	option device_code 'RUT24101XXXX'
	option devicename 'RUT241'
	option hostname 'RUT241'
root@RUT241:~#
9

Hi,

I’m a bit confused as to why you keep sending the logs. Is there still some kind of issue? As mentioned, the “warning” messages you’re getting can be safely ignored. If the backup is successfully applied after inputting the command, then I believe it is solved?

Regards,
M.

10

I’m suspicious of everything you do to be honest. These error messages should not appear instead of just being “safely ignored”.

If you think I’m overly paranoid - you folks just broke backups over sysupgrade with relative paths:

11

I believe that this error in specific is due to the fact that the device doesn’t have tpm2 support, so this definitely can be ignored.

This file is used by some OpenWrt scripts or by other Teltonika devices/models to track previously installed packages.
If the file doesn’t exist on the target system, the restore script warns you - nothing more.

As for the firmware different results, I believe since the newer firmware has it, and the older one doesn’t, this is just an update they’ve made to let the user know.

Regarding the pathing of the file, I don’t see an issue either, although it is slightly weird that cd’ing into /tmp/ and trying to run the command doesn’t work

12

This topic was automatically closed after 60 days. New replies are no longer allowed.