ryoko227

Hey Djoss, thank you for the responce. I ran the above, and while it seemed to install, I still have the "?" marks after a restart of the docker. Even if I change the application language to Japanese in options, the file names still show up "?" EDIT - ps, the blank file/folder names are because I redacted them from the image

After a reboot of the server those mem errors cleared out, only thing erroring at home now is the vmwrites, so I think we are in the clear ^_^v

Home server showed up some errors as well. Seemed to be related to memory, multiple entries in the log Jan 19 21:41:53 BEAST kernel: EDAC sbridge: CPU SrcID #0, Ha #0, Channel #0 has DIMMs, but ECC is disabled Jan 19 21:41:53 BEAST kernel: EDAC sbridge: Couldn't find mci handler Jan 19 21:41:53 BEAST kernel: EDAC sbridge: Couldn't find mci handler Jan 19 21:41:53 BEAST kernel: EDAC sbridge: Failed to register device with error -19. And the vmwrite error, had an entry for each VM Jan 19 21:42:16 BEAST kernel: br0: port 3(vnet1) entered forwarding state Jan 19 21:42:16 BEAST kernel: vmwrite error: reg 810 value 0 (err 0) Jan 19 21:42:16 BEAST kernel: CPU: 12 PID: 7591 Comm: CPU 0/KVM Not tainted 4.14.13-unRAID #1 Jan 19 21:42:16 BEAST kernel: Hardware name: MSI MS-7885/X99A SLI PLUS(MS-7885), BIOS 1.D0 07/15/2016 Jan 19 21:42:16 BEAST kernel: Call Trace:

Everything seems ok so far, noticed some of the vmwrite error things popping up, so I'll place it here. Jan 19 14:46:57 YES-MEDIASERVER dnsmasq-dhcp[11941]: read /var/lib/libvirt/dnsmasq/default.hostsfile Jan 19 14:46:57 YES-MEDIASERVER kernel: virbr0: port 1(virbr0-nic) entered disabled state Jan 19 14:46:57 YES-MEDIASERVER kernel: vfio-pci 0000:02:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Jan 19 14:46:57 YES-MEDIASERVER kernel: br0: port 2(vnet0) entered blocking state Jan 19 14:46:57 YES-MEDIASERVER kernel: br0: port 2(vnet0) entered disabled state Jan 19 14:46:57 YES-MEDIASERVER kernel: device vnet0 entered promiscuous mode Jan 19 14:46:57 YES-MEDIASERVER kernel: br0: port 2(vnet0) entered blocking state Jan 19 14:46:57 YES-MEDIASERVER kernel: br0: port 2(vnet0) entered forwarding state Jan 19 14:46:57 YES-MEDIASERVER kernel: vmwrite error: reg 810 value 0 (err 0) Jan 19 14:46:57 YES-MEDIASERVER kernel: CPU: 8 PID: 12092 Comm: CPU 0/KVM Not tainted 4.14.13-unRAID #1 Jan 19 14:46:57 YES-MEDIASERVER kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X99M Extreme4, BIOS P3.20 08/16/2016 Jan 19 14:46:57 YES-MEDIASERVER kernel: Call Trace: Jan 19 14:46:57 YES-MEDIASERVER kernel: dump_stack+0x5d/0x79 Jan 19 14:46:57 YES-MEDIASERVER kernel: kvm_lapic_reset+0x278/0x292 [kvm] Jan 19 14:46:57 YES-MEDIASERVER kernel: kvm_create_lapic+0xa5/0xb2 [kvm] Jan 19 14:46:57 YES-MEDIASERVER kernel: kvm_arch_vcpu_init+0xd9/0x22d [kvm] Jan 19 14:46:57 YES-MEDIASERVER kernel: kvm_vcpu_init+0xcd/0xee [kvm] Jan 19 14:46:57 YES-MEDIASERVER kernel: vmx_create_vcpu+0x54/0xd5c [kvm_intel] Jan 19 14:46:57 YES-MEDIASERVER kernel: ? pick_next_task_fair+0x102/0x3d9 Jan 19 14:46:57 YES-MEDIASERVER kernel: kvm_vm_ioctl+0x13b/0x66c [kvm] Jan 19 14:46:57 YES-MEDIASERVER kernel: ? __schedule+0x4ac/0x4e9 Jan 19 14:46:57 YES-MEDIASERVER kernel: vfs_ioctl+0x16/0x23 Jan 19 14:46:57 YES-MEDIASERVER kernel: do_vfs_ioctl+0x4f1/0x504 Jan 19 14:46:57 YES-MEDIASERVER kernel: SyS_ioctl+0x39/0x55 Jan 19 14:46:57 YES-MEDIASERVER kernel: entry_SYSCALL_64_fastpath+0x1e/0x81 Jan 19 14:46:57 YES-MEDIASERVER kernel: RIP: 0033:0x148614277727 Jan 19 14:46:57 YES-MEDIASERVER kernel: RSP: 002b:000014860ff72228 EFLAGS: 00000246 Jan 19 14:46:57 YES-MEDIASERVER kernel: vmwrite error: reg 810 value 0 (err 0) Jan 19 14:46:57 YES-MEDIASERVER kernel: CPU: 0 PID: 12097 Comm: CPU 1/KVM Not tainted 4.14.13-unRAID #1 Jan 19 14:46:57 YES-MEDIASERVER kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X99M Extreme4, BIOS P3.20 08/16/2016 Jan 19 14:46:57 YES-MEDIASERVER kernel: Call Trace: Jan 19 14:46:57 YES-MEDIASERVER kernel: dump_stack+0x5d/0x79 Jan 19 14:46:57 YES-MEDIASERVER kernel: kvm_lapic_reset+0x278/0x292 [kvm] Jan 19 14:46:57 YES-MEDIASERVER kernel: kvm_create_lapic+0xa5/0xb2 [kvm] Jan 19 14:46:57 YES-MEDIASERVER kernel: kvm_arch_vcpu_init+0xd9/0x22d [kvm] Jan 19 14:46:57 YES-MEDIASERVER kernel: kvm_vcpu_init+0xcd/0xee [kvm] Jan 19 14:46:57 YES-MEDIASERVER kernel: vmx_create_vcpu+0x54/0xd5c [kvm_intel] Jan 19 14:46:57 YES-MEDIASERVER kernel: ? pick_next_task_fair+0x102/0x3d9 Jan 19 14:46:57 YES-MEDIASERVER kernel: kvm_vm_ioctl+0x13b/0x66c [kvm] Jan 19 14:46:57 YES-MEDIASERVER kernel: ? __schedule+0x4ac/0x4e9 Jan 19 14:46:57 YES-MEDIASERVER kernel: vfs_ioctl+0x16/0x23 Jan 19 14:46:57 YES-MEDIASERVER kernel: do_vfs_ioctl+0x4f1/0x504 Jan 19 14:46:57 YES-MEDIASERVER kernel: SyS_ioctl+0x39/0x55 Jan 19 14:46:57 YES-MEDIASERVER kernel: entry_SYSCALL_64_fastpath+0x1e/0x81 Jan 19 14:46:57 YES-MEDIASERVER kernel: RIP: 0033:0x148614277727

I was just looking for a file (someone deleted something they shouldn't have) and noticed that none of my files/folders written in Japanese are showing up in the backup. I went in to Add Backup Set and any folder/file with Japanese is showing up as a "?" for the character. How do I add Japanese language support to the docker? Or, could I request that Japanese character support be added to the docker? The files look like this

You can find the plugin I reference in Community Apps - Apps tab, search for usb. It will be the only thing that shows up. Its full name is "Libvirt Hotplug USB". Ya, mine still is pretty much off and on. Sometimes it works on its own. Sometimes I can get it to connect the first try with the above plugin. Sometimes I have to attach and detach (via VM panel) like 5 times to get it to work. Its super hit and miss.

Updated- first log in attempt seemed to hang. So I stopped and restarted the docker. 2nd, 3rd, and 4th attempts gave me a blank white screen with a "could not connect to server error." Retarted this time and got the login prompt again. Logged in and the program began syncing the files again. Hopefully everything will go well without a need to reupload. Posting this just to doc my experiences, will update if there are any issues EDIT - So after it synced the files the total size was significantly less than previously. I had no compression selected before, so Im wondering if they are forcing compression now on their side of things? It seems like all of my folders are still correctly selected, so I'm not sure what might have changed (1.7TB ->.5TB) EDIT2 - I may have missed it, but looking deeper into the options it would seem that we no longer have the option to change the compression size of our backups.

Update - started the VM this morning and the mouse worked without my manually attaching it via the Libvirt Hotplug USB plugin. So now its not an issue of not working, but working intermittently. Will update this post if it works again on tomorrow's bootup. Update2 - Works intermitently. Sometimes it attaches at boot, sometimes it doesn't. Not sure where to go from here, diags and xmls posted above. Any help would be appreciated.

Additional information - After reading through some of the libvirt docs over here related to the HostDevSubsys, it would seem for USB devices that only the vendor id/product id OR the address can be called. Unfortunately, as JonP noted in this post, using the address isn't bulletproof as it can change with system reboots. I may have to use that as a work around though for now as the server itself isn't rebooted very often, but the VM is daily. When I ran udevadm info --name=/dev/bus/usb/003/008 --query=property for the mouse when it was connected, the results are below. I just wish I could call it with something like... <source> <serial_short id='F91C93FC280029'/> I'm open to any suggestions, thanks! BUSNUM=003 DEVNAME=/dev/bus/usb/003/008 DEVNUM=008 DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-12 DEVTYPE=usb_device DRIVER=usb ID_BUS=usb ID_MODEL=G9_Laser_Mouse ID_MODEL_ENC=G9\x20Laser\x20Mouse ID_MODEL_FROM_DATABASE=G9 Laser Mouse ID_MODEL_ID=c048 ID_REVISION=5000 ID_SERIAL=Logitech_G9_Laser_Mouse_F91C93FC280029 ID_SERIAL_SHORT=F91C93FC280029 ID_USB_INTERFACES=:030102:030000: ID_VENDOR=Logitech ID_VENDOR_ENC=Logitech ID_VENDOR_FROM_DATABASE=Logitech, Inc. ID_VENDOR_ID=046d MAJOR=189 MINOR=263 PRODUCT=46d/c048/5000 SUBSYSTEM=usb TYPE=0/0/0 USEC_INITIALIZED=1535780383

Using a Logitech G9 Laser mouse from forever ago. When the Win10 VM starts the mouse isn't working, if I add the mouse via the Libvirt Hotplug USB plugin, it works completely fine. I have added the mouse via the unRAID gui and have not had any issues using any different mice, just this one. The system in question is the office server in my sig. I will post the xml snippets below. It seems to not be passing through the mouse based off the vendor/product IDs? Might anyone have any suggestions to force this mouse to pass through properly to the VM on bootup? I regularly shutdown this VM, and its frustrating to not have a mouse at boot. Thanks in advance! Pre-boot xml <domain type='kvm'> <name>YES-MEDIAPC</name> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>6291456</memory> <currentMemory unit='KiB'>6291456</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>10</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='4'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='6'/> <vcpupin vcpu='4' cpuset='7'/> <vcpupin vcpu='5' cpuset='11'/> <vcpupin vcpu='6' cpuset='12'/> <vcpupin vcpu='7' cpuset='13'/> <vcpupin vcpu='8' cpuset='14'/> <vcpupin vcpu='9' cpuset='15'/> <emulatorpin cpuset='0,8'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/a5b29b54-1788-1efa-b192-33c0a178cb60_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='host-passthrough'> <topology sockets='1' cores='5' threads='2'/> </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='directsync' io='native'/> <source file='/mnt/user/vDisks/YES-MEDIAPC/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <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/virtio-win-0.1.140.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:0e:f8:05'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <rom bar='on' file='/boot/vbios.rom'/> <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='0x00' slot='0x1b' function='0x0'/> </source> <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='0xc048'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1c4f'/> <product id='0x0002'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </memballoon> </devices> </domain> Post mouse addition with the Libvirt Hotplug USB plugin <domain type='kvm' id='3'> <name>YES-MEDIAPC</name> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>6291456</memory> <currentMemory unit='KiB'>6291456</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>10</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='4'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='6'/> <vcpupin vcpu='4' cpuset='7'/> <vcpupin vcpu='5' cpuset='11'/> <vcpupin vcpu='6' cpuset='12'/> <vcpupin vcpu='7' cpuset='13'/> <vcpupin vcpu='8' cpuset='14'/> <vcpupin vcpu='9' cpuset='15'/> <emulatorpin cpuset='0,8'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/a5b29b54-1788-1efa-b192-33c0a178cb60_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='host-passthrough'> <topology sockets='1' cores='5' threads='2'/> </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='directsync' io='native'/> <source file='/mnt/user/vDisks/YES-MEDIAPC/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='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/virtio-win-0.1.140.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> <controller type='usb' index='0' model='nec-xhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </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:0e:f8:05'/> <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-3-YES-MEDIAPC/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='0x02' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom bar='on' file='/boot/vbios.rom'/> <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='0x00' slot='0x1b' function='0x0'/> </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='0xc048'/> <address bus='3' device='7'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1c4f'/> <product id='0x0002'/> <address bus='3' device='3'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc048'/> <address bus='3' device='8'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> yes-mediaserver-diagnostics-20171106-1622.zip

Completely forgot about doc'n my experiences with migration. I came over from the gfjardim version and followed the instructions. All of my settings came over smoothly, and had no issues getting things up and running. I did have to point the backup directory which end up causing a re-upload. Not an issue though as it was only 2TB worth anyways and I keep nightly backups using duplicati as well. Since the migration I have to say that I am loving this image. In fact, now the files that have Japanese characters used in their names can be seen properly! Only hickup is sometimes when I load the webui it the Crashplan Pro splash screen says something about not being able to find the backend or w/e, but I just click try again and it loads up with no issues. Just wanted to say thank you very much for your hard work Djoss!!

From what I found, it seems that the controller is working in ES. Pressing F1 while a ROM is running though brings up the RetroArch (think thats what its called) menu. Its there that for some reason in my case that the controller is going crazy. Disconnect the controller and the keyboard works fine, connect the controller and it gets like quadruple inputs per button press. Not sure about the amiga stuff though, sorry.

Hey grid, awesome guide! Wanted to say that I got everything setup the way you mentioned and even got my DS4 controllers connected via my passed through BT dongle. Sound seems to work for some ROMs, but not others. Im guessing thats probably just an ES or ROM file issue. Keyboard inputs seemed to work, but I did run into a bit of an issue that I have a question for you on. Were you able to actually use your DS4s inside any of the emulated games? Both of my DS4s work flawlessly outside the emulator in Kodi. Their buttons, sticks, touch pad, etc. all fine. I can open the emulator menu and configure the controllers with every button being recognized there as well. However, every ROM I open since adding the controllers, I end up with no input working. Even the keyboard won't input anymore, making me have to force stop the VM. I'm curious as to how you faired in this area and if you have any suggestions for me. Thanks mate!

Looking forward to hearing what your findings are on this as I just saw the email myself and my first thought was to come and check here, lol. Hope your testing goes well!

And we have a winner! Thank you Squid ^_^v

This is probably a stupid question with a super simple answer that for the life of me I can't seem to find an answer for. Namely, how do you create a linux vm from an iso that doesn't autostart, but instead takes you the to uefi shell? I have tried adjusting the boot device and boot order in the "bios" of the vm with no luck. I have a number of iso files from various different linux distros that do this and I'm not sure how to go about installing them. Pixel and Point are the first two that come to mind. All of the major distros like deb, ubuntu, mint, neon, etc load straight into the grub loader, so it would seem to be iso specific. Only thing I can think of is that perhaps the iso itself wasnt created to be bootable? If that is the case, how would I go about making it bootable? Any help would be appreciated.

This has been a reaccuring problem for a while on my gaming VM. Sometimes after only a few minutes of play, sometimes after a few hours of play. The VM will seemingly at random lock up and become unresponsive. The exact error I see in the syslog is ul 6 21:11:33 BEAST kernel: vfio_bar_restore: 0000:02:00.0 reset recovery - restoring bars This refers to the GTX960 in the 1st 2nd PCIe slot. This card is using the rom bar method which has a rom pulled from the 2nd identical gpu in the 2nd PCIe. I think this issue has been with me intermitently for quite some time now but have never been able to pindown any rhyme or reason to it. Many versions of unRAID ago, it would bring down the whole server. Luckily now though, after a crash a simple force stop and start will bring the VM back up. Open to any and all help on this. Diags attached. System for my house with specs in the sig. Thanks in advance! beast-diagnostics-20170706-2112.zip EDIT/CORRECTED- the VM is run headless (HDMI out to TV but rarely used). All interaction is either via Steam In-Home Streaming, or NoMachine. Here is also the VM xml in case its needed. <domain type='kvm' id='3'> <name>VM-GAMING</name> <uuid>####sANDletters#$@#$</uuid> <~~~~not important ^_^v <description>Gaming VM</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='9'/> <vcpupin vcpu='2' cpuset='10'/> <vcpupin vcpu='3' cpuset='11'/> <vcpupin vcpu='4' cpuset='20'/> <vcpupin vcpu='5' cpuset='21'/> <vcpupin vcpu='6' cpuset='22'/> <vcpupin vcpu='7' cpuset='23'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/3e511485-5f55-c443-3968-0015259b40a3_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='host-passthrough'> <topology sockets='1' cores='4' threads='2'/> </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/nvme/vDisks/VM-GAMING/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='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/virtio-win-0.1.135.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> <controller type='usb' index='0' model='nec-xhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </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:98:03:dd'/> <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-3-VM-GAMING/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='0x02' 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='0x02' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </memballoon> </devices> <seclabel type='none' model='none'/> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>

Sorry for taking so long to get back to your post on this, but thank you bonienl! Worked like a charm, +1 for all you do here for everyone!!!

Oh no worries Squid, I actually liked that the message was there. It let me know that something wasn't 100% on par. I was more curious if the plug-in was supposed to clear out the custom cron listing, or if I had borked something along the way, lol. Thank you for clearing that up for me though ^_^v

Possible Bug, possible user error: Was testing out rsync with this and made a super simplistic script called "rsync test". I told it to run in the background and had set it to run every minute while testing. When I got done testing, I deleted the script and forgot about it for a few days. Today I rebooted the server and later manually clicked mover, now every minute I have “Jun 2 16:45:01 YES-MEDIASERVER root: User Scripts: /boot/config/plugins/user.scripts/scripts/rsync test/script not found” popping up in the log file. Though, User Scripts no long has the script, so looks like it wasn’t completely removed. EDIT: Was mistaken, checked the actual sys log and found that it had been running ever since the reboot this morning. Found the cron job for the deleted script was still listed in... /boot/config/plugins/user.scripts/customSchedule.cron So it looks like when I deleted the script it didn't remove the cron entry.

Just a quick question about which would be recommended for my use case. I have my Games share (cache only) mirrored on cache and user0 right now. Since the home internet is obnoxiuously slow, and since that cache drive is in a btrfs raid0 pool, I thought a local "backup" would be a good idea. Since the games I play regularly need updates, I'm wondering wether I should use User Scripts plugin running something like.... rsync -av /mnt/cache/Games/ /mnt/user0/Games/ or if I should setup rclone following gridrunner's guide, just using a local directory. My concerns are as follows. Testing rsync in the terminal seemed to lock up putty. When I tried it from the server term it tossed a ton of errors about the media being unavailable, so I don't know if it's even working correctly. rclone syncs simultaniously was my impression, but having unreliable internet I am a bit worried about it syncing corrupt files. Anyways, you guys are always full of good knowledge and ideas so I thought it better to ask before I just start galavanting down a path.

This is such a cool post and great discussion. I love it when you guys start talking about all the different ways you have your systems configured, it always helps me find new ways of doing things. I would have never thought to use a hardware array to "create" a single large parity or cache drive outside of unRAID on my own. In fact, I have often wondered what I would do when I wanted to increase my array capacity as I'm starting off with a 3TB parity size limit. I have just never been able to justify to myself the cost of a larger drive solely for parity sake. Knowing now that I can just slap a few of those 3TB drives together later on is really helpful. That solves that future problem, thanks all!

Updated the office server today, no issues to note so far. Will update the post once I got the home server updated as well. EDIT- Home server seems to have updated with no issues as well. TY LT

+1 for multiple cache pools. For my specific use case, I have my VMs currently on my nvme drive which is loaded up via the go file at the moment. The cache pool is being utilized by my btrfs raid0 ssd pool. I like that UD "sees" my nvme, but I don't like not having temps on it, and TBH (while I already have it setup) having to add things in a round about way feels.... "dirty" I believe is the word someone else used, lol. Multiple cache pools please!

2 servers updated, no issues so far.