TOS 4.2.41 (ARM) Release Notes
Applicable models: F2-210, F4-210
This update includes the following bug fixes for the previous version:
1. Optimized the prompts when the system was initialized.
Important Notes
1. This update is only for TOS 4.2.01 or later versions. If your TOS is 4.1.27 or an earlier version, please refer to here.
2. Under normal circumstances, the system update will not affect the data in your hard drives, but for your data safety, it is strongly recommended that you back up your data before the update!
How to update your TOS?
Online update:
1. Go to TOS > Control Panel > General settings > Software update;
2. Check the option "Online update", click "Apply";
3. Follow the prompt to finish the update;
Manual update:
1. Download the update package: Update package for ARM models
2. Go to TOS> Control Panel> General Settings> Update & Restore, and click “Manual Update”;
3. Click "Browse" to select the update package;
4. Click "Apply";
Issue report
If you encounter issue during using, please report to TerraMaster official forum “TOS update”.
TOS 4.2.41(ARM) is Released for Update
TOS 4.2.41(ARM) is Released for Update
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: TOS 4.2.41(ARM) is released for update
Does it finally embed netatalk 3.1.13 to fix all the related known CVEs?
viewtopic.php?f=24&t=3253
Just for records:
https://netatalk.sourceforge.io/
22th of March 2022
Netatalk 3.1.13 is available!
The Netatalk development team is proud to announce latest release of the Netatalk 3.1 release series. Please update to this latest release as soon as possible as this releases fixes the following major security issues: CVE-2021-31439, CVE-2022-23121, CVE-2022-23122, CVE-2022-23123, CVE-2022-23124, CVE-2022-23125 and CVE-2022-0194.
All other NAS vendors have fixed it a while back: any concern over unpatched "major security issues" in TOS?
Thanks for consideration
viewtopic.php?f=24&t=3253
Just for records:
https://netatalk.sourceforge.io/
22th of March 2022
Netatalk 3.1.13 is available!
The Netatalk development team is proud to announce latest release of the Netatalk 3.1 release series. Please update to this latest release as soon as possible as this releases fixes the following major security issues: CVE-2021-31439, CVE-2022-23121, CVE-2022-23122, CVE-2022-23123, CVE-2022-23124, CVE-2022-23125 and CVE-2022-0194.
All other NAS vendors have fixed it a while back: any concern over unpatched "major security issues" in TOS?
Thanks for consideration
- sianderson
- Posts: 293
- Joined: 02 Aug 2020, 03:42
Re: TOS 4.2.41(ARM) is released for update
nice and simple update, thank you
Re: TOS 4.2.41(ARM) is released for update
an update to TOS 5 would have been better!
ARM owners get screwed! Thanks for nothing!
ARM owners get screwed! Thanks for nothing!
Re: TOS 4.2.41(ARM) is released for update
Hi. I updated my F4-210 to this version and I have problems...
After every single reboot, the nas is DISABLING SMB and SSH SERVICES.
After every reboot i can't access anymore to the nas and i need to log in the web-gui then enable SMB and SSH to use it...
After every single reboot, the nas is DISABLING SMB and SSH SERVICES.
After every reboot i can't access anymore to the nas and i need to log in the web-gui then enable SMB and SSH to use it...
Re: TOS 4.2.41(ARM) is released for update
{L_BUTTON_AT}rapcat
We have not reproduced your feedback and there may be some system configuration anomalies.
We recommend that you reinstall TOS to correct any possible misconfigurations:
viewtopic.php?f=76&t=423
In addition, please collect a log report to send to technical support for analysis.To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
- Saijin_Naib
- Posts: 79
- Joined: 23 Jun 2021, 01:19
Re: TOS 4.2.41(ARM) is released for update
Wifi SSID parsing is still broken as I reported years ago.
Interface bonding is also broken.
Interface bonding is also broken.
Re: TOS 4.2.41(ARM) is released for update
{L_BUTTON_AT}Saijin_Naib
According to the posts you have sent, we have learned about this problem. We will verify it.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
- Saijin_Naib
- Posts: 79
- Joined: 23 Jun 2021, 01:19
Re: TOS 4.2.41(ARM) is released for update
Thanks for confirming.
Re: TOS 4.2.41(ARM) is released for update
Hello. I have a F2-210 since november. Since the update to 4.2.41 versión im having problem with the device.
Sometimes when I try to login the navigator reports 404 not found, suddenly works again, sometimes de DLNA server stops working.
When i try to open some apps or the control panel, ex. the new window stay blank.
Since the update ADGUARD stop working and isnt possible to installa again.
Im about to ask to amazon to givit it back.
any solutions?
thanks.
Sometimes when I try to login the navigator reports 404 not found, suddenly works again, sometimes de DLNA server stops working.
When i try to open some apps or the control panel, ex. the new window stay blank.
Since the update ADGUARD stop working and isnt possible to installa again.
Im about to ask to amazon to givit it back.
any solutions?
thanks.