My Unraid server suddenly stopped serving files last night after working fine for a long time.  After renaming the plugin directories, I noticed that the tower would appear on the network for about a minute, and then stop.  I could use Putty to telnet into it but would lose connection after about a minute and the same with other ways of trying to connect.

 

So I need some help as to how to proceed.

 

Looking at the log file, this section seemed relevant.  Here's the link to the full log file.

 

Mar 25 13:28:13 Tower kernel: ------------[ cut here ]------------

Mar 25 13:28:13 Tower kernel: WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x10f/0x18e()

Mar 25 13:28:13 Tower kernel: Hardware name: 

Mar 25 13:28:13 Tower kernel: NETDEV WATCHDOG: eth0 (forcedeth): transmit queue 0 timed out

Mar 25 13:28:13 Tower kernel: Modules linked in: md_mod sg k8temp hwmon amd74xx ahci libahci forcedeth sata_nv

Mar 25 13:28:13 Tower kernel: Pid: 0, comm: swapper/0 Not tainted 3.9.6p-unRAID #5

Mar 25 13:28:13 Tower kernel: Call Trace:

Mar 25 13:28:13 Tower kernel:  [<c1029269>] warn_slowpath_common+0x77/0x8e

Mar 25 13:28:13 Tower kernel:  [<c139612e>] ? dev_watchdog+0x10f/0x18e

Mar 25 13:28:13 Tower kernel:  [<c139612e>] ? dev_watchdog+0x10f/0x18e

Mar 25 13:28:13 Tower kernel:  [<c10292fc>] warn_slowpath_fmt+0x2e/0x30

Mar 25 13:28:13 Tower kernel:  [<c139612e>] dev_watchdog+0x10f/0x18e

Mar 25 13:28:13 Tower kernel:  [<c139601f>] ? __netdev_watchdog_up+0x52/0x52

Mar 25 13:28:13 Tower kernel:  [<c1032a2c>] call_timer_fn+0x19/0x70

Mar 25 13:28:13 Tower kernel:  [<c1032bae>] run_timer_softirq+0x12b/0x15d

Mar 25 13:28:13 Tower kernel:  [<c102e99f>] __do_softirq+0x94/0x151

Mar 25 13:28:13 Tower kernel:  [<c102eabc>] irq_exit+0x33/0x6c

Mar 25 13:28:13 Tower kernel:  [<c101c43f>] smp_apic_timer_interrupt+0x72/0x7f

Mar 25 13:28:13 Tower kernel:  [<c1055901>] ? tick_nohz_stop_sched_tick+0x1d9/0x239

Mar 25 13:28:13 Tower kernel:  [<c14032b9>] apic_timer_interrupt+0x2d/0x34

Mar 25 13:28:13 Tower kernel:  [<c100865d>] ? default_idle+0x1c/0x2c

Mar 25 13:28:13 Tower kernel:  [<c100879d>] amd_e400_idle+0xcb/0xd1

Mar 25 13:28:13 Tower kernel:  [<c100880c>] cpu_idle+0x50/0x6f

Mar 25 13:28:13 Tower kernel:  [<c13f6a58>] rest_init+0x58/0x5a

Mar 25 13:28:13 Tower kernel:  [<c1574a0d>] start_kernel+0x2ad/0x2b3

Mar 25 13:28:13 Tower kernel:  [<c15745db>] ? repair_env_string+0x53/0x53

Mar 25 13:28:13 Tower kernel:  [<c15742a3>] i386_start_kernel+0x79/0x7d

Mar 25 13:28:13 Tower kernel: ---[ end trace e55a109fd0b428b8 ]---

It appears the network driver malfunctioned, which explains why you could not connect reliably.  A reboot will fix that, but I can't see a reason as to why it happened.  I would have recommended upgrading to the latest release, but the latest has the same version of forcedeth (Version 0.64).  I would carry on as you have, but watch for this happening again, it could be just a one time fluke.  If it does continue doing this, you may need to add a network card and disable the onboard NIC.

A reboot will fix that, but I can't see a reason as to why it happened.

 

Sorry, I should have said.  This isn't a one time thing.  It is happening every time.  The tower is currently unusable.  It boots up, a minute or two of network connection, then it disconnects.

 

I was hesitant about upgrading until I had an better idea of what was wrong, but I'll try that next.

Upgrading to the (almost) latest version didn't fix it.  I couldn't upgrade to the latest, it wouldn't boot, so I'll have to check into that later.

 

I went and bought a new network card, disabled onboard, and I'm off and running again.  I'll just write it off as the onboard network adapter dying out.