Page 2 of 9

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 12 Mar 2025, 06:08
by obvious
Hello team!

I've upgraded from 6.0.648 and I'm afraid the "UPS disabled" bug is still present. After upgrading, the UPS support is disabled without notificacion:

Image

Also, the remote UPS server configuration form requires an "http" protocol and a port that should not be necessary.

Image

Thank you!
Regards!

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 12 Mar 2025, 17:32
by TMzethar
viewtopic.php?p=43943#p43943
We have not observed the automatic disabling of the UPS as you reported.
We suspect that the connection between your UPS and NAS may require some time. Please wait a bit longer and then check the UPS configuration; it may return to normal display.
It appears that you are connecting this NAS to another device serving as a UPS Server. This port is necessary.

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 12 Mar 2025, 18:29
by Gremlin
TMzethar wrote: 12 Mar 2025, 17:32
For me the UPS issue is 2 fold. It does disconnect (eg when the network "changes") but it does not reconnect (apparently) - it just disables the function. The really bizarre point is that the port chosen (or suggested) is the default http port (8181)

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 12 Mar 2025, 19:15
by addx972
Thanks terramaster now the nas shuts down at the desired programming

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 12 Mar 2025, 20:09
by TMlinda
Gremlin wrote: 12 Mar 2025, 18:29
If the network address has changed, it may not connect automatically.
If the network is restored after being disconnected,it can connect automatically.
Is the UPS you are using a model in the compatibility list provided by our official website? Please use the model in this list:
https://www.terra-master.com/global/compatibility/

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 12 Mar 2025, 20:27
by Gremlin
TMlinda wrote: 12 Mar 2025, 20:09
Gremlin wrote: 12 Mar 2025, 18:29
If the network address has changed, it may not connect automatically.
Obviously. I will check later to see if it does reconnect. (I am using APC made devices that are known to be compliant - even if the exact model in one case does not appear in your list since it is an IBM branded unit)

With regard to my comment about the port used I also not that the NUT default port remains open so, hopefully, anyone using that (WinNut client for example) will continue to work.

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 13 Mar 2025, 12:05
by King7
As a long-time TerraMaster NAS user, I’ve just upgraded to the newly released TOS 6.0.650, and I’m blown away by the improvements! This update truly sets a new standard for user-friendly NAS management, especially for those of us juggling remote work and team collaboration. 

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 13 Mar 2025, 13:11
by kai
F2-223 | TOS 6.0.650

3. Fixed the issue that text on some pages was misaligned.

Are you serious? Third update in a row you can't center icons! Add just one CSS property, it's a matter of seconds.

Image

I'm tired of writing about problems with inheritance of rights when moving files...

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 13 Mar 2025, 17:07
by TMLila
tanktarta wrote: 12 Mar 2025, 05:30 Having no other avenue to try and fix my domain joining problem that started in 6.0.648, I thought i'd give this version a try. Its somehow even worse. The sequence of events was ...
  • Installed 6.0.650, rebooted into UI OK.
  • Go to Domain settings, try to join domain
  • Quite quickly, an error dialog was displayed, but with no actual message just a tiny error icon (sadly didnt get screenshot).
  • Stepped away for about 2 hours, came back and the web interface was broken with a 502 bad gateway error.
  • Rebooted. STILL have a 502 bad gateway, but I can SSH in. Yet again, I have an unusable NAS.
The following output keeps repeating in the system log.

Code: Select all

Mar 11 21:10:54 terra TOSDaemon[14561]: panic: runtime error: invalid memory address or nil pointer dereference
Mar 11 21:10:54 terra TOSDaemon[14561]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x7fe8b05f4c20]
Mar 11 21:10:54 terra TOSDaemon[14561]: goroutine 274 [running]:
Mar 11 21:10:54 terra TOSDaemon[14561]: github.com/oiweiwei/go-msrpc/ssp/gssapi.InitSecurityContext({0x67a3740, 0xc001965b00}, 0xc001da6210, {0xc001588068, 0x1, 0xc001818360?})
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/github.com/oiweiwei/[email protected]/ssp/gssapi/context.go:223 +0x2c0
Mar 11 21:10:54 terra TOSDaemon[14561]: github.com/oiweiwei/go-msrpc/smb2.(*Initiator).InitSecContext(0xc001818330)
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/github.com/oiweiwei/[email protected]/smb2/initiator.go:35 +0x8f
Mar 11 21:10:54 terra TOSDaemon[14561]: github.com/oiweiwei/go-smb2%2efork.sessionSetup(0xc0039d0410, {0x7fe8b27e8640, 0xc001818330}, {0x67a3740, 0xc0019649f0})
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/github.com/oiweiwei/[email protected]/session.go:29 +0xd8
Mar 11 21:10:54 terra TOSDaemon[14561]: github.com/oiweiwei/go-smb2%2efork.(*Dialer).DialContext(0xc001818300, {0x67a3740, 0xc0019649f0}, {0x67b58f0, 0xc000e7a240})
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/github.com/oiweiwei/[email protected]/client.go:67 +0x1af
Mar 11 21:10:54 terra TOSDaemon[14561]: github.com/oiweiwei/go-msrpc/smb2.(*NamedPipe).Connect(0xc00158a340, {0x67a3740, 0xc0019649f0})
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/github.com/oiweiwei/[email protected]/smb2/smb2.go:118 +0x1f1
Mar 11 21:10:54 terra TOSDaemon[14561]: github.com/oiweiwei/go-msrpc/dcerpc.(*conn).dialConn(0xc0014f0840, {0x67a3740, 0xc0019649f0}, {{0x0, 0x0}, {0x0, 0x0}, 0x0, 0x3, {0x0, ...}, ...})
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/github.com/oiweiwei/[email protected]/dcerpc/conn.go:453 +0xcd3
Mar 11 21:10:54 terra TOSDaemon[14561]: github.com/oiweiwei/go-msrpc/dcerpc.(*conn).dial(0xc0014f0840, {0x67a3740?, 0xc0019649f0?}, {{0x0, 0x0}, {0x0, 0x0}, 0x0, 0x3, {0x0, ...}, ...})
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/github.com/oiweiwei/[email protected]/dcerpc/conn.go:371 +0x65
Mar 11 21:10:54 terra TOSDaemon[14561]: github.com/oiweiwei/go-msrpc/dcerpc.(*conn).Bind(0xc0014f0840, {0x67a3740, 0xc0019649f0}, {0xc0014bad60, 0x2, 0x0?})
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/github.com/oiweiwei/[email protected]/dcerpc/conn.go:336 +0xd3c
Mar 11 21:10:54 terra TOSDaemon[14561]: github.com/oiweiwei/go-msrpc/msrpc/nrpc/logon/v1.NewLogonClient({0x67a3740, 0xc0019649f0}, {0x7fe8b27eda50, 0xc0014f0840}, {0xc0015d02b0, 0x1, 0x1})
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/github.com/oiweiwei/[email protected]/msrpc/nrpc/logon/v1/v1.go:19343 +0x139
Mar 11 21:10:54 terra TOSDaemon[14561]: gitlab.local/DO-module/domain-module/service/domain.GetWorkGroupByNetlogon({0xc003e1c2d0, 0xd}, {0xc00274ceb1?, 0xd?}, {0xc00274d1c0?, 0x0?})
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/gitlab.local/!d!o-module/[email protected]/service/domain/domain_model.go:674 +0x1f9
Mar 11 21:10:54 terra TOSDaemon[14561]: gitlab.local/DO-module/domain-module/service/domain.joinAdDomain({{0xc00274ce71, 0xd}, {0xc00274ce81, 0xd}, 0x0, 0x1, 0x0, {0x0, 0x0}, {0x0, ...}, ...}, ...)
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/gitlab.local/!d!o-module/[email protected]/service/domain/ad_model.go:133 +0x4ad
Mar 11 21:10:54 terra TOSDaemon[14561]: gitlab.local/DO-module/domain-module/service/domain.(*Service).ConnectToAdServer.func1()
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/gitlab.local/!d!o-module/[email protected]/service/domain/domain_model.go:240 +0x2f3
Mar 11 21:10:54 terra TOSDaemon[14561]: gitlab.local/TerraMaster/tos-modules/domain/domain_commom.(*Once).Do(...)
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/gitlab.local/!terra!master/[email protected]/domain/domain_commom/once.go:21
Mar 11 21:10:54 terra TOSDaemon[14561]: gitlab.local/DO-module/domain-module/service/domain.(*Service).ConnectToAdServer(0xc0028edc00, {{0xc00274ce71, 0xd}, {0xc00274ce81, 0xd}, 0x0, 0x1, 0x0, {0x0, 0x0}, ...})
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/gitlab.local/!d!o-module/[email protected]/service/domain/domain_model.go:189 +0x135
Mar 11 21:10:54 terra TOSDaemon[14561]: gitlab.local/DO-module/domain-module/service/domain.(*Service).recoveryConnect(0xc0028edc00)
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/gitlab.local/!d!o-module/[email protected]/service/domain/domain_cron.go:75 +0x2ca
Mar 11 21:10:54 terra TOSDaemon[14561]: gitlab.local/DO-module/domain-module/service/domain.(*Service).AutoUpdate(0xc0028edc00)
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/gitlab.local/!d!o-module/[email protected]/service/domain/domain_cron.go:102 +0x27
Mar 11 21:10:54 terra TOSDaemon[14561]: created by gitlab.local/DO-module/domain-module/controller.(*DomainController).Router in goroutine 1
Mar 11 21:10:54 terra TOSDaemon[14561]:         /home/test/go/pkg/mod/gitlab.local/!d!o-module/[email protected]/controller/DomainController.go:20 +0xcb
Mar 11 21:10:54 terra systemd[1]: TOSDaemon.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 11 21:10:54 terra systemd[1]: TOSDaemon.service: Failed with result 'exit-code'.
Looks very much related to domains in some way to me.

I have again re-tested domain joining from other clients, including Windows, Linux and Mac. All fine. I am also now evaluating TrueNAS and Unraid. Both of these also join the domain with no issues.

Dear tanktarta,

After reviewing the log information you provided, our engineering team has discovered that some parts of the domain service code have been corrupted. In order to expedite the resolution of the issue you are experiencing, we kindly ask you to provide us with your domain account details. This will allow us to quickly locate and resolve the issue.

We have sent you our contact information via private message and look forward to hearing from you.

Best regards

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 13 Mar 2025, 17:46
by TMLila
kai wrote: 13 Mar 2025, 13:11 F2-223 | TOS 6.0.650

3. Fixed the issue that text on some pages was misaligned.

Are you serious? Third update in a row you can't center icons! Add just one CSS property, it's a matter of seconds.

Image

I'm tired of writing about problems with inheritance of rights when moving files...

hi!

Thank you for bringing up the issue regarding CSS property settings. We have already resolved this problem and plan to introduce the fix in the upcoming version.

Additionally, regarding the file permission issue you mentioned during the file moving process, could you please provide more detailed information about the problem you encountered?

When moving or cutting folders, if the files or folders being moved have already been configured with permissions, these permissions will not be lost after they are moved to the new directory. However, if you wish for the moved files to adopt the permissions of the new directory, you will need to manually reconfigure the permissions of these files. Moreover, when copying files or folders to a new directory, they will inherit the permissions of the target directory.

We hope this clarifies the permission configuration issue. If you have any other questions or need further assistance, please feel free to contact us.