TOS 6.0.694 (X86) is Released for Update

[RyanYang]

Target Users:
Users currently running TOS 6.0.500 or later versions.
Note:
1. If your TOS version does not meet the requirements, please first check the update conditions for TOS 6.0.530.
2. This update package is not applicable to TOS 6 beta version.

Here, we sincerely thank user powerQ、billyBob、liability、Gremlin、Claus、FredMutter、seb、Arendatr、pepebetis、jositodc、sianderson、Polo、thierrys73、Vladimir、epx8dcm4、ArtMetz、Tom、Abernathy、therealguppy、Patryn、vignatiev and others, for their sharing and feedback. It is your support that has enabled us to quickly identify and resolve some issues.

Update Notes
Bugs fixed:
1. Fixed the issue that backing up system configurations might generate excessively large files in the root directory.
2. Fixed the issue that system configurations could not be reset when SPC was enabled.
3. Fixed the issue that NTP service and SPC activation status could not be restored.
4. Fixed the issue that fan speed might indicate abnormally high levels in Smart Mode.
5. Fixed the issue that system drives and M.2 hot spares might experience delayed activation.
6. Fixed the issue that mounting multi-partition hard drives might cause errors.
7. Fixed the issue that duplicate entries might appear in media index directories.
8. Fixed other known issues.

What's new:
1. Added ip6table firewall tool for IPv6 traffic management.
2. Improved domain user permission configuration.

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.

Other Software Downloads:
Download TNAS PC 5.2.003 for Windows OS:
https://download3.terra-master.com/Apps ... .2.021.exe
Download TNAS PC 5.1.202 for macOS (x86 and ARM architecture):
https://download3.terra-master.com/Apps ... .1.202.pkg
Download TNAS PC 5.1.202 for macOS (ARM architecture):
https://download3.terra-master.com/Apps ... .1.202.pkg
Download TNAS Mobile 3.3.057 for Android:
https://download2.terra-master.com/TNAS ... .3.057.apk
TNAS Mobile for iOS: Download from the iOS App Store.

[Gremlin]

And, yet again, I have to tell you that ClamAV does not re-enable "Realtime Protection" after the update.
ClamAV is the only app I have running on this particular machine (f5-221) so I cannot tell what else may be "broken" as yet.

ALSO:
Can you advise if this version is a suitable update for .688Beta? Does it include the 'Beta' functions (it only mentions adding Ip6table) or will that follow some time in the future. Your version numbering leaves a lot to be desired imo.

[sianderson]

updated to 6.0.694 no problem, out of interest is there any way the nas drive could email when there is an update? i only knew because i randomly checked the forum (the nas drive knew there was an update, but again you only get to know about it when you log in to the web desktop)

since the nas drives just work then theres no actual need to login to them, i think i mentioned before the buffalo nas drives actually flash a light on the front also when theres a notification as a prompt to go and check can something be done?

[sianderson]

ok i lied, following the upgrade, my backup USB drive now seems to identify itself as SDC_1, presumably because the upgrade didnt release it and it detected it as a new USB?, my TFM tasks are obviously set to SDB_1 so now they fail as it cant find it.

i managed to get it back to identify as SDB_1 by turning off the USB drive and turning it back on (leaving the nas drive alone) so it redetected it, but if i hadnt have noticed this then backups would have failed

[GevinKe]

ok i lied, following the upgrade, my backup USB drive now seems to identify itself as SDC_1, presumably because the upgrade didnt release it and it detected it as a new USB?, my TFM tasks are obviously set to SDB_1 so now they fail as it cant find it.

i managed to get it back to identify as SDB_1 by turning off the USB drive and turning it back on (leaving the nas drive alone) so it redetected it, but if i hadnt have noticed this then backups would have failed

Hello, we sincerely apologize for the inconvenience caused!

This issue occurs because the name of the USB drive changes dynamically based on the order in which it is plugged in. As a result, the backup source/destination folder paths become invalid, causing the task to fail. We have reported this issue to the TFM product team and will push for a fix as soon as possible.

As a suggestion for USB drive backups, we recommend using the USBcopy application. It identifies USB devices based on their unique ID, so even if the drive name changes, the backup tasks can still run normally, effectively avoiding path issues caused by name changes.

[Chelya]

Hello, everyone. I have an F5-221 model. Currently, it’s running TOS 5.1.67 with BIOS version MAPL0304V22. Up until now, I’ve hesitated to update the system to TOS 6.0. The control panel indicates that the latest version is already installed, but given the potential limitations for the F5-221 mentioned in other threads—even though MAPL0304V22 doesn’t seem to have hardware restrictions—I still didn’t risk upgrading.

Now, however, I’m thinking it might finally be time to update. But I’m really concerned about ending up with a bricked device if something goes wrong (especially since, as I understand it, the entire previous root filesystem is wiped—I’d hate for it to be erased only for the new system to fail due to hardware limitations).

So, my question for the experts is: How safe is it to upgrade to TOS 6 with my current hardware? And are there any recovery methods in case the update doesn’t go as planned?

[MikeZhang]

Hi, please follow our update guide carefully.
viewtopic.php?t=6809
If you are really worried, you can back up system configuration first then continue.

[seb]

Hello,

All seems good for me.
The only issue I noticed for the moment is that custom SMTP credentials for notifications has been cleared.

[liability]

I have been trying to download the update for the past 3 hours,and it gets stuck at 6%. Have rebooted the router, but same problem. Internet connections is fine 1GB fibre. Currently on 6.0.688.

Edit - it appears that the download keeps resetting, it is now at 2%.

Edit Edit - It eventually downloaded and updated overnight - took about 7 hours based on the emailed update notice. Seems to be working okay.

F2-221

[MikeZhang]

Hi, what is your NAS model?
Please generate system log and send to our engineer support at terra-master.com.