cap089

Hi, ich habe mir vor paar Jahren den ersten unRAID Server aufgebaut: Anwendungszweck ist/war vorrangig NAS und Gaming in einer "Kiste" zu haben. Zuerst paar Fakten: CPU: AMD Ryzen 5900X (war anfangs noch ein 3900X) Mainboard: Asus Strix E-Gaming x570 RAM: 32 GB 3200 MHz SATA: 2x HDD, 2x SSD NVMe: 1x Windows und 1x Cache für unRAID Ich habe quasi alles durchgeschliffen was geht, also GPU, NVMe, USB-Controller und damit läuft auch alles stabil. ABER... Kurz gesagt: Ich möchte/ brauch wieder eine dedizierte Zock-Maschine - habe dafür die bereits vorhandene Hardware vorgesehen - und entsprechend neue Hardware für mein unRAID System. Für ein möglichst stromsparendes System was dann 24/7 laufen soll, würde ich jetzt auf Intel setzen. Neben meinen bisher laufenden Docker Containern und paar kleineren Test-VMs, die nur bei Bedarf laufen, würde ich gern auch meinen Router über ein virtualisierte pfSense abbilden. Dazu würde ich mir eine Intel Quad PCI-E NIC auf Ebay zulegen und die der pfSense VM zuweisen. Durch den 24/7 Betrieb ergeben sich dann noch weitere Anwendungsszenarien für die Zukunft, die ich jetzt noch nicht alle auflisten kann. Bei der Hardware-Auswahl weiß ich an einem Punkt nicht mehr weiter, welches Mainboard bzw. Hersteller ist zu empfehlen? Habe bisher nur Erfahrungen mit Asus Mainboards gemacht und war da eigentlich immer zufrieden, aber ein Blick über den Tellerrand schadet ja nicht. Gibt es da größere Unterschiede beim Stromverbrauch zwischen den gängigen Herstellern? Wie groß ist der Unterschied zwischen ATX und mATX in Sachen Stromverbrauch? Bei der übrigen Hardware habe ich bisher folgendes ins Auge gefasst: CPU: i5 13400 (ein i3 wäre mir zu knapp bemessen) RAM: 32 GB DDR4/ DDR5 Netzteil: Taugt das Seasonic Prime Fanless PX 450W/ 550W was? Hat im Vergleich zum Pure Power von bequiet "80 Plus Platinum". Da die Komponenten nicht zwangsweise in ein kleines Gehäuse gequetscht werden müssen, bin ich nicht festgelegt ob ATX oder mATX. Beim Stromverbrauch will ich jetzt auch nicht zwangsweise jedes Watt einsparen, aber auch mit Standard-Hardware sollten ja unter 20 W im idle bzw. quasi idle wenn nur die pfSense aktiv läuft machbar sein? Oder bin ich da zu optimistisch und auf dem falschen Pfad? Freue mich auf eure Reaktionen

The problem are games which are using BattleEye. With my current settings I cannot run games like PUBG. Games which use Easy Anticheat are working without issues.

Hi, I know there might be a ton of threads discussing this topic but as each setup is sligthly different, I could not get an answer yet. Specifications: CPU: AMD Ryzen 5900X Motherboard: Asus x570 E-Gaming GPU: Nvidia RTX 4070 TI RAM: 32 GB DDR4 3200 MHz unRAID version: 6.12.3 Excluding the graphics card I am running this unRAID build since a while (upgraded from an 3900X) and of course upgraded unRAID OS. And I am quite happy with the setup as I could combine a small server and my gaming machine in one "box". For the gaming Windows 10 KVM I passthrough the GPU, an NVMe, NIC, USB controllers (expect the one which is used for the unRAID flash drive). The Windows KVM has access to 8 cores (16 threads) and 20 GB of RAM, filling up the cores starting in the end of the topology. I also have CPU pinning and CPU isolation for those cores activated. The configuration is ready for Windows 11 but I have not updated yet. The XML of the machine in the following: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='80'> <name>Windows 11</name> <uuid>UUID_WINDOWS</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>20971520</memory> <currentMemory unit='KiB'>20971520</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='16'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='17'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='18'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='19'/> <vcpupin vcpu='8' cpuset='8'/> <vcpupin vcpu='9' cpuset='20'/> <vcpupin vcpu='10' cpuset='9'/> <vcpupin vcpu='11' cpuset='21'/> <vcpupin vcpu='12' cpuset='10'/> <vcpupin vcpu='13' cpuset='22'/> <vcpupin vcpu='14' cpuset='11'/> <vcpupin vcpu='15' cpuset='23'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-7.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/0021f50a-d904-03f5-657f-04d9f50364da_VARS-pure-efi-tpm.fd</nvram> <smbios mode='host'/> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> <feature policy='disable' name='hypervisor'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.225-2.iso' index='1'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0xb'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xe'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/> </controller> <controller type='pci' index='8' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='8' port='0xf'/> <alias name='pci.8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x7'/> </controller> <controller type='pci' index='9' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='9' port='0x10'/> <alias name='pci.9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='10' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='10' port='0x11'/> <alias name='pci.10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='11' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='11' port='0x12'/> <alias name='pci.11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='12' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <alias name='pci.12'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='13' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='13' port='0x13'/> <alias name='pci.13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:e1:ca:6f'/> <source bridge='br0'/> <target dev='vnet79'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-80-Windows 11/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> <alias name='tpm0'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <boot order='1'/> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <alias name='hostdev4'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/> </source> <alias name='hostdev5'/> <address type='pci' domain='0x0000' bus='0x09' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x3'/> </source> <alias name='hostdev6'/> <address type='pci' domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Due recent changes in Easy Anti-Cheat I was forced to make two manual adjustments: <smbios mode='host'/> and: <feature policy='disable' name='hypervisor'/> With those adjustment the game is startable, again (see: https://forums.unraid.net/topic/127639-easy-anti-cheat-launch-error-cannot-run-under-virtual-machine/?do=findComment&comment=1313189 ) So is there anything in my setup and/ or my VM configuration which might cause an overhead which causes a decreased CPU performance or is the CPU and especially the 8 cores of the 5900X too weak for an RTX 4070 TI?

Just found this thread as since the new Hunt Showdown update 1.14 launched and is shipped with a hardened Easy Anti Cheat and I also encountered the specific error. For me just worked the following: 1. Add in the os section <smbios mode='host'/> 2. Add in the CPU section <feature policy='disable' name='hypervisor'/> 3. Deactivated Hyper-V in the forms view. Actually have no idea if this even necessary. In the first rounds I had also the option <kvm> <hidden state='on'/> </kvm> But here the overhead was instantly noticeable so I deleted this option. So the game is starting but runs with less FPS then before the update but this could also be caused by either overloaded servers or any other compatible issues with the graphics driver or whatsoever. But I think the two remaining options in 1. and 2. are not responsible for this?

Hi, I have followed the instructions of Spaceinvaders video and just installed a Mac OS Monterey VM (was automatically downloaded when selecting "Big Sur"). After copying the files from the EFI partition to the disk image, deleting the first two drives from the template, ran the helper script with the modifications, the VM is running in a kernel panic or something like that (see screenshot). Everything else remain untouched from the XML, so no further adjustments were made. Any ideas? Edit: And yes, if I add the Opencore image once again, it is working fine.

Update: Found out that for whatever reason from now on at "Wait for array inactivity" the option "Yes, exclude cache" drive must be chosen otherwise the server is not going to sleep anymore. Before the update this option was not necessary as the cache drive is not permanently busy. Could not figured out which plugin/ docker instance is responsible for that.

Hi, I updated to S3 Sleep version 2021.03.13 and since then the server (unRAID 6.9.2) is no longer going to sleep automatically. I just enabled debug mode and hope to find something. Since the update is from March this year, I wonder if this is a known bug? It was working fine with the previous version without any issues and of course I did not changed anything in the plugins settings. The "Sleep" button in the main tab is working and so far as I know the wakeup is also working. Debug mode "Console" is bullshit - I figured out Hope I find something within the syslog these days.

Hi, it seems that in the meanwhile the product ID again changed (?) Because I made these adjustment and he cannot find this ID or rather according the logs its freezes at: 2021-04-03 12:19:08,755 Selected macOS Product: 071-05432 How can I find the new ID to download Big Sur? Edit: Okay do not know which I have done different but after I tried it again it actually fetched the correct BaseSystem.img and now I can install Big Sur.

Hi, I justed started to begin my testings with the latest unRAID 6.9 beta and I wonder if the MakeMKV docker is compatible with it? I have added my optical drive within the extra parameters section: " --device /dev/sr0" The Docker container starts without any errors but MakeMKV do not regognize any optical drive. I have also tested it with " --device /dev/sr0 --device /dev/sg0", but no luck. I can remember that it worked over a year ago with my first tests with unRAID 6.8 but as this caused many bugs with my X570 board and Ryzen 3900X unRAID 6.8 is no option for me...

Hi! Am I blind or where can I download the beta version of unRAID 6.9? I want to test it out if with version 6.9 my unsolved bugs which I had with version 6.8.x in the past. Sorry for the retard question but until last year the beta releases could be downloaded direct on the website and/ or the USB creator application? Thanks in advance!

Hi! No problem. Thank you very much, anyway. Plugging in the mouse is not possible because its only Wireless mouse with batteries - so no way otherwise I would have tried this out.

Hi! So I tested it with the direct passthrough of the mouse but it seems to be even worse. Sadly with this limitation unRAID does not fit my needs...

Ok I will test it soon. Just thought about it could be a driver issue or something else (?) But I already reinstalled the G-Hub..

Hi thanks for your reply. So far I did not tested it by passing through the mouse itself because this is often mentioned to cause problems.... So I just discard this option for me. On the desktop everything works fine, the problem occurs just in games.

Really nobody?