July 3, 201115 yr Running UnRaid 4.7. I am seeing some odd network type errors. I can't tell if they are just timeout errors, or real errors that I should be concerned about. These are the two lines I'm worried about, complete syslog attached. Jul 3 12:05:45 Tower kernel: rpc-srv/tcp: nfsd: got error -104 when sending 140 bytes - shutting down socket (Errors) Jul 3 12:06:07 Tower kernel: RPC: fragment too large: 0x58c1edc4 Jul 3 12:09:39 Tower kernel: rpc-srv/tcp: nfsd: got error -104 when sending 140 bytes - shutting down socket (Errors) sounds like i might need to tweak my network settings? syslog-2011-07-03.txt
July 8, 201114 yr Author still seeing this... today i have this: Jul 8 02:00:19 Tower kernel: RPC: multiple fragments per record not supported Jul 8 02:04:18 Tower kernel: rpc-srv/tcp: nfsd: got error -104 when sending 140 bytes - shutting down socket Jul 8 02:26:30 Tower kernel: rpc-srv/tcp: nfsd: got error -104 when sending 140 bytes - shutting down socket Jul 8 02:27:24 Tower kernel: RPC: fragment too large: 0x7cfb84b6 Jul 8 06:47:47 Tower kernel: nfsd: recvfrom returned errno 104 Jul 8 07:27:14 Tower kernel: Hangcheck: hangcheck value past margin! also a tracert to the unraid machine takes nearly 10x as long as any other client on the network...
July 8, 201114 yr Try running the following: ethtool eth0 And see what output you get back. Hopefully it is inserted at 1000Mb/s with full duplex. Also, can run: ifconfig eth0 Can see if there are errors and such... Also make sure the MTU on this matches the rest of your network. Shawn
July 8, 201114 yr Author ethtool eth0 results in: root@Tower:~# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: d Wake-on: d Current message level: 0x00000007 (7) Link detected: yes ifconfig eth0 results in: root@Tower:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:0c:29:ca:07:9a inet addr:192.168.1.12 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:8361902 errors:0 dropped:0 overruns:0 frame:0 TX packets:5244776 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1646475517 (1.5 GiB) TX bytes:886877244 (845.7 MiB) i don't know much linux - but everything seems on the up and up here ..
July 9, 201114 yr Yep, looks good - course some of us had weird issues with Realtek chipsets... What mobo are you running and what chipset is the NIC? You may want to try and add-on NIC either in the PCI or PCI-E slot, disable onboard and see if that clears it up. What is on the rest of your LAN? Seems like an error when connecting with some other device. Shawn
July 9, 201114 yr Author Yep, looks good - course some of us had weird issues with Realtek chipsets... What mobo are you running and what chipset is the NIC? You may want to try and add-on NIC either in the PCI or PCI-E slot, disable onboard and see if that clears it up. What is on the rest of your LAN? Seems like an error when connecting with some other device. Shawn "it's complicated" ... the nic is an emulated intel e1000 passed over by ESXi (UnRaid is a VM)... one of the machines that was pushing data to UnR had a 10G vNic. I just changed that to a e1000. I'm thinking the 10GigE was pushing too fast to UnR? watching closely
July 9, 201114 yr Ahh... Esx eh? On your own there, but yes, 10GB may have been to much for it.... Shawn
July 10, 201114 yr Author marking as SOLVED - removing the 10GigE adapter from the machine that is sending data to the UnRaid machine helped.
Archived
This topic is now archived and is closed to further replies.