Jcloud

Members
  • Posts

    632
  • Joined

  • Last visited

Everything posted by Jcloud

  1. I can't claim this as mine, I feature requested from my OS, and was emailed this solution. I wanted a JBOD cache pool, as this would best leverage my upgrades and I don't need the protection of new btrfs-raid. Been running for two months, so far so good, figured I should share the knowledge. Instructions: 0.) Backup any data you don't want to lose. These steps will format your cache drive(s). You have been warned. ((appdata, DOMAINS, system?)) 1.a) If you are adding new drives to your cache pool; add them like normal. This is where your drive will get formatted by web-ui, using default RAID1. If you want to change your existing pool to JBOD, just move to 1.b. "Okay, People. Nothing to see here! Move along." -- Officer Barbraide 1.b) Navigate to the Main tab in the unRAID web ui, then click on blue link ‘Cache’ next to your first cache device. 2. ) Locate the Balance Status section. Next to the ‘Balance’ button there is a empty text box, paste this in there: -dconvert=single 3. ) Click the ‘Balance’ button. The process may take a while to convert the existing data in the cache pool but you’re free to keep using the server as this runs in the background. 4. ) Move back your data onto cache pool. Note: note entirely sure, but if one adds another drive onto their pool, I think web-ui (by it's design) will want to format the cache pool. So, safe play would be to backup first. Then again, I haven't tried it, so I don't know with 100% certainty if it will. Unfortunately I don't have a third ssd to try and test it. Thanks to Eric Schultz, and Lime Technology for their time and response to my question.
  2. I saw this Female USB-A header to USB2-internal header adapter, I've ordered two for myself to try. Looks completely passive in nature - I think I'll find this to be useful. My upside being I don't have to worry about my USB drive when I move my system around. I like the 2.0 variant, as that leaves another 3.0 port for my VM's. I though perhaps others in the community may like this, so here you go.
  3. Your first post mentioned sudden power outage, assuming your computer went down, Windows would have called that an unclean shutdown and at the very least would have ran chkdsk /f /x %BOOTDRIVE% Now if Windows 10 is interrupted trying to boot normally (ie the twirlly circle) this can cause Windows to trip into that Automatic repair. Could also happen if it hiccups on chkdsk and has to redefine the disk volume for boot manager -- I some times run into this issue with HD clones where I've resized the partition, and on first boot of clone tell it to run check disk. I could see it being a similar issue as an image file with your host possibly running a repair on file system in background? Few bits shift around. Just a hypothesis though.
  4. A co-worker was telling me about https://storj.io, and I am currently under-utilizing my storage array so this new app had peaked my curiousity. I'm a cave man with Docker, just now looking at "how to build a container," but I know, I don't know what I'm doing. So, I was just curious if Storj had hit anyone else's radar and perhaps someone with more experience was already on it? Have a good weekend all.
  5. +1 I have a Tripp Lite, and was using the built-in support. I quit using the built-in support due to USB devices on my VM would cause discommunication with UPS. I thought it was a VM/IRQ sort of "bleed." Unsure of exact cause, but after learning of only APC support, I've let the computer run without UPS communication. I wasn't aware of macester's plugin, I'll have to take a look. Thank you for your hard work.
  6. I "do it by hand." Feel free copy it and change it for yourself, if this would work for you.
  7. I'm not certain if this post belongs here, but I made a spreadsheet for tracking HD prices (Google Doc). My first thought was most in the community probably already have one, but figured I would share anyways - perhaps save someone else some time. Personally this sort of thing just helps me keep track pricing-trends, and when a sale is a deal versus stock reduction.
  8. So I recently got a Steam Controller, about a week ago, and have it functioning in my Win8.1 VM. I think the two working solutions would apply for any other kind of VM though. I'm running unRAID 6.1.9. Solution 1: Explicitly assigned the Steam controller to the VM - this breaks down into two parts. Part-A: like everyone else Steam controller does not show up in the webUI. Step 1. Open terminal to unRAID and ran terminal command "lsusb" root@HYDRA:~# lsusb Bus 002 Device 007: ID 09ae:2010 Tripp Lite Bus 002 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 003: ID 1532:0040 Razer USA, Ltd Bus 005 Device 002: ID 1532:011a Razer USA, Ltd Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 28de:1102 Bus 003 Device 002: ID 174c:2074 ASMedia Technology Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 046d:c21d Logitech, Inc. F310 Gamepad [XInput Mode] Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@HYDRA:~# --> Bus 003 Device 004: ID 28de:1102 Is the Steam Controller. Step 2. Opened the XML file for my VM while it was offline from the web page. Using Archdraft's "11b solution" while mimicing the items I explicitly selected from webUI I added the following code to my XML file: <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x28de'/> <product id='0x1102'/> </source> </hostdev> Start up the VM and it worked! One interesting bit to note was the product ID would change in lsusb depending if I was using the wireless dongle versus having the controller plugged in by USB cable. I also found that the Controller worked in my "solution 1" but would hang when trying to do the controller firmware update in Steam. Solution 2: Successfully implemented Archdraft's 11b solution for my usb controller, and implemented jonp's USB3.0 driver tweak ergo I no longer needed my "solution 1" and PnP was functioning properly in Windows - double win in my book. So implementing jonp's fix for USB3.0 controller looks like: <controller type='usb' index='0' model='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </controller> Where the address line was added automagicly by KVM. My USB controller boiled down to, Archdraft's 11b solution: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> </hostdev> When I finally made the connections in my head from all of his terminal commands. Especially running "readlink /sys/bus/usb/devices/usb*" I realized looking at terminal output: ../../../devices/pci0000:00/0000:00:1c.0/0000:06:00.0/usb3 ../../../devices/pci0000:00/0000:00:1c.0/0000:06:00.0/usb4 Basically meant: ../../../devices/pci0000:00/0000:00:1c.X/Domain:Bus:Slot.function/usbY In general form. Where Domain, buss, slot, function are in context to Archdraft's 11b solution/explanation. I hope this info helps others.
  9. I don't know if this post belongs here, but I saw Linus has a new video/project with unRAID at it's core, trying to 1-up his 7 Gamers box. Enjoy.
  10. My attempts to help TS fell flat, I guess this is the level of OC I can provide : Cropped sample from a background I downloaded.
  11. Neither am I. But it would be nice to have. I tried crossfire with my two R9 280X, but it didn't work. I could install the drivers and it would enable crossfire, but as soon as I ran 3D Mark the VM crashed. This was last year, so haven't tried it in newer version. I've been Running R9 290 in cross fire for quite some time now, I consider my VM to be very stable. Here is a copy of VM xml in case you see anything interesting. Are your video cards UEFI compatible? Just double checking. ATI cards don't require a bridge for Cross-fire, it's all done in software with windows drivers. Nvidia products on the other hand requires a hardware bridge between cards. <domain type='kvm' id='1' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Kraken</name> <uuid>dedccfd4-255c-a89a-2b27-7d16c8da5f49</uuid> <description>win8gpu</description> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>33030144</memory> <currentMemory unit='KiB'>33030144</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='9'/> <vcpupin vcpu='2' cpuset='10'/> <vcpupin vcpu='3' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' threads='1'/> </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/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/vDisks/coil/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='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/ISOs/win8_1/Windows.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/win7/virtio-win-0.1.102.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'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 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:7c:e6:b8'/> <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/Kraken.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> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x1532'/> <product id='0x0040'/> <address bus='5' device='3'/> </source> <alias name='hostdev0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x1532'/> <product id='0x011a'/> <address bus='5' device='2'/> </source> <alias name='hostdev1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=02:00.0,bus=root.1,addr=01.0,multifunction=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain> I hope that helps.
  12. /tmp/emby does not stay on reboot. Rather its recreated at the time of the emby docker restarting. And after its created is when you'd have to do the chown. Hence why I'm suggesting to create the folder first. Otherwise the chown in go will do nothing, because the folder doesn't exist at that point. Ah that makes since. I think last time I tried, I started Emby got an error with transcoding. Looked back and saw /tmp/emby/ owned by root and thought, "okay it's permissions issue, I just need to do chown." You just just saved me the step of having the error one more time and going, "Ah that's why Squid mentioned both commands." Thanks for helping me skip a step, shame on you robbing me of an "Ah HA!" moment. No, seriously, thanks.
  13. Ok, good to know. Will try it when I'm back at home tonight. When interim question though, is helping me understand users and how authentication works. When I created another second user account (let's call it "bob"), it didn't prompt me for a password anywhere. When i download the profile, and send to my device, how does it know who I want to auth as? While you are making "bob" or have made it, in User Permissions on OPEN-AS webui, to the right you should see a show link, click on that, from that dialog box you can change/set user passwords for VPN client. If the server is running you'll have to go to the top of UI an push the changes to the server. So now in your browser if you go to: https://foo_myIP.orDOMAIN:943/ you put in "bob" and password. This will get you DL's to OpenVPN client (if you don't have it already) and the client config files. Grab your config file and VPN client and go. If you already have your VPN client installed and configured, you can just open that put in bob and password. Unless it's the autorun profile which case your VPN client should autoconnect without username and password.
  14. Thank you sir. Actually all that I need is line-2; if I'm remembering what occurs correctly (it's been a month since my last reboot). You'll need them both, because without the mkdir, when it hits the chown it will error out if the directory isn't already made (and since emhttp starts in the background and whenever it gets around to it starts up the docker apps, the odds are really against the directory existing no matter where you put the chown in the go file unless you add appropriate waits. Understood, but that's what I was trying to say before, /tmp/emby had stayed on reboot but the ownership reverted back to root. Minor point - the information you provided me earlier is enough for me to get that working (regardless of the actual behavior). Thanks again for your time and post.
  15. Thank you sir. Actually all that I need is line-2; if I'm remembering what occurs correctly (it's been a month since my last reboot).
  16. This can be corrected in the Go file so it "appears" to be persistent on reboot. Sorry for being obtuse, I still consider myself an "end user" making my way towards "power-user." Can you, or someone in the community, point me to either the Go file, or to the link of documentation which outlines the Go file (so I can RTFM)? I'm assuming the go file is something other then rc.d scripts?
  17. Mine has the X79 chipset and not the c606 chipset, my board does not support SAS or Xeon cpus.
  18. The same idea for Emby. I added container volume /transcode and /tmp/emby host path for Dockers Volume mappings. Afterwards I then had to: [*]ssh into my unRAID: #: chown nobody:nobody /tmp/emby [*]open Emby webui >> go to: /web/encodingsettings.html [*]change "Transcode temporary path " to: /transcode Note: one downside, if you reboot unRAID the /tmp/emby folder's ownership changes to root, so you have to go in and change ownership back to nobody. #Edit: hopefully this is useful to people.#
  19. For any of those interested, and haven't done so themselves, I took jonp idea of Plex Transcoding and applied the same idea to Emby. I added container volume /transcode to /tmp/emby host path for Dockers Volume mappings. Afterwards I then had to: [*]ssh into my unRAID: #: chown nobody:nobody /tmp/emby [*]open Emby webui >> go to: /web/encodingsettings.html [*]change "Transcode temporary path " to: /transcode Note: one downside, if you reboot unRAID the /tmp/emby folder's ownership changes to root, so you have to go in and change ownership back to nobody. #edited for better grammar#
  20. Sorry for the late reply, I just seen your post. No this board does not have the c606 but instead: Intel® X79 chipset : 2 x SATA 6Gb/s port(s), black 4 x SATA 3Gb/s port(s), black Support Raid 0, 1, 5, 10 Marvell® PCIe 9230 controller : 4 x SATA 6Gb/s port(s), dark brown ASMedia® ASM1061 controller : 2 x SATA 6Gb/s port(s), dark brown 2 x Power eSATA 6Gb/s port(s), green I have no issue with the Intel or ASM1061 controller, but I do have issues with my Marvell controller with my VM. I hope that answers your question.
  21. Saw this sale on Newegg, Crucial BX200 2.5" 480GB SATA III Internal Solid State Drive (SSD) CT480BX200SSD1 thought someone might be interested.
  22. I'll admit that was one of the hooks that sold me on unRAID; one of these days I'm going to setup two 'mini-VMs' and give it a shot. For now I'm content with crossfire GPUs. Don't hate me, I'm single and lonely -- but no kids. My specs are linked in my footer. Watch out for Marvell sata controllers when shopping for MLB, that burned me - details in my link. That's my two-cents worth of electrons. Also, populating those M.2 slots on your MLB choices would be killer for cache pool, but I don't know what your budget is like either.
  23. I tried that plugin, but lost my server config, long story short I use the Docker. I recommend OpenVPN from this https://github.com/linuxserver/docker-templates source, worked for me. Any questions I had were stomped searching through: https://lime-technology.com/forum/index.php?board=56.0 and Google.
  24. Hello! I saw people posting their builds and I wanted to show off my system too -- and say hello. I'll list off some details I ran into, in-case anyone is interested, perhaps someone might point out any of my mistakes. Incidentally, I first heard of unRAID on voat forums when I asked about NAS solutions. I was dreaming about storage solutions, due to my lack of it, and two hard drives died on me recently. Alas, the drive was seven years old, it was fair game. Someone pasted URL. What sold me was the hyper-visor support; coupled with array setup ... I'm preaching to the choir. And in time, I believe, I'll become as fanatic to unRAID as an old school Amiga fanatic. Also my old motherboard died, which actually worked out well for unRAID - more up-to-date logic board. My gaming rig, is now my unRAID server and still functions as game rig. Motherboard: Asus X79-Deluxe CPU: Intel i7 3930k CFAN: Noctua NH-D14 RAM: 64GB - DDR3 1600 (PC3 12800) PSU: Antec HCG-900 900W CASE: Antec 1100 GPU: 2x Radeon R9 290 Parity: WD Blue 4TB Disk 1,2: WD 3TB Red Disk 3: Seagate 2TB Cache: OCZ 240GB SSD Flash drive: Kingston Data Traveler G3 16GB USB2 Tried to use Data Traveler G4 but it refused to boot. OS: unRAID 6.1.9, Win8.1VM (provisioned: kb, mouse, 4 cpu cores, 32GB RAM, crossfired GPUs), OS X 10.11.2 in VM/vnc-walkthrough-setup. Dockers (so far): binhex-couchpotato, sonarr; aptalca-duckdns; linuxserver-openVPN-as; Emby; Transmission; coppit-filebot; sparklyballs-handbrake, DokuWiki Hardware Issues on Initial Setup: [*]Had to disable on-board WiFi and Bluetooth in BIOS/EFI. Didn't leave notes for myself, but recall I/O conflicts with VM and host. [*]Unable to use 4 sata ports on mobo. Ran into this issue with Marvell controllers. [*]Windows 7 worked with one GPU but second GPU had I/O conflicts in Windows. Resolution, upgraded to Windows 8.1, that made me cringe. Windows 10 also worked, but F!!! W10! [*]Actually started with a Windows10 VM and then worked backwards. Figured newer would be easier to setup, which it was, then went to preference OS. Current issues or TO do items: setup two 1-gpu gammer VMs; run side-by-side. Flavor of the month OS ... I guess. SteamOS ... again, see above. Pass through my optical drive ... I guess. BDr is kind of a pain now. (Diverted to MakeMKV Docker) root@HYDRA:~# lspci | grep USB 00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 (rev 06) 00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 (rev 06) 06:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller 07:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller 08:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller root@HYDRA:~# lsusb Bus 008 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick Bus 008 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 1532:0040 Razer USA, Ltd Bus 003 Device 002: ID 1532:011a Razer USA, Ltd Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@HYDRA:~# readlink /sys/bus/usb/devices/usb* ../../../devices/pci0000:00/0000:00:1c.1/0000:07:00.0/usb3 ../../../devices/pci0000:00/0000:00:1c.1/0000:07:00.0/usb4 ../../../devices/pci0000:00/0000:00:1c.2/0000:08:00.0/usb5 ../../../devices/pci0000:00/0000:00:1c.2/0000:08:00.0/usb6 ../../../devices/pci0000:00/0000:00:1a.0/usb7 ../../../devices/pci0000:00/0000:00:1d.0/usb8 root@HYDRA:~# IOMMU Groups /sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/2/devices/0000:00:01.1 /sys/kernel/iommu_groups/3/devices/0000:00:02.0 /sys/kernel/iommu_groups/4/devices/0000:00:03.0 /sys/kernel/iommu_groups/5/devices/0000:00:05.0 /sys/kernel/iommu_groups/5/devices/0000:00:05.2 /sys/kernel/iommu_groups/5/devices/0000:00:05.4 /sys/kernel/iommu_groups/6/devices/0000:00:11.0 /sys/kernel/iommu_groups/7/devices/0000:00:16.0 /sys/kernel/iommu_groups/8/devices/0000:00:19.0 /sys/kernel/iommu_groups/9/devices/0000:00:1a.0 /sys/kernel/iommu_groups/10/devices/0000:00:1b.0 /sys/kernel/iommu_groups/11/devices/0000:00:1c.0 /sys/kernel/iommu_groups/12/devices/0000:00:1c.1 /sys/kernel/iommu_groups/13/devices/0000:00:1c.2 /sys/kernel/iommu_groups/14/devices/0000:00:1c.4 /sys/kernel/iommu_groups/15/devices/0000:00:1c.5 /sys/kernel/iommu_groups/16/devices/0000:00:1c.7 /sys/kernel/iommu_groups/17/devices/0000:00:1d.0 /sys/kernel/iommu_groups/18/devices/0000:00:1e.0 /sys/kernel/iommu_groups/19/devices/0000:00:1f.0 /sys/kernel/iommu_groups/19/devices/0000:00:1f.2 /sys/kernel/iommu_groups/19/devices/0000:00:1f.3 /sys/kernel/iommu_groups/20/devices/0000:04:00.0 /sys/kernel/iommu_groups/21/devices/0000:01:00.0 /sys/kernel/iommu_groups/21/devices/0000:01:00.1 /sys/kernel/iommu_groups/22/devices/0000:02:00.0 /sys/kernel/iommu_groups/22/devices/0000:02:00.1 /sys/kernel/iommu_groups/23/devices/0000:06:00.0 /sys/kernel/iommu_groups/24/devices/0000:07:00.0 /sys/kernel/iommu_groups/25/devices/0000:08:00.0 /sys/kernel/iommu_groups/26/devices/0000:09:00.0 /sys/kernel/iommu_groups/27/devices/0000:0a:00.0 /sys/kernel/iommu_groups/28/devices/0000:0b:00.0 /sys/kernel/iommu_groups/29/devices/0000:ff:08.0 /sys/kernel/iommu_groups/29/devices/0000:ff:08.3 /sys/kernel/iommu_groups/29/devices/0000:ff:08.4 /sys/kernel/iommu_groups/30/devices/0000:ff:09.0 /sys/kernel/iommu_groups/30/devices/0000:ff:09.3 /sys/kernel/iommu_groups/30/devices/0000:ff:09.4 /sys/kernel/iommu_groups/31/devices/0000:ff:0a.0 /sys/kernel/iommu_groups/31/devices/0000:ff:0a.1 /sys/kernel/iommu_groups/31/devices/0000:ff:0a.2 /sys/kernel/iommu_groups/31/devices/0000:ff:0a.3 /sys/kernel/iommu_groups/32/devices/0000:ff:0b.0 /sys/kernel/iommu_groups/32/devices/0000:ff:0b.3 /sys/kernel/iommu_groups/33/devices/0000:ff:0c.0 /sys/kernel/iommu_groups/33/devices/0000:ff:0c.1 /sys/kernel/iommu_groups/33/devices/0000:ff:0c.2 /sys/kernel/iommu_groups/33/devices/0000:ff:0c.6 /sys/kernel/iommu_groups/33/devices/0000:ff:0c.7 /sys/kernel/iommu_groups/34/devices/0000:ff:0d.0 /sys/kernel/iommu_groups/34/devices/0000:ff:0d.1 /sys/kernel/iommu_groups/34/devices/0000:ff:0d.2 /sys/kernel/iommu_groups/34/devices/0000:ff:0d.6 /sys/kernel/iommu_groups/35/devices/0000:ff:0e.0 /sys/kernel/iommu_groups/35/devices/0000:ff:0e.1 /sys/kernel/iommu_groups/36/devices/0000:ff:0f.0 /sys/kernel/iommu_groups/36/devices/0000:ff:0f.1 /sys/kernel/iommu_groups/36/devices/0000:ff:0f.2 /sys/kernel/iommu_groups/36/devices/0000:ff:0f.3 /sys/kernel/iommu_groups/36/devices/0000:ff:0f.4 /sys/kernel/iommu_groups/36/devices/0000:ff:0f.5 /sys/kernel/iommu_groups/36/devices/0000:ff:0f.6 /sys/kernel/iommu_groups/37/devices/0000:ff:10.0 /sys/kernel/iommu_groups/37/devices/0000:ff:10.1 /sys/kernel/iommu_groups/37/devices/0000:ff:10.2 /sys/kernel/iommu_groups/37/devices/0000:ff:10.3 /sys/kernel/iommu_groups/37/devices/0000:ff:10.4 /sys/kernel/iommu_groups/37/devices/0000:ff:10.5 /sys/kernel/iommu_groups/37/devices/0000:ff:10.6 /sys/kernel/iommu_groups/37/devices/0000:ff:10.7 /sys/kernel/iommu_groups/38/devices/0000:ff:11.0 /sys/kernel/iommu_groups/39/devices/0000:ff:13.0 /sys/kernel/iommu_groups/39/devices/0000:ff:13.1 /sys/kernel/iommu_groups/39/devices/0000:ff:13.4 /sys/kernel/iommu_groups/39/devices/0000:ff:13.5 /sys/kernel/iommu_groups/39/devices/0000:ff:13.6 Pictures! I can work on pictures, at some point. Any Docker or plugin recommendations? I've been trying to keep a good eye on the forums. If you have any questions, or comments about my build let me know.