TerraMaster Forum

Bug Reports, Operation Guides, and Experience Sharing
https://forum.terra-master.com/en/

TOS 6.0.650 (X86) is Released for Update

https://forum.terra-master.com/en/viewtopic.php?t=7674

Page 1 of 9

TOS 6.0.650 (X86) is Released for Update

Posted: 11 Mar 2025, 10:49
by RyanYang
Target Users:
Users currently running TOS 6.0.500 or later versions.
Note: If your TOS version does not meet the requirements, please first check the update conditions for TOS 6.0.530.

Here, we sincerely thank usersliability,FredMutter,jawiler,usersky,WhitePastor,kai,rfbjr,obvious,atmaterra,addx972,EthanBerg97,and others, for their sharing and feedback. It is your support that has enabled us to quickly identify and resolve some issues.

Update Notes
Bugs fixed:
1. Fixed the issue that the virtual disk was not consistently mounted on the same volume.
2. Fixed the issue that the file system compression level might not have been saved after restarting the system.
3. Fixed the issue that text on some pages was misaligned.
4. Fixed the issue that certain features did not provide prompts in some cases.
5. Optimized the fan intelligent control program, effectively reducing hardware temperature.
6. Fixed an issue where some pages still displayed Chinese text in non-Chinese language environments.
7. Updated the kernel version from 6.1.58 to 6.1.120, fixing an issue that caused the system kernel to crash under specific circumstances, and improving system stability.

Important Information:
1.Updating the system theoretically will not affect the data on your hard drives, but for safety, please make sure to back up your data in advance.
2.Before updating, ensure that your primary volume (usually volume1) has at least 3GB of available space. Insufficient storage space may cause the update to fail.
3.After the update, the IP address of your TNAS may change. Please use the TNAS PC desktop client to search for and reconnect to the device.

Update Procedure:
1.Go to TOS > Control Panel > General Settings > System > Update, and click "Check for updates."
2.Follow the prompts to update the system.
3.After the system update is complete, you may need to refresh your browser.
4.The TNAS IP address may change after the update. If you cannot connect to your TNAS using the previous IP address, use the TNAS PC client to search for the new IP address.

Other Software Downloads:
Download TNAS PC 5.2.003 for Windows OS:
https://download3.terra-master.com/Apps ... .2.021.exe
Download TNAS PC 5.1.202 for macOS (x86 and ARM architecture):
https://download3.terra-master.com/Apps ... .1.202.pkg
Download TNAS PC 5.1.202 for macOS (ARM architecture):
https://download3.terra-master.com/Apps ... .1.202.pkg
Download TNAS Mobile 3.3.057 for Android:
https://download2.terra-master.com/TNAS ... .3.057.apk
TNAS Mobile for iOS: Download from the iOS App Store.

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 11 Mar 2025, 10:59
by jpeckinp
I wonder if this was my issue. I reset my system configuration and when it would download bootloader and TOS I couldn't get my system to come back up. I tried a million different things, for some reason this time everything came up and I noticed the TOS was 6.0.650 at first I had to check if that was right cause I thought it was .648. Seen this post and it said 6 minutes ago you updated to 6.0.650.

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 11 Mar 2025, 11:03
by jpeckinp
Found first issue possibly. Clam AV was giving me a 404 error. Uninstalled and installed and now it works again.

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 11 Mar 2025, 11:16
by jpeckinp
Well maybe not. Clam AV will startup but it says the setting operation failed when you try to save. It does save though. I closed out and reopened and they were still set.

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 11 Mar 2025, 11:19
by RyanYang
jpeckinp wrote: ↑11 Mar 2025, 11:03 Found first issue possibly. Clam AV was giving me a 404 error. Uninstalled and installed and now it works again.
Based on the abnormal behavior after reinstalling the system, this issue may be caused by insufficient disk space or applications being installed across multiple volumes. Did you install applications on multiple volumes previously?

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 11 Mar 2025, 11:31
by jpeckinp
RyanYang wrote: ↑11 Mar 2025, 11:19
jpeckinp wrote: ↑11 Mar 2025, 11:03 Found first issue possibly. Clam AV was giving me a 404 error. Uninstalled and installed and now it works again.
Based on the abnormal behavior after reinstalling the system, this issue may be caused by insufficient disk space or applications being installed across multiple volumes. Did you install applications on multiple volumes previously?
No. And I have 30TB of 38TB free. I only have one volume also.

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 11 Mar 2025, 11:48
by RyanYang
jpeckinp wrote: ↑11 Mar 2025, 11:31
Another situation is when the system has just been reinstalled. It will initialize the startup items for all previously installed applications. If the initialization is not yet complete, clicking on an application immediately after entering the system may lead to this issue.

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 11 Mar 2025, 19:13
by rfbjr
Both updated and both have the disk activity now, but my logic right now is both were restarted with the old code. Will see later when I shutdown both after they have been running with 650 for most of the day. Stay tunned.

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 12 Mar 2025, 03:15
by sianderson
updated, did have a slight issue with virtual box following the update that the VM wouldnt not start, but then realised that there was also an update to virtual box, once i had done that then the VM started (had removed it from virtual box so added it back in as a new VM)

a quick google suggests this is a known virtual box issue and it happens whenever a kernel update is done (which 6.0.650 included)

Re: TOS 6.0.650 (X86) is Released for Update

Posted: 12 Mar 2025, 05:30
by tanktarta
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.
All times are UTC+08:00
Page 1 of 9

Powered by phpBB® Forum Software © phpBB Limited