Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by bastl

  1. bastl

    Isolating ram possible?

    @steve1977 With the following in the terminal you should see the memory allocation as I in the RC5 UI docker stats
  2. bastl

    Isolating ram possible?

    Oh ok. I forgot to mention I'am on the latest RC. 6.7.0_RC5 I'am not exactly sure what the minimum ammount of RAM is for Radarr, Sonarr and Plex is to run properly. Depends on how big your library is, I guess. Try to limit them to 2G each and check if they are running as usual. Currently all 3 together using almost 10G
  3. bastl

    Isolating ram possible?

    I've edited my last post. The % is the CPU usage, below that is the current RAM usage and the max ammount in your system.
  4. bastl

    Isolating ram possible?

    Go to your docker page and check the allocation for each container in the advanced view. And check which one is using all the RAM. Usual docker usage is a couple MB up to an gig. Above that is unusual. Edit: You can limit the memory usage of a specific docker if you edit the container and add another parameter
  5. bastl

    Isolating ram possible?

    8GB allocation for Unraid itself and the dockers are enourmous. What dockers are you running? With 8 dockers currently running for me they allocate 1 - 1.5GB only.
  6. True, but the actual copy process only uses 1 core and not really pushing it. It sits around 20-30% load and thats it. The collecting part at the beginning of the process and checking for new files is a multithreaded operation. The encryption, compression and copy process is using only one core. The main reason why it's slower than other solutions.
  7. bastl

    Unraid OS version 6.6.7 available

    @jbrodriguez that took some time for you to upgrade 😂
  8. Duplicati isn't the fastest solution thats right, but less 1mbps is way to slow. I usually always get above 30mb/s with encryption and compression enabled. At the point where Duplicati checks all the files first it stresses the CPU really hard, but after that when starting the copy/compression process it doesn't really use that much CPU resources.
  9. bastl

    Sound-card pass-through

    @Whoami Your sound device isn't in it's own IOMMU group. You won't be able to pass it through if it's not. The port you have plugged it in is connected via the chipset to the CPU where other devices also connected to. Splitting the devices with the ACS override patch mostly helps a bit but in your case the sound card is still grouped together with one of the PCIe Ports. Try to change to another PCIe slot which isn't connected to the PCH. Edit: What also could help is a updated BIOS version if available. If you're lucky this could fix it. Early days for me on Threadripper the IOMMU groupings were really bad and you couldn't really split them in individual groups with the ACS_patch. A couple BIOS revs. later and this wasn't a issue anymore for me. example without ACS: IOMMU group 13: [1022:43ba] 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset USB 3.1 xHCI Controller (rev 02) [1022:43b6] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset SATA Controller (rev 02) [1022:43b1] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] X399 Series Chipset PCIe Bridge (rev 02) [1022:43b4] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1d6a:d107] 03:00.0 Ethernet controller: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] (rev 02) [8086:1539] 04:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) [8086:24fb] 05:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) [8086:1539] 06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) Not possible to pass any of that network devices to a VM. With ACS applied all devices will be split in it's own groups now with an up-to-date BIOS. 1 year ago this looked different. All networking devices were still grouped together and also the SATA and the USB controller showed in one group. Unfortunately i can't provide you a screenshot from back in the days.
  10. bastl

    [Support] Linuxserver.io - Nextcloud

    @Razvan Rosca Login into nextcloud with an admin account. Go to settings >> overview and you should see on the right your current installed version and if an upgrade is available. Is this what you're looking for?
  11. Could also be an display bug from the Unraid UI showing the cores at 100%. Try the following command if it happens again and check the cores that are pegged if they're running at max clocks. If you aren't running the performance CPU scaling governor the CPU on idle should scale down in clock speeds. watch grep \"cpu MHz\" /proc/cpuinfo
  12. Most restarts for me are triggered by updating software, drivers for the GPU or from OS updates. If I remember correctly the longest I had the VM up without restarting was 14 days and than there was an Unraid update 😄 Are your windows updates delayed for a couple days or weeks or do you let the OS install them as soon as they are released? Wouldn't be surprised if again a Windows update causes issues. I think on Home versions you can't delay updates, only on Pro and Enterprise.
  13. Good start would be to provide us with a diagnostic file when it occours again. In over 1 year using a 1950x with unraid and a Win10 VM running often for a couple days without reboot I never saw something like you described. I'am also running RC5 without any issues so far. What was the last things you installed inside your VM? Is there any new software you installed before it happened? Did you changed something in the VM settings? Are there any log entries in the Windows logs before it crashes that may look suspicious?
  14. bastl

    Win10 VM MicroStutter

    @member378807 Did you tried to apply the MSI_FIX to resolve your audio issue? https://wiki.unraid.net/UnRAID_6/VM_Guest_Support#Enable_MSI_for_Interrupts_to_Fix_HDMI_Audio_Support
  15. bastl

    Win10 VM Locks Up When Installing AMD Driver

    @russdyer77 There are a couple reports from people with the same issue with newer AMD drivers. I can't really tell with which driver exactly it started to happen. I remember one user had success using a driver from end of last year. Oct or Nov release i think he used. I can't tell if there is an actual fix for it to be able to use newer drivers. Maybe someone can link you the right thread for it or @limetech has an solution ready that I don't know of.
  16. Even one 1080ti is to much, f*** it buy two 😂
  17. Gsync monitor maybe? Try changing that and see if it maybe helps.
  18. Not actual sure if this would work. Some older cards are still recognized without extra power plugged in. Worst case, server won't boot. I bet the layout will be the same as for me. Slot1 is connected to node1 and slot3 to node0.
  19. This fix changes the way the OS is comunicating with the card, so yes it will change something. My main card the 1080ti is connected via display port to my monitor and the audio portion is also passed through. I don't use the monitors sound output, but without I will have sound issues if I would use them. If you don't notice any sound issues leave that tweak by side for now but keep that in mind. Did you assigned cores from the node the card is attached to? Does it only flicker in games or also on desktop? Here as a example my main VM xml if you wanna play around a bit. notes: Unraid version 6.7.0_RC5 all cores on the second die are isolated emulatorpin and iothreadpin limited to the second die Q35 because of newly introduced PCIE-root-port-patch in RC5 (qemu part at the end needed) to have the OS and applications correctly notice the link speed of the slot the card is plugged in, otherwise Nvidia driver reports it as 1x speed only. For me feels smoother this way. not working for i440fx or on older Unraid versions numatune set to use only memory directly connected to the second node CPU model tweaks to get the right CPU cache reported to the VM except of the qemu part everything also works on i440fx type VMs for me VBIOS of the card dumped and modified, removed some Nvidia header (SpaceInvaderVideo) MSI_fix applied for GPU and audio devices CPU Scaling Governor set to "On Demand" (Tipps and Tweaks Plugin) some Windows settings tweaked, the usual stuff, power plan to high performance, a couple services disabled etc. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>WIN10_NVME_UEFI_Q35</name> <uuid>de625f4a-3dfd-9751-a28a-68449d424909</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>14</vcpu> <iothreads>1</iothreads> <cputune> <vcpupin vcpu='0' cpuset='9'/> <vcpupin vcpu='1' cpuset='25'/> <vcpupin vcpu='2' cpuset='10'/> <vcpupin vcpu='3' cpuset='26'/> <vcpupin vcpu='4' cpuset='11'/> <vcpupin vcpu='5' cpuset='27'/> <vcpupin vcpu='6' cpuset='12'/> <vcpupin vcpu='7' cpuset='28'/> <vcpupin vcpu='8' cpuset='13'/> <vcpupin vcpu='9' cpuset='29'/> <vcpupin vcpu='10' cpuset='14'/> <vcpupin vcpu='11' cpuset='30'/> <vcpupin vcpu='12' cpuset='15'/> <vcpupin vcpu='13' cpuset='31'/> <emulatorpin cpuset='8,24'/> <iothreadpin iothread='1' cpuset='8,24'/> </cputune> <numatune> <memory mode='strict' nodeset='1'/> </numatune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/de625f4a-3dfd-9751-a28a-68449d424909_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> <reset state='on'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>EPYC</model> <topology sockets='1' cores='7' threads='2'/> <cache level='3' mode='emulate'/> <feature policy='require' name='topoext'/> <feature policy='disable' name='monitor'/> <feature policy='require' name='hypervisor'/> <feature policy='disable' name='svm'/> <feature policy='disable' name='x2apic'/> </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.160-1.iso'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source file='/mnt/user/isos/clover/spaces_win_clover.img'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='none' io='threads' discard='unmap'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_850_EVO_1TB_S2RFNX0J606029L'/> <backingStore/> <target dev='hdd' bus='scsi'/> <alias name='scsi0-0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <controller type='usb' index='0' model='nec-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='scsi' index='0' model='virtio-scsi'> <driver queues='4' iothread='1'/> <alias name='scsi0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </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='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:65:2d:ab'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-WIN10_NVME_UEFI_Q35/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='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x43' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/Backup/vbios/Strix1080ti/AsusStrix1080TI_dump_edit.rom'/> <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='0x43' 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='0x0a' slot='0x00' function='0x3'/> </source> <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='0x41' slot='0x00' function='0x0'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc246'/> <address bus='5' device='2'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x1b50'/> <address bus='5' device='3'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> <qemu:commandline> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.speed=8'/> <qemu:arg value='-global'/> <qemu:arg value='pcie-root-port.width=16'/> </qemu:commandline> </domain> I think you have a bit to play with now 😄
  20. https://wiki.unraid.net/UnRAID_6/VM_Guest_Support#Enable_MSI_for_Interrupts_to_Fix_HDMI_Audio_Support http://forums.guru3d.com/showthread.php?t=378044 Usually it's an sound related issue passing through the audio portion of a GPU to a VM causing crackling sound. This tool helps fixing this issue. Has to be reapplied after a driver update and sometimes also after an OS update. I think I for some people it also fixes flickering video output. Edit: Btw it's advised to always pass through the audio part of the GPU
  21. @IamSpartacus To passthrough a card in slot 1 I have to specify the VBIOS for this card in the XML otherwise I have the same issue. What did you mean by that? Is it turning of your monitor or does it flicker? Did you applied the MS_fix tool inside the VM?
  22. You can have some shares specified as "cache only" and you will benefit from improved read speeds as well. Gigabit network is the limiting factor here. If you have multiple users accessing the server and have a 10gbit connection to the server you will highly benefit from cached shares. All depends on your usecase.
  23. congrats 👍 At least you're on the safe side with that 3.8 for stability.
  24. With all dockers and 2 VMs running, only browsing the web so kinda idling it sits around 38-40 °C. Some short spikes to 48-50, but thats it. Having a docker running backing up all my VMs and compressing them it sits around 50C and while gaming depends on the game. It can go up to 60C. Keep in mind this all are tdie temps. The Ryzen chips all have an offset on top of it showing as tctl. For the 1950x the offset is 27C. Some tools reporting the tctl temps only and people freak out seeing this high temperatures. The 1950x starts to throttle at 68C tdie. So I'am kinda maxed out on cooling capacity when gaming. With a stress test like Prime95 inside a VM with half the cores I can get it up to 70C still stable and without really throttling. Maybe because not the complete chip is utilised inside the VM and the throttling also depends on the power draw besides high temps. I had my old AIO Liqtech TR4 360 failling last year because of an manufacturing issue, where corrosion gunked up the rad. I saw idle temps between 40-50 and a small load and it jumped up to 70C and instant throttled down below 2GHz on all 16cores on a full windows install. So if you think your OC is limited by the temperatures you're seeing you might check which one you're reading @IamSpartacus
  25. Wait what??? ONLY 3.8GHz on water? I easy get my chip to 4GHz on air even 4.1 is possible without really throttling. I more and more think I got a golden chip. 4GHz @1.275 😂