Page 2 of 7
Re: TOS 7.0.0777 Official Release (X86) is Now Available
Posted: 07 Jul 2026, 22:52
by petrose
Got the Update, however, going to Install VirtualBox tools, the required dependency to PHP7.4 is failing install.
No detailed messages given, but the prompt after around 20% download: PHP7.4 Install failed
PHP8.0 Install works, but its not integrated into the VirtualBox, yet.
Any good reasons/answers around ?
Re: TOS 7.0.0777 Official Release (X86) is Now Available
Posted: 07 Jul 2026, 23:56
by crisisacting
Installed fine onto test bed units; will continue to assess for issues.
Finalizing deployment plan to client units.
Re: TOS 7.0.0777 Official Release (X86) is Now Available
Posted: 08 Jul 2026, 03:52
by Pe6yc
petrose wrote: ↑07 Jul 2026, 22:52Any good reasons/answers around ?
A few days earlier TM team posted direct link to download PHP7.4 deb module but for now the link is dead. I have the deb one but I'm not sure I may share it.
viewtopic.php?p=57676#p57676
Re: TOS 7.0.0777 Official Release (X86) is Now Available
Posted: 08 Jul 2026, 04:19
by jayjay
I'm still seeing problems with HDD drives not going into sleep mode, does anyone else have the same problem?
Re: TOS 7.0.0777 Official Release (X86) is Now Available
Posted: 08 Jul 2026, 08:16
by nitzer71
Plex/Jellyfin real-time library updates stopped working after upgrading from TOS 6 to TOS 7
I purchased my F4-425 Plus with TOS 6, and Plex and Jellyfin real-time library monitoring worked correctly. After upgrading to TOS 7, both Plex and Jellyfin stopped automatically detecting new media files.
My setup:
- TerraMaster F4-425 Plus
- TOS 7.0.0777
- BIOS MTWL0101.V07
- Media stored on Volume1 (TRAID)
- Plex and Jellyfin installed from the TerraMaster App Center
Manual scans and scheduled scans work normally, but real-time library updates no longer trigger when new files are added.
Has anyone else experienced this after moving from TOS 6 to TOS 7?
Edit: I later found an earlier forum thread describing what appears to be the same issue:
viewtopic.php?p=58108#p58108
Re: TOS 7.0.0777 Official Release (X86) is Now Available
Posted: 08 Jul 2026, 08:21
by CursaYang
jayjay wrote: ↑08 Jul 2026, 04:19
I'm still seeing problems with HDD drives not going into sleep mode, does anyone else have the same problem?
In this version, we fixed the system disk hibernation function. Is the hard drive you mentioned that cannot hibernate the system disk?
Re: TOS 7.0.0777 Official Release (X86) is Now Available
Posted: 08 Jul 2026, 08:23
by CursaYang
rfbjr wrote: ↑07 Jul 2026, 19:46
The issue of not recognizing daylight saving time in the logs has not been fixed in this version, but we plan to fix it in a future version.
Re: TOS 7.0.0777 Official Release (X86) is Now Available
Posted: 08 Jul 2026, 08:34
by rfbjr
CursaYang wrote: ↑08 Jul 2026, 08:23
rfbjr wrote: ↑07 Jul 2026, 19:46
The issue of not recognizing daylight saving time in the logs has not been fixed in this version, but we plan to fix it in a future version.
Thank you
Re: TOS 7.0.0777 Official Release (X86) is Now Available
Posted: 08 Jul 2026, 14:54
by JettNing
Hello, based on the issue you encountered, you may try the troubleshooting steps below:
1. Enter `apt update` in the TOS terminal tool to refresh APT repository metadata.
2. If the command completes without errors, reinstall PHP7.4 via App Center and retry VirtualBox Guest Additions installation.
3. Should PHP7.4 installation still return failure notifications after refreshing the APT repository, kindly get in touch with our technical support team. We will arrange remote debugging promptly to identify and resolve the underlying issue.
Thank you for your feedback.
Re: TOS 7.0.0777 Official Release (X86) is Now Available
Posted: 08 Jul 2026, 14:55
by Andy2026
DCCentR wrote: ↑07 Jul 2026, 21:26
However, it seems that after one of the updates, there are issues with launching Docker containers (via autorun at system startup).
It feels like they start earlier than they should, when the system or some of its components aren’t quite ready yet.
The problem occurs in the following containers, for example:
-
Homepage: The remaining space on mounted disks is displayed incorrectly (for example, a few gigabytes instead of 2 terabytes)
-
Jellyfin: A problem with file playback; most, if not all, files stop playing (the logs show the error “FFmpeg exited with code 254”).
- There may be other problematic containers as well...
All of this is resolved by restarting the containers shortly after TOS starts up.
I don’t have many details yet; I need to dig into it more in my free time.
Has anyone else encountered a similar problem?
Yes. There is a problem. Wordpress in docker. After turning on the NAS, you need to restart the container every time. Problems wordpress accessing the network. After rebooting the container it works