Search found 22 matches

by nale88
31 Mar 2025, 01:20
Forum: Update Notice
Topic: TOS 6.0.650 (X86) is Released for Update
Replies: 83
Views: 17271
Bosnia & Herzegovina

Re: TOS 6.0.650 (X86) is Released for Update

Thx, will work for now, but I would like to use the crontab, because of more flexibility with scripts.
by nale88
31 Mar 2025, 00:16
Forum: Update Notice
Topic: TOS 6.0.650 (X86) is Released for Update
Replies: 83
Views: 17271
Bosnia & Herzegovina

Re: TOS 6.0.650 (X86) is Released for Update

One bug to report also, after the reinstall, my crontab is not persistant.

Everytime I reboot the device, my crontab -e is empty, and I need to reenter the entries.
by nale88
24 Mar 2025, 01:26
Forum: Initialization & Installation
Topic: How to reinstall TOS for your TNAS?
Replies: 195
Views: 342940
Bosnia & Herzegovina

Re: How to reinstall TOS for your TNAS?

Can you try to press Ctrl + Shift + R on the keyboard (if you're using Chrome or similar), to clear the cache? Usually, this helps.
by nale88
23 Mar 2025, 15:10
Forum: Update Notice
Topic: TOS 6.0.650 (X86) is Released for Update
Replies: 83
Views: 17271
Bosnia & Herzegovina

Re: TOS 6.0.650 (X86) is Released for Update

@Lex: Just a quick update, after reinstalling the TOS (since my device was unavailable, I plugged the drives out and turn on it to initialize) and letting the drives sync, everything seems OK. No popping of the smbrichacl for now. It's been almost 12 hours.
by nale88
23 Mar 2025, 03:51
Forum: Update Notice
Topic: TOS 6.0.650 (X86) is Released for Update
Replies: 83
Views: 17271
Bosnia & Herzegovina

Re: TOS 6.0.650 (X86) is Released for Update

Good thing you can access the device. My was spinning for over 50h, I was unable to access it at all.

I'm currently reinstalling the system, after I pulled the plug. Hopefully, this will solve this smbrichacl error...
by nale88
21 Mar 2025, 00:23
Forum: Update Notice
Topic: TOS 6.0.650 (X86) is Released for Update
Replies: 83
Views: 17271
Bosnia & Herzegovina

Re: TOS 6.0.650 (X86) is Released for Update

HI TM support! I am stil having issues with the process hogging the device, no matter what I do, copy the file or whatever. Again, for the past 22 hours my device has been unavailable because the "smbrichacl" processes have spawned due to me connecting the external SSD via the USB. I could...
by nale88
18 Mar 2025, 17:57
Forum: Update Notice
Topic: TOS 6.0.650 (X86) is Released for Update
Replies: 83
Views: 17271
Bosnia & Herzegovina

Re: TOS 6.0.650 (X86) is Released for Update

I have no new containers, other the the ones I've been using for the past 6 months (Memos and Jellyfin). I don't even update them so oftenly, maybe once a month. Nevertheless, yesterday and today the situation looks OK. When I get the chance, I'll reboot the device once again with all containers dis...
by nale88
16 Mar 2025, 16:40
Forum: Update Notice
Topic: TOS 6.0.650 (X86) is Released for Update
Replies: 83
Views: 17271
Bosnia & Herzegovina

Re: TOS 6.0.650 (X86) is Released for Update

Something weird is happening with this version. This morning, upon login to the frontend, all my apps have been disabled - including the Log, Docker Engine, Portainer etc. After enabling them one by one, the `smbrichacl` popped up again, now with 10 processes and running sluggishly. I was logged to ...
by nale88
14 Mar 2025, 21:03
Forum: Update Notice
Topic: TOS 6.0.650 (X86) is Released for Update
Replies: 83
Views: 17271
Bosnia & Herzegovina

Re: TOS 6.0.650 (X86) is Released for Update

Hi TMzethar!
I guess you're right! After 18h this has finished, now just the syslog is using about 15% of CPU, but the overall the system feels OK. I'll reenable the services to see if all will go well!

Thank you!
by nale88
14 Mar 2025, 05:17
Forum: Update Notice
Topic: TOS 6.0.650 (X86) is Released for Update
Replies: 83
Views: 17271
Bosnia & Herzegovina

Re: TOS 6.0.650 (X86) is Released for Update

Hi! I've updated from last 6.0.xxx version to 6.0.650 and my server (F2-423) has been barely usable. Just after reinstall I've had the drives synchronisation (which lasted over a day), and afterward my CPU usage is constantly high - I couldn't even connect to it for about 24h. The main process that ...

Go to advanced search