February 8, 201214 yr I built/installed unRaid about 4 months ago and it has been working great. Its a basic system with 3- 2TB drives using the onboard SATA controller. Recently it started to freeze up while transferring files (movies) to and during movie play back. The web interface will not work after the "freeze" but I can still enter console commands. Attached is the syslog after the last freeze up. I ran a memory check yesterday and it passed. Thanks in advance for your help. Bob syslog.txt
February 8, 201214 yr Feb 7 23:48:02 Tower kernel: WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xf8/0x17b() Feb 7 23:48:02 Tower kernel: Hardware name: HP Compaq dx2300 Microtower Feb 7 23:48:02 Tower kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Feb 7 23:48:02 Tower kernel: Modules linked in: md_mod xor ata_piix r8169 i2c_i801 i2c_core [last unloaded: md_mod] Feb 7 23:48:02 Tower kernel: Pid: 0, comm: swapper Not tainted 3.1.1-unRAID #1 Feb 7 23:48:02 Tower kernel: Call Trace: Feb 7 23:48:02 Tower kernel: [<c1028550>] warn_slowpath_common+0x65/0x7a Feb 7 23:48:02 Tower kernel: [<c12a379e>] ? dev_watchdog+0xf8/0x17b Feb 7 23:48:02 Tower kernel: [<c10285c9>] warn_slowpath_fmt+0x26/0x2a Feb 7 23:48:02 Tower kernel: [<c12a379e>] dev_watchdog+0xf8/0x17b Feb 7 23:48:02 Tower kernel: [<c103117e>] run_timer_softirq+0x10a/0x182 Feb 7 23:48:02 Tower kernel: [<c12a36a6>] ? __netdev_watchdog_up+0x52/0x52 Feb 7 23:48:02 Tower kernel: [<c102c9ee>] __do_softirq+0x6b/0xe5 Feb 7 23:48:02 Tower kernel: [<c102c983>] ? irq_enter+0x3c/0x3c Feb 7 23:48:02 Tower kernel: <IRQ> [<c102c841>] ? irq_exit+0x32/0x53 Feb 7 23:48:02 Tower kernel: [<c101590d>] ? smp_apic_timer_interrupt+0x6c/0x7a Feb 7 23:48:02 Tower kernel: [<c130bd0a>] ? apic_timer_interrupt+0x2a/0x30 Feb 7 23:48:02 Tower kernel: [<c1007c7e>] ? mwait_idle+0x4a/0x50 Feb 7 23:48:02 Tower kernel: [<c1001a69>] ? cpu_idle+0x43/0x5a Feb 7 23:48:02 Tower kernel: [<c12fbd40>] ? rest_init+0x58/0x5a Feb 7 23:48:02 Tower kernel: [<c145172d>] ? start_kernel+0x28c/0x291 Feb 7 23:48:02 Tower kernel: [<c14510b0>] ? i386_start_kernel+0xb0/0xb7 Feb 7 23:48:02 Tower kernel: ---[ end trace 52773f7c509fbdec ]--- Feb 7 23:48:03 Tower kernel: r8169 0000:03:00.0: eth0: link up Feb 7 23:48:45 Tower kernel: r8169 0000:03:00.0: eth0: link up Looks like your link is dropping packets. I had a similar kernel panic when my router didn't re-boot properly after a power failure. Also this line is repeated multiple times indicating you are losing connectivity: Feb 7 23:48:45 Tower kernel: r8169 0000:03:00.0: eth0: link up L Post the result of ifconfig eth0 or if you have unMENU go to system info--ethernet. Don't have answer why the network is droppping packets. How do you have your unRAID connected on the home network? Possible bad cable, switch, router, or network card.
February 8, 201214 yr Author Do you have a link on how to install unMenu? The unRaid box is connected directly to the gigabit switch. There is an onboard 100M ethernet port that was disabled and a gigabit card (need to look up make/model) was added. I have just enabled the onboard 100M port and moved the ethernet cable to see if this makes a difference. Thanks
February 8, 201214 yr It may be easier to just telnet into the server, and type ifconfig eth0 Install unMENU http://lime-technology.com/wiki/index.php?title=Configuration_Tutorial#Install_UnMENU telnet http://lime-technology.com/wiki/index.php?title=Telnet#Opening_a_Telnet_session (you'l want to START-RUN then type cmd Telnet window will open then type telnet "IPAddress" where "IPAddress" is your server IP
February 8, 201214 yr Author Below is the result of ht efconfig eth0 command. This is after the server was rebooted from the 'freeze'. Tower login: root Linux 3.1.1-unRAID. root@Tower:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:e0:b3:10:c1:86 inet addr:10.1.0.50 Bcast:10.1.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2783473 errors:0 dropped:0 overruns:0 frame:0 TX packets:1801168 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3902189132 (3.6 GiB) TX bytes:870949563 (830.6 MiB) Interrupt:43 Base address:0xe000
February 8, 201214 yr I would attempt another transfer and see what happens with your new setup, as the RX Packets and TX Packets are reset after a reboot. Look for the bold below (from my syslog when I had the issue) Jan 24 21:20:24 Tower ifconfig[11452]: eth0 Link encap:Ethernet HWaddr 48:5b:39:79:f8:84 Jan 24 21:20:24 Tower ifconfig[11452]: inet addr:192.168.1.108 Bcast:192.168.1.255 Mask:255.255.255.0 Jan 24 21:20:24 Tower ifconfig[11452]: UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Jan 24 21:20:24 Tower ifconfig[11452]: RX packets:623402769 errors:0 dropped:0 overruns:0 frame:0 Jan 24 21:20:24 Tower ifconfig[11452]: TX packets:588838301 errors:0 dropped:828 overruns:0 carrier:0 Jan 24 21:20:24 Tower ifconfig[11452]: collisions:0 txqueuelen:1000 Jan 24 21:20:24 Tower ifconfig[11452]: RX bytes:3173812181 (2.9 GiB) TX bytes:3512700463 (3.2 GiB) Jan 24 21:20:24 Tower ifconfig[11452]: Interrupt:30 Base address:0x8000 Jan 24 12:03:45 Tower apcupsd[20589]: Power is back. UPS running on mains. Jan 24 12:10:28 Tower kernel: ------------[ cut here ]------------ Jan 24 12:10:28 Tower kernel: WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0xff/0x17f() Jan 24 12:10:28 Tower kernel: Hardware name: System Product Name Jan 24 12:10:28 Tower kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Jan 24 12:10:28 Tower kernel: Modules linked in: ntfs md_mod xor atiixp r8169 pata_jmicron jmicron ahci Jan 24 12:10:28 Tower kernel: Pid: 0, comm: swapper Not tainted 2.6.32.9-unRAID #8 Jan 24 12:10:28 Tower kernel: Call Trace: Jan 24 12:10:28 Tower kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 Jan 24 12:10:28 Tower kernel: [<c10244e9>] warn_slowpath_fmt+0x24/0x27 Jan 24 12:10:28 Tower kernel: [<c123b505>] dev_watchdog+0xff/0x17f Jan 24 12:10:28 Tower kernel: [<c1030d4a>] ? insert_work+0x43/0x4b Jan 24 12:10:28 Tower kernel: [<c1031042>] ? __queue_work+0x26/0x2b Jan 24 12:10:28 Tower kernel: [<c1031047>] ? delayed_work_timer_fn+0x0/0x24 Jan 24 12:10:28 Tower kernel: [<c123b406>] ? dev_watchdog+0x0/0x17f Jan 24 12:10:28 Tower kernel: [<c102bb23>] run_timer_softirq+0x105/0x158 Jan 24 12:10:28 Tower kernel: [<c1028261>] __do_softirq+0x84/0xf8 Jan 24 12:10:28 Tower kernel: [<c10282fb>] do_softirq+0x26/0x2b Jan 24 12:10:28 Tower kernel: [<c1028556>] irq_exit+0x29/0x2b Jan 24 12:10:28 Tower kernel: [<c10118f0>] smp_apic_timer_interrupt+0x6f/0x7d Jan 24 12:10:28 Tower kernel: [<c10031f6>] apic_timer_interrupt+0x2a/0x30 Jan 24 12:10:28 Tower kernel: [<c1008160>] ? default_idle+0x2d/0x42 Jan 24 12:10:28 Tower kernel: [<c100837c>] c1e_idle+0xc9/0xce Jan 24 12:10:28 Tower kernel: [<c1001a14>] cpu_idle+0x3a/0x4e Jan 24 12:10:28 Tower kernel: [<c128a8bf>] rest_init+0x53/0x55 Jan 24 12:10:28 Tower kernel: [<c13f580c>] start_kernel+0x27b/0x280 Jan 24 12:10:28 Tower kernel: [<c13f5091>] i386_start_kernel+0x91/0x96 Jan 24 12:10:28 Tower kernel: ---[ end trace 82427fee8825c889 ]--- Jan 24 12:10:28 Tower kernel: r8169: eth0: link up Jan 24 12:11:22 Tower kernel: r8169: eth0: link up Jan 24 12:12:46 Tower last message repeated 2 times Jan 24 12:14:10 Tower last message repeated 2 times Jan 24 12:15:58 Tower last message repeated 2 times Jan 24 12:17:40 Tower last message repeated 2 times Jan 24 12:19:22 Tower last message repeated 2 times Jan 24 12:21:04 Tower last message repeated 2 times Jan 24 12:22:52 Tower last message repeated 2 times Jan 24 12:25:58 Tower last message repeated 2 times Jan 24 12:33:09 Tower kernel: r8169: eth0: link down Jan 24 12:33:10 Tower ifplugd(eth0)[1388]: Link beat lost. Jan 24 12:33:13 Tower kernel: r8169: eth0: link up
February 8, 201214 yr Read your syslog on the way home.. First saw you were running 5beta14 and know the ethernet card is using the Realtek driver.. I am running 4.7, so you can forget unmenu. Second, IIRC there are some issues with that driver in the beta/newer kernels. Search for Realtek in the beta forums. Sent from my SAMSUNG-SGH-I897 using Tapatalk Edit: Found one other user that had the same issue running b14, but looks like the r8169 issues were fixed. Also, you were stable for ~4 months with the same setup? http://lime-technology.com/forum/index.php?topic=16840.msg164351#msg164351
Archived
This topic is now archived and is closed to further replies.