TerraMaster Forum

nale88 wrote: ↑16 Mar 2025, 16:40 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 frontend maybe some 10 mins before that via phone, and all was OK.

EDIT: Now I have 36 `smbrichacl` active...

When you enable Docker Engine, if you deactivate all your containers, will smbrichacl still be running? This looks like some program is modifying the inherited permissions of a directory or file.

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 disabled and once with all enabled.

The thing is, once I hit certain number of the smbrichacl, all my connection to the device is off. I cannot reach the frontend (503 error), the SSH is off and shared folders are all off. And the HDD keep grinding, the fan even hits maximum ever so often.

magnus4ever wrote: ↑17 Mar 2025, 21:02 I'm experiencing some odd behaviour as well:

I,ve updated two days ago and everything was running as before until today morning my F4-424 startet disc write activity (not read, just write) in parallel with constant network activity. I have no idea whats causing this, I even deinstalled every single app that i had on the NAS, but no avail.

Update:
so it turns out that disk activity is actually related to Web interface access. As long as i'm logged in and using the web interface, I see a lot of HDD activity. As soon as I log off, drives go to sleep after the set amount of time.

This was 100% not the case before the update as TOS was deliberately installed on SSD to prevent this from happening.
TOS still shows that SSD1 is the only system disk, but i can't shake the feeling that at least something from the update is causing constant access to the HDDs.

magnus4ever wrote: ↑18 Mar 2025, 18:36

What you describe has, I believe, really been the case for some time. On my F2-424 I have system on 2xnvme. When I log in (after device has been sleeping) there is a distinct "wake up" pause before the web interface comes alive. I have noisy HDD (old) and there is characteristic 'clattering' from the drives BEFORE the web interface comes alive. My apps are installed on volume 1 on nvme as well so, logically, there is nothing for the HDD to "do" at that point. However, TOS does appear to demand HDD are "alive and kicking" in order to do basic stuff.

Can't confirm that for me, i could comfortably do stuff on the NAS (change settings, install apps) with the drives being completely spun down. They would only wake when deliberately accessing the file structure via SMB or the integrated file explorer.

magnus4ever wrote: ↑18 Mar 2025, 18:36

When the disk is running frequently, you can use the `iotop` tool with the `iotop -o` command to collect information about which processes are occupying disk read/write operations. Additionally, you can gather a system log and send it to our support email. Thank you very much!

Gremlin wrote: ↑18 Mar 2025, 18:46

magnus4ever wrote: ↑18 Mar 2025, 18:36

What you describe has, I believe, really been the case for some time. On my F2-424 I have system on 2xnvme. When I log in (after device has been sleeping) there is a distinct "wake up" pause before the web interface comes alive. I have noisy HDD (old) and there is characteristic 'clattering' from the drives BEFORE the web interface comes alive. My apps are installed on volume 1 on nvme as well so, logically, there is nothing for the HDD to "do" at that point. However, TOS does appear to demand HDD are "alive and kicking" in order to do basic stuff.

When a system is accessed, not only do the connections between the storage pool and volumes need to be refreshed, but all application information must also be reloaded. Otherwise, even if you log into the system, you will hardly find any usable information. You should be aware that your applications are installed on the volumes, which is why your hard drive wakes up.

TMroy wrote: ↑19 Mar 2025, 13:18

I do understand what you are saying and have no issue with it particularly. But why, in this case being discussed, would the user NOT hear any HDD activity, as users are stating it was not the case previously. Something has changed??

Gremlin wrote: ↑19 Mar 2025, 18:11

I did not see the similar report, did I misunderstand any post?

ColaChen wrote: ↑19 Mar 2025, 00:36

magnus4ever wrote: ↑18 Mar 2025, 18:36

When the disk is running frequently, you can use the `iotop` tool with the `iotop -o` command to collect information about which processes are occupying disk read/write operations. Additionally, you can gather a system log and send it to our support email. Thank you very much!

Tried this , terminal says "command not found"