soltkr

Quick update: it was something to do with the specific VM config. After I rebooted a couple times the VM stopped trying to autostart and that stopped the stalling behavior when trying to edit the vm settings page. I redid the hardware pass through and deleted and recreated the VM. I just pointed it at the same virtual disk on the passed through nvme and poof it came back exactly as it was. I didn’t even have to reactivate windows. It was awesome. So now I am back up and running. I stopped the VM from auto starting so hopefully if anything like this happens again I won’t be locked out of the settings.

I noticed my windows VM was saying it was missing the video card after a reboot of the unraid host. I had the config page set to the xml editor instead of the form view so I switched it back and then readded the passed through 4070 super as a second card behind the vnc one. then suddenly the entire unraid interface became unresponsive. I was able to get it back by browsing to it using the host name instead of the IP I typically use in the address bar. as soon as I selected the vm tab the entire thing became unresponsive again. I was able to get into the dashboard again by using the unraid connect page to get to it. I was too afraid to click on vms so I just rebooted the host. when it came back up I was able to get into dashboard normally but once again it froze anytime I tried to get to the vms tab. one time I was able to get to it but if I tried to edit the settings of the vm it froze again. most times I don't even get that far. how can I troubleshoot whatever setting I must have accidentally misconfigured on the vm in order to return my installation to normal functionality? I did upgrade the OS to 7.0.0 since the notes said there were improvements to VM administration but this didnt change the behavior I described above. I tried using the main console to get into virsh but if I issue the connect or even the list command it just never comes back with any output or gives me the cursor back. I have to ctrl+C to kill the command to do anything else.

I have discovered that I was fundamentally misunderstanding how the docker is set to work. When using PIA for your vpn and if you connect to a server that has port forwarding the listening port will automatically set itself to match the port assigned by PIA. Thanks to @binhex for making such a cool docker container.

Anyone know how I can change the listening port setting permanently? I changed the host port 1 and 2 settings in the template but it still reverts to the default anytime the docker restarts

I feel like an idiot here but I cant figure out how to change the default port away from 6881 in the binhex-qbittorrentvpn docker. I changed the host port 1 and 2 environmental variables to the port I want but every time the docker restarts the settings page in qbittorrent on the connection tab still has 6881 as the port and I have to change it manually every time. can someone point out what I am doing wrong here?

This thread contained the solution to my problem, thanks for taking the time to look at my post and to find this answer. I have been looking for the solution for like 2 weeks! in case anyone stumbles upon this later and has the same problem the fix was to go into the bios, go into the PCI Subsystem settings under the advanced tab I think and setting the SR-IOV Support to ENABLED. as soon as I did that I rebooted and Unraid was able to see all my sata drives again. now I can go about getting everything configured. thanks again!

@itimpi Here is the file you requested, thanks for taking the time to respond to my post! soltkr-srv3-diagnostics-20231018-2042.zip

I am putting together my first ever unraid box and I had the OS booted up and assigned some of the spinning disks to the array and made 2 raid1 pools with 4 m.2 ssd which I have installed in a hyper card. when I rebooted the system it suddenly couldnt see any of the sata drives at all. there are 2 spinning disks attached to an hba and it can see them and it can see all 4 of the m.2 ssds but the sata port attached drives do not show up. they do show up in the POST in the list of detected drives but once the OS loads nothing. I didnt make any changes in the bios or anything, the only thing I did was assign drives. I didnt even start the array. I tried booting it up without the hyper card installed but that didnt make it work and I even put in a brand new usb drive with a fresh install just to see if it was something I changed in unraid but no joy. any ideas what could be going on here? I was so excited to actually start configuring things and now I am stuck. I did some testing and found the following: - no matter how few drives I connect to the onboard sata ports none of them are visible - I booted into hirens boot cd PE and found that all of the sata connected drives were visible and healthy in disk management - any drives that I move from the onboard Sata ports over to the break out cables attached to the HBA do show up in Unraid here are some screen shots of the drives not being in Unraid but showing up when I was running Hirens: Disk shots here are my hardware specs for this build in case that is useful: CPU: AMD Ryzen Threadripper PRO 5955WX Mobo: ASUS Pro WS WRX80E-SAGE SE WiFi II AMD WRX80 Ryzen™ Threadripper™ PRO Extended-ATX Workstation Motherboard GPU: Nvidia Quadro P4000 RAM: 4x 32GB Corsair VENGEANCE LPX DDR4 3200MHz CL16 HBA: LSI 6Gbps SAS HBA LSI 9201-8i (=9211-8i) P20 IT Mode (art of server ebay) PSU: GAMEMAX 1300W Power Supply, ATX 3.0 & PCIE 5.0 Ready, 80+ Platinum Certified HDD: 10x Seagate ST8000DM008 BarraCuda 8TB Internal Hard Drive HDD – 3.5 Inch Sata 6 Gb/s 5400 RPM 256MB Cache NVME: 4x SAMSUNG 980 PRO SSD 1TB PCIe 4.0 NVMe Gen 4 Gaming M.2 CPU Cooler: Noctua NH-U9 TR4-SP3 Case: Rosewill 4U Server Chassis RSV-L4500U Case Fans: 6x Noctua NF-P12 redux-1700 PWM, 2x Noctua NF-R8 redux-1800 PWM I have attached a copy paste of everything that shows up under tools -> system devices PCI Devices and IOMMU Groups.txt