TerraMaster Forum

I updated to TOS .535 and it went well as far as I can tell with my setup.

There are still 2 issues that I have reported in prior TOS updates that are still in this version that needs TM attention.

The issues have been reported before and they are:

1. The SSH Port in "Terminal & SNMP" always reverts back to its default setting of 9222. I set it to a different port and need to adjust back after every TOS update.

2. The "Network I/O" chart in the "Resource Monitor" still has some strange/blank displays depending on the time-frame selected.
a. I have a F4-423 with both LAN Ports bonded with 802.3ad.
b. The "All" graph is blank for all time-frames.
b. The LAN 1 & 2 graph selections are blank for the "Yesterday" selection.
c. The "Last 7 days" & "Last 30 days" have 17 digits in the "MB/s" chart scale.
1. See attached screenshots for the display errors.

TM: Kindly put some attention to these errors and fix for the next TOS update version. Many thanks.

F424 Pro
Updated to TOS 6.0.530 without issue except for media user group not visible. I tried adding it and it says "The name already exists!"

I updated to 535 and media group is still not visible with the same error as above... what is the best way to restore or make the group visible?

Cheers!

If i mount an extern or intern hdd or ssd with ext4 format, than the NAS crash after 1 Minute and i must restart the NAS.
It doesn't matter whether I mount the HDD/SSD via the TOS interface or with a command.
"mount /dev/sdzb1 /Volume1/@disk/Externaldrive_sdzb1".
It doesn't matter which directory I mount it in, it just crashes and the NAS doesn't respond at all. I've already tested various ext4 HDDs and it's always the same.

In tos6 I can't keep the read and write privileges for the various users in the newly created subfolders in "public", even if I checked the option to make them free to all the subfolders every time BitTorrent creates a new folder I have to go and change the privileges every time.
Quite boring.

I bought Terramaster for one purpose: to make backups. But I haven't been able to do it for half a year. WebDAV does not work. Technical support can't solve the problem, they say you need to use WinCP. But it's a program, and I need wordpress, I need a MacBook and many other programs.

I'm very disappointed in TerraMaster. If the problem is not solved within a week, I will sell TerraMaster and buy Synology or QNAP. Terramaster is a disgusting company. I'm very sorry to say this, but I'm tired of constant problems.

baf28 wrote: ↑17 Nov 2024, 20:25 I bought Terramaster for one purpose: to make backups. But I haven't been able to do it for half a year. WebDAV does not work. Technical support can't solve the problem, they say you need to use WinCP. But it's a program, and I need wordpress, I need a MacBook and many other programs.

I'm very disappointed in TerraMaster. If the problem is not solved within a week, I will sell TerraMaster and buy Synology or QNAP. Terramaster is a disgusting company. I'm very sorry to say this, but I'm tired of constant problems.

need help ?

star wrote: ↑15 Nov 2024, 06:50 Two nases updated to this version and they no longer send local smtp notifications

My email notifications stopped working too.

fcs001fcs wrote: ↑16 Nov 2024, 07:22 I had the same issue of the SSH port revering back to its default 9222 setting on the last few TOS updates. I reported it via this forum, but I guess that TM has not got around to fixing it yet.
I now just check it after each update and reset it to the port number I had set for it prior to the upgrade.
TM: This is a relatively minor issue, but can this be fixed in the next TOS update?

This issue will be fixed in a subsequent TOS6 version update.

star wrote: ↑15 Nov 2024, 15:24 I have now logged the error and i read the log and it shows why it happens for some reason it senses the link go down and then Registering new address record for 169.254.0.2 on eth1.IPv4.
despite being told to be static. wich is odd?
smtp local gave this error failed to sn.smtp.SendEmail(HandleSendEmail): remote error: tls: handshake failure
ive sent the entire log to the support mail

We have not found the email you sent at this time. Could you please attach a link to this forum post to the email as well, so we can recognize that you sent it?

Gremlin wrote: ↑16 Nov 2024, 18:19 and AUTO POWER ON failed this morning despite being set and enabled. Auto shutdown worked last night.

We will verify the situation you mentioned.