TerraMaster Forum

Target Users:
Users currently running TOS 7.0.0746 or later versions.

Note:
If your TOS version is TOS 6, please refer to the TOS 7 update instructions first.
Important: This update is only applicable to TOS 7.0.0746 and newer. Users with older versions must first upgrade to 7.0.0746 before applying this update.

Here, we sincerely thank @crisisacting, @thierrys73, @dgmigdot, @Gremlin, @rfbjr, @TMchris, @Pe6yc, @snapsh0t, @greentower, @Nitrokalel, @jpeckinp, @Zymphad, @Metrogeek, @benno, @sianderson, @SmartFox75, @joka388, @dcx41, @gustang, @digi999, @joergurmel, @hellotonothing, @AlexNo, @ambul, @OlRedRooster, @OttO1916, @apvm, @nikk, @davep1628 for your sharing and feedback. Your support helped us quickly identify and fix multiple issues.

Update Notes
Bug Fixes:
1. Fixed an issue where LDAP domain users could not log in via browser in certain scenarios.
2. Fixed an issue where some applications failed to retain their pre-restart state after a reboot.
3. Fixed an issue where a "Failed to receive data" prompt might be triggered when entering the desktop after an update.
4. Fixed an issue where the system drive could not enter sleep mode.
5. Fixed an issue where the identifier of an encrypted USB device changed after a reboot.
6. Fixed an issue where the upload speed displayed during remote access did not match the actual speed.
7. Fixed an issue where the prompt was inaccurate when mounting an unauthorized SMB file server directory.
8. Fixed an issue where the buzzer did not automatically turn off when the array was in an automatic repair state after a reboot.
9. Fixed other known issues.

Important Information:
1.Updating the system theoretically will not affect the data on your hard drives, but for safety, please make sure to back up your data in advance.
2.Before updating, ensure that your primary volume (usually volume1) has at least 3GB of available space. Insufficient storage space may cause the update to fail.
3.After the update, the IP address of your TNAS may change. Please use the TNAS PC desktop client to search for and reconnect to the device.

Update Procedure:
1.Go to TOS > Control Panel > General Settings > System > Update, and click "Check for updates."
2.Follow the prompts to update the system.
3.After the system update is complete, you may need to refresh your browser.
4.The TNAS IP address may change after the update. If you cannot connect to your TNAS using the previous IP address, use the TNAS PC client to search for the new IP address.

Client Downloads:
1. Download TNAS PC 5.2.540 for Windows OS.
- MD5: AFB7CD77DE2A4F0434D69D52D15959AF
2. Download TNAS PC 5.2.540 for macOS (x86 architecture).
- MD5: 715FEB00FDB06DF4CC9A228622566F70
3. Download TNAS PC 5.2.540 for macOS (ARM architecture).
- MD5: A6954F192DD23AF7374CF2AF20190B6C
4. Download TNAS PC 5.2.540 for Linux.
- MD5: A5B13A2C2C9B0F9FFFCBDF6F3BA9E342
5. Download TNAS mobile 3.5.077 for Android. (You can also search for "TNAS mobile" in the app store to install.)
6. TNAS Mobile for iOS: Please search for "TNAS mobile" in the App Store to install.

not installed F6-424 max

Andy2026 wrote: ↑07 Jul 2026, 12:57

You can return to this page to refresh the updates.

Updated ok.

For about 20 minutes download failed but later update was successful

F4-424 Pro(BIOS MADN0101.V05): update ok
F4-425 Plus(BIOS MTWL0101.V05): update ok
F5-422(BIOS MAPL0304V22): update ok
F4-423(BIOS 5.19): update ok

Updated 3 Tos7 models. Quick and smooth

Updated F5-221 to Tos7 (finally!) and then to current .0777 release. No obvious issues.

All three devices updated w/o any issues.

Clearly TOS 7 still doesn't not like Daylight Saving Time.

Looked at the CloudSync log and it showed a copy at 12:35AM, which isn't possible since the unit is off




Then I exported the cloudsync log: (Correct time is shown)
Info 7/7/2026 1:35 Copy-Robert-Downloads-V2 Molly Downloaded!(/Volume1/Robert/Cloud-Downloads/mvs-tk5.zip)

Then there is this from the dashboard. The time shown when you hover over something on the bottom is an hour off from the top clock.


I know some of this was reported before, but every time the summary of new releases mentions "Fixed other known issues" I have to check again.

The update was successful.

***

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?