TerraMaster Forum

Dear TerraMaster Users,

To continuously improve the TOS user experience, better align with real-world usage needs, and address existing pain points, we are officially launching the TOS Feature Satisfaction Survey. Your ratings and suggestions are extremely valuable and will serve as important references for future product iterations, feature optimizations, and issue fixes.

This survey covers the core and most widely used features of TOS. You are welcome to rate each feature based on your actual experience, and also freely share optimization suggestions, new feature requests, bug reports, or any other feedback. All comments and suggestions will be carefully collected, reviewed, and followed up by our team.

How to Participate
Click the link below to submit your ratings and feedback:
https://support.terra-master.com/tos-vote/en

We sincerely invite both new and existing users to participate. Based on the survey results, we will prioritize improving low-rated features, implementing popular requests, fixing existing issues, and reducing unnecessary updates — ensuring future upgrades focus on practical user needs while enhancing overall system performance, smoothness, and usability.

You are also welcome to share this survey with other TerraMaster users. We will continue to update product optimization progress on the forum. If you have any questions during participation or would like to provide more detailed suggestions, please feel free to leave a comment in this post, and we will follow up promptly.

Thank you sincerely for your continued support and valuable feedback. Let’s work together to build a better TOS experience!

Best regards,
TerraMaster
2026.5.20

just submitted my survey so you have at least one

Hi TerraMaster Team,I would like to request expanded UPS support in the upcoming TOS 7.Currently, TOS primarily supports standard USB-HID Power Devices. However, many popular, heavy-duty UPS models, such as the MUST EP21-0612 PRO and similar series, do not use the USB-HID protocol. Instead, they utilize a Serial-to-USB chip and communicate via older but highly reliable protocols (like Megatec / Q1).These specific UPS models are extremely popular among NAS users because they support large, high-capacity external batteries of various types (AGM, Gel, LiFePO4, etc.). This allows users to build long-running backup power setups for their server hardware. Unfortunately, due to their industrial-leaning design, they completely lack USB-HID chips.In standard Linux Network UPS Tools (NUT), these devices are fully supported and successfully handled by drivers like:blazer_usbnut-xml (or custom serial-over-usb drivers)Since TOS is based on Linux, it would be a huge upgrade if you could include these native NUT drivers (blazer_usb / nut-hex / richcomm_usb) in the TOS 7 UPS management service. This would allow users to manually select the appropriate driver if standard USB-HID auto-detection fails.Device details for reference:Model: MUST EP21-0612 PRO (and similar series with external battery support)Connection: USB (recognized as a serial/COM emulation device, not HID)Common Linux NUT driver: blazer_usb (subdriver cyan)Adding this would greatly expand compatibility for advanced users who rely on custom, long-lasting power backup solutions.Thank you for your hard work on TOS 7!

Hello, Terramaster. There are not enough functions for full-fledged deployment of websites, for example, in Web Station of another company, you know which one. In this case, I'm not talking about copying functions, but you can create something similar or even better. There is not enough support for issuing free SSL/TLS certificates, such as Let's Encrypt. Believe me, many people would be very grateful to you.

Stanislav123 wrote: ↑14 Jun 2026, 00:48 Hello, Terramaster. There are not enough functions for full-fledged deployment of websites, for example, in Web Station of another company, you know which one. In this case, I'm not talking about copying functions, but you can create something similar or even better. There is not enough support for issuing free SSL/TLS certificates, such as Let's Encrypt. Believe me, many people would be very grateful to you.

Thank you for your feedback. We have fully recorded your feedback and forwarded it to the product team for evaluation. It will be considered in future version planning. We will notify you if there are any adjustments or optimizations. Thank you again for your attention and patient feedback on TerraMaster products.

i TerraMaster team,

I'd like to request the ability to take granular, per-subvolume snapshots from within TOS.

I run a Docker homelab where the NAS is the single source of truth: all my container data (and the compose files) live in one shared folder exported over NFS, with each container getting its own subfolder. This lets me treat the Docker host as fully disposable — mount the share, bring everything up.

The current limitation is that the Snapshot app only operates at the shared-folder level. In the "Create Snapshot task" dialog, the Snapshot Destination dropdown lists whole shared folders (e.g. /Volume1/public) and nothing finer. There is no way to target an individual subfolder.

That leaves only two options today:

One global snapshot of the whole folder — every container is captured together, so I can't set different retention per app, and I can't roll back a single container to its own point in time without affecting the others.
A separate shared folder per container — this gives per-app snapshots, but it's fully manual, doesn't scale to dozens of containers, and multiplies NFS exports and permission entries for no real reason.

TOS already runs on Btrfs, so the underlying capability is right there (btrfs subvolume create / btrfs subvolume snapshot). I'd love to see it surfaced in the UI:

Create a subfolder as a Btrfs subvolume, or convert an existing subfolder into one, from the TOS interface.
Let the Snapshot app target individual subvolumes — each with its own schedule and retention policy — not just top-level shared folders.

This is exactly the per-container granularity that ZFS dataset-based systems (e.g. TrueNAS) and Unraid community scripts already provide, and it's one of the most requested patterns among Docker / self-hosting users. It enables independent retention per application, atomic rollback of a single service after a bad update, and — combined with pre/post hooks — application-consistent backups of databases.

Even a small first step would cover most of the need Having the Snapshot task picker enumerate subvolumes, not only shared folders. we can create the sub-volumes via terminal or shh (even though would be nice to do it in the UI)


As a bonus, a "snapshot all child subvolumes" task type, and optional pre/post-snapshot hooks (to stop a container or run a quick DB dump before the snapshot), would make this top notch

Thanks for considering it.

mordillo wrote: ↑20 Jun 2026, 21:07

Thank you for your feedback. I will pass your suggestions on to the product team for evaluation.

Hello everyone, the purpose of this post is to conduct a satisfaction survey, not to collect specific feature requests. If you have specific requests, please create a new thread. Please do not submit requests in this thread, as it will make it difficult for us to track and follow up.