• Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by mattz

  1. I am now running 6.9.2 without issues for either GPU or USB Controller. That is, 6.9.0 fixed the FLR issues that was causing my system to hang, without having to use the custom kernel with 6.8.3. If you are updated past 6.9.0 you should be good to use the VFIO-PCI Config interface under Settings in your Unraid admin web GUI to isolate USB controllers. The only caveat is that I had to be careful about which USB controller I isolated: One had the Unraid USB key drive, and that needs to stay. Another USB controller had my Network port on it, so I couldn't isolate that. Otherwise, I isolated one controller for pass-through to my Windows VM.
  2. Redacted... In my experience: currently on Centurylink Fiber in Portland, OR. and I can't crack the nut.
  3. That's a classic use case. It has not gone well for me personally, due to my ISP blocking incoming port 443 requests. I need to use a different port to forward requests via a Reverse Proxy. For example, I need to enter (notice the port number). Most ISP's lock down port 443, ISPs I have been with across the country locked 443. so you won't be able to use any domain without appending the port number you are using as a substitute (e.g. 1443 or something). It works, but it is not the super clean option I wanted. Other consideration is static vs. dynamic IP address - you can use a service like to get around that, and link to that with an ALIAS or A record from your domain. LDAP (or any Single Sign On) is not necessary and would be overkill for a family. You will not be managing users on a regular basis (you add them and they stay, right?). You would use NextCloud's built-in user management and separate logins for each Sonarr and Radar. If you want to remote access to YOUR server from outside, you would need to set up a VPN server to access your network. Check out OpenVPN Sever to do that. Wireguard VPN would be more about securing your server's outgoing connection.
  4. I am not an expert in this space, but the first thing we would need to help you is your use case: for what are you trying to solve? If you want to access your server or assets remotely, consider setting up a VPN on your server and connecting exclusively with that. The reverse proxy makes me think you want to be able to route requests from subdomains to specific applications, most likely for publicly hosting access to your server. In that case you do need to open port 80 and 443 to the reverse proxy app. LDAP makes me think you want to set up user management to one or more apps... maybe to have them register for your blog and also allow a user to use some completely separate front end app? It's a complicated process, for sure.
  5. You said it, @MsDarkDiva! Thank you for the GitHub link and FAQ quote. I guess it was just lazy/taking for granted the "Ignore IP" for me. Took me 2 weeks to finally sit down and try to solve this.
  6. Just did my upgrade to Unraid 6.9.1, and it is all smoothly running! I have not yet removed the Kernel VFIO definitions in the boot flash, but I will switch over to the new, integrated menu in the Settings when I get chance. Because I should be able to remove both the pci_no_flr (no longer need) and vfio-pci.ids (now in Settings > VFIO-PCI Config). 🍻
  7. Wanted to close the loop on this. I *think* this issue has been fully resolved with the release of UnRaid 6.9.0, since they are using the Linux Kernel 5.10.x branch: The original Linux Kernel fix for the AMD 3xxx/Xen CPUs was implemented in 5.8.x, so we should be good now: I have not yet tried it, but I will when I have potentially a few days to feel the frustration if I have to revert.
  8. I like this Q- my take: Best bet is a dedicated NAS- keep it up 24/7 and stable OS with no fuss, and this should be independent to your main desktop environment. (this is why I like using a VM as my main gaming desktop on top of Unraid) Like @trurl said, you can only do RAID when you have multiple disks (you need at least 3 drives for RAID 5). You only need any RAID setup for disaster recovery, so if you are not worried about a disk failure wiping your content, you wouldn't need it at all. Unraid let's you use a few different methods that are "like" RAID, using a "parity drive". You don't need to install all disks at the same time no matter what route you take. I like Unraid because adding/upgrading disks is EASY and SAFE. Plex is a common use case for Unraid, and it's as easy as searching for "plex" in the app store, which literally sets it up in a Docker container and allows you to access via a browser. Installing on your own (as in desktop) should be as easy as any other application, too. I also see roon server, but I never heard of it. (screen shot) Trurl answered the pool and cache questions but, in short, they represent potentially faster and better ways for your NAS to operate.
  9. Has the latest Unraid (6.9.0) included all the fixes this Kernel includes? I would like to upgrade to the latest version (or have a timeline for it), but not if it involves compiling a custom kernel to accommodate the whole x470 motherboards with Ryzen 2 3000 CPU's and pass-through. TY! Note, I am specifically referencing the FLR fix with the Kernel.
  10. @RaidBoi1904 You are a champ for jumping head-first into this issue with a new UnRaid setup. And, sorry to hear the problems all at once... they are not so bad when they pop up once every 2 years after a major hardware upgrade. But your first time out can be rough. So, to pass through Audio and USB (or anything), you will need to isolate them (in addition to the no_flr hack right now for this mobo/cpu combo). It looks like you know where you're going- Main > Flash > Syslinux Configuration to add these lines My setup looks like this for just the USB -- notice the vfio-pci.ids for isolation--I don't know if I need all of them, but I do them as a group and it works: pcie_no_flr=1022:149c,1022:1487,1022:1485 vfio-pci.ids=1022:149c,1022:1487,1022:1485 You will also need to isolate the Audio device to pass-through. on my mobo it looks like it's 10de:10f0, so you would add that to vfio-pci.ids: I use the Arctis Pro Wireless headset that has an external USB driver, so don't need the audio controller.
  11. Good idea adding limetech. They may defer for it to be included into the Linux Kernel, which should come based on that commit I reference. However, with the Ryzen 3600 and others SO CHEAP and performant I am sure there are quite a few people moving on them. BTW - Those steps you had to take, good points. Super annoying, it's because the VM image will "remember" devices that are "removed". You can also edit the XML directly to remove the reference so you don't need the checkbox; however, it's a little bit of guesswork to figure out which XML element(s) it is.
  12. Wanted to confirm this. First install of OPNsense (v 20.1 DVD ISO), and I was unable to see the default UnRaid network interface with Q35. Reinstalled with i44fx-4.2 and it worked without a hitch. See the same on the OPNsense forum - I should be getting my quad port NIC this week. Excited to get running.
  13. Wanted to follow-up. The cause for my issue [with the Ryzen 3900x hanging while trying to pass-through USB Controller 3.0] was totally that FLR issue posted above. Luckily, someone on this forum had already compiled a kernel with a temporary fix, and I used that. Find that custom kernel for Unraid 6.8.3 here: Note that I tried Unraid 6.9.0-beta1 and it did not yet have the FLR fix in the Linux kernel. It will eventually make it into the Linux Kernel, but probabaly not until 5.8... So, might be a while before it makes it into Unraid, read more about the commit - @killeriq - not sure how you got it to work with the Unraid 6.9.0 beta 1, but if it works, I would say that's the important part.
  14. Wanted to follow-up. The cause was totally that FLR issue posted above. Luckily, someone on this forum had already compiled a kernel with a temporary fix, and I used that. Note that I tried Unraid 6.9.0-beta1 and it did not yet have the FLR fix in the Linux kernel. Find that custom kernel for Unraid 6.8.3 here:
  15. @JoeBloggs - I just used the kernel. Yes, just copy it to your flash drive (the /boot/ directory). Save the stock kernels as .bak or something in case you need them. Everything will boot like normal. Just make sure you match the version. Leoyzen has an attached version earlier on this page for Unraid 6.8.3, same as I am using. @Leoyzen - Wanted to say thank you for the FLR fix, I used your kernel, added the parameters I needed and am up and running with the USB controller in my VM! Added `append pcie_no_flr=1022:149c,1022:1487,1022:1485` and used vfio-append to those same ones. Thanks again!
  16. @Leoyzen - I've never used a custom Kernel before, but I am running into a Ryzen 3000 FLR error. Does the Kernel you provide cover this issue? I found the commit that's [going to be??] included: What version of Linux kernel will that make it into? 5.7?
  17. So, I think this is the resolution to the problem "PCI: Avoid FLR for AMD Matisse HD Audio & USB 3.0": It should be brought into some new version of Linux... Does anyone know what version and when Unraid will get it?? My first time looking through these commits.
  18. @killeriq- I think I'm in the same boat now. I just upgraded my x470 board to the Ryzen 3900x from the 2700x (wanted the cores!). However, I am no longer able to pass through my motherboard's USB Controller 3.0 the same way I did with the 2700x. I now get the same error you had and the whole system will lock up, requiring a hard reboot: kernel: vfio-pci 0000:0c:00.0: not ready 1023ms after FLR; waiting It is something others are encountering--the only way to fix it is to avoid passing through that particular USB controller, and use other USB Controllers, if you can: There is also a Kernel patch, it appears, that could fix it. So, I am not sure, does the latest Unraid BIOS fix it for you? It could be the kernel patch made it in...
  19. I wanted to mention, this issue has just recently been affecting me. I am on an MSI x470 Gaming M7 AC motherboard. The issue occurred when I switched from the 2700x CPU to the 3900x CPU (I wanted more cores!!). I swapped the CPUs and all the VFIO Bus:Device.Function numbers changed (that's probably expected). However, the `USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller` (IOMMU group 22 in the pic below) I had passed-through with the 2700x no longer works in pass-thru, even after adjusting for the vfio numbers. Using it now locks up the system no matter what combo of "Non-essential" components I tag with vfio and pass with it. @Skitals described this problem with all x570 boards... Looks like it's the same for x470 boards with a 3000 series CPU. Why the heck is this a problem in the 3000 series, BTW?? I am going down the path of passing through the other USB controllers, as stated above. Unfortunately, on this board one of the controllers is the front USB, which are not very accessible to me. The other contains 3 regular USB ports and 1 USB-C port on the back to use, but that is contained in a very large IOMMU group that includes things like the Ethernet controller (IOMMU group 17), so I have my doubts about isolating that back USB panel. Will provide an update when I get this going... Worst case I buy a separate, PCI USB controller and go that route.
  20. @wbsmolen - I agree- I think it is unrelated to this particular BIOS issue. I found this post about an x570 earlier in this thread to confirm it's probably not this issue, but it also may be related to your problem... ? Good luck.
  21. There were some x570's that had the issue... can't remember which ones. However, you should be good with any BIOS after November 2019. Anything this version or later: AGESA AMD BIOS version Patch B (1004 B) fixes
  22. @mojotaker - Agree with @boris. It sounds unrelated to the pass-through issues. If this is the first time you are using the GPU for pass-through, you may need to double-check the Vbios is properly set up. Use this as a reference:
  23. Woo hoo! Glad it worked for you. I understand being hesitant to update the BIOS, but I think having an up-to-date BIOS, if not the latest, is super important. Cheers.
  24. Thanks for responding with the updates on the latest mobo BIOS tests, @klingon00, @boris, @juan11perez, @dodgypast, and others. Sounds like the AGESA AMD BIOS version Patch B (1004 B) is fixing this pass-through issues for folks across the board (pun intended) for x370 and x470 mobos! So, after 9 months from this issue first popping up, AMD has solved it! Better late than never... Just a note: if you update to this latest BIOS from a working old BIOS your CPU pinnings and IOMMU groups will change, so you will have to update your UnRaid configurations.
  25. @cgi2099 - It sounds like this was the issue causing your errors. Downgrading your motherboard BIOS fixed it, there is a new patch from AMD that is having success so you can update your BIOS to this version: AGESA AMD BIOS version Patch B (1004 B). It started rolling out in BIOSes after late November 2019.