[Help] 100% load after an hour F4-223

[impaladb]

My F4-223 goes to 100% load after running for an hour since I updated to ver 6.0.694-00165. It had been running fine on the version I installed when the unit was put into service in March. I don't use any docker, photo or media server apps on it. The only app installed now is ClamAV which I installed when the issue started. Media indexing is not being used. Only used as a basic file server for my home network. When I log in I can finally get to the resources and processes. The process using the most "resources" is MD0_raid5 which is using average of 3%. It finally stops responding completely. I have to pull the power.

Multiple reboots have not fixed the issue. All drives are green and no issues found when looking at the drive logs. The only scheduled items are rsync backups which are once a week and the backups finish successfully.

F4-223 and the OS is running on a M.2 ssd.

I'd rather not have to wipe the system and rebuild.

Thanks.

[MikeZhang]

Sorry for the inconvenience, please generate system log and send to our engineer to check for you support at terra-master.com

[TMjack]

Regarding the issue of the F4-223 product's load continuously rising to 100% after running for a period of time, it is recommended to temporarily disable the ClamAV application for testing to verify whether this phenomenon is related to ClamAV.

[impaladb]

Regarding the issue of the F4-223 product's load continuously rising to 100% after running for a period of time, it is recommended to temporarily disable the ClamAV application for testing to verify whether this phenomenon is related to ClamAV.

Thanks. I had the issue before I installed ClamAV. I installed it to see if there were any signs of virus, the results were no infected files. I will uninstall it anyway and see if there is a change.

At this point the system is un-usable so when I find time I will probably have to wipe and restore from a configuration save.

[impaladb]

I just read a post from user "mrslother"with the exact same issue. In their case, hypercache was an issue where the m.2 drive was benchmarking unrealistically slow. I am going to follow their process and see what my results are.

[impaladb]

Followup: hypercache issue caused file system corruption. I tried multiple times via ssh to run a repair. Eventually had to re-build the server and restore the files from my weekly backup. System just finished sync on the volume and now I have Duple running a complete backup as well as configuration backup.