Conjure

Members
  • Posts

    8
  • Joined

  • Last visited

Conjure's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Running the following seems to always put it into 1000Mbit: /etc/rc.d/rc.inet1 restart Wondering if I just need to script this to startup?
  2. Hey all, This is something that has slightly frustrated me since I got unRAID early last year, but I'm more interested in trying to diagnose and fix it now. I have an MSI Z590-A Pro motherboard on 6.11.5 (this has happened since 6.9.2). My motherboard has an Intel I225-V 2.5Gbps NIC onboard, which works great and I'm able to get the full 1000Mbit connected to my router. However, if I ever have to reboot the server, I only get 100Mbit on this NIC until I reboot 3 times. Then it's back to 1000Mbit. Things I've tried: -New Cat6a/7 cables, from different mfgs. The cable run is only 6~ feet from the server. -Different port on the router. I know the port is good because I used this motherboard on Windows without issue and at full speed. Not sure if it's a Linux kernel issue, since I've gone from 6.9.2 to now 6.11.5 with all of those kernel changes in between. Anything I can do here? Thanks! EDIT: To clarify, this happens when I cold boot the server too. I need to reboot it 3x to get 1000Mbit.
  3. Came to report this, glad I'm not the only one. Yeah, it looks bad.
  4. I've pinpointed the issue. It's whenever Mover runs. Fresh reboot, nothing going on, dashboard is running fine. After running Mover, everything like you see above happens. Telnet into the server and ran tail: Nothing after it, no errors. Just everything you see above in the pictures happens until I reboot. Any ideas?
  5. I had this thought and it's not even necessary. Just use any of the binhex VPN torrent clients (binhex-delugeVPN, etc). Configure your VPN to use with it. If it ever loses VPN connection the docker has a killswitch and will instantly stop.
  6. I should note, I was getting "Nchan communication error" on rc3 pretty frequently. EDIT: Yep, just happened again. "Nchan communication error", same thing happened as the pics above and can't open terminal now, and can't run Tools > Diagnostics > Download either.
  7. Hey all, I've noticed pretty much all of my displays/metrics for the Array and CPU/GPU/Interface/Motherboard/etc crash and stop displaying on both the dashboard, and the Array on the Main page. I'm on 6.10.0-rc2, just downgraded from rc3 due to this bug happening and it continues to happen. Just started today. Everything works fine when this happens, and the array is still up. Fix Common Problems has found nothing wrong at all. Attached are some pictures of what's going on. If you need any logs, just let me know what you need. Thanks!