TerraMaster Forum

Gremlin wrote: ↑14 Oct 2024, 22:39In fact the original 6.0.500 was, iirc, only available to beta testers.

It needs to be explicitly annonced in topic. It shouldn't done. That's why many people installed 6.0.500 as a release version not beta.

Gremlin wrote: ↑14 Oct 2024, 22:39

DBa wrote: ↑14 Oct 2024, 20:00 This is a stupid game. We - the Beta users - went an extra mile for you, by installing your BETA software on our devices and testing it - a job YOU should actually be doing (this is called Quality Assurance, y'know?). Now you are cutting us off further updates. This is EXACTLY the way to make sure potential beta testers are scared off.

That's your view. Beta testers were not 'cut-off'. In fact the original 6.0.500 was, iirc, only available to beta testers. If you chose not to update beyond 6.0.229 that was your choice. If you were beta testing but maintained 'important' data on your device, that was your choice. In fact, anything related to beta was your choice - you signed up for it. And, if you really want the official release version(s) on your device, there are ways to accomplish that, but it needs a clean install.

I must have missed the 6.0.500 announcement for beta testers. No email, no system notification.

And yes, of course everything related to beta is users choice - it is just that there was no notice about this choice being a dead end.

it is just that there was no notice about this choice being a dead end.

Couldn't agree more and I think I made sufficient noise about that at the time. And yes, the 6.0.500 release did make important announcements. (I was just about to paste them here, but realise you have now seen them.)

There are ways back, but not easy and not insignificant.

Updated today from .507 to .512. It all went well with no major problems.

Just 2 issues that are not .512 specific, but I noticed them on the last few updates, and they have not been fixed yet.

1. The port for the "Allow SSH access with username and password" reverted back to the default setting and I had to change the port to the prior config to allow access via SSH again. This was the same problem on .507 update but not prior versions, as far as I noticed.

2.Over many revisions the "System Info - Resource Monitor - Network I/O" graph timescale is not being presented correctly. See the screenshots below for how it is and also compared to "Disk I/O" that is presented correctly. Not critical but it would be nice to have it work correctly.

Note that I am using a "Bond" IEEE802.3ad on a F4-423 NAS and I am not sure if this is the issue that is causing the time scale to be incorrect. There is no graph for " Today, Yesterday, & Last 7 Days" for the "All" selection and the "Last 30 Days" is very incorrectly displayed.

Hope TM can look into these and fix for the next version.

DBa wrote: ↑14 Oct 2024, 23:48

Please calm down. In fact, the beta version of TOS 6 has gone through multiple updates. Like the initial beta test version, notifications for these updates were only released on the official forum. Unfortunately, as a beta test participant, you missed these updates. However, there's no need to worry. The TOS 6 updates for other users will be gradually rolled out in the next 1 to 2 weeks. Please be patient and wait for them.

I uninstalled php7. I thought it was in the repository. But only php8 is there.
How can I restore it?
I can get them from ubuntu 22.04, that should work

Hello
Bug on 512 :
Every time you change the permissions, even if you have disabled SMB, it reactivates itself.

dodusman58 wrote: ↑16 Oct 2024, 19:57 Hello
Bug on 512 :
Every time you change the permissions, even if you have disabled SMB, it reactivates itself.

Could you be more specific? Permissions via shared folders, permissions via file manager, permissions via applications>smb service? Something else?

I use only NFS, each time I change Permissions via shared folders SMB reactivate itself

dodusman58 wrote: ↑16 Oct 2024, 21:34 I use only NFS, each time I change Permissions via shared folders SMB reactivate itself

Thank you for your feedback. We will verify the situation you mentioned in the lab.