High CPU load results in an unreachable NAS TS-253PRO

[paulwi]

Dear all,

I have a TS253PRO and have currently a huge problem and I need help in order to find a solution to get it fixed.
Firmware which is installed is 5.0.0.1891
The Nas has currently the problem that the CPU load is getting higher and higher and after a few days the server is not reachable anymore via UI.
Only SSH can be used. The screenshot below is the situation after 1h24m uptime.
You can see that all cpu cores are very busy but in the list of processes nothing weird to see.

top.jpg

Next information is the last part of dmesg. (Unfortunately the -T option is not supported with this version of dmesg else I had a timestamp)
Here you can see that almost the entire 8GB of RAM is consumed. I really don't know why.

dmesg.jpg

Hope that someone can help me.

Thanks in advance,

Paul

[OneCD]

The Nas has currently the problem that the CPU load is getting higher and higher and after a few days the server is not reachable anymore via UI.
Only SSH can be used. The screenshot below is the situation after 1h24m uptime.
You can see that all cpu cores are very busy but in the list of processes nothing weird to see.

Your load averages look fine, and in-fact they're dropping in that first screenshot.

System load average of 2.0 is quite OK for your quad-core Celeron CPU.

Can you please check (and post) the load averages every few hours? Quickest way to view them is with:

Code: Select all

uptime

[paulwi]

Code: Select all

13:38:46 up  4:18,  load average: 2.76, 2.27, 2.06
Wed Jan 26 13:42:19 GMT 2022
14:55:41 up  4:36,  load average: 4.15, 3.43, 3.02
Wed Jan 26 14:55:41 GMT 2022
15:25:41 up  5:06,  load average: 2.53, 2.60, 2.97
Wed Jan 26 15:25:41 GMT 2022
15:55:41 up  5:36,  load average: 2.17, 2.86, 3.04
Wed Jan 26 15:55:41 GMT 2022
16:35:19 up  6:16,  load average: 1.80, 1.92, 2.09
Wed Jan 26 16:36:11 GMT 2022 

I think you're right.
A load average of 2 is quite normal. But the CPU percentage spread out over the cores remains high while I don't see anything in the list of processes.
But in the meantime something else popped up.
The NAS gave me an error notification:

[App Center] Failed to install Q'center. There is not enough space on the default volume to install this application.

Now I think that my (system)partitions are messed up somehow. Last week I also saw an error about the system partition.

It all starts with the fact that I made something wrong in the virtual switch a few weeks ago.
At that moment everything seems to be fine till I received a new firmware notification. Firmware installed and rebooted. Yes, I received the grand prize. The changed setting in the virtual switch became active and it was not possible anymore to reach the nas at all. To fix this I pressed the reset button for 10 secs to get the default settings back (without harddisks). I think that something went wrong in that period and it becomes quite complex to get the current problem properly fixed.
My partition layout:

Code: Select all

Filesystem                Size      Used Available Use% Mounted on
none                    400.0M    290.7M    109.3M  73% /
devtmpfs                  3.8G      4.0K      3.8G   0% /dev
tmpfs                    64.0M      1.4M     62.6M   2% /tmp
tmpfs                     3.8G    156.0K      3.8G   0% /dev/shm
tmpfs                    16.0M      4.0K     16.0M   0% /share
/dev/sdc5                 7.8M     28.0K      7.8M   0% /mnt/boot_config
tmpfs                    16.0M         0     16.0M   0% /mnt/snapshot/export
/dev/md9                493.5M    184.1M    309.3M  37% /mnt/HDA_ROOT
cgroup_root               3.8G         0      3.8G   0% /sys/fs/cgroup
/dev/mapper/ce_cachedev1
                          3.5T      2.7T    826.2G  77% /share/CE_CACHEDEV1_DATA
/dev/md13               417.0M    402.1M     14.9M  96% /mnt/ext
tmpfs                    32.0M     27.2M      4.8M  85% /samba_third_party
tmpfs                    48.0M     32.0K     48.0M   0% /share/CE_CACHEDEV1_DATA/.samba/lock/msg.lock
df: /mnt/ext/opt/samba/private/msg.sock: Permission denied
tmpfs                    16.0M         0     16.0M   0% /share/NFSv=4
/dev/mapper/ce_cachedev1
                          3.5T      2.7T    826.2G  77% /lib/modules/5.10.60-qnap/container-station
df: /share/CE_CACHEDEV1_DATA/.qpkg/container-station/system-docker/overlay2/1a10722a92f24b2969373e5117d1b9a9b093b9b9cce437b7d7f0063d837f5a6d/merged: Permission denied
tmpfs                   100.0K         0    100.0K   0% /share/CE_CACHEDEV1_DATA/Container/container-station-data/lib/lxd/shmounts
tmpfs                   100.0K         0    100.0K   0% /share/CE_CACHEDEV1_DATA/Container/container-station-data/lib/lxd/devlxd
df: /share/CE_CACHEDEV1_DATA/Container/container-station-data/lib/docker/overlay2/dced5e1247648b54167f0f6d1b2e0029e4e21ddc5e1d6f63ce242c8fbdaa8c14/merged: Permission denied

I think to start to install the nas from scratch again might be the best solution here.

Or do you have another suggestion?

Best regards,

Paul

[dolbyman]

To fix this I pressed the reset button for 10 secs to get the default settings back (without harddisks).

The system is on the disks, pressing the reset button without disks, will do nothing

[paulwi]

It took me a bit of time but I have reinstalled everything again. I think that something was messed up on system level.
Now the Nas works fine again.
We will never know I guess.
Thanks for your advice.