TOS 7.0.1225 (x86) Official Release Update

[Nitrokalel]

todos mis dispositivos se actualizaron bien exepto F2-221 (6TB+10TB, TRaid, 10GB, prod) update fail
se queda trabado al iniciar


que puedo hacer??
eso fue justo despues de cargar el paquete de actualizacion de manera manual y cuando termina de cargar el paquete y preparar la actualizacion se reinicio pero ya no regreso
se murio el nas F2-221???

F8 SSD Plus (8x4TB NVMe, TRaid, 48GB, prod) update ok
F8 SSD Plus (6x1TB+2x2TB, TRaid, 48GB, prod) update ok
F4-424 Pro (2x22TB+2x10TB HDD +1TB+500GB NVMe, TRaid, 32GB, prod) update ok
F2-423 (2x18TB, TRaid, 32GB, prod) update ok
F2-221 (6TB+10TB, TRaid, 10GB, prod) update fail
D1 SSD (2TB, prod) is recognized

[OttO1916]

Both F2-221 and F5-221 updated without any issues.
Thanks!

[DmMc]

The update installed normally.
The issue related to **"security_opt: - seccomp:unconfined"** is fully resolved; all Docker containers now start correctly without this instruction.
However, last night the temperature alert triggered again for no apparent reason at 87°C, even though the logs and detailed temperature monitoring showed absolutely nothing — possibly just a one‑second spike.
Please take a look! These notifications are annoying, and I had to disable the buzzer.

[ambul]

The update installed ok

[EriChan]

Based on your description and screenshot, it appears to have encountered an issue during the system boot/startup phase following the update.

To help diagnose and recover your device as quickly as possible, please contact our online technical support team via the link below for assistance:
https://salesiq.zohopublic.com/signatur ... 97d0be8892


Por los síntomas descritos y la captura de pantalla, parece tratarse de un problema durante la fase de arranque (boot) tras la actualización.

Para ayudarte a diagnosticar y recuperar el equipo lo antes posible, por favor contacta con nuestro equipo de soporte técnico en línea a través del siguiente enlace para que puedan asistirte en la solución del problema:
https://salesiq.zohopublic.com/signatur ... 97d0be8892

[EriChan]

Regarding the abnormal CPU temperature spikes and buzzer alarms you described: we have received similar feedback, and our engineering team has successfully reproduced the issue internally and is actively investigating.

Currently, we have confirmed that this behavior is isolated specifically to the F4-424 Pro and F4-425 Pro models; other models have not exhibited this issue. This has been flagged as a high-priority bug, and our team is working expeditiously to identify the root cause and deliver a solution as soon as possible. In the meantime, we kindly ask for your patience while we work on the fix.

We sincerely apologize for the inconvenience this has caused, and we truly appreciate your understanding and patience.

[sianderson]

upgraded both units remotely, all seems to be well, no issues while updating

[mnewland]

T6-423 updated no issues everything is working well.

[kmatas]

Regarding the abnormal CPU temperature spikes and buzzer alarms you described: we have received similar feedback, and our engineering team has successfully reproduced the issue internally and is actively investigating.

Currently, we have confirmed that this behavior is isolated specifically to the F4-424 Pro and F4-425 Pro models; other models have not exhibited this issue. This has been flagged as a high-priority bug, and our team is working expeditiously to identify the root cause and deliver a solution as soon as possible. In the meantime, we kindly ask for your patience while we work on the fix.

We sincerely apologize for the inconvenience this has caused, and we truly appreciate your understanding and patience.

I have experienced a similar issue with F4-425 Plus model this morning when it started beeping around 2:10AM due to high CPU temp.
Upon checking the CPU was at 87C and remained as such until I shut down the unit so was not just a short spike.
I shut it off via the mobile app as it was too early in the morning to focus on this problem and didn't want to wake up anyone.
I left the unit off until I woke up and upon turning it on nothing in the logs that would indicate this CPU behavior.
Since its been turned back on in the last 7 or so hours no CPU warning issues.
Updated to 7.0.1225 a day before, have not had any issues with previous TOS versions.

[Metrogeek]

Same issue on my side on my F4-425 Plus. Update to 7.0.1225 and few hours later got cpu temp alarm. Was on 7.0.1188 before without any problems.

When alarm triggered, My cpu was at 28% and temp between 87 and 92. Plex was running an audio loudness optimization task. So i temporarly disable the task in plex settings. I reboot the nas and the issue still present