Symon

Would be interested in this as well With a large amount of documents this is definitely very helpful .. I saw an installation description here and will propably try it like described:

Thanks for this great plugin! Currently, I'm looking for the docker Paperless and can't find it within CA. Is there a reason for this? I already tried the settings for depreciated and incompatible Apps. I'm aware that I can add repositories but I thought CA was based on hub.docker.com and I can find Paperless there. Thanks for your help

Did you plan that before buying or just luck ? Other users mentioned that the first pci slot on my MB would be covered by it .. but I might still try it if I can't get the current cooler to work properly with unRaid..

Tried to get this running with user scripts: https://github.com/leaty/camctl #!/usr/bin/env python3 import usb.core import usb.util import argparse import sys class CAM: def __init__(self, vid, pid): self.vendor = vid self.product = pid self._find() def _find(self): devices = list(usb.core.find(idVendor=vid, idProduct=pid, find_all=True)) self.device = devices[0] def claim(self): if self.device.is_kernel_driver_active(0): print('Detaching kernel driver..') self.device.detach_kernel_driver(0) def declaim(self): if not self.device.is_kernel_driver_active(0): print('Reattaching kernel driver..') usb.util.dispose_resources(self.device) self.device.attach_kernel_driver(0) def fan(self, speed): print('Setting fan speed to {}..'.format(speed)) self.device.write(1, [2, 77, 0, 0, speed, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]) def pump(self, speed): print('Setting pump speed to {}..'.format(speed)) self.device.write(1, [2, 77, 64, 0, speed, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]) # Change these if they differ from yours # See lsusb (e.g. Bus 001 Device 004: ID 1e71:170e NZXT) vid = 0x1e71 pid = 0x170e parser = argparse.ArgumentParser() parser.add_argument('-f', '--fanspeed', dest='fanspeed', type=int, default=None, help="Fan speed between 10 - 100") parser.add_argument('-p', '--pumpspeed', dest='pumpspeed', type=int, default=None, help="Pump speed between 10 - 100") args = parser.parse_args() if args.fanspeed: if args.fanspeed < 10 or args.fanspeed > 100: print('Fan speed must be between 10 - 100') sys.exit(0) if args.pumpspeed: if args.pumpspeed < 10 or args.pumpspeed > 100: print('Pump speed must be between 10 - 100') sys.exit(0) try: cam = CAM(vid, pid) cam.claim() if args.fanspeed: cam.fan(args.fanspeed) if args.pumpspeed: cam.pump(args.pumpspeed) cam.declaim() except Exception as e: cam.declaim() raise(e) I was able to install python 3 through nerd tools but am stuck at importing usb.core It would probably be possible to run a script like this periodically and adjust the fan / pump speed according to the CPU temperature. But this is not really my area so I'm kind of lost at this point now

Did you find anything? I realized now that the pump was never running faster than the base speed and thats also the reason why I got such bad cooling results .. feel kind of dumb now I think the CAM software isn't a very good solution anyways as a VM needs to be running for it to work. Bios control seems to be not possible with the kraken or I haven't found anything about it.. There are some solutions for linux described here: https://medium.com/@leinardi/how-to-control-a-nzxt-kraken-from-linux-with-a-gui-93367113f2f5 Maybe something like this could be run on Unraid itself ?

Crazy what a difference the quality of a chip can make I might try to overclock the system again with a higher CPU voltage and see if I can get it to run stable .. I also checked whether i could switch to a Noctua U14S but unfortunately it will cover PCI and Ram slots im using right now on my MB.

Do you know whether the CPU will throttle the speed itself when the temperature gets too high or will it just kill itself ? The system maybe also crashed because the CPU voltage wasn't high enough for higher temperatures ..

You are right, it will only show 50° all the time .. If you use "watch sensors" within unraid, youd should see the temperature of the CPU. With that command I can somehow see the temperature of each DIE of the CPU. Is this the same for you? What motherboard are you using? Im currently testing to configure the CPU Fan speed in the bios settings.

Before I was running the CPU at 3.875 GHz @ 1.25 V but the system wasn't stable (Unraid crashed) if I was running a stress test on 12 VCPUs on my VM. The temperature would go up to 70 ° within a minute before the whole host would crash (my guess is that the CPU would shut dow due to the high temperature). This wasn't really an issue for the daily usage as I would never have such a load on my Gaming VM so I used this for a while. Yesterday I did a Bios update and at the same time removed the OC settings and activated the Intel Turbo Boost in the Tips and Tweaks plugin. Now a single core will go up to 3.9 GHz and when doing a test with 12 cores they will be around 3.5 GHz during a stress test. The system runs stable now. Unraid Without Dockers and VM runnig: 40 - 43 ° (Single corese go up to 3.9) Unraid with multiple VM running: 45 - 50 ° (Single corese go up to 3.9) Additionally running a stress test on the gaming VM: 69° (All Cores running at 3.5) I don't know if I should switch back to OC the CPU or just leave it as it is.. I'm a bit worried to toast my CPU

Interesting .. I have similar issues (high temperatures) with a kraken x62 and a 1950. (MB Asus Rog Zenith Extreme) I always thought that it's an issue with the cooler/type and that it isn't cooling the CPU properly.. also reapplied the thermal paste. I was already thinking of getting a new one and replacing the kraken as other users seem to get much lower temperatures even with air cooling ones but was yert too lazy to do so .. To check the temperatures on thre kraken, i passed through the USB connector to the VM and used the ultility but also in the Bios the temperatures go up too high (idle and under high frequency) ...

Thanks for your help, I will create a new one to be safe Do you know if this creates problems with the Window 10 License as the hardware ID's change?

Can I change my i440FX VM to a Q35 or do I have to create a new one ?

Here is the post that you should read through : An here is my XML with my setup which is very simmilar to compare with: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='38'> <name>Monster</name> <uuid>18da3180-7fb3-6e5c-7013-963dfa89ec0a</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="freebsd.png" os="windows10"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='18'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='19'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='20'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='21'/> <vcpupin vcpu='8' cpuset='6'/> <vcpupin vcpu='9' cpuset='22'/> <vcpupin vcpu='10' cpuset='7'/> <vcpupin vcpu='11' cpuset='23'/> <emulatorpin cpuset='1,17'/> </cputune> <numatune> <memory mode='strict' nodeset='0'/> </numatune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/18da3180-7fb3-6e5c-7013-963dfa89ec0a_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>EPYC-IBPB</model> <topology sockets='1' cores='6' threads='2'/> <feature policy='require' name='topoext'/> <feature policy='disable' name='monitor'/> <feature policy='require' name='x2apic'/> <feature policy='require' name='hypervisor'/> <feature policy='disable' name='svm'/> </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='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Monster/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S39FNX0JB11716E'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.141-1.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-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='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:d6:6e:98'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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-38-Monster/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <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='0x0a' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc22a'/> <address bus='7' device='6'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc22b'/> <address bus='7' device='5'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0951'/> <product id='0x16a4'/> <address bus='7' device='4'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1532'/> <product id='0x0043'/> <address bus='7' device='2'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1e71'/> <product id='0x170e'/> <address bus='1' device='3'/> </source> <alias name='hostdev6'/> <address type='usb' bus='0' port='5'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> @david279 Do you see any other points that can be optimized besides changing passthrough disk to VirtIO?

I tried to find a place were the two setups are compared and a guide on how to pass through the disk with virtio as you described but couldn't find either... Did you test Sata vs Virtio of is VIrtio scsi just always better? Do you have a description or example on how to set it up (Primary disk is alreadry running on virtio but as a Vdisk and secondary should be passed through). I found some ressources outside of UnRaid community but am also a bit worried to messup my system

Thanks for the tip .. I will try to change this and see if the error messages will stop

Thank you.. I didn't know that .. I thought it would only work with pass through if I mount it first I will stop doing that from now on

tower-smart-20190129-1319.zipSince a few week I'm getting strange errors in the log of unraid: Jan 29 08:25:18 Tower ntfs-3g[89120]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 4096 usa_ofs: 0 usa_count: 0: Invalid argument Jan 29 08:25:18 Tower ntfs-3g[89120]: Index buffer (VCN 0x0) of directory inode 8708 has a size (24) differing from the directory specified size (4096). Jan 29 08:25:18 Tower ntfs-3g[89120]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 4096 usa_ofs: 0 usa_count: 0: Invalid argument Jan 29 08:25:18 Tower ntfs-3g[89120]: Index buffer (VCN 0x0) of directory inode 14458 has a size (24) differing from the directory specified size (4096). Jan 29 08:25:18 Tower ntfs-3g[89120]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 4096 usa_ofs: 0 usa_count: 0: Invalid argument Jan 29 08:25:18 Tower ntfs-3g[89120]: Index buffer (VCN 0x0) of directory inode 14501 has a size (24) differing from the directory specified size (4096). Jan 29 08:25:18 Tower ntfs-3g[89120]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000 size: 4096 usa_ofs: 0 usa_count: 0: Invalid argument Jan 29 08:25:18 Tower ntfs-3g[89120]: Index buffer (VCN 0x0) of directory inode 14531 has a size (24) differing from the directory specified size (4096). I managed to find out that it is related to an SSD disk which I mounted with unassigned devices and passed thorugh to a Windows 10 VM VM. <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_850_PRO_512GB_S39FNX0JB11716E'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> If I unmount and remount the disk, the errors will go away but usually reapear after a few hours While the errors are shown, I experience stutters on the VM and Games that are stored on this disk but I still have access. I can't tell whether this is because the log of unraid is getting spamed or the disk is not working properly. I already did an extended SMART test but there are now errors shown (File is attached). I'm kind of lost right now what to check next and hope somebody else has a clue tower-smart-20190129-1319.zip logs.zip

Were you guys able to solve this issue? Im currently getting simmilar errors on the log: Jan 23 20:34:34 Tower ntfs-3g[7725]: ntfs_mst_post_read_fixup_warn: magic: 0x61636f6c size: 4096 usa_ofs: 8300 usa_count: 11333: Invalid argument Jan 23 20:34:34 Tower ntfs-3g[7725]: Actual VCN (0x286b6361706e7520) of index buffer is different from expected VCN (0x0) in inode 0x389b. Jan 23 20:34:45 Tower ntfs-3g[7725]: ntfs_mst_post_read_fixup_warn: magic: 0x54484346 size: 4096 usa_ofs: 46002 usa_count: 19978: Invalid argument Jan 23 20:34:45 Tower ntfs-3g[7725]: Actual VCN (0x72657473696e6953) of index buffer is different from expected VCN (0x0) in inode 0x5cbb. Jan 23 20:34:45 Tower ntfs-3g[7725]: ntfs_mst_post_read_fixup_warn: magic: 0x2c275527 size: 4096 usa_ofs: 12891 usa_count: 23857: Invalid argument Jan 23 20:34:45 Tower ntfs-3g[7725]: Actual VCN (0x325b2c2757273d5d) of index buffer is different from expected VCN (0x1) in inode 0x3562. Jan 23 20:34:45 Tower ntfs-3g[7725]: ntfs_mst_post_read_fixup_warn: magic: 0x22657275 size: 4096 usa_ofs: 8236 usa_count: 11565: Invalid argument Jan 23 20:34:45 Tower ntfs-3g[7725]: Actual VCN (0x756e6f4274654722) of index buffer is different from expected VCN (0x0) in inode 0x364d. Jan 23 20:34:45 Tower ntfs-3g[7725]: ntfs_mst_post_read_fixup_warn: magic: 0x5b5b2d2d size: 4096 usa_ofs: 11565 usa_count: 11565: Invalid argument Jan 23 20:34:45 Tower ntfs-3g[7725]: Actual VCN (0x2d2d2d2d2d2d2d2d) of index buffer is different from expected VCN (0x0) in inode 0x4d72. Jan 23 20:34:45 Tower ntfs-3g[7725]: ntfs_mst_post_read_fixup_warn: magic: 0x2069553c size: 4096 usa_ofs: 28024 usa_count: 28268: Invalid argument Jan 23 20:34:45 Tower ntfs-3g[7725]: Actual VCN (0x6c622e7777772f2f) of index buffer is different from expected VCN (0x0) in inode 0x3840. If I unmount/mount the disk the error messages dissapear but reapear after some time .. Running 6.6.6

1950 owner 👍

Did you find out what caused the problem within the xml? (comparing the old and the new one) Update: I looked for differences from my VM to a new Windows 10 and changed <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> into <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type> Afterwards the Chache showed up correctly in CPU-Z... I have not clue for what this configuration is or why it changed afterwards but maybe this was also just related to the restart of the VM and has nothing to do with it at all 🤣

Tried it with "strict". The VM takes quite a bit longer to start but now the RAM is completely set to one node. I will have to do some tests Update: After doing a Cinebench test, memory has been moved to the other node again Update2: Did a Cinebench test on my wives VM (which is on the same node as GPU / cache disks) and the memory stayed on the same node. So my guess is that 'strict' only works if the node is connected to the storage (cache/passthorugh discs) as well.

For me it works this way . If I use interleave, it uses the configured node for most of the RAM.. (10 MB always seem to get taken from the other node) If I use strict, the VM takes longer to boot but all of the RAM is on one node. Same as you, I have the problem that my cache disks are on a differente node than my GPU.. For now I decided to go with the node that the GPU is connected to for the gaming VM. My configuration currently looks now like this: (Cores 1-7, 18-23 are isolated from unraid) <vcpu placement='static'>12</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='18'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='19'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='20'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='21'/> <vcpupin vcpu='8' cpuset='6'/> <vcpupin vcpu='9' cpuset='22'/> <vcpupin vcpu='10' cpuset='7'/> <vcpupin vcpu='11' cpuset='23'/> <emulatorpin cpuset='1,17'/> </cputune> <numatune> <memory mode='strict' nodeset='0'/> </numatune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/18da3180-7fb3-6e5c-7013-963dfa89ec0a_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>EPYC-IBPB</model> <topology sockets='1' cores='6' threads='2'/> <feature policy='require' name='topoext'/> <feature policy='disable' name='monitor'/> <feature policy='require' name='x2apic'/> <feature policy='require' name='hypervisor'/> <feature policy='disable' name='svm'/> </cpu> On the second node I run 6 x Windows 2016 servers and the Win 10 VM of my wife (with numatune)

Tried these points on my computer and finally solved the stutter problems while gaming (TR1950) What I did: Changed Bios Ram settings (Asus Rog Zenith Extreme): Advanced > DF common options > Memory interleaving: Auto > Channel Added CPU patch: <cpu mode='custom' match='exact' check='partial'> <model fallback='allow'>EPYC-IBPB</model> <topology sockets='1' cores='3' threads='2'/> <feature policy='require' name='topoext'/> </cpu> And Numatune: <numatune> <memory mode='interleave' nodeset='1'/> </numatune> Thanks for your help guys! 👍

The whole testing just shows me how much I'm not undestanding yet .... But thats also why I built this system to learn something new 😁 I still feel like there was a performance drop when upgrading from 6.5.X to 6.6.2 but I did not do enough performance test before such as I could verfiy that. It just feels like it from the feeling in games. I'm using the default UMA mode. How do you check what memory the VM is currently using?

I pass through an SSD for my games partition (Samsung 850 Pro). I just checked the Samsung magician tool and it doesn't recognize the drive. Any Idea how to fix that? The Bus of the disk is Sata.