Leaderboard

I appreciate all the enthusiasm towards this issue, but there is a bit more drama here than is warranted. This situation is no different than formatting an XFS disk on another Linux machine, adding data to the disk and then plugging it into unRAID and expecting it to go into the array without a format. LT has committed to fold UD into unRAID and I think it best to not do anything right now that will distract them from that effort. You all need to appreciate that UD has morphed into something that it was not originally designed for. It was originally a USB disk mount and data transfer to/from a USB disk. @gfjardim and I have done the best we can to make UD into what it is and @gfjardim has done a great job coordinating UD and preclear. Now it's time to let LT handle the incorporation into unRAID and determine the features that make sense for their objectives. UD is pretty complicated and LT will have to spend some time fitting it into unRAID. It is best to let them decide how to handle the formatting of UD disks and the array format compatibility issue. I don't want to interfere with their effort and make any changes at this point.

Now that Ryzen is official I'm quite interested in it. Upto 8 Cores/16 Threads, excellent SMT implementation, ECC RAM support, IOMMU, 8 port on-CPU SATA with the X370 chipset and the high end models are half the price of comparable Intel CPUs. It seems to tick all boxes but I'm concerned whether it'll play nice with unRAID and VM PCI/GPU passthrough. Is anybody planning to test this? Update to make things a bit easier for people interested in running Unraid on Ryzen: unRAID 6.4rc7+ generally works fine with Ryzen as of July 2017. Be sure to follow your motherboard manufacturers instructions to update to the latest UEFI version with AGESA 1.0.0.6. As of right now (6.4rc6) there appears to be one bug related to CPU power-managment that causes unRAID to crash intermittently. Good news: This bug was fixed in 6.4rc7! The way to fix this is to either disable "Global C-State Control" in the motherboard's UEFI/BIOS or have a constant load on the machine (i.e. with a Windows VM idling) so that the CPU never throttles frequency down completely at idle. Either of these fixes will lead to slightly increased power consumption. The second bug is in KVM and leads to decreased video performance when passing through GPUs into VMs on Ryzen. The problem is related to Nested Page Tabling; Ryzen owners have observed decreased CPU and I/O performance inside the VM when NPT is off and decreased FPS in graphic intensive applications (i.e. video games) when NPT is on. Gaming performance inside a unRAID VM with passed through GPU can be disappointing for that reason. Some systems seem to be affected more than others. The good news is that Xen hypervisor is not affected by this problem so it looks like the bug is in the KVM software, not AMD's hardware; KVM lead developers have acknowledged the issue but are lacking time/resources and did not mention a timeframe for a fix. There are some more advanced workarounds that can improve the situation by turning off NPT and passing through entire storage controllers but don't work around it completely. If you are affected by this issue please take a look at https://bugzilla.kernel.org/show_bug.cgi?id=196409 and consider commenting to raise awareness among developers and perhaps even AMD.

Only 20% of the RAM is used for caching by default, other option is to enable turbo write, you should be able to achieve line speed with gigabit.

You can also boot with the GUI option and use it to reconfigure your network settings.

Fix Common Problems plugin - Troubleshooting mode will save logs to flash periodically.

Ah, yea I see what you're saying. My case is pretty much purpose built as a storage/server/workstation case, in place of the normal 5.25" bays I have space for a mix of 10 3.5" and 2.5" drives that are rotated 90 degrees (long side is against front of case), so I have 3x 120mm fans blowing directly across them and I believe there is one 120mm exhaust fan at the rear. Also the top of the case is "open" since below the shroud there is space for 2x 200mm fans to cool a 240mm radiator...which I will be utilizing shortly My previous case, a Silverstone DS380, was a nightmare for cooling. It supported 8x 3.5" hot swappable bays in the front and 4x 2.5" static bays in a cage in the upper rear. The rear drives had no cooling at all, and the front cage had 2x 80mm fans blowing against the side of the drive cage but.....engineering failed miserably because where the opening for air flow were were blocked when the HDD was installed and there was no gap between each drive so air would just hit the side of the cage and take the path of least resistance and just go along side of it and exhaust out the back. The fans are on the opposite side, as you can see there is no space for anything in there, it's a MicroATX case so it's pretty tiny, about as tall as a 2L soda bottle. Complete waste of $180.

Not enough flow over the drives. Most normal mini and mid towers just aren't designed for 10+ hdd, and cooling them can be a challenge, especially during monthly parity checks where all the drives are running at nearly full speed for 12+ hours. Typically I recommend all incoming air be directed to the drives, any other case openings should be taped over or set to actively exhaust with a fan. Much different than your typical gaming tower.

I don't consider it a bug. UD was never intended to format disks for inclusion in the array. I'm really unclear why anyone would want to do this. Just put the disk in the array and copy the data to it.

Well gents, just wanted to give you a update on Ryzen w/ c-states enabled locking up unRAID... or rather how we've fixed it! On my Ryzen test machine, with array stopped (to keep it idle) with c-states enabled in bios, I'm approaching 7 days of uptime. Before the changes we made to the kernel in the upcoming RC7, It would only make it a few hours and lockup. I think you guys will find RC7 just epyc! (sorry, couldn't resist) FYI, these are the two kernel changes we had to add to make it stable for Ryzen: - CONFIG_RCU_NOCB_CPU: Offload RCU callback processing from boot-selected CPUs - CONFIG_RCU_NOCB_CPU_ALL: All CPUs are build_forced no-CBs CPUs Thanks to everyone here for testing and helping narrow it down to c-states. That made it easier for us to test and find a solution.

Template repositories are just that: Repositories for templates (They are generated by dockerMan, and the xml can just as easily be stored at /boot/config/plugins/dockerMan/templates-user). Its basically a guarantee that if the repository url isn't published here, then there are no templates contained within. Your primary issue is probably more that you want to use a container with the build contained on GitLab instead of dockerHub. That cannot be done using the UI with unRaid. All containers have to be stored on dockerHub. You can however install and use your own containers and avoid dockerHub by cloning locally and issuing appropriate docker build commands. But to directly answer the question, template repositories are tied directly to how GitHub manages everything, and it is not going to work to have a template repository stored elsewhere online.

A little tricky but I think this is complete: 1: Enable dockerhub access in the settings section of the Community Applications and then search for primiano/docker-webvirtmgr and add it to the system. You'll get a dialog like this. Change the port and /data/vm path to your appdata directory as needed. it will place a sqllite db in the appdata location. 2: connect into the container: docker exec -it docker-webvirtmgr bash 3. run this to add a user in the container..it will prompt for user/password/email. /webvirtmgr/manage.py createsuperuser 4. exit out of the container: exit 5. edit /etc/libvirt/libvirtd.conf and comment out the line: listen_addr = "127.0.0.1" by putting a # symbol in front of it. 6. add a new line to /etc/libvibvirt/libvirtd.conf: listen_addr = "0.0.0.0" and save it 7) Restart the KVM system via unraid: Settings->VM Manager->Enable VMs to No and apply, Enable VMs to Yes and Apply. 8 ) Connect to your WebvirtMgr: http://<unraid ip>:8089 in my case 9) log into it with your new user created in step 3 10) Select Add connection and choose TCP and I filled in my unraid IP/root/root_password

Try looking at webvirtmgr and virt-manager. Webvirtmgr is a web interface to manage KVM hypervisors and virt-manager is a GUI package to do the same. There are docker images for both of them on docker hub. I would suggest unws/webvirtmgr and tukiyo3/virt-manager.