FreeNAS crashing when transferring files.

Status
Not open for further replies.
Joined
Sep 6, 2016
Messages
3
Hello,

I'm having a big issue, when i transfer files to my FreeNAS server it ends up disconnecting mid transfer and totally going offline, The computer is still online but i cant ping, ssh, ftp or anything into it.

Here is my specification


Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz
HyperX Fury 16GB
4 * WD Red 3TB
Some random SSD for OS
Gigabyte GA-B85M-DS3H-A S1150 B85 MATX


I was running tail -f /var/log/messages

Here is the output when the server crashed

Code:
Sep  7 02:18:03 Vault afpd[4219]: AFP statistics: 0.06 KB read, 0.06 KB written

Sep  7 02:20:10 Vault afpd[4275]: Login by ChadTaljaardt (AFP3.4)

Sep  7 02:22:32 Vault kernel: Limiting closed port RST response from 273 to 200 packets/sec

Sep  7 02:22:32 Vault kernel: Limiting closed port RST response from 273 to 200 packets/sec

Sep  7 02:25:57 Vault proftpd[4324]: 127.0.0.1 (192.168.2.154[192.168.2.154]) - FTP no transfer timeout, disconnected

Sep  7 02:32:47 Vault proftpd[4731]: 127.0.0.1 (192.168.2.154[192.168.2.154]) - FTP no transfer timeout, disconnected

Sep  7 02:49:53 Vault re0: watchdog timeout

Sep  7 02:49:53 Vault kernel: re0: link state changed to DOWN

Sep  7 02:49:53 Vault kernel: re0: link state changed to DOWN

Sep  7 02:49:54 Vault mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.2.200/re0/1

Sep  7 02:49:54 Vault mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.2.200/re0/1

Sep  7 02:49:54 Vault mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.2.200/re0/1

Sep  7 02:49:55 Vault mDNSResponder: mDNSPlatformSendUDP got error 55 (No buffer space available) sending packet to 224.0.0.251 on interface 192.168.2.200/re0/1

Sep  7 02:49:57 Vault dhclient[973]: send_packet: No buffer space available

Sep  7 02:49:57 Vault devd: Executing '/etc/rc.d/dhclient quietstart re0'

Sep  7 02:49:57 Vault kernel: re0: link state changed to UP

Sep  7 02:49:57 Vault kernel: re0: link state changed to UP

Sep  7 02:50:01 Vault dhclient: New IP Address (re0): 192.168.2.200

Sep  7 02:50:01 Vault dhclient: New Subnet Mask (re0): 255.255.255.0

Sep  7 02:50:01 Vault dhclient: New Broadcast Address (re0): 192.168.2.255

Sep  7 02:50:01 Vault dhclient: New Routers (re0): 192.168.2.1


Here is the FTP Messages when the server died

Code:
Status:      Disconnected from server

Status:      Disconnected from server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Status:      Disconnected from server

Status:      Disconnected from server

Status:      Disconnected from server

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Disconnected from server

Status:      Disconnected from server

Status:      Disconnected from server

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Command: PASV

Error:        Connection timed out after 25 seconds of inactivity

Error:        File transfer failed

Status:      Disconnected from server

Status:      Connecting to 192.168.2.200:21...

Status:      Connection attempt failed with "EHOSTDOWN - Host is down".

Error:        Could not connect to server

Status:      Disconnected from server

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Disconnected from server

Status:      Disconnected from server

Status:      Disconnected from server

Status:      Disconnected from server

Status:      Disconnected from server

Status:      Disconnected from server

Status:      Disconnected from server

Status:      Disconnected from server

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 5 seconds due to previously failed connection attempt...

Status:      Delaying connection for 1 second due to previously failed connection attempt...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Status:      Connecting to 192.168.2.200:21...

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server

Error:        Connection timed out after 25 seconds of inactivity

Error:        Could not connect to server




Here is a ping i was running to the server while the FTP Transfer was in place

Code:
64 bytes from 192.168.2.200: icmp_seq=2598 ttl=64 time=2.246 ms

64 bytes from 192.168.2.200: icmp_seq=2599 ttl=64 time=3.072 ms

64 bytes from 192.168.2.200: icmp_seq=2600 ttl=64 time=4.167 ms

64 bytes from 192.168.2.200: icmp_seq=2601 ttl=64 time=4.579 ms

64 bytes from 192.168.2.200: icmp_seq=2602 ttl=64 time=5.274 ms

64 bytes from 192.168.2.200: icmp_seq=2603 ttl=64 time=5.022 ms

64 bytes from 192.168.2.200: icmp_seq=2604 ttl=64 time=0.200 ms

64 bytes from 192.168.2.200: icmp_seq=2605 ttl=64 time=1.489 ms

64 bytes from 192.168.2.200: icmp_seq=2606 ttl=64 time=2.267 ms

64 bytes from 192.168.2.200: icmp_seq=2607 ttl=64 time=2.430 ms

64 bytes from 192.168.2.200: icmp_seq=2608 ttl=64 time=0.105 ms

64 bytes from 192.168.2.200: icmp_seq=2609 ttl=64 time=2.652 ms

64 bytes from 192.168.2.200: icmp_seq=2610 ttl=64 time=0.338 ms

64 bytes from 192.168.2.200: icmp_seq=2611 ttl=64 time=2.414 ms

64 bytes from 192.168.2.200: icmp_seq=2612 ttl=64 time=3.195 ms

64 bytes from 192.168.2.200: icmp_seq=2613 ttl=64 time=0.246 ms

64 bytes from 192.168.2.200: icmp_seq=2614 ttl=64 time=2.220 ms

64 bytes from 192.168.2.200: icmp_seq=2615 ttl=64 time=0.115 ms

64 bytes from 192.168.2.200: icmp_seq=2616 ttl=64 time=1.265 ms

Request timeout for icmp_seq 2617

Request timeout for icmp_seq 2618

Request timeout for icmp_seq 2619

Request timeout for icmp_seq 2620

Request timeout for icmp_seq 2621

Request timeout for icmp_seq 2622

Request timeout for icmp_seq 2623

Request timeout for icmp_seq 2624

Request timeout for icmp_seq 2625

Request timeout for icmp_seq 2626

Request timeout for icmp_seq 2627



I was running a ping to google at the same time to make sure it wasn't my laptop causing the issue.

I turned off the firewall on my router as well during the transfer.



Here is the TOP command running before the crash

Code:
Chads-MacBook-Pro:~ chadtaljaardt$ 

 4275 root             1   4    0   139M 15128K select  0   0:17   5.08% afpd

 5349 root             1  20    0 70040K 10132K select  2   0:01   1.76% proftpd

 5344 root             1  20    0 65944K  9348K select  2   0:01   1.56% proftpd

 5341 root             1  20    0 70040K 10100K select  2   0:01   1.37% proftpd

 5340 root             1  20    0 65944K  8628K select  2   0:00   1.07% proftpd

 5347 root             1  21    0 65944K  8716K select  1   0:00   0.98% proftpd

 5348 root             1  20    0 65944K  8648K select  0   0:00   0.98% proftpd

 5343 root             1  20    0 65944K  8664K select  1   0:00   0.78% proftpd

 5346 root             1  20    0 65944K  8688K select  1   0:00   0.68% proftpd

 5342 root             1  20    0 65944K  8160K select  1   0:00   0.68% proftpd

 5345 root             1  20    0 65944K  7964K CPU2    2   0:00   0.68% proftpd

 3126 root            12  20    0   235M 19432K nanslp  2   0:03   0.00% collectd

 2879 root             6  20    0   355M   150M select  2   0:02   0.00% python2.7

 2852 root             1  52    0   221M 62860K select  2   0:02   0.00% python2.7

 3917 ChadTaljaardt    1  20    0 26064K  3200K CPU1    1   0:01   0.00% top

 4278 root             1  20    0 52068K 11196K select  3   0:00   0.00% cnid_dbd

 3817 root             1  52    0   161M 49632K ttyin   2   0:00   0.00% python2.7

 3217 root             4  52    0   169M 48332K usem    2   0:00   0.00% python2.7

 2820 root             1  20    0   101M 10820K select  1   0:00   0.00% afpd

 1891 root             1  20    0 30260K 18104K select  3   0:00   0.00% ntpd

 2800 root             2  20    0 32932K  3308K kqread  1   0:00   0.00% netatalk

 1396 root             1  20    0 68920K  8648K kqread  0   0:00   0.00% syslog-ng

 2571 root             1  20    0 30728K  4460K nanslp  1   0:00   0.00% smartd

 3914 ChadTaljaardt    1  20    0 88152K  7496K select  3   0:00   0.00% sshd

 5321 root             1  20    0 65944K  7108K select  0   0:00   0.00% proftpd

 2778 www              1  20    0 34116K  6448K kqread  1   0:00   0.00% nginx

 2079 root             1  20    0 39132K  6480K select  1   0:00   0.00% proftpd

 2594 root             1  31   10 17064K  3572K wait    0   0:00   0.00% sh

 3912 root             1  20    0 88152K  7448K select  3   0:00   0.00% sshd

 4258 root             1  20    0 88152K  7452K select  1   0:00   0.00% sshd

 2821 root             1  20    0 28568K  3104K select  3   0:00   0.00% cnid_metad

 4260 ChadTaljaardt    1  20    0 88152K  7500K select  1   0:00   0.00% sshd

 2796 nobody           1  20    0 17036K  2796K select  2   0:00   0.00% mdnsd

 1810 root             1  52    0 22720K  3960K select  3   0:00   0.00% nfsd

 3755 root             1  20    0 51708K  4808K select  2   0:00   0.00% zfsd

 4264 root             1  20    0 72128K  5984K select  3   0:00   0.00% sudo

 1121 root             1  32    0 13772K  5500K select  0   0:00   0.00% devd

 1403 root             1  20    0 20728K  2176K select  0   0:00   0.00% rpcbind

 3765 root             1  20    0 20740K  2340K nanslp  1   0:00   0.00% cron

 1804 root             1  22    0 18596K  3940K select  2   0:00   0.00% mountd

 4261 ChadTaljaardt    1  20    0 19868K  3576K wait    3   0:00   0.00% bash

 3915 ChadTaljaardt    1  20    0 19868K  3572K wait    3   0:00   0.00% bash

 1811 root             4  52    0 14476K  1964K rpcsvc  3   0:00   0.00% nfsd

 1817 root             1  52    0 20704K  3948K rpcsvc  3   0:00   0.00% rpc.lockd

 1030 _dhcp            1  20    0 14624K  2172K select  3   0:00   0.00% dhclient

  973 root             1  52    0 14624K  2152K select  3   0:00   0.00% dhclient

 2374 root             1  20    0 65444K  6980K select  0   0:00   0.00% sshd

 1814 root             1  20    0   276M  3956K select  2   0:00   0.00% rpc.statd

 4265 root             1  20    0 12332K  1972K kqread  1   0:00   0.00% tail

 3820 root             1  52    0 14488K  2048K ttyin   0   0:00   0.00% getty

 3822 root             1  52    0 14488K  2048K ttyin   2   0:00   0.00% getty

 3824 root             1  52    0 14488K  2048K ttyin   1   0:00   0.00% getty

 3821 root             1  52    0 14488K  2048K ttyin   1   0:00   0.00% getty

 3818 root             1  52    0 14488K  2048K ttyin   1   0:00   0.00% getty

 3819 root             1  52    0 14488K  2048K ttyin   2   0:00   0.00% getty

 3823 root             1  52    0 14488K  2048K ttyin   2   0:00   0.00% getty

 2777 root             1  52    0 34116K  5916K pause   3   0:00   0.00% nginx

 5229 root             1  31   10  8228K  1880K nanslp  1   0:00   0.00% sleep

 1395 root             1  52    0 38416K  3564K wait    2   0:00   0.00% syslog-ng

 3010 messagebus       1  52    0 21260K  2780K select  0   0:00   0.00% dbus-daemon

 3216 root             1  52    0 14460K  2000K sigwai  0   0:00   0.00% daemon




Can anyone help me, i have no idea why its doing this.
 

Robert Trevellyan

Pony Wrangler
Joined
May 16, 2014
Messages
3,778
Have you tried disabling the built-in Realtek NIC and installing an Intel NIC?
 

gpsguy

Active Member
Joined
Jan 22, 2012
Messages
4,472
Start by putting an Intel NIC in it. A Pro/1000 CT costs about $30 USD.

You've got a Realtek NIC. They cause a lot of problems with FreeNAS.
 
Joined
Sep 6, 2016
Messages
3
Start by putting an Intel NIC in it. A Pro/1000 CT costs about $30 USD.

You've got a Realtek NIC. They cause a lot of problems with FreeNAS.
Is it a network issue then?

I dont want to waste money if thats not the issue but i dont mind spending money if it will fix this problem.


Have you tried disabling the built-in Realtek NIC and installing an Intel NIC?
I dont have any Nic's right now :/
 

Robert Trevellyan

Pony Wrangler
Joined
May 16, 2014
Messages
3,778
I dont want to waste money if thats not the issue but i dont mind spending money if it will fix this problem.
We're just pointing out the most obvious deficiency of your hardware. When troubleshooting, you change one thing at a time, starting with the most obvious, and then test to see if the problem is fixed.
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Realtek nic's just don't work very well in freeBSD. The recommended hardware suggests having intel nics.
 

wblock

Documentation Engineer
Joined
Nov 14, 2014
Messages
1,506
Realtek cards are not the greatest, but they should not cause crashes, either. The newer Realtek cards (re driver) are far better than the old ones (rl driver). Of course, the Intel cards are the best.

Offloading of various calculations is a common problem with network cards. Like everything else, the Intel cards generally get that right.
 

Mirfster

Doesn't know what he's talking about
Joined
Oct 2, 2015
Messages
3,215

Sakuru

Guru
Joined
Nov 20, 2015
Messages
527
+1 for Intel NIC.

P.S. I don't think that board supports ECC, and is more of a Desktop, so -2 (on top of the -1 for RealTek). :p
Correct, plus they have a Core i5 which doesn't support ECC either.
I recommend running a memtest to make sure the RAM isn't bad.
 
Joined
Sep 6, 2016
Messages
3
+1 for Intel NIC.

P.S. I don't think that board supports ECC, and is more of a Desktop, so -2 (on top of the -1 for RealTek). :p
Correct, plus they have a Core i5 which doesn't support ECC either.
I recommend running a memtest to make sure the RAM isn't bad.

I never knew ECC was that important when building the server, thats a problem on my part but its too late to change that now :/
 
Status
Not open for further replies.
Top