TerraMaster Official Forum

Gamalon wrote:
> TheBoomKing wrote:
> > Was hoping this update would fix the speed issues the last update broke.
> > But nope. No change. Please fix it!!!
>
> INDEED SMB IST STILL UNUSEABLE!
-> Hm with encryption disabled - it works now :/

Hi, since Monday i updated my NAS F5-422 to TOS 5.1.29, hopping it coud get more stable, but now I can´t even map the same folder I had mapped before on my windows 10 22h2 updated fully.

Please, can you check if there is some bug affecting smb protocol sharing ?

Surprise Surprise another update, another thing broken...why do we all still do it to ourselves? Suppose it's the devil you know, I have been threatening to buy another make for the last three years but still haven't guess it's the prospect of the outlay and getting a new machine functioning as you want it to, just can't understand quite why they can't get the software right from what I have read here there are some individuals here that could do a much better job.

Is it possible to downgrade to TOS 5.0.176? This version works well for me.

Another thing I have noticed is that on two of my TVs the main TNAS is showing as media as well as the usual link but when I access the media it shows a lot of films that I have previously lost due to yet another fcuk up by the TNAS but obviously when you try to play them they won't as they are not there it just seems to have kept the index....very strange!

norman0 wrote:
> Is it possible to downgrade to TOS 5.0.176? This version works well for me.
yes i have downgraded to 5.0.176 without loosing files or data...just perform a reset and download the full 5.0.176 package and you will be OK.
just my problem was to clear cache since it had old login and didnt showed menus.

@emperorgr: Thank you. I'll try that.

Can we have a tuto to do downgrade back to 5.1.176 please ?

It was working great. At least really much better than the 5.1.24 and 5.1.29 ?

What could happen if you update from 5.0.176 to 5.1.29?

I was on 5.0.176 and downloaded TOS 5.1.24 and 5.1.29 update packets, when I was going update to 5.1.24 I selected the wrong file and updated directly to 5.1.29.

Looks like its working, maybe slower than usual, but working. What shoul I do, keep the 5.1.29 or do a clean install ?

So, seems like disk space is an issue still.
Feature request, if I start uploading a file to do an update and there's not enough space for it, maybe catch that and throw an error to the ui instead of just sticking at 53%?