erichner

Just jumping in here as I experienced all of my Shares disappearing as well about 10 minutes ago. No logs saved unfortunately.

Would something like this work? i like the idea of it coming with cables and supporting 24 drives when I upgrade in the future.

I wish I could do the 8i but I have 9 HDD drives. Also, my NVMe drive is mounted to board directly for a bare metal VM, so no worry there. I figure with the 9305-16i or 9400-16i I can get one or two dual SSD 2.5in drive to 3.5in HDD adapters and put in another one or two of my extra drives as well. Thanks for all the info!

I don't have any experience with SAS HBA boards, so please excuse my ignorance. Would any of these work that are closer to my budget of $200 or less: LSI SAS9750-16I4E 16 Port Internal 4 Port External 6Gb/s PCI SATA+SAS https://www.ebay.com/itm/LSI-SAS9750-16I4E-16-Port-Internal-4-Port-External-6Gb-s-PCI-SATA-SAS/372880810737?hash=item56d16da2f1%3Ag%3AsEsAAOSwbTVd-nha&LH_BO=1 LSI Megaraid SAS 9260-16I SAS 512MB Controller L3-25243-20D W/ BATTERY & CABLES https://www.ebay.com/itm/LSI-Megaraid-SAS-9260-16I-SAS-512MB-Controller-L3-25243-20D-W-BATTERY-CABLES/254427115539?hash=item3b3d09b013%3Ag%3AaIMAAOSwk5Fd1EMy&LH_BO=1 ----------------------- Would this one be better than the 9305-16i if I was going to spend $300: Broadcom LSI SAS 9400-16i (05-50008-00) 12Gb 16 Port HBA - New Sealed Box https://www.ebay.com/itm/Broadcom-LSI-SAS-9400-16i-05-50008-00-12Gb-16-Port-HBA-New-Sealed-Box/264370017310?hash=item3d8dae541e:g:z1UAAOSweOldAPB8

Is the 3rd server still around? I'm looking for my second to house my smaller drives....

The 1050 runs in PCIe 1x due to an converter / extension I used to mount the card upside down. Wasn't due to the actual motherboard.

Any suggestions on a LSI card that can do SATA/SAS and support 16 drives (up to 16tb) and won’t break the bank? Any idea of how much of a performance increase a 6GBps vs a 12GBps card would make? I have (9) 3.5in drives + (2) cache SSDs + (1) SSD for VM. Does it make sense to use the Marvell controller only for drives that are not in the array and for specific VMs? This would be for the use of unassigned drives will not be consistently pushed as they are now with seeding/uploading torrents in Qbittorrent (and causing the disk errors).

Running Qbittorrent causes massive file errors that normally knocks off 1 parity and 1 data drive offline. Rebuilds required to get back online. I've replaced the parity drive that I thought was in question and recently added a new one that is now suffering from these disk errors, regardless of the SATA port. I usually have these running simultaneously without error in the past: Plex Qbittorrent Radarr Radarr4k (same but for 4K) RadarrSync Sonar Jackett Lidarr Krusader Logs attached tower-diagnostics-20200320-0152.zip

Logs for 6.8.0rc7 tower-diagnostics-20191201-0250.zip

Everything has been running fine on 6.4.3 for 2+ years now. When I try and upgrade, the drives running off the external sata card disappear. I have removed all of the Dynamix plugins as previously suggested. Meant 6.8.0rc7 not rc8. Logs for 6.4.3 tower-diagnostics-20191130-2125.zip

I've actually disabled the debug mode for CA Auto Turbo as of yesterday, before the most recent crash. EDIT: I followed your link and updated the items suggested. We'll see if it is still showing more OOM errors today!

Issue: Whenever my Cache drive has less than 64GB of free space (total amount of ECC Ram I have), the system goes haywire. GUI is unresponsive. I get the following error since the /user folder disappears: Transport endpoint is not connected Mover is run every hour to keep the Cache drive as empty as possible. I have a share IncomingMedia that is set to use the Cache and have a MEGAdownloader program on my physical Mac mapped to the share as the download location. My process for getting media and transporting it to unRAID: 1) Select files to start auto downloading on the Mac 2) Files start to save on unRAID IncomingMedia share from Mac 3) After files have downloaded, I move them from a "Downloading" folder to a "Completed" folder (no moving actually happens from Cache, since both folders are under IncomingMedia) 4) I then do a move via Midnight Commander (MC) in terminal to my PlexMedia share (also set to use Cache) Diagnostics are attached. System: unRAID 6.3.5 Intel® Xeon® CPU E5-2650 v3 @ 2.30GHz 2 Cache drives (506GB useable) - 512GB 850 Pro - 500GB 850 Evo 1 Parity drive - 8TB WD Pro 7 Data drives - 2x 8TB WD Reds - 4x 3TB Seagate NAS - 1x 3TB Toshiba 3 Unassigned drives - 512GB SSD 850 Pro NVMe (used for VM) - 960GB SSD for (games for VM) - 32GB Flash drive for backups of unRAID USB unraid-diagnostics-20180104-1051.zip

Yes, you're right. I updated my post to reflect the correction. My homebridge has been running all day so far!

So for all of you that are having issues with the Homebridge docker quitting after X amount of time (most likely due to the harmonyhub plugin). Try this: Edit the docker Turn on Advanced In parameters add: --restart=unless-stopped This should restart the docker if it crashes unexpectedly.

I had to upgrade my unRAID setup to 6.3.3 a few months back after a USB drive died. I feel like an idiot, but how would I run your script in Windows 10? I am still trying to get this to work again.

Can you share the file or version number? I don't have backups for it.

Yes, I am having issues with it stopping as well.

I am also running into this as well. Below is my docker log for an app that is failing to update: [Info] Bootstrap: Starting Sonarr - /opt/NzbDrone/NzbDrone.exe - Version 2.0.0.4645 [Info] AppFolderInfo: Data directory is being overridden to [/config] [Error] PidFileProvider: Unable to write PID file /config/nzbdrone.pid [v2.0.0.4645] System.IO.IOException: Disk full. Path /config/nzbdrone.pid at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) <0x2b9513bcd240 + 0x005ed> in <filename unknown>:0 at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, System.String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) <0x2b9513bcd190 + 0x0004d> in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int,System.IO.FileOptions,string,bool,bool,bool) at System.IO.StreamWriter.CreateFile (System.String path, Boolean append, Boolean checkHost) <0x2b9513a3fd50 + 0x00095> in <filename unknown>:0 at System.IO.StreamWriter..ctor (System.String path, Boolean append, System.Text.Encoding encoding, Int32 bufferSize, Boolean checkHost) <0x2b9513a3fa10 + 0x00073> in <filename unknown>:0 at System.IO.StreamWriter..ctor (System.String path, Boolean append, System.Text.Encoding encoding, Int32 bufferSize) <0x2b9513a3f9d0 + 0x00035> in <filename unknown>:0 at System.IO.StreamWriter..ctor (System.String path, Boolean append, System.Text.Encoding encoding) <0x2b9513a3f990 + 0x0002b> in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.IO.StreamWriter:.ctor (string,bool,System.Text.Encoding) at System.IO.File.WriteAllText (System.String path, System.String contents, System.Text.Encoding encoding) <0x2b9513bcb930 + 0x0003d> in <filename unknown>:0 at System.IO.File.WriteAllText (System.String path, System.String contents) <0x2b9513bcb900 + 0x00022> in <filename unknown>:0 at NzbDrone.Common.Processes.PidFileProvider.Write () [0x0001e] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Processes\PidFileProvider.cs:36 [Fatal] ConsoleApp: EPIC FAIL! [v2.0.0.4645] System.IO.IOException: Disk full. Path /config/nzbdrone.pid at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) <0x2b9513bcd240 + 0x005ed> in <filename unknown>:0 at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, System.String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) <0x2b9513bcd190 + 0x0004d> in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int,System.IO.FileOptions,string,bool,bool,bool) at System.IO.StreamWriter.CreateFile (System.String path, Boolean append, Boolean checkHost) <0x2b9513a3fd50 + 0x00095> in <filename unknown>:0 at System.IO.StreamWriter..ctor (System.String path, Boolean append, System.Text.Encoding encoding, Int32 bufferSize, Boolean checkHost) <0x2b9513a3fa10 + 0x00073> in <filename unknown>:0 at System.IO.StreamWriter..ctor (System.String path, Boolean append, System.Text.Encoding encoding, Int32 bufferSize) <0x2b9513a3f9d0 + 0x00035> in <filename unknown>:0 at System.IO.StreamWriter..ctor (System.String path, Boolean append, System.Text.Encoding encoding) <0x2b9513a3f990 + 0x0002b> in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.IO.StreamWriter:.ctor (string,bool,System.Text.Encoding) at System.IO.File.WriteAllText (System.String path, System.String contents, System.Text.Encoding encoding) <0x2b9513bcb930 + 0x0003d> in <filename unknown>:0 at System.IO.File.WriteAllText (System.String path, System.String contents) <0x2b9513bcb900 + 0x00022> in <filename unknown>:0 at NzbDrone.Common.Processes.PidFileProvider.Write () [0x0001e] in M:\BuildAgent\work\b69c1fe19bfc2c38\src\NzbDrone.Common\Processes\PidFileProvider.cs:36

I got everything working on my 6.3.0-rc5 setup using an m.2 Samsung NVMe 950 Pro 512GB and an Asus Strix GTX 1080 with the following steps. Preliminary: Figure out which PCIe controller you need to stub / passthrough to the VMs in the Flash syslinux.cfg editor (click your USB drive's name on the Main page) 1. Install Windows 10 VM: RAM/CPU - minimum +4GB / +2 CPUs Virtio-1.118-2 Q35-2.4 Set VNC to Cirrus No external PCIe components passed through USB Mode - EHCI 2.0 2. After VM install: Install VirtIO Host package in VM (located on CD image in This PC) Download and install TeamViewer free (to remove need of VNC and use TeamViewer to remote in) Download Geforce Experience and preload the drivers 3. Shutdown VM: Enable GPU passthrough via regular VM editor Connect Vive through USB 2.0 motherboard port Enable all Vive components via VM editor (take note of 0x2c87 & 0x2101 duplicated devices) Go to Tools -> System Devices -> Scroll down to USB Devices Take note of the "Bus 002 Device 003" for the IDs listed above Go to Edit XML for the VM and add: <address bus='1' device='52'/> after the 4 entries (two for 0x2c87 and two for 0x2101) <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0bb4'/> <product id='0x2c87'/> (Change the Bus and Device #'s to whatever yours says in System Devices) 4. Startup VM for initial Vive Install: Drivers for parts of the Vive will install Download Steam & Vive Setup; install in that order Your Vive should be working with basic functionality (no camera) Enable and then install the Bluetooth driver via SteamVR settings 5. Final setup for full Vive functionality: Edit VM normally, not XML Disable VNC, enable passthrough of your GPU Set USB Mode - XHCI 3.0 Disconnect Vive USB from USB 2.0 and reconnect to additional PCIe 3.1 card Boot VM Additional USB Audio and Camera driver should install Your Vive should be working with full functionality Enjoy! Notes: I used a dual USB 3.1 + Ethernet card so that I can have a dedicated connection to the VM: Syba 3 Port USB 3.1 Gen 1 and Gigabit Ethernet PCI-e 2.0 X1 Card Components Other (SD-PEX50100) $29.99 https://www.amazon.com/gp/product/B01JT5KB8M/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&tag=erichner-20&camp=1789&creative=9325&linkCode=as2&creativeASIN=B01JT5KB8M&linkId=683f11016b1a2d5f779081a351bbb5b5

PCI Devices and IOMMU Groups IOMMU group 0 ff:0b.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring [8086:2f81] (rev 02) ff:0b.1 Performance counters [1101]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring [8086:2f36] (rev 02) ff:0b.2 Performance counters [1101]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring [8086:2f37] (rev 02) IOMMU group 1 ff:0c.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers [8086:2fe0] (rev 02) ff:0c.1 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers [8086:2fe1] (rev 02) ff:0c.2 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers [8086:2fe2] (rev 02) ff:0c.3 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers [8086:2fe3] (rev 02) ff:0c.4 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers [8086:2fe4] (rev 02) ff:0c.5 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers [8086:2fe5] (rev 02) ff:0c.6 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers [8086:2fe6] (rev 02) ff:0c.7 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers [8086:2fe7] (rev 02) IOMMU group 2 ff:0d.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers [8086:2fe8] (rev 02) ff:0d.1 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers [8086:2fe9] (rev 02) IOMMU group 3 ff:0f.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent [8086:2ff8] (rev 02) ff:0f.1 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent [8086:2ff9] (rev 02) ff:0f.2 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent [8086:2ffa] (rev 02) ff:0f.3 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent [8086:2ffb] (rev 02) ff:0f.4 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers [8086:2ffc] (rev 02) ff:0f.5 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers [8086:2ffd] (rev 02) ff:0f.6 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers [8086:2ffe] (rev 02) IOMMU group 4 ff:10.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCIe Ring Interface [8086:2f1d] (rev 02) ff:10.1 Performance counters [1101]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCIe Ring Interface [8086:2f34] (rev 02) ff:10.5 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers [8086:2f1e] (rev 02) ff:10.6 Performance counters [1101]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers [8086:2f7d] (rev 02) ff:10.7 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers [8086:2f1f] (rev 02) IOMMU group 5 ff:12.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 0 [8086:2fa0] (rev 02) ff:12.1 Performance counters [1101]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 0 [8086:2f30] (rev 02) ff:12.4 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 1 [8086:2f60] (rev 02) ff:12.5 Performance counters [1101]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 1 [8086:2f38] (rev 02) IOMMU group 6 ff:13.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Target Address, Thermal & RAS Registers [8086... (rev 02) ff:13.1 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Target Address, Thermal & RAS Registers [8086... (rev 02) ff:13.2 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder [8086:2faa] (rev 02) ff:13.3 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder [8086:2fab] (rev 02) ff:13.6 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Channel 0/1 Broadcast [8086:2fae] (rev 02) ff:13.7 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Global Broadcast [8086:2faf] (rev 02) IOMMU group 7 ff:14.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 0 Thermal Control [8086:2fb0] (rev 02) ff:14.1 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 1 Thermal Control [8086:2fb1] (rev 02) ff:14.2 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 0 ERROR Registers [8086:2fb2] (rev 02) ff:14.3 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 1 ERROR Registers [8086:2fb3] (rev 02) ff:14.4 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 [8086:2fbc] (rev 02) ff:14.5 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 [8086:2fbd] (rev 02) ff:14.6 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 [8086:2fbe] (rev 02) ff:14.7 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 [8086:2fbf] (rev 02) IOMMU group 8 ff:16.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Target Address, Thermal & RAS Registers [8086... (rev 02) ff:16.1 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Target Address, Thermal & RAS Registers [8086... (rev 02) ff:16.2 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder [8086:2f6a] (rev 02) ff:16.3 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel Target Address Decoder [8086:2f6b] (rev 02) ff:16.6 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Channel 2/3 Broadcast [8086:2f6e] (rev 02) ff:16.7 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Global Broadcast [8086:2f6f] (rev 02) IOMMU group 9 ff:17.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel 0 Thermal Control [8086:2fd0] (rev 02) ff:17.1 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel 1 Thermal Control [8086:2fd1] (rev 02) ff:17.2 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel 0 ERROR Registers [8086:2fd2] (rev 02) ff:17.3 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel 1 ERROR Registers [8086:2fd3] (rev 02) ff:17.4 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 [8086:2fb8] (rev 02) ff:17.5 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 [8086:2fb9] (rev 02) ff:17.6 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 [8086:2fba] (rev 02) ff:17.7 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 [8086:2fbb] (rev 02) IOMMU group 10 ff:1e.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit [8086:2f98] (rev 02) ff:1e.1 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit [8086:2f99] (rev 02) ff:1e.2 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit [8086:2f9a] (rev 02) ff:1e.3 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit [8086:2fc0] (rev 02) ff:1e.4 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit [8086:2f9c] (rev 02) IOMMU group 11 ff:1f.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 VCU [8086:2f88] (rev 02) ff:1f.2 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 VCU [8086:2f8a] (rev 02) IOMMU group 12 00:00.0 Host bridge [0600]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMI2 [8086:2f00] (rev 02) IOMMU group 13 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 1 [8086:2f02] (rev 02) IOMMU group 14 00:01.1 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 1 [8086:2f03] (rev 02) IOMMU group 15 00:02.0 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 2 [8086:2f04] (rev 02) IOMMU group 16 00:03.0 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 3 [8086:2f08] (rev 02) IOMMU group 17 00:03.2 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 3 [8086:2f0a] (rev 02) IOMMU group 18 00:05.0 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Address Map, VTd_Misc, System Management [8086:2f28] (rev 02) 00:05.1 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Hot Plug [8086:2f29] (rev 02) 00:05.2 System peripheral [0880]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 RAS, Control Status and Global Errors [8086:2f2a] (rev 02) 00:05.4 PIC [0800]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 I/O APIC [8086:2f2c] (rev 02) IOMMU group 19 00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR [8086:8d7c] (rev 05) 00:11.4 SATA controller [0106]: Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] [8086:8d62] (rev 05) IOMMU group 20 00:14.0 USB controller [0c03]: Intel Corporation C610/X99 series chipset USB xHCI Host Controller [8086:8d31] (rev 05) IOMMU group 21 00:16.0 Communication controller [0780]: Intel Corporation C610/X99 series chipset MEI Controller #1 [8086:8d3a] (rev 05) IOMMU group 22 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (2) I218-LM [8086:15a0] (rev 05) IOMMU group 23 00:1a.0 USB controller [0c03]: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 [8086:8d2d] (rev 05) IOMMU group 24 00:1b.0 Audio device [0403]: Intel Corporation C610/X99 series chipset HD Audio Controller [8086:8d20] (rev 05) IOMMU group 25 00:1c.0 PCI bridge [0604]: Intel Corporation C610/X99 series chipset PCI Express Root Port #1 [8086:8d10] (rev d5) IOMMU group 26 00:1c.3 PCI bridge [0604]: Intel Corporation C610/X99 series chipset PCI Express Root Port #4 [8086:8d16] (rev d5) IOMMU group 27 00:1c.4 PCI bridge [0604]: Intel Corporation C610/X99 series chipset PCI Express Root Port #5 [8086:8d18] (rev d5) IOMMU group 28 00:1c.7 PCI bridge [0604]: Intel Corporation C610/X99 series chipset PCI Express Root Port #8 [8086:8d1e] (rev d5) IOMMU group 29 00:1d.0 USB controller [0c03]: Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #1 [8086:8d26] (rev 05) IOMMU group 30 00:1f.0 ISA bridge [0601]: Intel Corporation C610/X99 series chipset LPC Controller [8086:8d47] (rev 05) 00:1f.2 SATA controller [0106]: Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] [8086:8d02] (rev 05) 00:1f.3 SMBus [0c05]: Intel Corporation C610/X99 series chipset SMBus Controller [8086:8d22] (rev 05) IOMMU group 31 03:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) 03:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio Controller [10de:10f0] (rev a1) IOMMU group 32 04:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller [1b4b:9230] (rev 11) IOMMU group 33 05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) 05:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:0fb9] (rev a1) IOMMU group 34 06:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller [144d:a802] (rev 01) IOMMU group 35 07:00.0 USB controller [0c03]: VIA Technologies, Inc. VL805 USB 3.0 Host Controller [1106:3483] (rev 01) IOMMU group 36 08:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller [1b21:1242] IOMMU group 37 09:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03) USB Devices Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0bb4:2744 HTC (High Tech Computer Corp.) Bus 001 Device 003: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 001 Device 004: ID 0bb4:2134 HTC (High Tech Computer Corp.) Bus 001 Device 005: ID 0bb4:0306 HTC (High Tech Computer Corp.) Bus 001 Device 006: ID 28de:2000 Bus 001 Device 007: ID 0424:274d Standard Microsystems Corp. Bus 001 Device 008: ID 0bb4:2c87 HTC (High Tech Computer Corp.) Bus 001 Device 009: ID 0d8c:0012 C-Media Electronics, Inc. Bus 001 Device 010: ID 0bb4:2c87 HTC (High Tech Computer Corp.) Bus 001 Device 011: ID 28de:2101 Bus 001 Device 012: ID 28de:2101 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 002 Device 003: ID 0781:5590 SanDisk Corp. Bus 002 Device 004: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub

Here are my settings. syslinux.cfg default /syslinux/menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS GUI Mode menu default kernel /bzimage append pci-stub.ids=1106:3483,8086:8d26,8086:8d2d,1b21:1242 initrd=/bzroot,/bzroot-gui label unRAID OS kernel /bzimage append initrd=/bzroot label unRAID OS GUI Mode (Safe) kernel /bzimage append initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest Windows 10 VM XML <domain type='kvm'> <name>Steam-WIN10</name> <uuid>26875e39-d4c5-4cde-61dd-89f9975c2b47</uuid> <description>Steam In-Home Streaming</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="steamos.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='6'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='8'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='16'/> <vcpupin vcpu='5' cpuset='17'/> <vcpupin vcpu='6' cpuset='18'/> <vcpupin vcpu='7' cpuset='19'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-2.4'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/26875e39-d4c5-4cde-61dd-89f9975c2b47_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' 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/disks/Samsung_SSD_950_PRO_512GB_S2GMNX0H804473L/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win10_1607_English_x64.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <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.117-1.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='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='dmi-to-pci-bridge'> <model name='i82801b11-bridge'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/> </controller> <controller type='pci' index='2' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='2'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:0b:b6:02'/> <source bridge='virbr0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' 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='0x03' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1a' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1d' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0424'/> <product id='0x274d'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0bb4'/> <product id='0x0306'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0bb4'/> <product id='0x2c87'/> <address bus='1' device='8'/> </source> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0bb4'/> <product id='0x2c87'/> <address bus='1' device='10'/> </source> <address type='usb' bus='0' port='1.1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0d8c'/> <product id='0x0012'/> </source> <address type='usb' bus='0' port='1.2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x28de'/> <product id='0x2000'/> </source> <address type='usb' bus='0' port='1.3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x28de'/> <product id='0x2101'/> <address bus='1' device='11'/> </source> <address type='usb' bus='0' port='1.4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x28de'/> <product id='0x2101'/> <address bus='1' device='12'/> </source> <address type='usb' bus='0' port='1.5'/> </hostdev> <hub type='usb'> <address type='usb' bus='0' port='1'/> </hub> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x02' slot='0x0a' function='0x0'/> </memballoon> </devices> </domain>

Try a different USB port dor the link box, maybe a 2.0. Also, I wasn't able to get it working without passing a usb controller to my VM. I stubbed a PCIE 3.1 USB Controller and was able to get it to see the Windows 10VM to see all of the USB devices for the Vive. Only problem was that the base stations and remotes continuously disconnected. Weirdest thing is that when I first tried Q35-2.3 it worked for a few minutes. I think once certain drivers got installed it went bonkers. I have deleted every single USB driver not in use (and the renasas controller) that would pop up. Every USB hub, device, all separate to try and isolate the issue. Switched to USB 2.0 and 3.0 in the dropdown as well. I am now trying to put in the individual <address bus='3' device='12'/> to the duplicated devices that are being passed via USB 2.0 on the motherboard.

Are you still working on this? I cannot get my Vive to work for the life of me. Continuously dropping the connection to the Base Stations and the controllers not connecting.

64GB ECC DDR4