TerraMaster Forum

sergiot wrote: ↑11 Jul 2025, 19:15 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.

I have the same requirements here. And apart from some upgrade nuisances, TerraMaster gives me all I need, performs well, and for an affordable price. I have no plans to run.

Would be nice to have a simple "roll-back" facility for when you find the new update was not quite as good as was thought .......

Gremlin wrote: ↑11 Jul 2025, 20:08 Would be nice to have a simple "roll-back" facility for when you find the new update was not quite as good as was thought .......

We're talking "just" Ubuntu here? Should be possible to boot from a stick that makes an image of the TerramasterUSB and copy the contents of the OSpartition of one of the drives.. And use that to restore the old version. (Of course that doens't work for changes in the filesystem). Or do I see things too simple? (Happens very often I'm afraid)

rvescovi wrote: ↑11 Jul 2025, 15:25

your solution helped me to get access - assign an IP locally on the NAS in the console and then manually run /lib/systemd/systemd-networkd

I would like an official solution to the problem!

s2x3d wrote: ↑11 Jul 2025, 21:22

rvescovi wrote: ↑11 Jul 2025, 15:25

your solution helped me to get access - assign an IP locally on the NAS in the console and then manually run /lib/systemd/systemd-networkd

I would like an official solution to the problem!

Glad to help you, I went more in deep on the issue discovering several services not running (you can check with systemctl command) but also the previous update, if you had a look in the post .694 few users highlight the same network issue without any solution provided.

[/quote]

Glad to help you, I went more in deep on the issue discovering several services not running (you can check with systemctl command) but also the previous update, if you had a look in the post .694 few users highlight the same network issue without any solution provided.
[/quote]
thanks a lot indeed - systemctl shows errors with many network services. but it's not right to run them manually every time or manually refine them for the developers. :(in the end, I may not have enough competence. I wanted more reliable software.

If you find a command line option that works for you, you can set this up as a "scheduled task" Triggered by startup. At least until TM get it figured out.

OttO1916 wrote: ↑11 Jul 2025, 20:52

Gremlin wrote: ↑11 Jul 2025, 20:08 Would be nice to have a simple "roll-back" facility for when you find the new update was not quite as good as was thought .......

We're talking "just" Ubuntu here? Should be possible to boot from a stick that makes an image of the TerramasterUSB and copy the contents of the OSpartition of one of the drives.. And use that to restore the old version. (Of course that doens't work for changes in the filesystem). Or do I see things too simple? (Happens very often I'm afraid)

Not that simple. The USB has very little to do with it since TOS is not installed on it. It should be simple to install an earlier (known good) TOS version but, as you conjecture, hidden changes internally can complicate matters. Recently one version released included a newer kernel version that was barely remarked upon. You are also faced with the dilemma of knowing what is a GOOD version, (seem to be few and far between recently), AND finding an installation package (*.ins) in the support download pages.

The newly added system disk first partition is formatted with EXT2 file system
while all of the older system disks first partition were formatted with EXT4.

Is it supposed to be this way?

Newly added system disk


Older system disk

Hi everyone, сould anyone confirm whether Portainer is working correctly on TOS version *.750 (F4-424)?
When I try to run Portainer, it returns to the main TOS desktop without displaying the authorization window. Restarting the NAS and reinstalling Portainer didn't resolve the problem. Has anyone encountered similar behavior?