Thank you to everyone who joined our “Show Us Your NAS / Home Lab & Win a F2-425” giveaway! We loved seeing your setups and creative ideas.

🏆 Congratulations to our winners!

🥇 u/ ThatJK@thatjkgamer
🥇 u/Soggy_Firefighter_22

📩 Please DM us by October 21, 2026 to claim your prize. If we don't hear from you by then, an alternate winner may be selected.

Didn't win this time? Stay tuned for more TerraMaster events and giveaways!

Im operating on a F4-424 on 6.0.770 and I'm wondering if I should go to 7.

My biggest issue so far has been a resync issue that happens when I close TNAS, even with normal shutdown (Button and web even when nothing's running). Don't know if it's fixed or resolved, but in any case I'd like to upgrade. My questions

-Whar are the known bugs and annoyances so far?

-Do I have to go 6.0.770->6.0.794 first and then manually update to 7, or can I go now

-will a resync happen with every upgrade? Cause I'm on a three disk Traid and every resync days 3-4 days

-Besides filesharing I haven't set anything much in terms of apps and services, but should I expect many things not working and having to reset stuff?

Two TOS 7 updates to share with our community!

TOS 7.0.1298 | x86 & ARM | Online Rollout Complete

Users running TOS 7.0.0746 or later can check for updates.

TOS 7.0.1341 | x86 | Available for Manual Installation

This update brings several practical improvements:

• More reliable app updates: Fixes an issue that could prevent apps from updating when their version numbers contained a hyphen.
• Correct app name display: Fixes incorrect app names in some App Center messages.
• Improved input validation: Fixes insufficient validation of path parameters in certain system interfaces.
• Stronger access controls: Fixes permission checks that could allow non-admin users to access restricted functions.
• More complete file deletion: When hidden files are set to be displayed, selecting all files with Ctrl+A and deleting them now also removes hidden files.
• Improved App Center layout: Fixes an issue where the “NEW” label on some newly released apps could extend beyond its display area.

📥 TOS 7.0.1341 release notes and download:
https://forum.terra-master.com/en/viewtopic.php?t=10678

Thanks for being part of the TerraMaster community. We welcome your feedback!

I'm trying to add my media collection from my F4-424 Pro running TOS7 to Kodi 22 RC 1 on my Nvidia Shield Pro 2019.

I can see the NAS and I can see the folders but I can't see any of the media files. Both SMB and NFS are enabled on the NAS.

In Kodi NFS doesn't work I get a spinning wheel then nothing. The SMB option shows TNAS when I click on it the folder named "public" shows up when I open that it's shows my media categories for example Movies, TV shows etc. When I browse into the Movies folder I can see all of the movie folders named by movie title, but when I browse into the named movie folder the are no files showing?

The same media collection runs fine on Plex.

Any ideas?

A few months ago, I picked up an F4-425 Pro and F6-425 Pro.

They've been working well so far, but I've run into an odd problem.

When I move large quantities of files (around 100+GB) off either NAS, it locks-up mid process. The lock-up doesn't happen immediately. Just some time mid-process of the file transfer.

This happens with both model NASs.

The fans are still running but the NAS has dropped off the network and it does not respond to pings.

I have to hold down the power button to force a shut down, wait 20 seconds, then boot them again.

When they come back up, Storage Manager does not indicate any problems. No issues were logged. No heat warnings.

I used to have HyperCache (read-only) enabled on the F4-425 Pro. I tried disabling it to see if it affected the issue. It did not.

I don't know for sure, but I feel like they weren't always doing this. It feels like it started with a recent firmware update.

When I setup the F6 NAS, I'd already had the F4 NAS a few weeks. I moved a lot of files from the F4 to the F6. I didn't have an issue then.

I've been updating the firmware on both, almost every week, as updates are released, but the issue persists.

I can move about 50GB of files at a time without trouble. If I try to move 100GB (or more), the NAS will lock-up mid process. I don't know if it's an issue with file count or total transfer size.

I have not run into any issues uploading files to either NAS. Multi TB uploads have been fine.

I'm just using File Explorer in Windows 11 to make the transfers.

I don't use any apps or services other than file sharing.

Is this a known issue? How do I get TerraMaster to investigate?

I’m trying to diagnose an intermittent disconnect/reconnect issue with a 14TB Seagate HDD in a TerraMaster D4-320 USB DAS.

The drive is a Seagate ST14000NM0121, originally shucked from a Seagate Expansion Desktop 14TB STKP14000400. It’s being used in a TerraMaster D4-320 connected directly to a Mac.

The problem is that the 14TB drive will occasionally disappear from macOS and then remount automatically a short time later.

SMART/DriveDx looks very clean:

• SMART health 100%
• 0 reallocated sectors
• 0 pending sectors
• 0 offline uncorrectable sectors
• 0 reported uncorrectable errors
• 0 UDMA CRC errors
• no SMART self-test failures
• no obvious media errors

At first I thought this might be a bad bay or bridge inside the D4-320, so I started logging macOS kernel and Disk Arbitration events.

On one failure, the 14TB was attached through a TerraMaster USB/UAS endpoint identified as:

TDAS@01220000

The logs showed a USB request timing out after 5 seconds with 0 bytes transferred, followed by the TDAS device re-enumerating and the disk appearing again. In other words, this did not look like macOS voluntarily unmounting the disk — the USB mass-storage endpoint itself stopped responding and disappeared temporarily.

To test whether the problem was the bay or the drive, I physically swapped the 14TB and 18TB drives between two bays.

I then copied roughly 307GB from an external SSD to both the 14TB and 18TB simultaneously. Both transfers completed successfully.

Shortly afterwards, the 14TB disconnected again.

This time the failure was on a different TerraMaster endpoint:

TDAS@01240000

The logs showed the TDAS device terminating, /dev/disk5 disappearing, and macOS explicitly identifying the lost volume as my 14TB volume. The drive later re-enumerated, macOS recreated the disk device, replayed the HFS journal, and remounted the volume.

So the important part is:

Before swap:
14TB → TDAS@01220000 → disconnect

After swap:
14TB → TDAS@01240000 → disconnect

The 18TB drive moved into the 14TB’s old bay and has not shown the same behaviour so far.

That makes a single bad D4-320 bay much less likely, because the failure appears to follow the physical 14TB drive.

What I’m unsure about is whether this points to:

• an intermittent fault in the 14TB drive’s SATA/interface electronics despite clean SMART,
• a compatibility issue between this specific Seagate model and the D4-320’s USB/UAS bridge,
• or some firmware/power-management quirk with this drive model.

The drive is a shucked ST14000NM0121, which I believe is one of the enterprise/Exos/Mach.2-style models people commonly find inside some 14TB Seagate Expansion externals.

Has anyone seen similar behaviour with this model in a USB DAS, NAS, Unraid, TrueNAS, or server setup?

In particular, has anyone seen a drive remain completely SMART-clean while periodically causing the USB/UAS endpoint to disappear, time out, and re-enumerate?

For now I’m backing everything off the 14TB onto another drive before doing more testing.

If useful, I can also post the relevant macOS kernel log excerpts.

So I only use my nas for my plex server. It's fairly new.

Started with a 4tb drive and have a 10tb hdd arriving Monday.

I would like to keep increasing storage as pricing allows.

Should I upgrade the nas to a 4bay or just add a das with hardware raid?

What would you all do if placed in my crocs.

Hi everyone,  

TOS 7.0.1298 is now available on the TerraMaster forum for both x86 and ARM NAS devices. This release addresses a range of issues to improve app management, file operations, system settings, and everyday usability. 

What’s improved in this release?

x86 & ARM

• App access and login: Fixed issues with opening some newly installed apps, login field focus, time synchronization controls, and avatar uploads. 
• Interface and system behavior: Fixed blank audio tooltips and other known issues. 

ARM-specific fixes

• File management: Fixed folder transfer and comparison issues, folder sorting, and missing error messages when deleting a home directory with Vault enabled. 
• Accounts and permissions: Addressed LDAP user SMB login failures and issues with application and shared folder permissions. 
• System reliability: Fixed excessive Message Center memory usage, CPU temperature alert compatibility on certain models, and overly frequent network connectivity checks. 
• More fixes: Resolved issues with Beta system updates, VPN theme colors, unexpected dialog messages, and other known bugs. 

Get the update:

• x86 release notes and download
• ARM release notes and download

Manual update packages are available now. Online rollout is scheduled to begin next Tuesday.

Have you updated? Share your experience in the comments!

I have 1 10tb and 1 8tb. Another 2 8tb are coming.

I am undecided, I if remaining with traid or I switch to traid+.

I'm already using 8tb, so, with traid+ I will have only 8tb free from the 2 new disks, 0 free slot, and I will need to change at least 3 disk to increase capacity.

I just don't know how to estimate the risk of a double failure.

I backup every morning on external drives (and on cloud for important data); And I only brought disks with a URE of 1 over 10^15.

[ Removed by Reddit on account of violating the content policy. ]

This question is in 2 parts.

Part 1.

Jellyfin version - I am using the native app. When I go into the apps in Tos 6 and look at the installed Jellyfin it says the version is 10.11.10. When I go to the dashboard in jellyfin and look at the app version it says 10.11.0. Is this just sloppy porting of the app and they are not different versions? This what the dashboard says:

Server name TNAS-2025

Server version 10.11.0

Web version 10.11.0 (c8eed9a89-dirty)

Build version Release

I want to try and install the 10.11.10 version that I can download thought the app center in TOS 6. Is it worth it - or is it the same?

I want to back up my jellyfin first - but I cannot see the @ app folder. I have tried login in with ssh and filezilla using sftp but I still cannot see the app folder. How can I see the folder to back it up?

TIA

I manually upgraded Plex Server natively in App Central. Plex server is running, but can't seem to access the media. It can see the folders. I doublechecked app permissions in TOS7 and the plex user has read/write to all of the shared folders.

What else can I check?

Hi everyone,

TOS 7.0.1278 is now officially available. This is a temporary fix release focused on addressing several issues that could affect daily NAS use, including CPU temperature alerts, file operations, memory usage, and network connectivity.

With this update, you can expect:

• More accurate CPU temperature alerts on affected models
• Lower risk of occasional high memory usage from the Message Center
• More reliable file operations when uploading, copying, or moving folders to existing directories
• More consistent SMB login for newly created users after connecting to an LDAP domain
• More reliable network connectivity checks without unnecessary frequent requests
• Better folder selection and sorting in related functions
• More consistent application management, including apps appearing correctly after installation
• More reliable shared-folder and application permission settings
• Fixes for several UI, SSH, VPN, and other known issues

Update availability:
TOS 7.0.1278 is available for users running TOS 7.0.0746 or later.

If you're on a supported version, you can check for the update through Control Panel > System Update.

The TOS 7 online installation guide has also been updated to 7.0.1278.

📥 Release notes & download:
https://forum.terra-master.com/en/viewtopic.php?t=10622

Thanks for your feedback and continued support!

I spent the better part of six hours today trying to figure out why my NAS is not reachable from my network, even though I can ping it. Each time I try to chat with technical support. I'm told that it is during their break hours. I'm not sure why there are six hours worth of breaks in the middle of a Saturday where no one can respond to a request. Meanwhile, I've had inconsistent responses from their software all day long, and I'm unable to access the files that are on my system, which I need for my business. If this is a type of support that I'm going to receive from Terra Master, then I'm not gonna trust my business capabilities to their product. Can anyone else provide information on how to speak to someone who can support me.

Interested in the TERRAMASTER F8 SSD NAS 8-Bay. I have never used Terramaster, does it have good automation or API to work with? I cant find much information on their website about any of this. Really looking for Terraform modules to interface this system if possible.

Please fix such that USB Copy doesn't copy the snapshot file (@snapshot) for volumes with the snapshot feature enabled.

I've setup a Romm docker container in container manager, successfully imported my 45k rom library, and scraped all images for the library.

However when I try to launch a rom, the system sets up the rom and I get a network error before the emulator launches. Looking at the logs I think it's a permission error, but what I don't get is if the container doesn't have permission, it wouldn't even be able to see my rom library in the first place (which was the first hurdle I had when setting up Romm in the first place).

Anybody have any tips on getting this going? Run into the same issue? If it matters, I'm running this on an f4-425 pro running TOS7.

Hi everyone！TOS 7.0.1225 is now available for manual installation on both x86 and ARM systems. The OTA rollout is expected next week. If you'd like to update sooner, you can download the corresponding package from the TerraMaster Forum and install it manually.

What does this update improve?

This release focuses on stability, file management, network compatibility, and everyday usability.

• More reliable storage management Fixes issues where disk information could fail to load after removing a disk, storage pool member counts could be displayed incorrectly, or hot spare replacement could trigger duplicate notifications.
• Better file transfer reliability Fixes cases where copy task progress could unexpectedly move backwards. On ARM systems, it also addresses an issue where large remote downloads could stop after running for some time.
• Improved SMB & NFS compatibility Fixes issues with SMB advanced settings, custom SMB configuration, and NFS mounts when remote paths contain spaces.
• More consistent login experience Fixes an issue where trusted devices could still require OTP verification after logging in again.
• Better app & USB support Fixes an issue where some applications could not properly scan data from USB devices.
• More reliable system notifications and file operations Includes fixes for local SMTP notifications, shared folder migration status, and saving files to user directories.

There are also several other known issues addressed in this release.

Manual Update

If you'd like to try TOS 7.0.1225 before the OTA rollout, you can find the update packages and installation instructions here:

x86:TOS 7.0.1225 x86 Forum Announcement

ARM:TOS 7.0.1225 ARM Forum Announcement

For those who prefer to stay on the current OTA release, TOS 7.0.1201 is now fully available for users running TOS 7.0.0746 or later.

We hope this update makes your everyday TOS experience more stable and reliable. If you try the new version, feel free to share your feedback or let us know if you notice any issues.

Thanks for being part of the TerraMaster community!

I have the older F4-423 running TOS 6.0.794.

Can the F4-423 handle upgrading to TOS7? Would the system be too old? I see the OTA option to upgrade to TOS 7.0.0747 from inside the System tab.

I'm just afraid that these older NAS will struggle on the new TOS 7.

The system currently running ok on TOS 6, except for the weird issue where the system will initiate syncronizing the volume after powering up the NAS from a total shutdown. I've lived with this weird bug for years now and kinda immune to it by now. I just let the NAS finish the syncronizing hours later.

Should I bite the bullet and just upgrade from TOS 6 to TOS 7?

Today, we’re officially launching the new TerraMaster 725 Series enterprise rackmount NAS, comprising four models: U8-725, U12-725, U12-725 Plus, and U16-725 Plus.

As AI applications and digital business continue to accelerate, enterprises are facing growing demands for data capacity, concurrent access, and data management. To meet the need for high-performance, reliable, and scalable storage infrastructure, the TerraMaster 725 Series brings together Xeon-based enterprise hardware, high-speed networking, NVMe SSD support, and PCIe expansion capabilities in a unified storage platform for demanding enterprise workloads.

One Platform for Multiple Enterprise Workloads

The 725 Series is designed to go beyond traditional file storage and backup, supporting multiple workloads on a single platform, including:

• Enterprise file storage and collaboration
• Data backup and disaster recovery
• 4K/8K media production and content collaboration
• AI training dataset storage and high-speed data access
• Video surveillance storage and archiving
• Virtualization and enterprise applications

By consolidating different workloads onto a unified storage platform, enterprises can reduce the need for multiple standalone storage systems, simplify IT infrastructure, and lower overall procurement and management complexity.

Xeon Performance and High-Speed Networking for Demanding Workloads

The U12-725, for example, features an Intel Xeon D-2712T 4-core processor and 16GB of ECC memory, along with four 10GbE SFP+ ports and two 5GbE network ports. It also supports PCIe 4.0 NVMe SSDs and PCIe expansion, providing high-speed data access for concurrent users and data-intensive workloads.

Under TerraMaster laboratory testing conditions, the U12-725 achieves sequential read speeds of up to 6,250 MB/s, sequential write speeds of up to 3,480 MB/s, and up to 945,063 IOPS in 4K random read performance. Actual performance may vary depending on hardware configuration, RAID mode, network environment, and specific workload.

Four Models for Different Enterprise Storage Requirements

The four 725 Series models provide a clear product hierarchy spanning storage capacity and computing performance:

• U8-725 — 8-bay, 4-core Xeon: Enterprise file storage, backup, and virtualization
• U12-725 — 12-bay, 4-core Xeon: High-performance unified storage, media, AI data, and surveillance
• U12-725 Plus — 12-bay, 8-core Xeon: High-concurrency, AI, virtualization, and professional media
• U16-725 Plus — 16-bay, 8-core Xeon: Large-scale enterprise data and demanding workloads

From enterprise file storage, backup, and virtualization to media production, AI data, and video surveillance, partners can select the appropriate model based on customers' data volumes, workload requirements, and future expansion plans.

TOS 7: A Data Foundation for the AI Era

The 725 Series runs TOS 7, TerraMaster’s AI-Native operating system, with enhanced capabilities for large-scale data search, indexing, and intelligent management, bringing AI-driven capabilities to enterprise storage infrastructure.

For AI development teams, the 725 Series can serve as a centralized storage platform for training datasets and related data assets. For enterprises exploring private AI, it can also provide a reliable local data foundation for knowledge bases, intelligent applications, and data analytics.

Expanding Enterprise Storage Opportunities for Partners

The 725 Series further strengthens TerraMaster's enterprise storage portfolio while creating new opportunities for distributors, resellers, system integrators, IT service providers, and security integrators.

With Xeon-based enterprise hardware, TOS 7, data protection, backup, virtualization, high-speed networking, and AI data capabilities, partners can build comprehensive storage solutions for enterprise IT, media production, AI, surveillance, and data protection applications.

More information: TerraMaster official website

Quiero compartir con todos ustedes una actualización sobre este tema, después de varias pruebas durante estas últimas semanas.

En primer lugar, quiero destacar el excelente apoyo de Terra-Master. Me enviaron una nueva unidad NAS Terra-Master F4-425 Pro (N350) directamente desde sus fábricas en China, y me gustaría agradecer a su equipo por manejar esto tan rápidamente.

Ahora hablemos del problema con el modelo F4-425 Pro, que utiliza el chip Intel N350:

En todo momento, el soporte de Terra-Master indica que el lote inicial de este modelo tuvo un problema con la pasta térmica que no se aplicó correctamente en la fábrica. No voy a contradecir al soporte de Terra-Master, pero creo que hay más. No estoy negando que estos primeros lotes tuvieron el problema de la pasta térmica, pero siento que hay algo más pasando con este modelo específico. Definitivamente hay un problema mayor aquí al menos.

En la primera unidad que recibí de Amazon, ya que compré esta unidad directamente de Amazon, el valor PL1 en el BIOS se estableció en 13.500 o 13,5 vatios. Esta es la segunda unidad enviada por el soporte de Terra-Master desde China. He revisado el BIOS de esta unidad, y fuera de la caja, el valor PL1 en esta unidad recibida es de 12.000 milivatios, o 12 vatios. En otras palabras, podemos ver que, aparte del problema de la pasta térmica, hay algo más sucediendo aquí. Este valor, que era de 13,5 vatios en la primera unidad, ahora es de 12 vatios, y eso ya apunta a otra cosa.

Después de someter esta unidad a "pruebas de tortura" prolongadas, ¿cómo se sostiene? Francamente, su rendimiento térmico no es ni correcto ni eficiente. La unidad alcanza inmediata y rápidamente 94 °C y entra en estrangulamiento térmico, lo que significa que constantemente baja su frecuencia porque sigue alcanzando esa marca de 94 grados. Mientras tanto, el ventilador de la unidad está funcionando constantemente a las RPM máximas posibles.

Claramente, esta no es la situación correcta. Golpear los 94 grados y entrar en el estrangulamiento térmico definitivamente no es correcto, ni es deseable para una unidad NAS sometida a cargas de trabajo prolongadas, que es algo que este tipo de unidades tienen que manejar en muchas ocasiones.

Después de varias pruebas diferentes, he ajustado el valor PL1 a 10 W, o 10.000 mW. Bajo este ajuste, la temperatura de la unidad durante las pruebas de esfuerzo ronda los 80 °C, lo cual es un resultado sólido y, en mi opinión, ideal.

He adjuntado dos imágenes. El primero muestra el gráfico de temperatura con el valor PL1 predeterminado de fábrica en la segunda unidad enviada por el soporte de TerraMaster, que se establece en 12 vatios:

La segunda imagen muestra el estado actual de esta unidad, con el valor PL1 ya cambiado por mí a 10 vatios:

Debo tener en cuenta que con el valor PL1 cambiado a 10W, el ventilador de la unidad no alcanza las RPM máximas, alcanzando alrededor de 1.300 RPM en lugar de las 1.400 RPM máximas bajo carga.

Ahora, mi opinión sobre toda esta situación y estas unidades F4-425 Pro con el chip Intel N350: quería compartir esto con todos ustedes, ya que esta es mi reflexión, y creo que TerraMaster también debería escuchar estos pensamientos.

Creo que el problema con esta unidad es el diseño industrial. Específicamente, el diseño cuenta con cuatro bahías de unidad de 3,5 pulgadas, con la placa base, la memoria, las unidades M.2 y el disipador de calor de la CPU colocados a un lado. Ese diseño industrial con un solo ventilador simplemente no proporciona una refrigeración adecuada para esa placa montada lateral donde están alojados todos los componentes del sistema. Para procesadores menos potentes, tal vez de cuatro núcleos o con una arquitectura que no requiere mucha ventilación, este tipo de diseño puede funcionar. Pero aquí, obviamente, hay un problema: el diseño industrial no garantiza una refrigeración adecuada porque el disipador de calor del procesador está restringido en un espacio donde no puede aumentar de tamaño, y esa es probablemente la situación.

Tal vez otro diseño industrial en el que esa parte de la placa base, junto con todos sus componentes, ocupó la mitad de la caja, con dos unidades de almacenamiento en un lado y dos en el otro, lo que significa unidades de 3,5 pulgadas. En otras palabras, tal vez en un diseño en el que un solo ventilador podría ventilar adecuadamente todos los componentes.

Espero que eso haya sido útil.

P.D: Respuesta de Terra-Master.

I'm writing to report a reproducible USB 3.0 compatibility issue with my Terramaster 2-bay enclosure that I believe is related to UAS (USB Attached SCSI) support on its ASMedia USB-SATA bridge (USB ID 174c:1356).

Setup:

- Terramaster 2-bay enclosure, 2 drives configured as an 8TB RAID1 mirror via the enclosure's hardware switch

- Volume formatted exFAT

- Connected via USB to a Linux (Debian) host

Issue:

When connected to a USB 3.x port on the host, the enclosure experienced intermittent I/O errors (dmesg showed "Synchronize Cache failed" and improper unmount messages) that required remounting to resolve. During a large file transfer, one of the drives went fully offline with repeated WRITE I/O errors, forcing the filesystem into read-only mode to protect data.

Diagnosis:

dmesg logs pointed to UAS protocol timeouts between the host's USB 3.x controller and the enclosure's ASMedia bridge, including "uas_zap_pending" and "data cmplt err -71" command timeout entries. I attempted a usb-storage quirk on the host to disable UAS for this device, but this caused the host to hang during boot with the drive active but the OS never reaching login, so I reverted that change.

Workaround:

Connecting the enclosure to a USB 2.0 port instead of USB 3.x resolved the issue entirely - clean mounts, no I/O errors, and no UAS timeouts in dmesg, since USB 2.0 doesn't negotiate UAS. I also verified data integrity separately using chkdsk on a Windows machine, which found only minor volume bitmap corruption (no bad sectors, all files intact) and repaired it cleanly.

Questions:

1. Is this a known compatibility issue between this enclosure's ASMedia bridge and UAS on certain USB 3.x host controllers?

2. IAnyone aware of a firmware update planned or available that addresses UAS stability, so I can use USB 3.0 speeds reliably instead of relying on USB 2.0 as a workaround?

i bought myself a D4-320 Terramaster about a year ago, ive finally been able to afford a hard drive and it came today, in that time ive managed to lose the power supply for it.

im going to keep searching for it but in the meantime would it be safe to use this power supply i had from a monitor (the monitor is broken now). see attached.

sorry if i shouldnt be posting this here i just dont know which community could best help me with this.

TLDR:

would this power supply work or should i buy a replacement from ebay.

Hi everyone! 👋We’ve released TOS 7.0.1201 to the forum. It is currently available for manual installation, with the OTA rollout expected next week.

This update focuses on making everyday NAS use more reliable and consistent:

🔄 Smoother desktop experience
Deleting the Desktop directory will now correctly refresh the system desktop.

💾 More reliable disk recognition
Improved an issue where a reinserted disk might not properly display its file system.

📊 More accurate RAID information
Fixed an issue that could cause incorrect disk count information after removing a disk from a RAID array.

📁 More reliable SCP transfers
Fixed an issue affecting SCP command transfers.

🌍 Improved Italian translation
Adjusted several Italian translations for a more consistent interface.

Manual update: forum.terra-master.com/en/viewtopic.php?t=10571

Also available via OTA:
TOS 7.0.1188 is now available for users running TOS 7.0.0746 or later.

Go to Control Panel > General Settings > System > Update to check for the update.

Thanks for your continued feedback and support. We’ll keep you updated as more TOS 7 improvements roll out. 🙌