NeoID

Thanks. Please post any suggestions on the GitHub page if you think it can benefit others. I know the docs (or the lack thereof) is a mess, but great you got it to work.

Multiple Unraid Array Pools! I would pay a premium just so I could convert my unRAID servers to DAS instead and connect all servers to a single one.

Do you use the Compose.Manager plugin for docker-compose over GUI templates and wish for a tool that can effortlessly update all or specific containers with a single command? This script might be just what you need! While not strictly an "Unraid script," I've successfully employed it on my two Unraid hosts for the past few years and wouldn't consider going back to running docker-compose commands directly. My transition to Unraid was driven by the flexibility to mix different drives and independently spin them down. Since I already had numerous docker-compose files, I opted not to migrate to Unraid's templates. I prefer maintaining clean docker-compose configurations, avoiding unnecessary ties to OS-specific settings. Thanks to the fantastic "Compose.Manager" and "Python" plugin, seamlessly integrating my docker-update script with Unraid was a breeze. For those interested, I've shared it on GitHub: https://github.com/IDmedia/docker-update-script

I'm running two 4U servers (Norco/Inter-Tech) with Unraid and since they are placed near the bedrooms I had to come up with a solution to reduce the noise. The solution was to turn on disk spin down and create a custom script for controlling the fans. I have now used this script for a few years and have become really happy with it, so I think it's time to share it with you guys hoping you enjoy it as much as I and my friend does. There exists some scripts on this forum already, but I had issues with either the disks being waken up unnecessarily or the script not supporting enough fans. It's not hard to "install" thanks to the awesome "User Scripts" plugin, but it takes some time to figure out the correct path to fan headers. Please not that some motherboard also switches these around if you install new hardware such as a NVMe. Source code and more information: https://github.com/IDmedia/fan-control-script

Thanks a ton for the fast reply. It seems to work again now And yes, it seems I needed to install it in order to get my Huawei to work properly with USB modeswtich running in docker.

Upgraded to Unraid 6.12.5 and got error messages that the "USB Manager Serial Options Addon" couldn't be installed. Trying to install it returns the following error. I assume it's not compatible? plugin: installing: usb_manager_serial_options_addon.plg Executing hook script: pre_plugin_checks plugin: downloading: usb_manager_serial_options_addon.plg ... done Executing hook script: pre_plugin_checks ---------------------Downloading usb serial options, please wait...!------------------------ -----------------This could take some time, please don't close this window!----------------- -----------ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR--------------- ----------------------------Can't download usb serial options -------------------------------- plugin: run failed: '/bin/bash' returned 1 Executing hook script: post_plugin_checks

I've installed the latest version of "Intel GPU TOP" and "GPU Statistics". I'm using an Intel Xeon E-2176G (Coffee Lake) with Intel® UHD Graphics P630. Running intel_gpu_top seems to work as intended, but the UI doesn't show any information, just "N/A". Strange thing is that if I take the output of the command below and run that through the json_decode() function in Intel.php it seems to parse it. Any ideas? Pulling up Chrome devtools gives me a 303 and 302-error: {"clock":"N\/A","fan":"N\/A","memclock":"N\/A","memutil":"N\/A","memused":"N\/A","power":"N\/A","powermax":"N\/A","rxutil":"N\/A","txutil":"N\/A","temp":"N\/A","tempmax":"N\/A","util":"N\/A","error":[{"code":303,"message":"Vendor data valid, but not enough received.","extra":"Count: 1"},{"code":302,"message":"Vendor command returned unparseable data.","extra":""}]} ~# lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics P630] ~# timeout -k .500 .400 intel_gpu_top -J -s 250 { "period": { "duration": 90.608790, "unit": "ms" }, "frequency": { "requested": 0.000000, "actual": 0.000000, "unit": "MHz" }, "interrupts": { "count": 11.036457, "unit": "irq/s" }, "rc6": { "value": 0.000000, "unit": "%" }, "power": { "GPU": 0.000000, "Package": 72.905686, "unit": "W" }, "imc-bandwidth": { "reads": 3889.498243, "writes": 392.686080, "unit": "MiB/s" }, "engines": { "Render/3D/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Blitter/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "Video/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" }, "VideoEnhance/0": { "busy": 0.000000, "sema": 0.000000, "wait": 0.000000, "unit": "%" } }, "clients": { } } Parsed: Array ( [0] => Array ( [period] => Array ( [duration] => 87.503119 [unit] => ms ) [frequency] => Array ( [requested] => 0 [actual] => 0 [unit] => MHz ) [interrupts] => Array ( [count] => 11.428164 [unit] => irq/s ) [rc6] => Array ( [value] => 0 [unit] => % ) [power] => Array ( [GPU] => 0 [Package] => 68.086998 [unit] => W ) [imc-bandwidth] => Array ( [reads] => 3272.466358 [writes] => 580.776591 [unit] => MiB/s ) [engines] => Array ( [Render/3D/0] => Array ( [busy] => 0 [sema] => 0 [wait] => 0 [unit] => % ) [Blitter/0] => Array ( [busy] => 0 [sema] => 0 [wait] => 0 [unit] => % ) [Video/0] => Array ( [busy] => 0 [sema] => 0 [wait] => 0 [unit] => % ) [VideoEnhance/0] => Array ( [busy] => 0 [sema] => 0 [wait] => 0 [unit] => % ) ) [clients] => Array ( ) ) [1] => Array ( [period] => Array ( [duration] => 343.388793 [unit] => ms ) [frequency] => Array ( [requested] => 0 [actual] => 0 [unit] => MHz ) [interrupts] => Array ( [count] => 0 [unit] => irq/s ) [rc6] => Array ( [value] => 0 [unit] => % ) [power] => Array ( [GPU] => 0 [Package] => 48.034494 [unit] => W ) [imc-bandwidth] => Array ( [reads] => 2443.961719 [writes] => 278.706568 [unit] => MiB/s ) [engines] => Array ( [Render/3D/0] => Array ( [busy] => 0 [sema] => 0 [wait] => 0 [unit] => % ) [Blitter/0] => Array ( [busy] => 0 [sema] => 0 [wait] => 0 [unit] => % ) [Video/0] => Array ( [busy] => 0 [sema] => 0 [wait] => 0 [unit] => % ) [VideoEnhance/0] => Array ( [busy] => 0 [sema] => 0 [wait] => 0 [unit] => % ) ) [clients] => Array ( ) ) ) Screenshots:

I'm having the same issue. I managed to hide the visual elements and you can read about it here: https://www.reddit.com/r/unRAID/comments/rlbubo/hide_update_info_from_the_docker_page_when_using/ But I have not found any way of disabling the notifications only for docker containers. Is there a way to do so? I have my own python-script to update all on one go and the notification doesn't seem to go away even though the container has been updated. I have 50+ docker containers and I'm not really into rewriting them as I prefer portability. I like FCP, would it be possible to ignore all container updates somehow so I don't have to ignore them on a per-container basis?

Awesome! I also struggled a lot with this yesterday!

Turns out that setting VSync to ON and rebooting Unraid did the trick...

Hi, I'm running two Windows 10 VMs on the latest version of Unraid 6.2. It works well with gaming on a normal PC monitor, but on my TV I'm experiencing severe screen tearing. I've tried to turn Vsync on in the Nvidia control panel, but it does't seem to solve it. Especially in gaming or movies in fast scenes are almost unbearable. I've also tried to turn on Vsync in the particular games/Kodi. Other people having this issue?

Is it possible to hide multiple PCI USB controllers from the host that have the same product/vendor ID? lspci -n gives me: 06:00.0 0c03: 104c:8241 (rev 02) 07:00.0 0c03: 104c:8241 (rev 02) I've added this to syslinux.cfg: pci-stub.ids=104c:8241 However, one of the cards is still visible. Am I supposed to add the same again using: pci-stub.ids=104c:8241,104c:8241 ?

I'm wondering if this issue can be related to having two GPU's with the same name. Not sure if anyone else here has this kind of configuration... The issue seems to be worse if I start a game on both VMs at the exact same time... so maybe UnRaid can't handle that as it struggles with USB devices with the same name/vendor ID?

The pause icon means the VM has gone into sleep mode. I recommend to read and follow this page: http://lime-technology.com/wiki/index.php/UnRAID_6/VM_Guest_Support#Post-Install_Tuning

Hi guys, I'm experiencing som really weird issues after configuring my new rig. I've tried to swap the GPU, reinstall the VM/driver, but that doesn't change anything. If I remember right I also tried to change the PCI port with no effect. Pretty sure it's not a hardware issue, but software/BIOS/sleep related. I'm not using ACS for the time being, so I've one GPU in a PCI3 port and the other in a PCI2 port since they are in different IOMMU groups. GPU: Asus GTX 1070 UnRaid: 6.2 RC3 The only two issues I have are: 1. Screen flickering, especially when the mouse is hovering over the taskbar window preview. This starts off small and becomes worse and worse depending on how long I keep the mouse over the window preview or move the mouse around. When it first starts it will quickly become so bad that the driver will crash. A reboot fixes this immediately however, so I don't think that this is a HW issue even though it looks quite similar to bad VRAM. Screenshot: http://i.imgur.com/iO8biYd.jpg 2. Mouse pointer disappearing. When leaving a VM for some time, the mouse pointer disappears for some reason or another. I can still use it, but just not see it. For now I've configured the screen to go to sleep (but not the VM), so it might be related to that, but not sure yet. A reboot fixes the issue immediately. Anyone experienced the same issues?

I've been playing around with this setup for hours and struggled to get both VMs to work. While one of the machines work (using CPU core 3 and 7 only), the other VM using core 1,2,5 and 6 did not. While I managed to install Windows 10 on it, it stops right after the setup is complete, only displaying the Windows flag on the screen (boot screen). Once I change it to only use core 5 and 6 it boots... is there any logic that explains this behavior? I've also moved my GPU to other PCI slots and disabled ACS Override since it caused read errors on my SSD cache for some reasons... I thought I shouldn't use Core 0, since UnRaid favoured it, but is it really core 1 I should worry? Is there another explanation and can I utilize my cores in a better way or just stick using two cores per VM? My system has the following cores: CPU 0 CPU 1 CPU 2 CPU 3 CPU 4 CPU 5 CPU 6 CPU 7

I think I may have figured it out... For some reason I had to go to the BIOS and change the GPU setting from auto to CPU GPU. Even tough it worked with my AMD GPU, it didn't work with Nvidia...

Hi, I've just brought two Asus GTX 1070 Founders edition GPUs (in order to create two VMs) and want to replace my old AMD GPU which has been working great until now. I've installed one of the Nvidia pci cards, but when I try to turn the VM back on, the screen remain black. I've also tried to remove and re-create the VM without any luck. I'm able to turn the VM on in the GUI, but nothing happens on the monitor. I can't find any errors in UnRaid, so hope anyone here has some suggestions. Version: unRAIDServer-6.2.0-rc3 Enable PCIe ACS Override: Yes My XML: <domain type='kvm' id='1'> <name>Kodi</name> <uuid>a908771e-08a4-5e6a-6e28-5644bce7c59d</uuid> <description>Kodi and gaming vm connected to TV</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>13107200</memory> <currentMemory unit='KiB'>13107200</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='6'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/a908771e-08a4-5e6a-6e28-5644bce7c59d_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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/Kodi/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Kodi/vdisk2.img'/> <backingStore/> <target dev='hdd' bus='virtio'/> <alias name='virtio-disk3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/os/en_windows_10_multiple_editions_x64_dvd_6846432.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.118-2.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='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:c5:72:ca'/> <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 port='0'/> <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-Kodi/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> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' 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='0x01' 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='0xc52b'/> <address bus='3' device='2'/> </source> <alias name='hostdev2'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </memballoon> </devices> </domain> Edit: Not sure if this means anything:

As far as I can see, editing the VM through the UI will "undo" the changes to the XML file. Wouldn't USB assignment on a port level be a better choice than the current one? I just assume that this is an issue most people will face eventually. If you for example add two Logitech unifying receivers or Xbox360 adapters they will obviously have the same name. I assume most people would rather use specific ports for VMs instead of having to worry about this issue? Edit: Some sort of setting on the VM page that toggles the format vendor/product or address would be awesome.

I have a ASUS Z97-A motherboard with 3 PCIe ports. Two of them are PCIe 3 while the last one is PCIe 2. My issue is that when I have two GPU's connected to the two PCIe 3 port this message appears when trying to boot the second VM: However, everything works if one card is moved to the PCIe 2 slot. Unfortunately there isn't a lot of space in the case and I'm trying to figure out a way to make the second PCIe 3 port work. I've tried changing all the GPU-related settings in the BIOS without any success. Is this a known issue with a simple fix or do I have to move the GPU to PCIe 2 again? Edit: I assume that both PCIe slots being presented as "/sys/kernel/iommu_groups/1/" is the real issue here. Is there any setting to split them? I've heard "PCIe ACS Override" could, but with a performance penalty(?). System Devices says the following:

@gridrunner: Thanks for the comment. I've been trying the stable release and it seems to work, but I'm currently waiting for my GTX 1070 to arrive so I'm not sure how well that works until it does. I've also tried a AMD R9 390, but the reset bug drives me crazy and makes it unusable. I assume I'll give the beta a try and downgrade if I encounter any issues instead of the other way around. @testdasi: Could be hardware specific? @Lebowski: A valid point. The only thing I'm currently concerned about is the improved NVIDIA support and the (hopefully) better handling of USB devices. Especially if you have multiple USB devices with the same name is a bit messy. It should not only display the name of the device, but also the port/path.

Hi, I'm new to unRAID and in the process of configuring it as a "Two gamers, one CPU" build. That in mind I'm seeing that the beta has some major improvements to virtual machines. Especially since I intend to use two Nvidia GTX cards... So my question is... should I start with the beta now that I start from scratch anyway or isn't it stable enough for normal use? Will it be possible to upgrade to stable once 6.2 is released?

Hi, I'm new to unRAID and have just brought new hardware for a "2 Gamers 1 CPU"-build. I'm using a new R9 390 (Strix) and an old 7870 GPU. While my old GPU works perfectly, the new one sometimes goes black and doesn't recover unless I reboot unRAID. Windows event logger only says that the hardware crashed with no further useful info. I doubt the issue is my PSU (1000W) or my motherboard as only the VM using the 390 card is affected by this. Anyone else having issues with this card? Are there any settings I should be aware off? I'm wondering if I should take it back to the store and wait for an Nvidiea 1070 instead...