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.

Lost connection with Unraid

Featured Replies

Hello, this is my first post in this forum :)

 

My problem is that after some idle time, my server cannot be reached. Not with SMB shares nor SSH or through web interface.

At the first time I had this issue I pushed the power button on the server and the system went down properly, so it wasn't frozen. After power ON again, it worked for 2 days without any problem. Of course the log mirror to the flash drive was turned OFF so I did not know what the problem was.

 

Today I lost the connection again but instead of resetting the server again, I tried to unplug and plug the LAN cable. And tadaaam, I can reach Unraid again!

I checked the log and found this:

Aug 31 09:16:57 NAS kernel: pcieport 0000:00:1c.2: AER: Uncorrected (Non-Fatal) error message received from 0000:02:00.0
Aug 31 09:16:57 NAS kernel: r8125 0000:02:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
Aug 31 09:16:57 NAS kernel: r8125 0000:02:00.0:   device [10ec:8125] error status/mask=00004000/00500000
Aug 31 09:16:57 NAS kernel: r8125 0000:02:00.0:    [14] CmpltTO                (First)
Aug 31 09:16:57 NAS kernel: r8125 0000:02:00.0: AER: can't recover (no error_detected callback)
Aug 31 09:16:57 NAS kernel: pcieport 0000:00:1c.2: AER: device recovery failed

->I unplugged the LAN cable

Aug 31 10:31:12 NAS kernel: r8125: eth0: link down
Aug 31 10:31:12 NAS kernel: bond0: (slave eth0): link status definitely down, disabling slave
Aug 31 10:31:12 NAS kernel: device eth0 left promiscuous mode
Aug 31 10:31:12 NAS kernel: bond0: now running without any active interface!
Aug 31 10:31:12 NAS kernel: br0: port 1(bond0) entered disabled state
Aug 31 10:31:15 NAS ntpd[1319]: Deleting interface #1 br0, 192.168.1.51#123, interface stats: received=158, sent=162, dropped=0, active_time=99230 secs
Aug 31 10:31:15 NAS ntpd[1319]: 216.239.35.4 local addr 192.168.1.51 -> <null>

->I plugged the LAN cable

Aug 31 10:31:17 NAS kernel: r8125: eth0: link up
Aug 31 10:31:17 NAS kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex
Aug 31 10:31:17 NAS kernel: bond0: (slave eth0): making interface the new active one
Aug 31 10:31:17 NAS kernel: device eth0 entered promiscuous mode
Aug 31 10:31:17 NAS kernel: bond0: active interface up!
Aug 31 10:31:17 NAS kernel: br0: port 1(bond0) entered blocking state
Aug 31 10:31:17 NAS kernel: br0: port 1(bond0) entered forwarding state
Aug 31 10:31:19 NAS ntpd[1319]: Listen normally on 2 br0 192.168.1.51:123
Aug 31 10:31:19 NAS ntpd[1319]: new interface(s) found: waking up resolver

 

Do you have any idea what went wrong with the ethernet at 09:16:57 ?

  • Author

Thanks, I"ll give it a try.

What NIC is fully supported and no issues at all, even work with C-state >C3?

  • Community Expert

Intel is usually better, but don't know about C-states.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

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.