TerraMaster Forum

There is an update package for TOS 5.1.145~6.0.229 coming soon, please wait.

TMRyan wrote: ↑23 Sep 2024, 21:52

bonerserk wrote: ↑23 Sep 2024, 21:23 Hi. Can I have some specification about the relase bugfix : "2. Fixed some issues with Sleep Mode."
Does this fix solve the problem of degraded RAID status while rising Seagate disks in sleeping mode?
Thanks!

I did not find any records of this issue. I will inform the relevant personnel to check this issue.

It seems that version 6.0.500 solved the sleep problem. I installed TOS on NVMe only, and the disks are going to sleep and waking up correctly. Finally, there have been no more RAID corruptions in 5 days!

bonerserk wrote: ↑26 Sep 2024, 23:03

Thank you for your use and feedback.

I will update from TOS 5.1.145 to 6.0.229 when available. Enough experimenting with the TOS 5, and wanting to get a feel of 6.

At the same time, will reinitiate the HDD/SSD for applicable designation and allocation.

Somehow, hearing that the final official TOS 6 possibly be released next month. Hoping so...

I actually installed TOS only on a nvme disk.
Is it possibile to create 2 volumes on the nvme disk and use these 2 volumes, one for TOS and disk storage and the other for Hyper Cache?
Thanks

bonerserk wrote: ↑27 Sep 2024, 18:56 I actually installed TOS only on a nvme disk.
Is it possibile to create 2 volumes on the nvme disk and use these 2 volumes, one for TOS and disk storage and the other for Hyper Cache?
Thanks

No. Unfortunately an ssd-nvme can only be used EITHER for data storage (Vol) OR cache.

Wil lthis latest firmware be a walk in the park for only plex usage and backups of pictures from mobiles and laptops? Will only setup the nas for this purpose when the new max line is available again.

I have noticed that SMB service is not advertising my chosen Workgroup/{Domain} name on the network. Despite changing it from the default "WORKGROUP" to {the name I use on all my windows machines} it still uses the default. I have tried this several times including several reboots and another clean install.

Gremlin wrote: ↑28 Sep 2024, 05:11 I have noticed that SMB service is not advertising my chosen Workgroup/{Domain} name on the network. Despite changing it from the default "WORKGROUP" to {the name I use on all my windows machines} it still uses the default. I have tried this several times including several reboots and another clean install.

I don't quite understand, can I make an assumption? You have user "user1". After changing the workgroup to workgroup123, you cannot use "workgroup123\user1" to access TOS through SMB. Is this your problem?

How long does it take to revert the commit and release the hot fix ?