System fails to be useful

CPU, memory, fan, process, services status, system log, tempreture
User avatar
Gianluca
Posts: 4
Joined: 23 Mar 2023, 21:30

System fails to be useful

Post by Gianluca »

It is since TOS 4 that I am experimenting continuously failing in the usability of this hardware. I have a F220 with 2 brand new WD RED 4 TB currently in RAID1. I tried different configurations, a number of backups and reinitializations, different versions of the TOS (currently 5.1) but the NAS works for a few hours and then stop being accessible. Once inaccessible by WEB, once only accessible via VPN, once accessible only by SMB. Now completely inaccessible. I am sick and tired to spend hours on managing a system that should help and not waste my time.
I had a number of chats with the support. They tried several times to understand what goes wrong but the point is always there.
We bought a system for making accessible our files from anywhere but this happens very rarely and never when you need them.
You set plex and plex doesn't see your NAS. You set the NAS as a VPN server and it is inaccessible. You need a file but the FTP server doesn't respond.
Terramaster please tell me what is wrong with you?
User avatar
TWlhq
TerraMaster Team
Posts: 29
Joined: 29 Jun 2022, 18:12

Re: System fails to be useful

Post by TWlhq »

{L_BUTTON_AT}Gianluca

Try booting the machine empty for a while to see if the device is inaccessible and unsearchable, and check if the drive is on the compatibility list. If the boot up is normal, we recommend backing up the data and repairing the file system once, then backing up the data and rebuilding the file system if there is still a problem. If the last b does not work, you can only use professional software to test and repair the hard drive or replace it. rIf plex does not see TNAS, you can edit the media user group to share folder permissions.
User avatar
Gianluca
Posts: 4
Joined: 23 Mar 2023, 21:30

Re: System fails to be useful

Post by Gianluca »

Dear,
thank you for replying.
I am doing this for months. What do you mean by boot empty? If I boot empty (without disks?? the system will request a new installation). I have just installed the latest version of the TOS. The disks are brand new WD RED. Fully compatible. If there is a corrupted filesystem how is possible that the system works for a while and then becomes inaccessible? Why today also the on/off button did not respond properly? I had to shout it down keeping pressing for the 10 secs.
Thank you for your support.
g
User avatar
Gianluca
Posts: 4
Joined: 23 Mar 2023, 21:30

Re: System fails to be useful

Post by Gianluca »

I tried to reinstall TOS. Installation was successfull. 10 minutes later the system is again inaccessible
User avatar
TMnight
TerraMaster Team
Posts: 29
Joined: 30 Sep 2022, 16:40

Re: System fails to be useful

Post by TMnight »

You can try to install the system with a brand new hard drive and check if there will be no access
User avatar
fabdg
Posts: 5
Joined: 05 Apr 2023, 16:24

Re: System fails to be useful

Post by fabdg »

Gianluca wrote: 23 Mar 2023, 21:45 It is since TOS 4 that I am experimenting continuously failing in the usability of this hardware. I have a F220 with 2 brand new WD RED 4 TB currently in RAID1. I tried different configurations, a number of backups and reinitializations, different versions of the TOS (currently 5.1) but the NAS works for a few hours and then stop being accessible. Once inaccessible by WEB, once only accessible via VPN, once accessible only by SMB. Now completely inaccessible. I am sick and tired to spend hours on managing a system that should help and not waste my time.
I had a number of chats with the support. They tried several times to understand what goes wrong but the point is always there.
We bought a system for making accessible our files from anywhere but this happens very rarely and never when you need them.
You set plex and plex doesn't see your NAS. You set the NAS as a VPN server and it is inaccessible. You need a file but the FTP server doesn't respond.
Terramaster please tell me what is wrong with you?

...please see my answer to your other post. I believe this firmware is just not been designed to run on our 'consumer' NAS... The only solution for Terramaster is to completely re-work the firmware to allow to run with their NAS with 1-2 GB of RAM (in my case the it's the F2-210). Until there there's nothing we can do... as the NAS crash with an OUT OF MEMORY message in the kernel logs...
User avatar
norman0
Posts: 4
Joined: 15 Aug 2022, 22:13
Germany

Re: System fails to be useful

Post by norman0 »

If it is a memory issue, you can upgrade the memory of your F2-220 to 4GB.
F2-220 4GB + 2*Seagate IronWolf 4TB
User avatar
fabdg
Posts: 5
Joined: 05 Apr 2023, 16:24

Re: System fails to be useful

Post by fabdg »

Not on the F2-210.

Here's the logs:

[ 1153.329676] lowmem_reserve[]: 0 0 0
[ 1153.333295] DMA: 443*4kB (UMEC) 85*8kB (UMEC) 42*16kB (UMEC) 31*32kB (UMC) 1*64kB (M) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 4180kB
[ 1153.346854] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
[ 1153.355491] 11256 total pagecache pages
[ 1153.359419] 6400 pages in swap cache
[ 1153.363078] Swap cache stats: add 140264, delete 133864, find 11150/14270
[ 1153.370027] Free swap = 1464776kB
[ 1153.373507] Total swap = 1997820kB
[ 1153.376988] 262144 pages RAM
[ 1153.379936] 0 pages HighMem/MovableOnly
[ 1153.383862] 16239 pages reserved
[ 1153.387164] 4096 pages cma reserved
[ 1154.248789] r8169 98016000.gmac eth0: eth0: Rx buffers exhausted
[ 1154.254969] r8169 98016000.gmac eth0: eth0: Rx buffers exhausted

[ 1154.328819] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[ 1154.337741] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
[ 1154.346665] r8169 98016000.gmac eth0: link up
[ 1160.551017] lowmemorykiller: Killing 'smbd' (9191), adj 0,
to free 486524kB on behalf of 'kswapd0' (64) because
cache 5912kB is below limit 6144kB for oom_score_adj 0
Free memory is 1188kB above reserved


The only way to recover the system is the hard reset (plug the cord!); the system is completely unresponsive. All I was doing was to copy a 10Gb files on a samba share. And this happen ALL THE TIME (with transferring files bigger than 1 GB)
User avatar
TMroy
TerraMaster Team
Posts: 2578
Joined: 10 Mar 2020, 14:04
China

Re: System fails to be useful

Post by TMroy »

It seems the memory has been used up. do you have more other processes running?
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
User avatar
fabdg
Posts: 5
Joined: 05 Apr 2023, 16:24

Re: System fails to be useful

Post by fabdg »

TMroy wrote: 09 Apr 2023, 11:41 It seems the memory has been used up. do you have more other processes running?
Nope. All the file services are disabled (apart from SAMBA). I have configured only one user on the system 'Backup' and defined one share 'Backup'.

The crash is easily repeatable:

1) Start the F2-210
2) Copy a file to the samba share that it is bigger than the RAM (in my case, 1 Gbyte)
3) Looking at the top command, you will see that the Samba process will immediately allocate all of the memory and the NAS will become completely unresponsive (see below and also note the Load Average)

Mem: 900760K used, 82860K free, 40K shrd, 1388K buff, 19216K cached
CPU: 1% usr 7% sys 0% nic 12% idle 54% io 0% irq 24% sirq
Load average: 112.76 55.72 21.98 3/357 24139
PID PPID USER STAT VSZ %VSZ %CPU COMMAND
20579 14215 root S 1729m 180% 4% /usr/sbin/smbd -D
1516 1 root S 513m 53% 3% syscontrol /tmp/sys_log 0
4130 1 root D 34476 4% 1% /usr/bin/redis-server *:6379
17575 12840 root R 3272 0% 1% top -d 1

Looking at the output of dmesg, you will see that the OOMKILLER has killed the process Samba as well as the network card is unresponsive.

This means that as soon as any backup is attempted, the NAS will become unresponsive.

Am I and Gianluca (the user above reporting more or less the same issues) the only one experiencing this? It looks to me a clear flawed firmware... that makes this device completely useless...
Locked