TerraMaster Forum

Hello, yes, everything is disabled. From what I've seen, it's the system memory reserve that's using most of the memory. After restarting the NAS, I'm back to around 40%.

Felix wrote: ↑30 Apr 2026, 16:26

Frynes wrote: ↑30 Apr 2026, 14:44 Thanks for the feedback so far.

Regarding the questions you raised, here are our unified responses:
* UPS Compatibility: We suggest you check the "UPS Compatibility List" on this forum; you can usually find a suitable solution there.

* Hard Drive Hibernation Issue: To more accurately pinpoint the fault, we would like to confirm whether this issue first appeared after upgrading to TOS7, or whether it has always existed in previous versions?

* Kernel Update: Due to hardware limitations, it is currently impossible to effectively update the kernel to the latest version. Therefore, there are no related upgrade plans at this time. We apologize for any inconvenience.

Okay thanks!

The UPS works fine normally but the battery is failing. The issue for my use case is that I do not want to sleep the NAS when the UPS sends a low battery signal especially when still on MAINS power. I already worked around all that until I get a new battery.

The hard drive hibernation issue is on TOS 5.1.73. For my use case, I never want the drives to sleep or hibernate. I posted a work around here viewtopic.php?t=9832 Since then the NAS has been changed so that all the drives are WD Red Plus, but the spindown script issue would still be true.

On the kernel update, I hear you.

For now I will stay with TOS 5, I am not seeing any significant advantage to moving to TOS 7 beta ARM. At his point, I have worked around everything that causes reliability issues...for my particular use case (single user NAS, direct attached via ethernet, used for working archive repository of photography practice).

I will point out, surprisingly considering I purchased this NAS last year, my F4-212 sounds like it has been thoroughly orphaned. I would feel differently about this if there had been a roadmap that showed that the sunset on this NAS was coming soon.

Hello, when I move certain files to overwrite existing ones, I get the error message "source file corrupted" in TOS 7.
I checked the hard drive, no problem, it's normal, green. It's when I move a file to overwrite the one on the other hard drive that I get the corrupted source error message.

The problem affects volume 1, which has two 18TB hard drives in "traid" mode, and also volume 2, which has only one 4TB hard drive.

I can move a new folder onto the drive, but I can't overwrite an existing folder.

Lukin wrote: ↑02 May 2026, 07:03

We will reproduce this issue in our laboratory and find a solution or fix in the next release.

Good afternoon! How are things going with TOS 7?

Platunum wrote: ↑14 May 2026, 03:25

Thanks for your attention to TOS 7, The final verification and debugging phase is underway, and the final version will be released after testing is completed. Please stay tune and wait patiently.

MikeZhang wrote: ↑14 May 2026, 16:51Thanks for your attention to TOS 7; The final verification and debugging phase is underway, and the final version will be released after testing is completed. Please stay tune and wait patiently.

For the ARM build? With seemingly only one public beta?

Or was that statement meant for the ×86/×64 release, which has been tested over months and multiple builds?

crisisacting wrote: ↑14 May 2026, 17:29

For the ARM build

Why is this topic not on the general list on the forum?

Platunum wrote: ↑22 May 2026, 22:24

We temporarily moved this post to the homepage ("Latest News") to give it maximum visibility while the ARM version of TOS 7 public beta is fresh. It'll head back to its standard home under "Update Notice" in a little bit.