Home

FreeNAS - Bug #1850 - Bug Tracking System

1. see there is a solution by Martin Bailey post 21 but I m not comfortable with fiddling and patching the system had hoped that the freeness or BSD community would have fixed this issue considering how long it s been known This doesn t give me a very good feeling have over 20TB of data on my server it makes me nervous K My system is a Asus Z87 A motherboard and yes it uses Realtek 8111GR gigabit lan controller FreeNAS 9 3 STABLE 201 503200528 Platform Intel R Core TM i5 4670K CPU 3 40GHz Memory 16230MB 06 22 2015 9 10 Files if re ko 351 KB 12 19 2014 Martin Bailey ril bsd drv v188 tgz 80 8 KB 12 19 2014 Martin Bailey 06 22 2015 10 10
2. seem to be having some success with the following suggestion still get watchdog errors occasionally however they no longer as severe as to lead to a failed connection http www thewebernets com 201 1 06 20 freenas re0 watchdog timeout error 14 01 28 2013 09 14 AM owling Replying to comment 9 cflemm EDIT seem to be having some success with the following suggestion 1 still get watchdog errors occasionally however they no longer as severe as to lead to a failed connection 06 22 2015 6 10 hitip www thewebernets com 201 1 06 20 freenas re0 vvatchdog timeout error As stated in the original ticket have also tried disabling Enable autotune and Tuneables but it didn t work 15 01 28 2013 10 39 AM William Grzybowski Long shot but try to disable TSO before the problem happens 1 ifconfig re0 tso 16 01 29 2013 12 27 AM Anonymous For the record we iX have a Gigabyte and now ASRock board that uses this CPU NIC chipset combo and have never seen any watchdog timeout messages while testing the Gigabyte board under NAS load The RTL8111E chip tends to just hang if there are Layer 1 Ethernet issues so check your cabling svvitch etc and ensure you are using quality Cat 6 cables and your svvitch is operating normally 17 04 13 2013 07 10 PM cflemm Replying to comment 10 owling Replying to comment 9 cflemm EDIT seem to be having some success with the following sugge
3. FreeNAS 9 Bug 1850 Realtek 8111F fails at high traffic reO Watchdog Timeout Error 10 21 2012 02 10 PM owling Status Priority Assignee Category 3rd party to resolve Expected Target version Seen in Description Start date Due date Done 0 Estimated time 0 00 hour When using a ASUS C60M1 I motherboard with a Realtek 8111F interface and copy alot of data via NFS looses connection after 20 minutes The console prints re0 Watchdog Timeout Error When start a shell from the console can t ping anything except my loopback interface Before the permanent timeout occurs it looses connection for a short time but continues after 4 seconds When this happens a re0 watchdog timeout is also printed to the console At the short and permanent timeout messages show this var log messages Oct 21 Oct 21 Oct 21 Oct 21 Oct 21 Oct 21 Oct 21 Oct 21 Oct 21 Oct 21 Oct 21 Oct 21 15 39 37 stor kernel 15 39 37 stor kernel 15 39 41 stor kernel 15 43 37 stor kernel 15 43 37 stor kernel 15 43 41 stor kernel 15 43 46 stor kernel 15 43 46 stor kernel 15 43 50 stor kernel 15 45 07 stor kernel 15 45 07 stor kernel 15 45 11 stor kernel re0 re0 re0 re0 re0 re0 re0 re0 re0 re0 re0 re0 watchdog timeout link state changed to DOWN link state changed to UP watchdog timeout link state changed to DOWN link state changed to UP watchdog timeout lin
4. changed from Unscreened to Srd party to resolve Seen in set to Assuming realtek driver still sucks this one is going to be a FreeBSD problem to fix Just not on our roadmap 1121 12 18 2014 09 26 PM Martin Bailey File ril bsd drv v188 tgz added File if re ko added Jordan Hubbard wrote Assuming realtek driver still sucks this one is going to be a FreeBSD problem to fix Just not on our roadmap felt it would be wasteful to buy an Intel NIC when the onboard RTL8111 works flawlessly in other operating systems so found a solution After tweaking every possible setting with nothing resolving the constant watchdog timeout issue realized Realtek publishes its own driver for FreeBSD 9 It definitely looks like some binary firmware code is embedded in the source file but I m glad to report it works flawlessly can finally transfer files with 9KB MTU at 99 network utilization without a single hiccup A better solution would be to compare the registers being set for both the open source and binary FreeBSD drivers to understand how to fix the open source driver but in the meantime here s how to make your Realtek network work Download attached module or alternatively compile driver yourself Setup a FreeNAS jail with FreeBSD ports Dowload the latest source code from Realtek site or see tgz attachment Extract the source files to usr src sys dev re and the Makefile to usr src sys modules re From the latter folder type make
5. 28 0 200 netmask OxffffffOO broadcast 192 128 0 255 media Ethernet autoselect 1000baseT lt full duplex gt status active pciconf Iv grep C 4 re0 re0 pci0 4 0 0 class 0x020000 card 0x85051043 chip 0x816810ec rev 0x09 hdr 0x00 vendor Realtek Semiconductor device Gigabit Ethernet NIC NDIS 6 0 RTL8168 8111 8111c class network subclass ethernet netstat m 258 1407 1665 mbufs in use current cache total 0 404 404 262144 mbuf clusters in use current cache total max 0 384 mbuf clusters out of packet secondary zone in use current cache 0 54 54 131072 4k page size jumbo clusters in use current cache total max 256 818 1074 65536 9k jumbo clusters in use current cache total max 0 0 0 32768 16k jumbo clusters in use current cache total max 2368K 8737K 11106K bytes allocated to network current cache total 0 0 0 requests for mbufs denied mbufs clusters mbuf clusters 0 0 0 requests for jumbo clusters denied 4k 9k 16k 0 0 0 sfbufs in use current peak max 0 requests for sfbufs denied 0 requests for sfbufs delayed 17 requests for I O initiated by sendfile 0 calls to protocol drain routines 5 05 13 2013 11 32 PM Anker also have the same problem with 8 3 1 p2 It happens while extracting files with Winrar or if two processes use the shared drive simultaniously Speeds get slower over time but are fine after reboot NIC is On board Realtek RTL8111E get this output May 14 00 3
6. 6 37 freenas kernel bridge0 Ethernet address 02 29 2f 29 79 00 May 14 00 36 37 freenas kernel epair0a Ethernet address 02 f1 6e 00 0b 0a May 14 00 36 37 freenas kernel epairOb Ethernet address 02 f1 6e 00 0c 0b May 14 00 36 37 freenas kernel epairOa link state changed to UP 06 22 2015 4 10 May 14 00 36 37 freenas kernel epairOb link state changed to UP May 14 00 36 37 freenas kernel epair0a promiscuous mode enabled May 14 00 36 37 freenas kernel re0 promiscuous mode enabled May 14 00 36 37 freenas kernel re0 link state changed to DOWN May 14 00 36 40 freenas kernel re0 link state changed to UP May 14 00 39 31 freenas kernel re0 vvatchdog timeout May 14 00 39 31 freenas kernel re0 link state changed to DOVVN May 14 00 39 34 freenas kernel re0 link state changed to UP May 14 00 40 11 freenas kernel re0 vvatchdog timeout May 14 00 40 11 freenas kernel re0 link state changed to DOVVN May 14 00 40 14 freenas kernel re0 link state changed to UP May 14 00 43 39 freenas kernel re0 vvatchdog timeout May 14 00 43 39 freenas kernel re0 link state changed to DOVVN May 14 00 43 42 freenas kernel re0 link state changed to UP May 14 00 44 14 freenas kernel re0 vvatchdog timeout May 14 00 44 14 freenas kernel re0 link state changed to DOVVN May 14 00 44 17 freenas kernel re0 link state changed to UP May 14 00 44 32 freenas kernel re0 vvatchdog timeout May 14 00 44 32 freenas kernel re0 link state changed to DO
7. Copy the if re ko module file outside the jail Move the if re ko module to your boot kernel folder Add if_re_load YES to your loader config Reboot and confirm you see re0 version 1 88 in the dmesg boot output Enjoy 22 03 14 2015 07 19 PM Tom B Martin Bailey wrote Jordan Hubbard wrote 06 22 2015 8 10 Assuming realtek driver still sucks this one is going to be a FreeBSD problem to fix Just not on our roadmap felt it would be wasteful to buy an Intel NIC when the onboard RTL8111 works flawlessly in other operating systems so I found a solution After tweaking every possible setting with nothing resolving the constant watchdog timeout issue realized Realtek publishes its own driver for FreeBSD 9 It definitely looks like some binary firmware code is embedded in the source file but I m glad to report it works flawlessly can finally transfer files with 9KB MTU at 99 network utilization without a single hiccup A better solution would be to compare the registers being set for both the open source and binary FreeBSD drivers to understand how to fix the open source driver but in the meantime here s how to make your Realtek network work Download attached module or alternatively compile driver yourself Setup a FreeNAS jail with FreeBSD ports Dowload the latest source code from Realtek site or see tgz attachment Extract the source files to usr src sys dev re and the Makefile to usr src sys modules re F
8. VVN May 14 00 44 35 freenas kernel re0 link state changed to UP May 14 00 45 24 freenas kernel re0 vvatchdog timeout May 14 00 45 24 freenas kernel re0 link state changed to DOVVN May 14 00 45 27 freenas kernel re0 link state changed to UP Image http i43 tinypic com 2w4jugh png 6 11 21 2012 01 21 AM Phillip Marshall I m getting the same issue on my ASRock B75 Pro3 which has the Realtek 8111E transferring a bunch of data over AFP Oddly it didn t break a sweat running a 5TiB replication over SSH when first installed it yesterday EDIT Rather than worrying about this just dropped 25 on an Intel NIC as apparently Realtek ones are trash http www newegg com Product Product aspx Item N82E 16833106121 7 11 24 2012 04 03 PM stuom This bug also applies to 8 3 0 RELEASE Tested with CIFS share on high load three clients reading data from share and one client writing Enable autotune is disabled and no Tuneables has been configured 8 11 28 2012 05 21 AM chris3955 am seeing the same issue with my system MB MSI E3501S E45 NIC IRealTekll 8111E This issue is reproduced during large transfers over CIFS protocol 06 22 2015 5 10 9 11 28 2012 07 28 AM Vadim Built in driver for realtek 8 3 0 works correctly My problem was due to the router which blocked a virtual machine 10 12 26 2012 09 26 PM kingcharles I am also using a ASUS 60 1 as the original bug
9. g any attention to re0 and FreeBSD 8 3 You might have better luck with FreeNAS 9 X 4 06 17 2013 08 02 AM Greyproc I ve been experiencing this also Board Asus 60 1 1 Realtek 8111E Something which might be worth noting is one of the first things did when installing FreeNAS was to set mtu 9000 I m going to remove that and see if it helps as well as any features 1 don t think need such as WOL_MAGIC and try the above suggested tso Regarding mtu though the Realtek specification explicitly states it can handle it maybe BSD s driver isn t doing something correctly haven t noticed any pattern I ve only been using CIFS turned off NFS FTP etc and was only accessing with one system if that helps narrow it down However was doing large copy operations so heavy load 06 22 2015 3 10 System information Build FreeNAS 8 3 1 RELEASE p2 x64 r12686 b770da6_dirty Platform AMD C 60 APU with Radeon tm HD Graphics Memory 8126MB dmesg grep re0 re0 lt RealTek 8168 8111 B C CP D DP E F PCle Gigabit Ethernet gt port 0xd000 0xd0ff mem 0xfe004000 0xfe004fff Oxfe000000 0xfe009fff irq 17 at device 0 0 on pci4 re0 Using 1 MSI X message re0 Chip rev 0x48000000 re0 MAC rev 0x00000000 ifconfig re0 flags 8843 lt UP BROADCAST RUNNING SIMPLEX MULTICAST gt metric mtu 9000 options 2098 lt VLAN_MTU VLAN_HWTAGGING VLAN_HWCSUM WOL_MAGIC gt ether 30 85 a9 3e 10 c7 inet 192 1
10. k state changed to DOWN link state changed to UP watchdog timeout link state changed to DOWN link state changed to UP This is what happens with the connection a few times before it becomes permanently lost 64 bytes from 192 168 1 2 64 bytes from 192 168 1 2 64 bytes from 192 168 1 2 64 bytes from 192 168 1 2 64 bytes from 192 168 1 2 64 bytes from 192 168 1 2 64 bytes from 192 168 1 2 Eventually it looses connection 06 22 2015 icmp reg 1536 ttl 64 time 0 118 ms icmp reg 1537 ttl 64 time 7998 ms icmp reg 1538 ttl 64 time 6989 ms icmp reg 1539 ttl 64 time 5989 ms icmp req 1540 ttl 64 time 4989 ms icmp reg 1544 ttl 64 time 989 ms icmp reg 1545 ttl 64 time 0 249 ms 1 10 64 bytes from 192 168 1 2 icmp_req 2144 ttl 64 time 0 121 ms From 192 168 1 92 icmp seg 2235 Destination Host Unreachable ifconfig re0 down ifconfig re0 up has no effect tcpdump capture 0 packets on re0 after it looses connection When reboot the connection is restored have Enable autotune off in my configuration and have not added any Tuneables have recreated this 4 times History 1 07 05 2013 03 55 PM mjboerma upgraded to FreeNAS 9 x and am still having issues under heavy load Also using Asus 60 1 1 Realtek 8111 The first couple of times when the re0 watchdog message appears network drops but it recovers Eventually it doesn t recover and it requires a reboot o
11. o Ltd device RTL8111 8168B PCI Express Gigabit Ethernet controller class network subclass ethernet netstat m 259 1031 1290 mbufs in use current cache total 257 523 780 262144 mbuf clusters in use current cache total max 257 511 mbuf clusters out of packet secondary zone in use current cache 0 237 237 131072 4k page size jumbo clusters in use current cache total max 0 0 0 65536 9k jumbo clusters in use current cache total max 0 0 0 32768 16k jumbo clusters in use current cache total max 578K 2251K 2830K bytes allocated to network current cache total 0 0 0 requests for mbufs denied mbufs clusters mbuf clusters 0 0 0 requests for mbufs delayed mbufs clusters mbuf clusters 0 0 0 requests for jumbo clusters delayed 4k 9k 16k 0 0 0 requests for jumbo clusters denied 4k 9k 16k 0 0 0 sfbufs in use current peak max 0 requests for sfbufs denied 0 requests for sfbufs delayed 97 requests for I O initiated by sendfile 0 calls to protocol drain routines 2 06 30 2013 07 49 AM Greyproc looked for a release of FreeNAS 9 x but all see is an alpha version with a big warning about how it s not for production use I m using my FreeNAS for production use do understand correctly that no one cares about a release that s barely been out 3 months at this point Is there a significantly improved version of the re driver in 9 x 3 06 17 2013 10 59 AM William Grzybowski Nobody is givin
12. rdered a Intel Gigabit CT PCI E Network Adapter EXPI9301CTBLK to see if that fixes the problem re0 watchdog timeout re0 link state changed to DOWN re0 link state changed to UP Build FreeNAS 9 1 0 BETA e5ef238 x64 Platform AMD C 60 APU with Radeon tm HD Graphics Memory 7767 ifconfig re0 flags 8843 lt UP BROADCAST RUNNING SIMPLEX MULTICAST gt metric mtu 1500 options 8209b lt RXCSUM TXCSUM VLAN_MTU VLAN_HWTAGGING VLAN_HWCSUM WOL_MAGIC LINKSTATE gt ether 60 a4 4c 3f db 68 inet 192 168 37 103 netmask Oxffffff00 broadcast 192 168 37 255 nd6 options 29 lt PERFORMNUD IFDISABLED AUTO_LINKLOCAL gt media Ethernet autoselect 1000baseT lt full duplex gt status active ipfwO flags 8801 lt UP SIMPLEX MULTICAST gt metric O mtu 65536 nd6 options 29 lt PERFORMNUD IFDISABLED AUTO_LINKLOCAL gt 100 flags 8049 lt UP LOOPBACK RUNNING MULTICAST gt metric mtu 16384 options 600003 lt RXCSUM TXCSUM RXCSUM_IPV6 TXCSUM_IPV6 gt inet6 1 prefixlen 128 inet6 fe80 196lo0 prefixlen 64 scopeid inet 127 0 0 1 netmask Oxff000000 nd6 options 21 lt PERFORMNUD AUTO_LINKLOCAL gt pciconf lv grep C 4 re0 none2 pci0 1 0 0 class 0x028000 card 0x84b61043 chip 0x817810ec rev 0x01 hdr 0x00 vendor Realtek Semiconductor Co Ltd device RTL8188CE 802 11b g n WiFi Adapter class network 06 22 2015 2 10 re0 pci0 4 0 0 class 0x020000 card 0x85051043 chip 0x816810ec rev 0x09 hdr 0x00 vendor Realtek Semiconductor C
13. report and can also reproduce this just by copying large files with NFS The C60M1 only has one expansion slot which is used for a storage board in my setup so adding another NIC is not possible for me Using 8 3 0 Release 11 01 06 2013 01 23 PM Moritz do have the exact same error with the same hardware and same freenas release It also occurs whilst having high load Writing to the RaidZ1 array via a CFS share roughly 37 mb s with simultanious streaming of SD Video materials also do not like the idea of putting another NIC into the one expansion slot as might want to put another SATA controller there in the future Are there any fixes to be hoped for with future relases of FreeNas or is this a general problem with the bad onboard NIC of the C60M1 12 01 26 2013 01 41 PM inaki miz Hi everyone same problem using an ASUS C60M1 I board only have FTP enabled for file transfers and MiniDLNA for streaming media If I m uploading or downloading big files from the NAS get re0 watchdog timeout and MiniDLNA stops Currently using FreNAS 8 3 0 P1 x64 13 01 27 2013 10 46 PM cflemm Same problem here with MB Biostar A681 350 Deluxe CPU AMD Fusion 350D NIC On board Realtek 8111F Under heavy load get intermittent and increasing amounts of re0 watchdog timeout errors until the connection fails altogether Hard reboot of server required to get the NIC working again EDIT
14. rom the latter folder type make Copy the if re ko module file outside the jail Move the if re ko module to your boot kernel folder Add if_re_load YES to your loader config Reboot and confirm you see re0 version 1 88 in the dmesg boot output Enjoy Old bug surprised to find it s still causing issues in the 9 3x builds Driver issue Not a bug Found 1 was getting the same errors when pushing through large files via ftp and wget between two FreeNAS Servers Martin Thanks for your information using the driver you provided worked and has actually made the interface far more responsive than it was in the past 23 04 12 2015 07 35 PM Kamal Soor too am having this problem since building my server about 6 months ago I m relatively new to FreeNas so I m not sure how to save a log to submit sorry access my FreeNas server via a Mac and use Apple AFP shares Use the Freenas server mainly to store files and to run the Plex server I ve had failures if try to copy files from one volume to another via the mac drag to copy although no problems using a unix copy when log on using terminal and ssh I m not sure but think also have had the freenas network link go down when I ve tried to copy over very large amount of data sometime it works and other times have issues Just a few minutes ago tried to copy two streams at the same time and got a failure and had to reboot my freeNas server
15. stion 1 still get watchdog errors occasionally however they no longer as severe as to lead to a failed connection http www thewebernets com 201 1 06 20 freenas re0 watchdog timeout error As stated in the original ticket have also tried disabling Enable autotune and Tuneables but it didn t work My issue is still there not solved Very noticeable when under traffic from more than 1 source can copy files to my freeness server at 7OMB s and never get any timeout errors but if somebody else is trying to access the server simultaneously the timeout errors begin and both connections are interrupted 18 04 20 2013 02 32 PM Djef Same here with 8 3 1 p2 Many watchdog error the link goes down and goes up many time Motherboard C60M1 i 19 09 03 2013 11 49 AM Antonio Bugan owling wrote When using a ASUS C60M1 motherboard with a Realtek 8111F interface and copy alot of data via NFS looses connection after 20 minutes The console prints 06 22 2015 7 10 Have the same Issue with the ASUS C60M1 I GB 6 WD Red 3TB System Information Hostname FreeNas local Build FreeNAS 8 3 1 RELEASE p2 x64 r12686 b770da6 dirty Platform AMD C 60 APU vvith Radeon tm HD Graphics Memory 7773MB System Time Tue Sep 03 13 39 34 CEST 2013 Uptime 1 39PM up 20 mins 0 users Load Average 0 82 0 87 0 76 Should 1 Try with an other NIC 20 01 28 2014 09 16 PM Jordan Hubbard Status

FreeNAS - Bug #1850 - Bug Tracking System

Contents

Download Pdf Manuals

Related Search

Related Contents