This is in response to my locked post about TNAS F2 212 Disk Thrashing at viewtopic.php?t=6326
So, I had a power bump, my UPS drained, and when the power came back I once again had TNAS issues with random reboots, and generally total slowness. I remembered my post and tried stopping that process and the world was good again. I have now renamed /usr/sbin/ter_smartfan to be /usr/sbin/ter_smartfan-NOT-WORKING and after a scheduled reboot things are still working. I will keep my rename in place until the next update.
Please comment if you are seeing similar issues. Other than this I'm happy with the product. But talk about shooting yourself in the foot and making something not usable. Odd. Please someone, fix this issue.
[Discussion] TNAS F2 212 Disk Thrashing Part 2
Re: [Discussion] TNAS F2 212 Disk Thrashing Part 2
Hello, please enable debug mode. After the issue occurs again, wait for the device to restart and then download and send the debug log to our email: [email protected].
If possible, record the time when the problem occurs, as this will greatly help us in troubleshooting.
If possible, record the time when the problem occurs, as this will greatly help us in troubleshooting.
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: [Discussion] TNAS F2 212 Disk Thrashing Part 2
So I have not done this yet. However, I can confirm the disks thrash when sleep mode is turned off unless I neuter the file mentioned previously. If I set sleep to happen at any of the times available then it's OK. For now, I've allowed the file but set it to 5 hrs before sleep. In reality it should never happen now.CursaYang wrote: ↑04 Sep 2025, 08:46 Hello, please enable debug mode. After the issue occurs again, wait for the device to restart and then download and send the debug log to our email: [email protected].
If possible, record the time when the problem occurs, as this will greatly help us in troubleshooting.

