TOS 6.0.650 (X86) is Released for Update

[TMroy]

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.

This part has not been changed from TOS 5.

[nale88]

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 couldn't even acces the files and after few moments my device's front end is unavailable. SSH doesn't work, all background processes stop (I have a CRON script to turn off one device outside - even that stopped).

Can you tell me has anybody else reported these issues? Do you have any suggestion? Is the system reinstall only option, or anything else?

[dhfh522]

I've noticed replacements for failed drives are not marked as system drives as the originals are. The partition tables look correct, but I assume the system files are not being restored on these replacement drives when the raid resyncs on the new disk.

[TMzethar]

Unfortunately, yes.
If you need to designate another partition as the system drive, you can contact us for remote assistance or we can provide the corresponding instructions based on your storage configuration.
We will discuss adding customizability for the system drive in future versions.

[sianderson]

Unfortunately, yes.
If you need to designate another partition as the system drive, you can contact us for remote assistance or we can provide the corresponding instructions based on your storage configuration.
We will discuss adding customizability for the system drive in future versions.

just so i understand, what you are saying is in a 2 bay system, if one drive fails you replace it and it resyncs = OK as you still have one system partition
then if after some time the other drive fails, you replace it the nas drive no longer works?

or is it a bit simpler that in a 2 bay system, only one drive out of the two is a system drive, so if that ONE drive fails then the unit then becomes unusable as there would be no system partitions if you are unlucky to have had a fault with the system partition drive?

this seems crazy to me if this is what i understand and surely goes against the whole idea of a raid nas system? where you should be free to replace any drives and the system resyncs and carries on working from the healthy hard drive

[Lex]

/usr/bin/smbrichacl freezes system.
It`s create many process and it use all available memory.
I try check memory use. Run "free" command and it run 57 second...

Code: Select all

# time free -h
               total        used        free      shared  buff/cache   available
Mem:            31Gi        30Gi       240Mi       729Mi       917Mi        61Mi
Swap:          1.9Gi       1.9Gi          0B

real	0m57.771s
user	0m0.003s
sys	0m0.049s

[nale88]

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...

[nale88]

@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.

[Lex]

@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.

it's been going on for two days.
And it shouldn't freeze the system

[TMzethar]

Regarding the issue of high resource usage by the smbrichacl process, we will fix it in a future TOS version. If you are experiencing this problem, you can contact the technical support team for remote assistance or to obtain a temporary solution.