TerraMaster Forum

I guess f2-210 has been completely forgotten about? So I bought a $150 dollar door stop???
How about putting your asses in gear and do an UPGRADE!

I have 2 x F2-221's. Both were running 5.0.176. I downloaded the 5.1.24 update package in order to run the manual updates. One of the F2-221's completed the update without any issues. The other one failed. I rebooted and tried again but it failed again.

Both run EXT4 and haven't had any operational issues. The only difference between the units that I can tell is the level of the init boot. The one that fails is on 5.12. The one that was successful is running MAPL0304V17. Can this be the issue preventing the update?

Any news on HW decoding for Plex on F4-223?

Long reconstruction time:
I add one disk of 6To yesterday (original : 1T, used 54Go), time estimed : 160min.
After 24H, only 54%
On my Synology DS218-, i Replace a 6To by a 12To (occuped 79%), time to reconstruct raid : 10H

Hey,
for all of you who got Plex on this ver.
mine is keep closing after a while.
I need to Enable it all the time.
got f5-422

You cannot understand what a relief it is to have installed OMV on my F221 after reading theese threads with pages and pages of user complaints again.

Do yourself a favor and get a small memory stick, an external SSD, and the most recent version of Debian install it on your machines and then install OMV on top of that.

Quick updates, no restrictions, all the software you need in the repositories, and immediate security patches if necessary.
Since leaving this broken piece of terrible and insecure software, I have had no regrets.

If Terramaster simply abandoned TOS and joined forces with OMV or any other NAS open source project, even if they added a personalisation layer on top of it, they would be doing themselves and their users a favor.

A little tip, take a small USB stick (Sandisk Ultra Fit or Samsung FIT Plus) and install Armbian CLI on it. You can also install OMV with Bullseye CLI (armbian-config -> Software -> Softy -> OMV).
Unscrew the housing, remove the old stick, put in the new one, screw the housing, start and wait about 5-10 minutes. Possibly the old HDDs could pose a problem since they have their own bootloader on the board. What can still happen is that your NAS is now always woken up at 12:00 a.m. because the BIOS has a BUG so that your NAS is always woken up at 0:00 a.m. The BIOS MAPL0304V22 provides a remedy.
That's how I used it in the end, because the many errors and the constant updates, which 1 step forward and 2 back were just too much for me.

Why not xpenology? I' m using it and I am very happy with it

OK, what the hell has happened with the 5.1.24 update? F5221 X2 was running the 22 update without problem now most of my devices TVs Media players cant see or loose the TNAS from the network connection or just cant see all the supposedly shared files!

Gone back through all the setup for shared folders and all are exactly the same configuration as before and all were visible with the previous update, so what's going on??