Jump to content

DANgerous25

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

1 Neutral

About DANgerous25

  • Rank
    Newbie
  1. I solved this myself by adding a "Peer DNS server" [like google DNS] in the advanced config. For some reason local DNS forwarding just doesn't work with my setup.
  2. @Koenig - those lines of XML you quoted did not work for me. In fact, they did not make any difference that I could notice whether they were included or not. I solved this problem by doing two things: 1) Changed the "CPU" XML 2) Used the Tools -> System Devices page to enable passthrough of my graphics card, instead of manually overriding as a kernel parameter in the syslinux config. Below is my post in another forum with how I solved it and a couple of references that helped me to get there. https://forums.serverbuilds.net/t/guide-remote-gaming-on-unraid/4248/130?u=dangerous25
  3. Thanks for the excellent guide. Indeed I was up and running within minutes. Sorry if this is really a stupid question, but I am pretty clueless! I've set up Wireguard exactly as per the guide as type "Remote tunneled access". It's working, and I can connect in remotely and access hosts on my LAN. However my internet access doesn't work from my client devices while I'm connected to the VPN. Is there a setting somewhere I've missed or something I need to do? My Unraid server has internet access locally at least, so not sure why it doesn't work when I'm connected via VPN. I have a hunch that this might be something to do with "local tunnel network pool" and adding a static route somewhere, as in the advanced settings it says "Remark: docker containers on custom networks need static routing 10.253.0.0/24 to 10.10.10.5" which are my tunnel pool and server IP respectively. But I don't know how or where to do this. Thanks a lot for your help.
  4. Thanks as always @Jessie from the response. Actually this doesn't exactly cover my use case, as I'm not sure if this is an Unraid question or a network question, I posted in another forum but I'd be happy to take any advice if you have it. https://forums.serverbuilds.net/t/guide-remote-gaming-on-unraid/4248/124
  5. Superb, @Jessie! I made some simple modifications to the "AMD reset bug" script like below, which enables a successful workaround. Indeed the same solution works for the network adapter. Thanks so much! Also thanks to the SpaceInvader One video for the great overview this. My solution script: #!/bin/bash # #replace xx\:xx.x with the number of your PCIE device that you want to reset # echo "disconnecting Aquantia network card" echo "1" | tee -a /sys/bus/pci/devices/0000\:2e\:00.0/remove #echo "1" | tee -a /sys/bus/pci/devices/0000\:xx\:xx.x/remove echo "Entered suspended state... press power button to continue!" echo -n mem > /sys/power/state echo "Reconnecting Aquantia network card..." echo "1" | tee -a /sys/bus/pci/rescan echo "Aquantia network card reset, all done!" Regarding the suggestion for making the 10G adapter for Unraid; the reason I didn't is because I wasn't getting 10G out of the virtual driver, I had actually thought it was limited to 100Mb. It looks like I didn't do this properly the first time, as I've just done this again and here are the results using some simple iperf3 tests: From a client computer to the Unraid server I am getting 8-9GB/s, f From a client computer to the Win10 VM using the bridged adapter in Unraid I am getting ~1.25Gb/s. For comparison, when passing through the 10G adapater to the VM I get ~7Gb/s from the client computer but have to use the reset script above if I shut down the VM without rebooting. = So the bridged adapter setup significantly reduces the bandwidth, but actually 1.25Gb/s is fine for my use case and is an acceptable tradeoff to the "AMD reset bug". Edit: Updated with results of the bridging suggestion. Thanks again @Jessie.
  6. Short story: I have an ASRock x570 motherboard that has an on board Aquantia Aqtion 10Gbit network adapter. I've successfully passed through the adapter card to the VM (leaving the other onboard adapter for Unraid). If I reboot Unraid and then start the VM, the adapter in Windows gets an IP address via DHCP and the connection remains stable and I am happy. However, if I stop the VM [nicely] and then restart it, then the adapter doesn't pick up an IP address and its status fluctuates between the three states below. Nothing I've tried other than rebooting Unraid seems to solve the issue. Identifying -> Network cable unplugged -> Enabled -> ... repeat ... Longer story; Here are some of the things I've tried: Updated the Aquantia drivers in Window with a) Those listed on the ASRock site, b) From the Aquantia site. -> No joy. Tried both static and dynamic IP with DHCP. -> No difference. Disabled the other adapters in Windows. -> No difference apart from making it impossible for me to log in to the VM without rebooting! Reset the adapter, uninstall/re-installed in device manager, enabled/disabled in device manager, manually set link speed to 10G, turned off power features. -> Nope. Checked to see if the adapter port is overheating on the motherboard (just using my finger, so not massively scientific, but doesn't seem very hot). -> Inconclusive. Left the Unraid server and VM running while in the working state for hours to see if at some point the connection drops (it doesn't). -> Inconclusive, it has only been hours. Changed the CAT 7 network cable for another cable. -> No difference. Reset the SPF+ module in the switch, tried a different and definitely working SPF+ module in the switch. -> That's right, no change. Run the VM from the Unraid array and from its own unassigned drive. -> Clutching at straws I know, but I was doing this for another unrelated purpose. Checked for errors coming up when I start the array. -> No errors come up (but maybe there are errors behind the scenes?) Stop VM / start VM nicely or Force Stop VM / Start VM from the Unraid VM page. -> Windows starts nicely, but the 10G adapter says meh. Searched the internet/forums for similar issues. -> I'm yet to find anything similar. Checked for flashing lights on the interface. -> Yep, lights are on. Rebooted Unraid and start the array then VM -> Works. My setup: I'm using Unraid Version 6.9.0-beta1 2020-03-06, Windows 10 May 2020 Update VM on its own SSD, Ryzen 3950X / 128 GB RAM / Asrock x570. Pretty much vanilla Unraid install, I've only just set it up so it's just this VM and an Ubuntu server I'm playing with. The Unraid server connects to a Mikrotik 10Gb switch via cat 7 RJ/45 -> SPF+ adapter module in the switch. Another computer connects to the switch in the same way without issues. The rest of the network is 1Gb LAN / ethernet over power / Wifi 5. I'm pretty new to Unraid and so I'm really stuck as to how to diagnose this issue beyond what I've done above. I am also very aware that this could be a Windows issue or unrelated to Unraid. Any help would be appreciated.
  7. Hi all, first post but felt compelled given the amount of great community info out there that has helped me. I spent many, many hours trying to solve this issue and finally did. My setup: Ryzen 3950X, RTX 2080 Super. Tried and didn't work: * Clean install using UEFI boot, vanilla setup without editing XML or adding any parameters * With UEFI boot, adding "vfio-pci.ids=10de:1e81,10de:10f8,10de:1ad8,10de:1ad9" to the syslinux configuration (Main -> Syslinux, device IDs are the x4 nvidia device IDs derived from Tools -> System Devices), editing the xml to add multifunction='on' and aligning the bus/slot/function parameters for all four devices, re-install nvidia drivers in Win10 Eventually I got it to work by: * Doing all of the above, but changing to legacy bios boot, then in Windows remove the nvidia display adapter from device manager (having previously updated the driver from the web), then re-scan hardware -> hey presto, no error 43. Conclusion: Don't give up in Windows just because you get error 43, there is almost certainly mileage in updating the nvidia driver from the web and then removing/re-adding in device manager. However, this only worked for me once I'd configured all the passthrough in xml and set boot mode to legacy. It would not work without all of those actions completed. I hope this helps someone, and I'd like to thank all of the posters above and Space Invader 1 for his great videos that helped me to have some basic understanding of what needed to be done here.