TOS 7.0.1225 (ARM) Official Release Update

[RyanYang]

Target Users:
Users currently running TOS 7.0.1113 (ARM) or later versions.

Applicable Models:
F2-211, F2-212, F4-212

Note:
If your TOS version is TOS 5.1 or TOS 6 Beta, please refer to the TOS 7 ARM official release announcement.
If you are on a different TOS 7 Beta version, please refer to the TOS 7 update guide first.

Here, we sincerely thank @Flatron, @byo12us2z, @hk87, @crisisacting, @funnyplace, @Lukin, @pennypacker, @Gremlin, @FredMutter, @Flyingbike, @Arktander, @tetrapack15, @Jragg and others for your sharing and feedback. Your support helped us quickly identify and fix multiple issues.

Release Notes:
This update adopts a phased gray release strategy to ensure stability across different device models and network environments.
Phase 1 (Starting Today): The manual update package is now available for download on our forum. It will be rolled out in batches based on system version, device model, and region.
Phase 2 (In One Week): The full online push will officially begin. At that time, all users will receive an update notification and can complete the update by following the on-screen prompts.

Update Notes
Bug Fixes:
1. Fixed the issue where local SMTP email notifications failed to send in some scenarios.
2. Fixed the issue where SMB advanced settings could not be properly configured in some scenarios.
3. Fixed the issue where the page might incorrectly prompt a failure when migrating shared folders.
4. Fixed the issue where the database usage of file task records for copy and move operations was not detected in a timely manner.
5. Fixed the issue where some applications could not scan USB device data.
6. Fixed the issue where NFS mounting failed when the remote directory contained spaces.
7. Fixed the issue where the SMB mount prohibition rule became invalid after enabling the Guest user.
8. Fixed the issue where downloading large files during remote access might stop after a period of time.
9. Fixed the issue where regular users failed to save files to their user directory via the text editor in File Manager.
10. Fixed various 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:
Manual Update:
1.Download TOS 7.0.1225 update package (MD5: 764dedd52be3789a3f2cd6f86817d706);
2.Go to TOS > Control Panel > General Settings > System;
3.Under "Manual Update", upload the update package;
4.Click "Apply";
5.After the system update is complete, please refresh your browser;
6.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.548 for Windows OS.
- MD5: 72701B52336AF9FD8B97A6BE9D5D5A7C
2. Download TNAS PC 5.2.548 for macOS (x86 architecture).
- MD5: BAA63A179C43F73965EA9C31EEB9D61E
3. Download TNAS PC 5.2.548 for macOS (ARM architecture).
- MD5: BB933DA867058884C4ADFE44EAD24AFC
4. Download TNAS PC 5.2.548 for Linux.
- MD5: 06FE93F9FFE47147854A34F28D57FCC2
5. TNAS mobile for Android: Please 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.

[hk87]

I have the exact same problem as before, the version stays at 7.0.1078. So the existing issue has not been solved with this version either.

The update to 7.0.1079 fails with an error message (update guide):
[26-09-28 09:52:03] === Update started ===
[26-09-28 09:52:03] Log file: /home/henry/update_before_reboot_2026-09-28-09-52-03.log
[26-09-28 09:52:03] Update package: /Volume1/.update_6cf63d40d9af5463182da96e489889c1/TOS_ARM2.0_Update_7.0.1079_1579_2607211136.bz2
[26-09-28 09:52:03] Decompress dir: /update
[26-09-28 09:52:03] Package dir: /Volume1/.update_6cf63d40d9af5463182da96e489889c1
[26-09-28 09:52:03] System version: 7.0.1078
[26-09-28 09:52:03] Boot version: 419
[26-09-28 09:52:04] isRunning set to true, timeout set to 20 minutes from now
[26-09-28 09:52:04] Writing initial progress: 10/100
[26-09-28 09:52:04] Starting decompression of /Volume1/.update_6cf63d40d9af5463182da96e489889c1/TOS_ARM2.0_Update_7.0.1079_1579_2607211136.bz2 to /update
[26-09-28 09:53:47] Decompression completed successfully
[26-09-28 09:53:47] Starting package verification, rootPath=/update, infoPath=/update/INFO
[26-09-28 09:53:47] Package verification FAILED: cannot open INFO (/update/INFO): open /update/INFO: no such file or directory
[26-09-28 09:53:47] Update aborted due to verification failure
[26-09-28 09:53:47] Cleanup: removed package dir /Volume1/.update_6cf63d40d9af5463182da96e489889c1
[26-09-28 09:53:47] isRunning set to false

Version 7.0.1225

[26-09-28 09:14:42] === Update started ===
[26-09-28 09:14:42] Log file: /home/henry/update_before_reboot_2026-09-28-09-14-42.log
[26-09-28 09:14:42] Update package: /Volume1/.update_6cf63d40d9af5463182da96e489889c1/TOS_ARM2.0_Update_7.0.1225_1725_2609091910.bz2
[26-09-28 09:14:42] Decompress dir: /update
[26-09-28 09:14:42] Package dir: /Volume1/.update_6cf63d40d9af5463182da96e489889c1
[26-09-28 09:14:42] System version: 7.0.1078
[26-09-28 09:14:42] Boot version: 419
[26-09-28 09:14:42] isRunning set to true, timeout set to 20 minutes from now
[26-09-28 09:14:42] Writing initial progress: 10/100
[26-09-28 09:14:42] Starting decompression of /Volume1/.update_6cf63d40d9af5463182da96e489889c1/TOS_ARM2.0_Update_7.0.1225_1725_2609091910.bz2 to /update
[26-09-28 09:15:35] Decompression completed successfully
[26-09-28 09:15:35] Starting package verification, rootPath=/update, infoPath=/update/INFO
[26-09-28 09:15:51] Package verification passed
[26-09-28 09:15:51] Starting version comparison check...
[26-09-28 09:15:51] compareVersion: starting, root=/update
[26-09-28 09:15:51] checkKernelVersion: checking for root=/update
[26-09-28 09:15:51] checkKernelVersion: current kernel version: 5.10.107
[26-09-28 09:15:51] checkKernelVersion: no .kernel file found, skipping kernel version check
[26-09-28 09:15:51] checkVersionCompatibility: checking system version compatibility
[26-09-28 09:15:51] checkVersionCompatibility: current system version: TOS_ARM2.0_7.0.1078
[26-09-28 09:15:51] checkVersionCompatibility: update package version: TOS_ARM2.0_7.0.1225
[26-09-28 09:15:51] checkVersionCompatibility: firmware ID matched: ARM2.0
[26-09-28 09:15:51] checkMinVersion: checking minimum version, currentVersion=7.0.1078
[26-09-28 09:15:51] checkMinVersion: minimum required version: 6.0.794
[26-09-28 09:15:51] checkMinVersion: current version 7.0.1078 meets minimum requirement 6.0.794
[26-09-28 09:15:51] checkPackageVersion: comparing system=7.0.1078 with package=7.0.1225
[26-09-28 09:15:51] checkPackageVersion: version check passed, system <= package
[26-09-28 09:15:51] checkVersionCompatibility: all compatibility checks passed
[26-09-28 09:15:51] compareVersion: all checks passed
[26-09-28 09:15:51] Version check passed
[26-09-28 09:15:51] Starting kernel update (tos7 -> tos7)...
[26-09-28 09:15:51] updateKernel: detected architecture: arm64
[26-09-28 09:15:51] updateKernel: updating kernel for ARM architecture
[26-09-28 09:15:51] updateKernelARM: starting ARM kernel update
[26-09-28 09:15:51] updateKernelARM: mtdKernel=/dev/mtd2, mtdRootfs=/dev/mtd3, bootDir=/update/boot/new
[26-09-28 09:15:51] updateKernelARM: boot/new directory not found at /update/boot/new, skipping
[26-09-28 09:15:51] Kernel update completed successfully
[26-09-28 09:15:51] All pre-reboot update steps completed, progress=100%, preparing for reboot
[26-09-28 09:15:51] Package dir removed, syncing filesystem and rebooting in 2 seconds...
[26-09-28 09:15:51] Cleanup: removed package dir /Volume1/.update_6cf63d40d9af5463182da96e489889c1
[26-09-28 09:15:51] isRunning set to false

[EriChan]

Since your current version is TOS7.0.1078, updating directly from an older version to the latest version may cause update failures or feature incompatibilities. To minimize risks and ensure system stability, an intermediate update to TOS7.0.1133 is required first.

Please follow these steps to update:

• Refer to this thread to download the package and manually update to TOS7.0.1133 first: viewtopic.php?t=10417

• Once your device is running TOS7.0.1133, proceed with updating to the latest TOS7.0.1225.

Thank you for your understanding and support!

[hk87]

During the update, I already reported the errors causing it to abort. All reports have been submitted. Following my inquiry, I was directed to this version, which also fails and aborts.
So there has been no fix for weeks to install the official version or perform an upgrade.

Version 7.0.1113 -> failed

[26-09-10 11:24:21] === Update started ===
[26-09-10 11:24:21] Log file: /home/henry/update_before_reboot_2026-09-10-11-24-21.log
[26-09-10 11:24:21] Update package: /Volume1/.update_6cf63d40d9af5463182da96e489889c1/TOS_ARM2.0_Update_7.0.1113_1613_2607291219 .bz2
[26-09-10 11:24:21] Decompress dir: /update
[26-09-10 11:24:21] Package dir: /Volume1/.update_6cf63d40d9af5463182da96e489889c1
[26-09-10 11:24:21] System version: 7.0.1078
[26-09-10 11:24:21] Boot version: 419
[26-09-10 11:24:21] isRunning set to true, timeout set to 20 minutes from now
[26-09-10 11:24:21] Writing initial progress: 10/100
[26-09-10 11:24:21] Starting decompression of /Volume1/.update_6cf63d40d9af5463182da96e489889c1/TOS_ARM2.0_Update_7.0.1113_1613_2607291219 .bz2 to /update
[26-09-10 11:25:13] Decompression completed successfully
[26-09-10 11:25:13] Starting package verification, rootPath=/update, infoPath=/update/INFO
[26-09-10 11:25:30] Package verification passed
[26-09-10 11:25:30] Starting version comparison check...
[26-09-10 11:25:30] compareVersion: starting, root=/update
[26-09-10 11:25:30] checkKernelVersion: checking for root=/update
[26-09-10 11:25:30] checkKernelVersion: current kernel version: 5.10.107
[26-09-10 11:25:30] checkKernelVersion: no .kernel file found, skipping kernel version check
[26-09-10 11:25:30] checkVersionCompatibility: checking system version compatibility
[26-09-10 11:25:30] checkVersionCompatibility: current system version: TOS_ARM2.0_7.0.1078
[26-09-10 11:25:30] checkVersionCompatibility: update package version: TOS_ARM2.0_7.0.1113
[26-09-10 11:25:30] checkVersionCompatibility: firmware ID matched: ARM2.0
[26-09-10 11:25:30] checkMinVersion: checking minimum version, currentVersion=7.0.1078
[26-09-10 11:25:30] checkMinVersion: minimum required version: 6.0.794
[26-09-10 11:25:30] checkMinVersion: current version 7.0.1078 meets minimum requirement 6.0.794
[26-09-10 11:25:30] checkPackageVersion: comparing system=7.0.1078 with package=7.0.1113
[26-09-10 11:25:30] checkPackageVersion: version check passed, system <= package
[26-09-10 11:25:30] checkVersionCompatibility: all compatibility checks passed
[26-09-10 11:25:30] compareVersion: all checks passed
[26-09-10 11:25:30] Version check passed
[26-09-10 11:25:30] Starting kernel update (tos7 -> tos7)...
[26-09-10 11:25:30] updateKernel: detected architecture: arm64
[26-09-10 11:25:30] updateKernel: updating kernel for ARM architecture
[26-09-10 11:25:30] updateKernelARM: starting ARM kernel update
[26-09-10 11:25:30] updateKernelARM: mtdKernel=/dev/mtd2, mtdRootfs=/dev/mtd3, bootDir=/update/boot/new
[26-09-10 11:25:30] updateKernelARM: boot/new directory not found at /update/boot/new, skipping
[26-09-10 11:25:30] Kernel update completed successfully
[26-09-10 11:25:30] All pre-reboot update steps completed, progress=100%, preparing for reboot
[26-09-10 11:25:30] Package dir removed, syncing filesystem and rebooting in 2 seconds...
[26-09-10 11:25:30] Cleanup: removed package dir /Volume1/.update_6cf63d40d9af5463182da96e489889c1
[26-09-10 11:25:30] isRunning set to false

[TMzethar]

Based on the information currently available, we are unable to pinpoint the cause of the issue at this time.
Please check to see if there is sufficient space on the volume and in the root directory. The timestamps in the logs do not match the current date; you may want to try adjusting the system time and then retry.
If the above steps do not resolve the issue, please go to the online chat window to schedule a remote troubleshooting session with an engineer. (Please include the forum URL and your forum username.)
https://salesiq.zohopublic.com/signatur ... 97d0be8892

[hk87]

Based on the information currently available, we are unable to pinpoint the cause of the issue at this time.
Please check to see if there is sufficient space on the volume and in the root directory. The timestamps in the logs do not match the current date; you may want to try adjusting the system time and then retry.
If the above steps do not resolve the issue, please go to the online chat window to schedule a remote troubleshooting session with an engineer. (Please include the forum URL and your forum username.)
https://salesiq.zohopublic.com/signatur ... 97d0be8892

I tried to install version 7.0.1113 on 2026-09-10. Errors occurred. These were reported. Here is your response (2026-09-11):

Our internal lab tests have reproduced the issue you described, and we are continuing to investigate. We will notify you once there is an update; we appreciate your patience.

Best regards
Phil - NAS Technical Advisor

Technical Support Team

TerraMaster global technical support


I have now inquired about the current status viewtopic.php?t=10417. I was directed to the version 7.0.1225, and this one doesn't work either.

And now I'm being recommended to install 7.0.1113. You probably notice it yourselves.

In summary, versions -1079, -1113, and -1225 do not work, and within these versions, we are always redirected to a different one.

Everything has been documented in the threads regarding this version. It is very concerning that new versions keep being launched while the actually reported bugs seem to be ignored.

It is more than questionable whether I will continue to participate in the beta program if such serious bugs are not fixed and I am excluded from official versions.

[EriChan]

We sincerely apologize for the frustration and circular instructions you experienced throughout this process.

Following a thorough investigation with our team, we have confirmed that the update failure from 7.0.1078 is indeed caused by a bug within the system update mechanism itself.

This issue has already been resolved in our upcoming version. To save you time and prevent further failed attempts, please remain on your current 7.0.1078 version for now—there is no need to try any intermediate update packages. You will be able to update directly once the next version is released.

We truly appreciate your detailed logs and continuous dedication as a beta tester. Thank you for your patience and understanding!

[hiteksam]

Hello, I have been unable to reach support, after performing TOS 7 update, the TMAX is asking to reinitialize.
F6-424 Max entered TNAS Initialization after direct TOS 6 → TOS 7 upgrade; need non-destructive recovery preserving existing TRAID/Btrfs data

Device:
- TerraMaster F6-424 Max
- Six 8 TB SATA HDDs installed
- One 1 TB M.2 NVMe SSD installed; second M.2 slot empty
- Existing storage configuration before upgrade:
- Storage Pool 1: 29.07 TB, TRAID, status Normal
- Volume 1: Btrfs, status Normal
- Volume usage: 25.16 TB / 29.07 TB (approximately 3.91 TB free)
- Disk overview showed SATA 6/6 present and disks reported Good

Pre-upgrade software / firmware:
- TOS version: 6.0.794
- BIOS/initBoot version shown in TOS: 5.26
- TOS offered the official package:
TOS_X642.0_Update_7.0.0747_1247_2607310709.bz2
- Device was upgraded using TOS Control Panel → System → Update.
- The official June 2026 TOS 7 release post lists F6-424 Max as a model that can update directly from TOS 6.0.794 to TOS 7.0.0747.

Sequence:
1. Before the upgrade, Storage Pool 1 and Volume 1 both displayed Normal.
2. We selected the offered TOS 7.0.0747 update in the TOS 6 Control Panel.
3. TOS displayed the TOS 7 notification/release-note confirmation screen. We confirmed it.
4. TOS displayed:
- “Unzipping the software package. Please wait!”
- then “The system is being updated…”
5. The NAS later became unavailable at its former address, 192.168.1.2.
6. TNAS discovery / browser now finds it at 192.168.1.82.
7. At the new address, it presents the “TNAS Initialization” web interface, specifically:
- Heading: “Load the Bootloader”
- “Online download (recommended)” is preselected
- Alternative: “Manually upload (Click to download the bootloader)”
- Buttons: Back and Next
8. We have NOT clicked Next, selected a bootloader, started Automatic Initialization, created a new pool/volume, formatted disks, removed disks, or otherwise initialized the NAS.
9. The goal is to retain the existing six-disk TRAID storage pool and Btrfs Volume 1 with all data intact.

[TMzethar]

Your question does not match the topic of this thread.
The technical support email may not be able to respond to your question on the same day.

We need more information to determine the cause of the problem.
What does the initialization screen you mentioned look like? We recommend providing a screenshot to illustrate it.

If you prefer to communicate via email, please wait for a reply.
If you wish to continue discussing this issue on the forum, please start a separate thread of your own.

[iindeec]

Hello
I've installed ISCSI Manager from official store, created Target and LUN, but can not connect to it from my pc - getting error like "no portal found". Also on NAS service for open-iscsi not running. Can it be fixed or there is no way of making iscsi target on this version? i'm using f2-212 with TOS7 1125