Readynas 102 unavailable after some hours working

[thatanos]

hello, after using some differents Readynas (Since redaynas duo, to 102-202 nas 104) Now I´m having and issue with a 104 (equipped with 2 WD RED for NAS 6Gb) and firmware 6.9.3

Since 4 or 5 weeks I have and issue, that my nas is not accesible through the net (I used NO IP services and everything is correct on it and at the router) when I restarted it it start working again for 1,5 or 2 days again and fail again.

I have tried to reinstall the firmware and it still failing again. And I can´t do it a fabric restore as I have to move up and down about 4 Tb th the cloud.

Any idea? the nas is working as an FTP service for backup 2 servers working at the cloud, and I´m using wasabi services also. ( I connect to the readynas by acronis FTP utility backup and plesk ftp utility backup, an I have been working like this withpout any problem for almost 1 year till now.)

Thank you in advance.

[StephenB]

Does it fail only on internet connections, or is it failing also on the local LAN?

Also, what firmware are you running?

[thatanos]

I´m using 6.9.3 firmware, as it isn´t accesible via lan, but some times the webpage admin is accesible but not responding for switching off or other options.

[StephenB]

Can you download the log zip file?

[thatanos]

sure, the system logs from registry page isn´t it? looking at the page I can´t anything strange. las time I have to switch it off was like 6 hours ago.

I have it, wich one will you need? as the forum didnt allow me to post it as it a zip file.

[StephenB]

You shouldn't post them publicly as there is info in them that could potentially be used to identify you.   There is a process to get them to mods here:  https://kb.netgear.com/21543/How-do-I-send-all-logs-to-ReadyNAS-Community-moderators  However, I'm not a mod.  Perhaps PM @mdgm-ntgr and ask him if he'd like to take a look.

I suggest checking the ethernet statistics for errors (collisions, errors, dropped packets, etc).  They are in network_settings.log.

Also, open volume.log and scroll down to the === df -h === section, and look at the /dev/md0 line. It's normally about 25% used, and if it gets too full the system will misbehave.  Also, scroll down further to === df -h === and look at the inodes used on /dev/md0.  Usually that will say only 1% of the inodes are used.

You could also browse system.log and kernel.log, looking for any crashes (perhaps related to ftp).

Did this begin right after you upgraded to 6.9.3? 

[thatanos]

sorry bur yesterday I post 2 times but someone delete my post as I have publish part of the logs ( withour any personal info)

I have been working with 6.9.3 since 1 weej after it has been release without any problem till 5/6 weeks ago.

[StephenB]

---

@thatanos wrote:

sorry bur yesterday I post 2 times but someone delete my post 

---

That's not what happened.  The automatic spam filter triggered for some reason, and quarantined your posts.  I just looked, and saw them briefly there, but then they disappeared. 

Can you repost your results?

[thatanos]

sure! i ll do in 2 differents post.

=== df -h ===
Filesystem      Size  Used Avail Use% Mounted on
udev             10M  4.0K   10M   1% /dev
/dev/md0        3.7G  1.5G  2.1G  41% /
tmpfs           249M     0  249M   0% /dev/shm
tmpfs           249M  7.0M  242M   3% /run
tmpfs           125M  1.2M  123M   1% /run/lock
tmpfs           249M     0  249M   0% /sys/fs/cgroup
/dev/md127      5.5T  4.1T  1.4T  75% /data
/dev/md127      5.5T  4.1T  1.4T  75% /home
/dev/md127      5.5T  4.1T  1.4T  75% /apps
tmpfs            50M     0   50M   0% /var/replicate/shm
/dev/md127      5.5T  4.1T  1.4T  75% /var/ftp/Backup
/dev/md127      5.5T  4.1T  1.4T  75% /var/ftp/Media
=== df -i ===
Filesystem      Inodes IUsed   IFree IUse% Mounted on
udev             63085   386   62699    1% /dev
/dev/md0       1048576 15570 1033006    2% /
tmpfs            63535     1   63534    1% /dev/shm
tmpfs            63535   517   63018    1% /run
tmpfs            63535    26   63509    1% /run/lock
tmpfs            63535     9   63526    1% /sys/fs/cgroup
/dev/md127           0     0       0     - /data
/dev/md127           0     0       0     - /home
/dev/md127           0     0       0     - /apps
tmpfs            63535     7   63528    1% /var/replicate/shm
/dev/md127           0     0       0     - /var/ftp/Backup
/dev/md127           0     0       0     - /var/ftp/Media

[thatanos]

LeafNets  Link encap:Ethernet  HWaddr XXX.XXX.XXX.XXX
          inet addr:XXX.XXX.XXX.XXX Bcast:5.255.255.255  Mask:255.0.0.0
          inet6 addr: XXX.XXX.XXX.XXX/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1400  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:140 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:36583 (35.7 KiB)

eth0      Link encap:Ethernet  HWaddr XXX.XXX.XXX.XXX
          inet addr:192.168.1.20  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: XXX.XXX.XXX.XXX/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:2244167 errors:1 dropped:950 overruns:0 frame:0
          TX packets:479232 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:532
          RX bytes:2769797417 (2.5 GiB)  TX bytes:1189982241 (1.1 GiB)
          Interrupt:26

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:156 errors:0 dropped:0 overruns:0 frame:0
          TX packets:156 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:30498 (29.7 KiB)  TX bytes:30498 (29.7 KiB)

zt0       Link encap:Ethernet  HWaddr XXX.XXX.XXX.XXX
          inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.XXX Mask:255.255.0.0
          inet6 addr: XXX.XXX.XXX.XXX/64 Scope:Link
          inet6 addr: XXX.XXX.XXX.XXX/40 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:2800  Metric:1
          RX packets:142 errors:0 dropped:0 overruns:0 frame:0
          TX packets:195 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:35496 (34.6 KiB)  TX bytes:48770 (47.6 KiB)

[thatanos]

they get triggered again by spam filter, could you read it at least?

[StephenB]

You are mainly using the NAS as the backup destination, correct?  What is your ISP connection speed?

---

@thatanos wrote:

=== df -h ===
Filesystem      Size  Used Avail Use% Mounted on
/dev/md0        3.7G  1.5G  2.1G  41% /

---

This value is ok, but is higher than usual.  What apps do you have installed?  Have you installed any packages with ssh?

---

@thatanos wrote:

eth0      Link encap:Ethernet  HWaddr XXX.XXX.XXX.XXX
          RX packets:2244167 errors:1 dropped:950 overruns:0 frame:0

---

Also not horrible, but somewhat higher drop rate than I'd expect, especially when receiving over the internet..

[thatanos]

actually the speed is 600/600  Mbps and yes, it´s used basically to received the backups from the clouds servers via FTP.

I have installed only zerotier one nt app, and directly via the webpage manager

[StephenB]

This began when you installed 6.9.3?  What firmware were you running before then?

[thatanos]

no, I have been using it for some months before getting this errors, I come from 6.9.2.  this problems appears suddenly like 4/6 weeks ago maybe

[StephenB]

Maybe PM @mdgm-ntgr and ask if he'd be willing to look at the logs.

If you aren't using ZeroTier to access the cloud servers, then you might try turning that off.

[thatanos]

I use it to make the backup to a readynas 104 that I have in another office as I hah have problems without it.

O have already sent a pm to him yesterday but I haven’t receive any reply yet. 🙂

[mdgm-ntgr]

Please send me your logs (see the Sending Logs link in my sig)

[thatanos]

I have send last Friday, hope that you can find what is the problem.

Thank you in advance.

[mdgm-ntgr]

Maybe try running a balance.

[thatanos]

I though I have setup it for a monthly balance and desfrag, but it must be delete. I ll start it now, thank you very much.

any other idea after checking the logs?