TOS 6.0.750 (X86) is Released for Update

[spleenrun]

Unable to connect remotely





no detection of the NAS on IP SCANNER

[spleenrun]

Hello, may I ask which version you upgraded from to TOS6.0.750? Are you able to search for your NAS device using the TNAS PC application? It’s possible that the IP address changed after the update. If the issue persists, you can try connecting a monitor via HDMI and send us a photo of the displayed content to help with the analysis. If there are no errors on the current display, you can also try restarting the NAS and recording a video of the output on the monitor with your phone, then send it to our technical support email: [email protected].

Hello,

I performed the update using the automatic tool integrated into the NAS. Before updating to TOS 6.0.750, I was already running the latest available version of TOS.

When I use the TNAS PC application, it tells me that remote access is unavailable.
I also tried using IP Scanner, but it doesn’t detect the NAS on the network at all.

What should I do next?

Best regards,

[TMvalen]

Regarding this issue, we require your configuration details for further analysis:

Enable debug mode, perform the operation once, then submit the generated logs.
Provide your OpenVPN configuration file and certificates after redacting all sensitive information.

Support Notification:
Our technical support team has sent you a remote assistance invitation. Please check your notifications.

To contact our team, please send email to following addresses, remember to replace (at) with @

Technical team: support(at)terra-master.com(for technical support)
Service team: service(at)terra-master.com(for purchasing, return, replacement, RMA service)

[jpeckinp]

I haven't seen it mentioned in the last few releases, but are we OK to reenable SPC?

Also like to add boot times much improved. Up and running in less than 2 minutes. Using M.2 as system disk again. Last time I used M.2 it still took 4 minutes to boot.

[TMvalen]

Hello,To facilitate efficient resolution of this issue, please follow these steps to provide the relevant log files:

Navigate to:
Support and Help → Report Issues → Complete basic information → Download

Email the downloaded files to our support team for technical analysis.

To contact our team, please send email to following addresses. "(at)" = "@"
Technical team: support(at)terra-master.com
Service team: service(at)terra-master.com

[rvescovi]

Hello,To facilitate efficient resolution of this issue, please follow these steps to provide the relevant log files:

Navigate to:
Support and Help → Report Issues → Complete basic information → Download

Email the downloaded files to our support team for technical analysis.

To contact our team, please send email to following addresses. "(at)" = "@"
Technical team: support(at)terra-master.com
Service team: service(at)terra-master.com

Thanks I will do, in the meantime last night after I discovered the error during the boot and within the log:

systemd-networkd.service: Failed to execute /lib/systemd/systemd-networkd: Operation not permitted

I did a workaround opening the main terminal session through HDMI and manually start

/lib/systemd/systemd-networkd

disconnecting HDMI (leaving the terminal session open) the NAS bring back interfaces UI TAB and remote access through tnas.online BUT at the first boot the Network will go down again due that error.

So I need support team to fix and will follow your suggestion

[sergiot]

If this is a beta update only. Why do I get it recommended for update on 6.0.694?
I installed it as I am used to coming from Synology.

[Gremlin]

If this is a beta update only. Why do I get it recommended for update on 6.0.694?
I installed it as I am used to coming from Synology.

CAN be used to update previous Beta release to bring it to Official release status. (Trying to update Beta to (say) version .694 was not a good experience ) Wording of release note could have been better imo.

[OttO1916]

If this is a beta update only. Why do I get it recommended for update on 6.0.694?
I installed it as I am used to coming from Synology.

I used to have the same "mindset".
And learned the hard way that being an early adopter is not the best way to go, unless you have time and effort in abundance.
This time I installed the upgrade on my testbox right away because it could fix some issues. Normally however I try to wait a week or two..

[sergiot]

I fully understand that. Will do updates definitely not automatically. And first have a look into the forum. Maybe I will move to OMV, but I am not sure. I just need SMB, NFS and mediaservice. For Docker and Applications I have a homeserver.