Turnspit

Cheers! My remote backup server, connected via OpenVPN, had suddenly lost its connectioction on 14.07. somwhere around 22:00. When checking out what was wrong, I saw that the OpenVPN docker had suddenly stopped - which has never happened before in 1+ year. After starting it again manually, every was up and running remotely again. I took a look at the logs, but they didn't enlighten me... Logs attached, thanks in advance! 🙂 backupserver-diagnostics-20210719-0715.zip backupserver-syslog-20210719-0515.zip

Cheers! I've set up a Gaming VM to use via Steam Remote Play a couple of month ago, and so far it's working really smooth. The problem is, after an extended amount of use or a couple of days, performance suddenly seems to drop and gameplay as well as sound become extremely laggy and choppy. This is only resolved with a reboot of the VM. CPU and network load seem to be fine, and I'm unsure if this is an UnRAID, Windows or Steam Remote Play issue. I've had other Windows 10 installations (baremetal) run 24/7 and never had any performance issues there. Logs and Diagnostics are attached. Thanks in advance! 🙂 homeserver-syslog-20210715-0511.zip homeserver-diagnostics-20210715-0712.zip

Hi! To help speed up copying large amounts of data, go to Settings -> Disk Settings and set "Tunable (md_write_method)" to "Reconstruct write" for the transfer process. I've never used Unbalance myself, but when copying files over directly I would advise to copy to the UnRAID-managed share, not directly to a single disk - this way unRAID will manage the balancing itself according to you settings. The target directory would then be /mnt/user/SHARE/. You could also take a look at the Krusader docker, which adds a nice GUI to help with file management directly in UnRAID.

Settings -> Management Access

This is an awesome and comprehensive guide on setting up a Gaming VM on UnRAID, which helped me a lot: https://forums.serverbuilds.net/t/guide-remote-gaming-on-unraid/4248 For me personally, the setup was extremely easy and straightforward (Ryzen 9 3900X + GTX 1070) without changing a single line of code. First of all you need to make sure to have virtualization as well as IOMMU enabled in your BIOS. On top of that you should set your iGPU as default, so that the system won't assign one of your GPUs for itself and make passing them through to your VM problematic. In UnRAID under Tools -> System Devices check the GPUs you want to pass through to your VM, to isolate them from the host system. I would also suggest to isolate the CPU cores pinned to your VMs (Settings -> CPU Pinning) since I had a huge performance degradation of my Gaming VM before isolation the associated cores. When setting up your VM first, don't assign a GPU and do the inital installation and setup via VNC, then install something like AnyDesk (my favourite) or Parsec to remotely access it after assigning a GPU. When assigning a GPU to the VM, make sure to assign all parts of the GPUs IOMMI group to it, like USB-controllers or (very importantly) the audio controller. You might also need to add a BIOS file (described in the guide above). I just fear that your CPU is a bit on the low end to support 2 simultaneous Gaming VMs. With the first Core left free for UnRAID itself, you have a mere 2 respectively 3 cores for each VM...

Try something like Teamviewer, Anydesk or even Windows Remote Desktop - they all should do the trick with a GPU passed through.

Cheers! I've got a problem with your OpenVPN-Client docker. I've been using it for quite some while now, but today I rebuilt my OpenVPN-server and thus had to add new authentication files. At first I had some problems with old and/or wrong shortcuts, but (presumably) got it to work. While the connection seems to get established and I can ping the VPN-IP, the tun-interface doesn't seem to be created and I can't access the server GUI. This is what the log says: Doing an "ifconfig" from UnRAID terminal doesn't show that tun0-interface though, which previously had worked. EDIT: Accessing the Container via Console and doing an "ifconfig" the tun0-interface showed up. After a tad more tinkering, I changed the default network type "Bridge" to "Host", and now everything works as intended! 🙂

Try using a different CDRom Bus (IDE has worked perfectly for me so far concerning installing any Windows OS) to possibly mitigate the first screen. Upon reaching the UEFI Interactive Shell, type "exit" without the quotation marks, and then again leave the UEFI settings to boot into the Windows installer.

Have you installed the drive into another Windows or Linux system and tested it out over there, with the same problems?

Just wanted to give an update - Parity has been successfully updated, and as expected the content of the formatted drive is gone. Currently rebuilding the missing 4 TB from my Backup. Next time (which hopefully won't happen) I'll be more patient and cautious. 🙂

The popup did show up, and it was more than clear - I was just a complete and utter idiot I guess and somehow expected a different outcome... 🙂

Hi itimpi, and thanks for the super fast response, wow! I have to shamefully admit that I acted incredibly hasty and premature - I removed the two disabled disk, restarted and stopped the array, added the disks again and then formatted and started rebuilding parity. I thought UnRAID would then think those were two replacement disks for lost ones and would start rebuilding my initial data situation. As you stated correctly, it now starts rebuilding parity with data disk 3 being completely empty, the files that were stored on it are gone. I was just way to impatient, idiot me... Luckily, I have a full offsite-backup which I'm gonna grab and rebuild the lost data over night after parity has been rebuilt. This will teach me to wait for the pros the next time. Anyhow, thanks again for your super quick reply itimpi! I will report back once the parity rebuild and data recovery has been (hopefully successfully) completed.

Cheers everyone! After having some trouble with a new 4-port SATA-controller dropping offline every few days, I did a larger troubleshooting session today - reaseating and/or exchanging all cables, exchanging my 2 SATA-controllers, swapping them around through the available PCIe-ports, and so on... It seems that it hasn't been a problem with a specific SATA-controller, but rather a bad seating in the PCIe slot due to it getting a tad loosened uping screwing it into the slot. Having this fixed, after the next boot 2 of my drives (one parity and one data drive) have been marked as disabled. Again, swapping around cables and ports, the error stays on those two drives. SMART-checks on those drives pass without any errors. I gotta admit I'm not completely sure on how to proceed from here on. Should I just format the unmountable disk 3 and then rebuild parity and data? Thanks in advance for your help! homeserver-syslog-20210627-1031.zip

I also set up Encryption for my Array as well as all Cache pools some time ago... If i remember correctly, you will be asked to to choose a passphrase or set up a keyfile as soon as trying to start the array.

From the screenshots you've attached, you have set WAN port 12345 in UnRAID, while port 443 is forwarded on your router. Are you sure that you chose the same ports on both devices at the same time? EDIT: I just saw that you forwarded the whole range from 12000-13000. Maybe try just forwarding the single port, and not the whole range. Plus: Don't expose unRAID itself directly to the internet, I would strongly recommend to remove the 443 port forward.

I'm not familiar with your Asus router, but did you configure static routes on each of those router into the other network? Attached a screenshot with a static route configuration of my USG-3P. Otherwise the devices in your subnet won't know how to reach the other subnet via which router/interface/ip-address. On your USG-3P the destination network would be "192.168.0.0/24" and the next hop "192.168.1.4"

I myelf am running a 2xSSD Raid1 pool as Cache for my shares, as well as dockers and (not performance-sensitive) VMs. I've got a NVME in a second pool for my Gaming VM. So far, all the Dockers and multiple VMs on the shared mirrored pool have a good to great performance.

Had this same issue as well, UnRAID server would not boot after having migrated to another Mainboard and not having a display connected. In my place the problem was with the mainboard, expecting to have a display connected to boot past the POST screen. Didn't find any setting in the UEFI to fix this. I bought myself a HDMI-dummy for 10 bucks which solved the problem. The mainboard thinks that a display is connected and boots correctly into UnRAID.

Cheers! Didn't know where to drop this, so I thought the Lounge might be the best place. Just wanted to say how awesomely easy it has become passing through devices to VMs, thanks a ton to everyone involved! I've wanted to migrate from my multiple gaming PCs cluttered around the house to a central Gaming VM for a long time, but always felt hesitant about it because of all the problems many people seem to have, especially regarding GPU-passthrough. But (at least for home) it has been a buttery smooth and easy process without changing one single line of code. Bind the GPU to VFIO at boot via the GUI, add the GPU as video and audio device in the VM settings, and boom - everything's working without any hassle! My UnRAID rig has now become so much more than just the NAS it used to be. I LOVE it! 🙂

Hi! After migrating my VMs to a new NVME-cache-pool, my VMs don't seem to autostart anymore. Manually starting them makes no problems however. Here's the libvirt-log in case it might help: 2021-05-06 06:00:58.940+0000: 14836: warning : qemuDomainObjTaint:6075 : Domain id=12 name='checkmk' uuid=a977a9ef-9ee1-e662-d23e-dfe05a200717 is tainted: host-cpu 2021-05-06 06:20:32.207+0000: 25724: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor 2021-05-06 06:21:22.031+0000: 14835: warning : qemuDomainObjTaint:6075 : Domain id=13 name='checkmk' uuid=18cd3a12-4504-4650-30ce-c1971253e998 is tainted: high-privileges 2021-05-06 06:21:22.031+0000: 14835: warning : qemuDomainObjTaint:6075 : Domain id=13 name='checkmk' uuid=18cd3a12-4504-4650-30ce-c1971253e998 is tainted: host-cpu 2021-05-06 06:42:19.405+0000: 14839: warning : qemuDomainObjTaint:6075 : Domain id=14 name='checkmk' uuid=18cd3a12-4504-4650-30ce-c1971253e998 is tainted: high-privileges 2021-05-06 06:42:19.405+0000: 14839: warning : qemuDomainObjTaint:6075 : Domain id=14 name='checkmk' uuid=18cd3a12-4504-4650-30ce-c1971253e998 is tainted: host-cpu 2021-05-06 12:30:51.658+0000: 31773: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor 2021-05-06 12:32:16.940+0000: 14835: warning : qemuDomainObjTaint:6075 : Domain id=15 name='Windows Server 2019' uuid=9bb38256-bda0-d38d-6d3d-7beb15c3739f is tainted: high-privileges 2021-05-06 12:32:16.940+0000: 14835: warning : qemuDomainObjTaint:6075 : Domain id=15 name='Windows Server 2019' uuid=9bb38256-bda0-d38d-6d3d-7beb15c3739f is tainted: host-cpu 2021-05-06 13:39:13.262+0000: 14839: warning : qemuDomainObjTaint:6075 : Domain id=16 name='Nextcloud' uuid=a4e42937-e325-cb76-e950-2f60b3d623ae is tainted: high-privileges 2021-05-06 13:39:13.262+0000: 14839: warning : qemuDomainObjTaint:6075 : Domain id=16 name='Nextcloud' uuid=a4e42937-e325-cb76-e950-2f60b3d623ae is tainted: host-cpu 2021-05-07 13:01:02.052+0000: 31821: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor 2021-05-07 13:01:02.601+0000: 26902: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor 2021-05-07 13:01:05.511+0000: 3856: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor 2021-05-07 13:04:24.338+0000: 2141: info : libvirt version: 6.5.0 2021-05-07 13:04:24.338+0000: 2141: info : hostname: Fileserver 2021-05-07 13:04:24.338+0000: 2141: warning : qemuDomainObjTaint:6075 : Domain id=1 name='Windows Server 2019' uuid=9bb38256-bda0-d38d-6d3d-7beb15c3739f is tainted: high-privileges 2021-05-07 13:04:24.338+0000: 2141: warning : qemuDomainObjTaint:6075 : Domain id=1 name='Windows Server 2019' uuid=9bb38256-bda0-d38d-6d3d-7beb15c3739f is tainted: host-cpu 2021-05-07 13:04:25.420+0000: 2139: warning : qemuDomainObjTaint:6075 : Domain id=2 name='Nextcloud' uuid=a4e42937-e325-cb76-e950-2f60b3d623ae is tainted: high-privileges 2021-05-07 13:04:25.420+0000: 2139: warning : qemuDomainObjTaint:6075 : Domain id=2 name='Nextcloud' uuid=a4e42937-e325-cb76-e950-2f60b3d623ae is tainted: host-cpu 2021-05-07 13:04:28.371+0000: 2139: warning : qemuDomainObjTaint:6075 : Domain id=3 name='Pi-hole' uuid=c4ca736d-c0d5-aec9-5d83-597266fe5c5d is tainted: high-privileges 2021-05-07 13:04:28.372+0000: 2139: warning : qemuDomainObjTaint:6075 : Domain id=3 name='Pi-hole' uuid=c4ca736d-c0d5-aec9-5d83-597266fe5c5d is tainted: host-cpu 2021-05-07 13:04:31.837+0000: 2139: warning : qemuDomainObjTaint:6075 : Domain id=4 name='checkmk' uuid=18cd3a12-4504-4650-30ce-c1971253e998 is tainted: high-privileges 2021-05-07 13:04:31.837+0000: 2139: warning : qemuDomainObjTaint:6075 : Domain id=4 name='checkmk' uuid=18cd3a12-4504-4650-30ce-c1971253e998 is tainted: host-cpu 2021-05-07 20:01:12.004+0000: 5325: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor 2021-05-07 20:01:13.359+0000: 5200: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor 2021-05-07 20:01:17.011+0000: 5468: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor 2021-05-07 20:04:40.150+0000: 30422: info : libvirt version: 6.5.0 2021-05-07 20:04:40.150+0000: 30422: info : hostname: Homeserver 2021-05-07 20:04:40.150+0000: 30422: warning : qemuDomainObjTaint:6075 : Domain id=1 name='Windows Server 2019' uuid=9bb38256-bda0-d38d-6d3d-7beb15c3739f is tainted: high-privileges 2021-05-07 20:04:40.150+0000: 30422: warning : qemuDomainObjTaint:6075 : Domain id=1 name='Windows Server 2019' uuid=9bb38256-bda0-d38d-6d3d-7beb15c3739f is tainted: host-cpu 2021-05-07 20:04:40.561+0000: 30420: warning : qemuDomainObjTaint:6075 : Domain id=2 name='Nextcloud' uuid=a4e42937-e325-cb76-e950-2f60b3d623ae is tainted: high-privileges 2021-05-07 20:04:40.561+0000: 30420: warning : qemuDomainObjTaint:6075 : Domain id=2 name='Nextcloud' uuid=a4e42937-e325-cb76-e950-2f60b3d623ae is tainted: host-cpu 2021-05-07 20:04:40.977+0000: 30418: warning : qemuDomainObjTaint:6075 : Domain id=3 name='Pi-hole' uuid=c4ca736d-c0d5-aec9-5d83-597266fe5c5d is tainted: high-privileges 2021-05-07 20:04:40.977+0000: 30418: warning : qemuDomainObjTaint:6075 : Domain id=3 name='Pi-hole' uuid=c4ca736d-c0d5-aec9-5d83-597266fe5c5d is tainted: host-cpu 2021-05-07 20:04:41.395+0000: 30421: warning : qemuDomainObjTaint:6075 : Domain id=4 name='checkmk' uuid=18cd3a12-4504-4650-30ce-c1971253e998 is tainted: high-privileges 2021-05-07 20:04:41.395+0000: 30421: warning : qemuDomainObjTaint:6075 : Domain id=4 name='checkmk' uuid=18cd3a12-4504-4650-30ce-c1971253e998 is tainted: host-cpu 2021-05-07 20:07:22.984+0000: 6577: error : qemuMonitorIO:578 : internal error: End of file from qemu monitor 2021-05-07 20:07:54.001+0000: 30419: warning : qemuDomainObjTaint:6075 : Domain id=5 name='Windows Server 2019' uuid=9bb38256-bda0-d38d-6d3d-7beb15c3739f is tainted: high-privileges 2021-05-07 20:07:54.001+0000: 30419: warning : qemuDomainObjTaint:6075 : Domain id=5 name='Windows Server 2019' uuid=9bb38256-bda0-d38d-6d3d-7beb15c3739f is tainted: host-cpu Thanks in advance for any ideas on how to fix this 🙂

I went on to test different switches, different cables and even isolated the server as well as different clients completely from the rest of the network, sadly without any improvements. I'm still capped at around 60 MB/s and out of ideas... 😞

I already tested the read and write procedures from 5 different clients, via LAN as well as via Wi-Fi, all with the same results of a pretty much stable max 60 MB/s read/write. 😞

Naturally, this with also my next task. 🙂 I ran the DiskSpeed plugin with a short test on all disks. While the two slowest disk have a minimum speed of 77 and 83 MB/s, all other disks are at 100 MB/s and well above...

Hi Jorge! I just did that between the two UnRAID servers, reaching a bitrate of around 950Mbits/sec., which looks pretty good and normal.

Hi! After having my main UnRAID fileserver successfully up and running for the past few month, I finally finished setting up my Backup-UnRAID machine which is meant to be moved off-site and connected via OpenVPN. While my main server runs buttery smooth with full Gigabit Read/Write, I am only getting a max. of 60 MB/s to and from my new Backup-UnRAID server. No parity (yet), no cache, direct read and write from and to the array. I've switched around cables and switches and tested from 5+ clients, all of them with the same result: Stable 100 MB/s on the main server, a max. of 60 MB/s on the new one - be it a single big file or fewer smaller ones. I'm a tad out of ideas at this point... Might anyone have an idea where I could look out for the problem? The diagnostics file is attached... Thanks in advance! :-) backupserver-diagnostics-20210223-1501.zip