• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

phoebus's Achievements


Newbie (1/14)



  1. Thanks Squid. Yes, so the VM had been in sleep display mode. I changed its network bridge mode from Br0 to virBr0 and had a few days without problems. So I then shut the VM down but had problems again last night at around 22:40. Oddly the log doesn't show any problems (diagnostics attached). I've kept all but essential dockers but Home Assistant is reporting a lot of network problems so I've disabled that and will wait and see. Apologies but not sure what this means. In System Devices that is an audio adaptor and it has a green light next to it (the only item to do so) but can't find what that means. Have I isolated it in my VM then as looking in Advanced View for my VM I can't see it. I can't recall isolating via syslinux and don't even know how to do so! May have been when I first installed Unraid and was playing around.
  2. I switched to Unraid earlier this year and loved how easy it was to set up dockers, VMs and services and paid up before the end of my trial period. However the past month I've had network disconnection issues that I can't seem to solve, and looking at similar posts on the forum I'm not alone. I mainly use Unraid to host shared network folders, Plex and related services and a Windows 10 VM for Slack and Teams. I can watch about 20 mins of Plex then will get network dying (no Plex, no access to any Dockers) till I go up and wake up the VM, then I'll get a few in a row. It seems worse in evenings and mainly when playing Plex locally, I played remotely Saturday morning no problems. PLex has never had a problem running on the Windows VM, only Smart TV and other devices. I'm at my wit's end and while I don't want to leave I'm starting to look at Plan B for a Plex server. I've tried: * installing an Intel NIC in addition to my motherboard's Broadcom one * updated to the latest Unraid Beta, rc-2 * changed my network settings to have bonded, single connections, checked and replaced the cables, checked ports on my hubs * checked other network related settings in Unraid * uninstalled network monitoring tools in case they were interfering * reset Plex app on my TV in case it was causing problems * checked the PCIe connections and re-set as I am getting PCIe messages * disabled IPv6, set all network settings to automatic where possible, checked my router's settings and upgraded firmware and set the static IP * checked my router logs to ensure I'm not being DDoS/hacked etc and changed myServers port just in case * used Tweak tools to check and tweak network settings * disabled un-needed Dockers I'm not sure what it is, it may be a VM issue if activating it seems to restore it but not sure what to change. However I have made no VM changes in the past few weeks. Any help appreciated as sticking with Unraid will be easiest for me but feel I'm running out of options.
  3. Okay so the mystery deepens as now I am getting spammed by these messgaes several times per minute Nov 26 18:05:35 Unraid kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex Nov 26 18:05:35 Unraid kernel: bond0: (slave eth0): making interface the new active one Nov 26 18:05:35 Unraid kernel: device eth0 entered promiscuous mode Nov 26 18:05:35 Unraid kernel: bond0: active interface up! Nov 26 18:05:35 Unraid kernel: br0: port 1(bond0) entered blocking state Nov 26 18:05:35 Unraid kernel: br0: port 1(bond0) entered forwarding state Nov 26 18:06:07 Unraid kernel: e1000e 0000:05:00.0 eth0: Reset adapter unexpectedly Nov 26 18:06:07 Unraid kernel: bond0: (slave eth0): link status definitely down, disabling slave Nov 26 18:06:07 Unraid kernel: device eth0 left promiscuous mode Nov 26 18:06:07 Unraid kernel: bond0: now running without any active interface! Nov 26 18:06:07 Unraid kernel: br0: port 1(bond0) entered disabled state Nov 26 18:06:11 Unraid kernel: e1000e 0000:05:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
  4. Okay so despite adding eth1 to bonding members eth0 I still have been losing my internet connection. I have also upgraded to the latest Unraid Beta. I keep getting Nov 25 22:16:03 Unraid kernel: r8169 0000:03:00.0 eth1: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). Nov 25 22:16:14 Unraid kernel: r8169 0000:03:00.0 eth1: rtl_txcfg_empty_cond == 0 (loop: 42, delay: 100). r8169 is eth1 so I thought that if eth0 is fine it should be okay. It always seems to happen around 9pm at night, I'd been using it all day. And when I reopen my laptop where I'm logged into my Unraid dashboard and/or the Windows VM running on it it tends to, but not always, fix itself. The Intel NIC seemed to be okay but after an error I thought that bonding the flakey r8169 motherboard device to eth0 it would mean that if one fell out then the other would kick in and I'd have a stable connection. Any thoughts?
  5. Due to recent hardware network issues I'd like my eth1 (motherboard network) to serve as a backup to my main network connection eth0 (NIC) and can't seem to get it right. I've assigned my Unraid a static IP locally to help with bookmarks etc. But when I disconnect the eth0 cable I can never connect. I've looked but can't seem to find the settings I need to change. Any advice welcome.
  6. Ah, thanks. I just assumed that it would write over previous files. Yes looking at my dashboard I see it at 100%.
  7. Thanks Squid, yes you're right I am using a Mac and had been trying to transfer several gigs from one onto my Unraid array earlier. However I have the setting on Yes. I've enabled syslog write to my flash so I can access it more easily in future. Think I'll reboot my Unraid device and see that helps.
  8. My network died for a few minutes on Unraid (depsite a new NIC and updated drivers) so I went to diagnose via the syslog. However while the problem occurred at 18:45, my log only runs till 11:30, cutting out mid-entry: Nov 24 11:30:05 Unraid smbd[16572]: Nov 24 1 Any ideas what happened and how I can find out what caused my network to die? Diagnostics attached
  9. For any future readers, I solved this (so far the error hasn't reappeared) by updating my Unraid install to a beta. I went from 6.9.2 to 6.10.0-rc2 2021-11-01. Looking online it seems that Realtek drivers have a known issue around r8169 and the beta may include the latest drivers.
  10. Over the past week I've been having problems with my Unraid setup, disconnecting from my local network. I've looked and it seems to be an Unraid rather than a Plex Media Server problem (where I first spotted it). Plex won't connect until I wake the Windows VM I am running on the Unraid device or I log into Unraid, though it could be a coincidence. It does tend to be in the evening and night time rather than morning. Looking in the log (attached) I keep getting: eth0: rtl_txcfg_empty_cond As you can see in the syslog-2 I keep getting this from when I try to use Plex from 21:25 until I log into Unraid at 21:28 and the error corrects itself. This problem only started the last week or 2 and will creep in while Plex is playing, either disconnecting or slowing down, but has become worse the last couple of days. I've disconnected and reconnected the ethernet cable and rebooted Unraid to no avail. I use the motherboard's built in ethernet adaptor. syslog-2
  11. Thanks @frakman1 you just saved me a lot of frustration
  12. I recently upgraded my system to a 10th gen i5 Intel and have 16GB of RAM. On my Unraid I have a Windows 10 VM running plus Plex Server and Dockers running. CPU use isn't that high but RAM stays around 89% and when I do a few things (such as if I'm watching Plex on the Windows VM and someone else is watching a transcode) both CPU and RAM hit 100%, or Plex starts to stutter. Even if I stop watching anything on the VM but keep it running it can max out. I use a USB monitor rather than HDMI out as I use the CPU graphics for Plex hardware transcode, though the output is so blocky I'm not sure it's worth it. However the USB monitor does put a strain on resources of other machines when using it. Even if I did want to use HDMI out my main monitor is used by another device anyway so the USB-3 monitor is the best option. My question is whether getting more RAM help, ie is CPU hitting 100% because I'm running out of memory as it's hard for me to tell with the Unraid logging what is happening.
  13. Looks like the USB mode was the issue for me. Changing USB controller to USB 2 or USB 3.0 (nec XHCI) seems to have fixed it.
  14. Likewise I had Windows 10 installed and now it rarely starts. I have just tried to create a new Win10 VM in case my previous one corrupted but no luck, it keeps dying on me. I'm on 6.9.2 and have made the Tips and Tweaks change to Performance and Turbo enabled. All my cores end up reaching 100% even if I only allocated one or two, then the VM dies. EDIT: Ubuntu 20.04 VM is fine, just the Win10 one that won't work