Leaderboard

My server has always used an old WD Raptor 150GB as the cache drive. I recently added a Crucial 240GB SSD as an unassigned device and added some Windows VMs to it which (currently) aren't taking up much space. I'm wondering: 1) Should I keep the Raptor as the Cache drive or make the SSD the cache & VM drive? I suppose that *may* cause VM performance to suffer a bit. 2) Maybe the Raptor should stay the Cache drive but perhaps I should move the docker image, appdata and downloads folder over to the SSD as it has more room to spare. I'm Finally in the process of setting up dockers other than Plex and am wondering where to put downloads. I've seen people put them on a user share, which protects them but means at least another disk needs to be spinning. In terms of power consumption, that's another point for putting it on the SSD. Should the SSD fail before a download gets moved, I can probably re-download whatever is lost. What would you do with those drives at your disposal?

These are plugins which are installable by Community Applications, just as many things are, but in general only those plugins specifically labelled CA are part of the Community Applications suite. Various other plugins and dockers have various other authors and support threads. The author of Community Applications does not officially support these others (though he is very helpful in general). This won't work as stated since you need to let unRAID format the new drives in the array. So inserting new drives after copying then removing the old drives will not work. You could: replace parity with larger disk, resync add new data drives, format as XFS copy old drives contents to new drives remove old drives New Config with only new drives resync parity. Of course, this would require having enough bays/ports to have old and new drives installed at the same time. Do you have backups of any irreplaceable or important files? Assuming you do have backups, I think I would just start with a new array with only new disks formatted XFS, and then mount the old disks one at a time using Unassigned Devices, and copy their contents to the new array. If you wait until after all the copying was done to install parity it would make the writes faster.

From "tools" -> "system devices" IOMMU group 0 [1002:5a14] 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD9x0/RX980 Host Bridge (rev 02) IOMMU group 1 [1002:5a16] 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GFX port 0) IOMMU group 2 [1002:4390] 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] (rev 40) IOMMU group 3 [1002:4397] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4396] 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller IOMMU group 4 [1002:4397] 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4396] 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller IOMMU group 5 [1002:4385] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 42) IOMMU group 6 [1002:439c] 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller (rev 40) IOMMU group 7 [1002:4383] 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40) IOMMU group 8 [1002:439d] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40) IOMMU group 9 [1002:4384] 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40) IOMMU group 10 [1002:4399] 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller IOMMU group 11 [1002:43a0] 00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) [1002:43a1] 00:15.1 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 1) [1002:43a2] 00:15.2 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB900 PCI to PCI bridge (PCIE port 2) [1b21:1042] 04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller [10ec:8168] 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) IOMMU group 12 [1002:4397] 00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4396] 00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller IOMMU group 13 [10de:11c6] 01:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 650 Ti] (rev a1) [10de:0e0b] 01:00.1 Audio device: NVIDIA Corporation GK106 HDMI Audio Controller (rev a1)

Are you trying to use port 80? Unraid gui runs on there so you have to pick a different port

This question has an answer. Sorry, see Docker FAQ in Docker Engine subforum. More specifically, But, if you look up just one post from yours you will see the zoneminder docker isn't getting much support.

I don't use this, but in general the syslog will often not help with diagnosing dockers since dockers are isolated from the system. Have you read the Docker FAQ at the top of this subforum?

We keep an eye on the Radarr stuff and the container is rebuilt weekly so don't worry.

I know that I have a friend who complained about similar speed with his gigabit network. Last week he finally replaced the switch and is now seeing gigabit speeds (100MB/sec. +). Drops are not uncommon in congested networks. But your counters are pretty high - especially if you've been restarting while troubleshooting this issue. Yes, if you connect directly to the switch you will remove the router and most of the cabling in your test. Good idea.

Updated for 6.3.3

Uploaded to dropbox. Unzip and give it a go. https://www.dropbox.com/s/ohxe2zhq8mkgl6d/LibreELEC-Generic.x86_64-8.0-devel-20170330140555-r25524-gba275c4-unRAID-Krypton.img.gz?dl=0

Here's the rundown: I found tweaks that were made on a nightly build that's actually already running Kodi 18.0. These tweaks allowed LibreELEC to run in the manner we're looking, no dedicated graphics card on a VM. Unfortunately, Kodi 18 has migrated to MyVideos108 rather than MyVideos107, so this wouln't help with our library syncing/updating goals. So what I did was I took the source files from LibreELEC running Kodi 17.1, took the individual changes that were made to allow for us to be able to run without the GPU, compiled, and created what is essentially a new version of LibreELEC 8.0. So yes, the end result of compiling the source code is an .img file which is precisely what we need to create a VM. This will start out as our primary vdisk location. Check out the below image to see how to set things up on the unRAID GUI: I believe you could also set the IMG file as the "OS Install ISO" instead, but I've always gone the route shown above. Probably no difference. After hitting create, you'll get brought back to the unRAID VM GUI. Click the green triangle and connect via VNC. At this point, it should look like a standard LibreELEC install. It will ask you for an install location, and the only option should be the "2nd vDisk Location" which you created above. Allow it to clear/format and overwrite this disk when performing the install. When done, it'll says it's time to reboot. At this point, go back to the VM screen and force kill the VM. Then tap the red square and go to "EDIT". Go to the Primary vDisk location and select NONE. You no longer want the VM to run off of the original .img file. Now, the secondary vDisk which is what we just installed the OS to will become your main drive. After saving your changes, go back and this time after clicking on the red square, select "EDIT XML": The XML is the blueprint for the VM, presenting information ranging from resource allocation to peripheral location. Here's what I would do. Again, this is guess work fudging, but it's what worked for me. Find the bracket towards the middle bottom starting with <channel type='unix'> and delete it along with everything below it to the bottom. Now copy and paste my XML and replace it: <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-LibreELEC - Krypton/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5901' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='virtio' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </memballoon> </devices> </domain> The first part of your XML is specific to your setup, referencing resource allocation as well as disk locations. They second half represents some of the tweaks needed to be made to allow VNC to work. After these changes, save and boot! EDIT: @hernandito to answer your last question about version changing. If I understand correctly, your goal was about updating libraries, so just make sure that all of your client devices along with this VM stay on Krypton. They can move from 8.0.0 to 8.0.1 and beyond, as long as it's still on Krypton. Once you move something off of Krypton and onto Kodi 18, it will be on a different database at which poitn you'll either have to roll it back, or move everything else up. Fortunately, we also have a working file of Kodi 18 as this is where I got these fixes from, so we should be safeguarded for quite some time.

May Your Data Storage Be Plenty and your Parity Checks always come up Error Free.