Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

unresponsive over the network

mr-hexen
in General Support (V5 and Older)

Featured Replies

i tried to start a movie and it timed out. telnet wouldnt work, no pings returned either.

 

was able to log in to the console and save the syslog, here is the snippet that is relevant to the error.

 

 

 

May 18 11:20:02 Tower kernel: ------------[ cut here ]------------
May 18 11:20:02 Tower kernel: WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0xff/0x17f()
May 18 11:20:02 Tower kernel: Hardware name: P35-DS3R
May 18 11:20:02 Tower kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
May 18 11:20:02 Tower kernel: Modules linked in: md_mod xor i2c_i801 i2c_core r8169 pata_jmicron jmicron ahci
May 18 11:20:02 Tower kernel: Pid: 0, comm: swapper Not tainted 2.6.32.9-unRAID #8
May 18 11:20:02 Tower kernel: Call Trace:
May 18 11:20:02 Tower kernel:  [<c102449e>] warn_slowpath_common+0x60/0x77
May 18 11:20:02 Tower kernel:  [<c10244e9>] warn_slowpath_fmt+0x24/0x27
May 18 11:20:02 Tower kernel:  [<c123b505>] dev_watchdog+0xff/0x17f
May 18 11:20:02 Tower kernel:  [<c1037139>] ? sched_clock_cpu+0x136/0x14a
May 18 11:20:02 Tower kernel:  [<c123b406>] ? dev_watchdog+0x0/0x17f
May 18 11:20:02 Tower kernel:  [<c102bb23>] run_timer_softirq+0x105/0x158
May 18 11:20:02 Tower kernel:  [<c1028261>] __do_softirq+0x84/0xf8
May 18 11:20:02 Tower kernel:  [<c10282fb>] do_softirq+0x26/0x2b
May 18 11:20:02 Tower kernel:  [<c1028556>] irq_exit+0x29/0x2b
May 18 11:20:02 Tower kernel:  [<c10118f0>] smp_apic_timer_interrupt+0x6f/0x7d
May 18 11:20:02 Tower kernel:  [<c10031f6>] apic_timer_interrupt+0x2a/0x30
May 18 11:20:02 Tower kernel:  [<c10085f9>] ? mwait_idle+0x4c/0x52
May 18 11:20:02 Tower kernel:  [<c1001a14>] cpu_idle+0x3a/0x4e
May 18 11:20:02 Tower kernel:  [<c128a8bf>] rest_init+0x53/0x55
May 18 11:20:02 Tower kernel:  [<c13f580c>] start_kernel+0x27b/0x280
May 18 11:20:02 Tower kernel:  [<c13f5091>] i386_start_kernel+0x91/0x96
May 18 11:20:02 Tower kernel: ---[ end trace dae207a9e59adbec ]---
May 18 11:20:05 Tower kernel: r8169: eth0: link up
May 18 11:22:41 Tower kernel: r8169: eth0: link up
May 18 11:24:59 Tower kernel: r8169: eth0: link up
May 18 11:27:23 Tower kernel: r8169: eth0: link up
May 18 11:30:30 Tower kernel: r8169: eth0: link up
May 18 11:32:54 Tower kernel: r8169: eth0: link up
May 18 11:35:30 Tower kernel: r8169: eth0: link up
May 18 11:38:25 Tower kernel: r8169: eth0: link up
May 18 11:40:37 Tower kernel: r8169: eth0: link up
May 18 11:43:43 Tower kernel: r8169: eth0: link up
May 18 11:46:02 Tower kernel: r8169: eth0: link up
May 18 11:48:02 Tower kernel: r8169: eth0: link up
May 18 11:51:08 Tower kernel: r8169: eth0: link up
May 18 11:53:57 Tower kernel: r8169: eth0: link up
May 18 11:57:03 Tower kernel: r8169: eth0: link up
May 18 12:00:22 Tower kernel: r8169: eth0: link up
May 18 12:02:40 Tower kernel: r8169: eth0: link up
May 18 12:06:16 Tower kernel: r8169: eth0: link up
May 18 12:09:23 Tower kernel: r8169: eth0: link up
May 18 12:12:11 Tower kernel: r8169: eth0: link up
May 18 12:15:59 Tower kernel: r8169: eth0: link up
May 18 12:20:42 Tower kernel: r8169: eth0: link up
May 18 12:24:06 Tower kernel: r8169: eth0: link up
May 18 12:27:25 Tower kernel: r8169: eth0: link up
May 18 12:30:55 Tower kernel: r8169: eth0: link up
May 18 12:33:20 Tower kernel: r8169: eth0: link up
May 18 12:36:32 Tower kernel: r8169: eth0: link up
May 18 12:39:56 Tower kernel: r8169: eth0: link up
May 18 12:44:03 Tower kernel: r8169: eth0: link up
May 18 12:47:21 Tower kernel: r8169: eth0: link up
May 18 12:51:40 Tower kernel: r8169: eth0: link up

 

can anyone tell me what happened, as far as i can see the network card had an error.

  • Quote

    Attach the entire syslog. zip if needed. Also what MB or NIC?

  • Quote
    • Author

    motherboard is gigabyte P35-DS3R rev 2.0 NIC is onboard realtek 8111B.

     

    server has been online for 6+ months and i never have seen this error before.

  • Quote
    • 2 weeks later...
    • Author

    this just happened twice yesterday again.

     

    after months of smooth running, nothing has changed.

     

    any idea's?

  • Quote

    I'm not sure if this is related to your original problem or not but I did notice this while scanning your syslog:

     

    May 18 12:56:31 Tower ifconfig[6039]: eth0      Link encap:Ethernet  HWaddr 00:1a:4d:57:90:eb 

    May 18 12:56:31 Tower ifconfig[6039]:          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0

    May 18 12:56:31 Tower ifconfig[6039]:          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

    May 18 12:56:31 Tower ifconfig[6039]:          RX packets:197765703 errors:0 dropped:0 overruns:0 frame:0

    May 18 12:56:31 Tower ifconfig[6039]:          TX packets:234183357 errors:0 dropped:1472 overruns:0 carrier:0

    May 18 12:56:31 Tower ifconfig[6039]:          collisions:0 txqueuelen:1000

    May 18 12:56:31 Tower ifconfig[6039]:          RX bytes:1823215203 (1.6 GiB)  TX bytes:1789899069 (1.6 GiB)

    May 18 12:56:31 Tower ifconfig[6039]:          Interrupt:29 Base address:0xe000

     

    Edit: Also probably unrelated but have you noticed all the USB warnings in your syslog? Most are pretty old but I'm guessing they're related to the driver you are using for your UPS:

     

    ...

    Apr 27 21:06:51 Tower kernel: hub 2-0:1.0: unable to enumerate USB device on port 6

    Apr 27 21:06:51 Tower kernel: hub 2-0:1.0: unable to enumerate USB device on port 5

    Apr 27 21:06:51 Tower kernel: hub 2-0:1.0: unable to enumerate USB device on port 5

    Apr 27 21:06:51 Tower kernel: hub 2-0:1.0: unable to enumerate USB device on port 6

    (repeated for about 1/2 the length of your entire syslog)

    ...

    May 11 22:51:01 Tower kernel: hub 8-0:1.0: port 1 disabled by hub (EMI?), re-enabling...

    May 11 22:51:01 Tower kernel: usb 8-1: USB disconnect, address 103

    May 11 22:51:02 Tower kernel: usb 8-1: new low speed USB device using uhci_hcd and address 104

    May 11 22:51:02 Tower kernel: usb 8-1: configuration #1 chosen from 1 choice

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: cannot reset port 1 (err = -71)

    May 11 22:51:02 Tower last message repeated 4 times

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: Cannot enable port 1.  Maybe the USB cable is bad?

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: cannot disable port 1 (err = -71)

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: cannot reset port 1 (err = -71)

    May 11 22:51:02 Tower last message repeated 4 times

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: Cannot enable port 1.  Maybe the USB cable is bad?

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: cannot disable port 1 (err = -71)

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: cannot reset port 1 (err = -71)

    May 11 22:51:02 Tower last message repeated 4 times

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: Cannot enable port 1.  Maybe the USB cable is bad?

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: cannot disable port 1 (err = -71)

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: cannot reset port 1 (err = -71)

    May 11 22:51:02 Tower last message repeated 4 times

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: Cannot enable port 1.  Maybe the USB cable is bad?

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: cannot disable port 1 (err = -71)

    May 11 22:51:02 Tower kernel: hub 8-2:1.0: cannot disable port 1 (err = -71)

    May 11 22:51:02 Tower kernel: generic-usb 0003:051D:0002.0005: hiddev98,hidraw3: USB HID v1.10 Device [APC Back-UPS ES 550G FW:843.K4 .D USB FW:K4 ] on usb-0000:00:1d.2-1/input0

    May 11 22:51:02 Tower kernel: hub 8-0:1.0: port 2 disabled by hub (EMI?), re-enabling...

    May 11 22:51:02 Tower kernel: usb 8-2: USB disconnect, address 100

    May 11 22:51:02 Tower kernel: usb 8-2.1: USB disconnect, address 101

    May 11 22:51:02 Tower kernel: usb 8-2.4: USB disconnect, address 102

    May 11 22:51:03 Tower kernel: usb 8-2: new full speed USB device using uhci_hcd and address 105

    May 11 22:51:03 Tower kernel: usb 8-2: configuration #1 chosen from 1 choice

    May 11 22:51:03 Tower kernel: hub 8-2:1.0: USB hub found

    May 11 22:51:03 Tower kernel: hub 8-2:1.0: 4 ports detected

    May 11 22:51:03 Tower kernel: usb 8-2.1: new low speed USB device using uhci_hcd and address 106

    May 11 22:51:03 Tower kernel: usb 8-2.1: configuration #1 chosen from 1 choice

    May 11 22:51:03 Tower kernel: input: Gaming Keyboard as /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2.1/8-2.1:1.0/input/input6

    May 11 22:51:03 Tower kernel: generic-usb 0003:046D:C221.0006: input,hidraw0: USB HID v1.10 Keyboard [Gaming Keyboard] on usb-0000:00:1d.2-2.1/input0

    May 11 22:51:03 Tower kernel: input: Gaming Keyboard as /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2.1/8-2.1:1.1/input/input7

    May 11 22:51:03 Tower kernel: generic-usb 0003:046D:C221.0007: input,hiddev96,hidraw1: USB HID v1.10 Device [Gaming Keyboard] on usb-0000:00:1d.2-2.1/input1

    May 11 22:51:03 Tower kernel: usb 8-2.4: new full speed USB device using uhci_hcd and address 107

    May 11 22:51:03 Tower kernel: usb 8-2.4: configuration #1 chosen from 1 choice

    May 11 22:51:03 Tower kernel: input: G11 Keyboard as /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2.4/8-2.4:1.0/input/input8

    May 11 22:51:03 Tower kernel: generic-usb 0003:046D:C225.0008: input,hiddev97,hidraw2: USB HID v1.11 Keypad [G11 Keyboard] on usb-0000:00:1d.2-2.4/input0

    May 11 22:51:08 Tower apcupsd[8133]: Communications with UPS restored.

    ...

  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.