TOS 7.0.1201 (x86) Official Release Update

[apvm]

Just found out 1188 report status that no internet and cannot find update something like that in red, anyway this is for manual update so i updated it to 1201 and now status say current system is the latest version, I'll see if my system will go back to sleep.

[DmMc]

after just a few minutes CPU temp warning triggered 83c, forced fan to high, after a few minutes temp dropped 40c. The issue was going to capture didn't happen. Rebooted unit again, still with debug mode on, same high temp after a few. This time left fan in auto mode, point being forcing high speed didn't help dropping temp, whatever the system was doing, it finished then temp dropped.

I am experiencing the exact same issue: once an hour, the temperature spikes to 94–95°C, triggering a system alert. This has never happened before.
Log analysis revealed that the CPU is being heavily loaded by Plex (running in Docker)—even though it was idle, with no active streams or transcoding sessions taking place.

Furthermore, there is another Docker-related issue: following the update, 3 out of my 30 containers (`metube`, `paperless-ngx`, and `stirling-pdf`) failed to start, falling into a crash/restart loop with similar errors in their logs:

Code: Select all

[FATAL tini (7)] exec ./docker-entrypoint.sh failed: Operation not permitted
[FATAL tini (7)] exec /scripts/init.sh failed: Operation not permitted

[Errno 1] Operation not permitted
s6-rc: warning: unable to start service init-migrations: command exited 1

After consulting an AI assistant, I managed to isolate the root cause. For every affected container, I had to manually add the following directive to the Compose stack:

Code: Select all

yaml
security_opt:
  - seccomp:unconfined

Once applied, the containers booted up and functioned normally.
The AI attributes this failure to a kernel-level architectural conflict associated with the `faccessat2` and `clone3` syscalls. Paperless-ngx uses the `s6-overlay` process supervisor, while metube and stirling-pdf rely on `tini`, and all three are built on modern base images (recent Alpine/Debian releases).

[Crashoveride]

Have you previously had an NVME configured as Hyper-Cache?

No, I've never used that. All drives were secure erased before installation. The system was installed cleanly, and I tried swapping drives and installing the system, as well as installing NVMe drives after the system was installed—the result was the same.

[CursaYang]

Generally speaking, the page should display disk1 and disk2, whereas sdzc is an internal system name. This may be a front-end output issue. We need to analyze it in combination with the system report. Please collect a system report and send it to our technical support email [support(at)terra-master.com]; we will analyze it.

[CursaYang]

This issue is still in development and has not been addressed in this version. Please wait for a future release. Thank you for your understanding and support.

[DmMc]

I am experiencing the exact same issue: once an hour, the temperature spikes to 94–95°C, triggering a system alert. This has never happened before.
Log analysis revealed that the CPU is being heavily loaded by Plex (running in Docker)—even though it was idle, with no active streams or transcoding sessions taking place.

The CPU overheating issue caused by Plex was also resolved after adding the following instruction to its stack:

Code: Select all

security_opt:
  - seccomp:unconfined
 

Apparently, these are parts of the same chain. The Plex engine encounters the same security restriction (seccomp) in the new TOS build as Paperless does.

UPD: Additionally, it was necessary to implement the same changes to the Flaresolver container, indicating a significant issue for Docker.

[sianderson]

both units updated, no issues noticed

[Alak]

Coucou,

Un tout petit truc à signaler de mon coté, tout de même, mais c'est peut-être normal : lorsque l'on clique sur "notes de version" suite à la mise à jour et que l'on est redirigé sur la page "https://support.terra-master.com/posts/ ... ease_Notes", les notes de cette version, mentionnées sur cette page, n'apparaissent pas. les dernières qui apparaissent sont celles de la version TOS 7.0.1188 .

Mais tout ça est peut-être normal lorsque l'on installe la version manuellement avant la distribution automatique généralisée.

[Asdrubal]

Hi.

Même constat en actualisant la mise à jour officielle ...
La version finit par se mettre à jour après un certain temps ?

F4 424 Pro

[Nitrokalel]

debo de decir que mis dispositivos todos se actualizaron bien
pero ahora noto un aumento en las alertas de temperatura como obseban en la imagen



en varios de mis dispositivos ahora me saltan esas alertas sin embargo al revisar la temperatura esta normal, o por lo menos las condiciones de uso
son las normales, no esta en un lugar sin ventilacion o encerrado, siempre ha opoerado asi mi equipo pero justo esta actualizacion hay un tema con el manejao de la temperatura o algo esta haciendo que aumente esta temperatura