Leaderboard

This is a bug fix and security update release. Due to a security vulnerability discovered in forms-based authentication: ALL USERS ARE STRONGLY ENCOURAGED TO UPGRADE To upgrade: If you are running any 6.4 or later release, click 'Check for Updates' on the Tools/Update OS page. If you are running a pre-6.4 release, click 'Check for Updates' on the Plugins page. If the above doesn't work, navigate to Plugins/Install Plugin, select/copy/paste this plugin URL and click Install: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer.plg Refer also to @ljm42 excellent 6.4 Update Notes which are helpful especially if you are upgrading from a pre-6.4 release. Bugs: If you discover a bug or other issue in this release, please open a Stable Releases Bug Report. Version 6.8.1 2020-01-10 Changes vs. 6.8.0 Base distro: libuv: version 1.34.0 libvirt: version 5.10.0 mozilla-firefox: version 72.0.1 (CVE-2019-17026, CVE-2019-17015, CVE-2019-17016, CVE-2019-17017, CVE-2019-17018, CVE-2019-17019, CVE-2019-17020, CVE-2019-17021, CVE-2019-17022, CVE-2019-17023, CVE-2019-17024, CVE-2019-17025) php: version 7.3.13 (CVE-2019-11044 CVE-2019-11045 CVE-2019-11046 CVE-2019-11047 CVE-2019-11049 CVE-2019-11050) qemu: version 4.2.0 samba: version 4.11.4 ttyd: version 20200102 wireguard-tools: version 1.0.20200102 Linux kernel: version 4.19.94 kernel_firmware: version 20191218_c4586ff (with additional Intel BT firmware) CONFIG_THUNDERBOLT: Thunderbolt support CONFIG_INTEL_WMI_THUNDERBOLT: Intel WMI thunderbolt force power driver CONFIG_THUNDERBOLT_NET: Networking over Thunderbolt cable oot: Highpoint rr3740a: version v1.19.0_19_04_04 oot: Highpoint r750: version v1.2.11-18_06_26 [restored] oot: wireguard: version 0.0.20200105 Management: add cache-busting params for noVNC url assets emhttpd: fix cryptsetup passphrase input network: disable IPv6 for an interface when its settings is "IPv4 only". webgui: Management page: fixed typos in help text webgui: VM settings: fixed Apply button sometimes not working webgui: Dashboard: display CPU load full width when no HT webgui: Docker: show 'up-to-date' when status is unknown webgui: Fixed: handle race condition when updating share access rights in Edit User webgui: Docker: allow to set container port for custom bridge networks webgui: Better support for custom themes (not perfect yet) webgui: Dashboard: adjusted table positioning webgui: Add user name and user description verification webgui: Edit User: fix share access assignments webgui: Management page: remove UPnP conditional setting webgui: Escape shell arg when logging csrf mismatch webgui: Terminal button: give unsupported warning when Edge/MSIE is used webgui: Patched vulnerability in auth_request webgui: Docker: added new setting "Host access to custom networks" webgui: Patched vulnerability in template.php

Well, personally I preclear every drive I add to my unraid server prior to making it a part of my array 🙂 While "most" drives come up uneventful, I did just two weeks ago shuck and add a handful of 8TB's to my backup unraid server and low and behold preclearing saved me ahead of time on a disk that started to mark and reallocate bad sectors. Easier to identify ahead of time, rather than add a disk, put data on the disk, and then in time realize through smart somethings happening. For me, I love the integration of this plugin into UD (UD+), and being able to preclear at the click of a button.

It's pretty painless, and of course not vetted by anyone at this point. - Download the 12.1 DVD ISO - SATA disk - Be sure to install SRC - Apply patch per instructions - Comment out NETMAP from kernel - Build/Install custom kernel - Done And yes it's going to seriously suck to get a new VM built back to how i had it on 11.2 . Edit: I should add that I used USB flash drive to copy patch to VM

Awesome! Bring on 6.9 with that new 5.4 kernel

Overview: Support for Docker image arch-preclear in the binhex repo. Application: Preclear - https://forums.unraid.net/topic/2732-preclear_disksh-a-new-utility-to-burn-in-and-pre-clear-disks-for-quick-add/ Docker Hub: https://hub.docker.com/r/binhex/arch-preclear/ GitHub: https://github.com/binhex/arch-preclear Documentation: https://github.com/binhex/documentation If you appreciate my work, then please consider buying me a beer 😁 For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

CA Appdata Backup / Restore (v2) Due to some fundamental problems with XFS / BTRFS, the original version of Appdata Backup / Restore became unworkable and caused lockups for many users. Development has ceased on the original version, and is now switched over to this replacement. Fundamentally they are both the same and accomplish the same goals (namely, backing up your Appdata share and USB / libvirt), but this version is significantly faster at the job. This version uses tar instead of rsync (and offers optional compression of the archive - roughly 50% if not including any downloads in the archive - which you really shouldn't be anyways). Because of using tar, there is no longer any incremental backups. Rather, every backup goes into its own separate dated subfolder. Old backups can optionally be deleted after a successful backup. Even without incremental backups, the speed increase afforded by tar means that there should be no real difference in the end. (ie: A full backup using my appdata on the old plugin takes ~1.5 hours. This plugin can do the same thing uncompressed in about 10 minutes, and compressed in 20 minutes. The optional verification of the archive takes a similar amount of time. An incremental backup on the old plugin using my appdata averaged around 35 minutes). The options for separate destination for USB / VM libvirt backups is changed so that if there is no destination set for those backup's then they will not be backed up. Additionally, unlike the original plugin, no cache drive is necessary, and the appdata source can be stored on any device in your system (ie: unassigned devices). The destination as usual can go to any mount point within your system. Unfortunately because of no more incremental backups, this version may no longer be suitable for ultimately backing up offsite to a cloud service (ie: via rclone) You can find this within the Apps tab (Search for Appdata Backup). The original v1 plugin should be uninstalled if migrating to this version.

here u go, it should be /transcode only and not /mnt.... your transcode buffer currently runs inside the container

Check the link in my signatures. If you don't see it, then you have to turn on signatures in your control panel. Or check the docker faq.

If you think this is a simple compile on boot job, you have clearly not read much in this thread or understand anything about how much work, manual that is, to get this to compile. If it was a simple script job for each unraid release, it would have been released shortly after. But it is not. If you want to test unraid releases the second they are ready, run a clean unraid build.

Limetech would just have to include the nvidia driver in the unraid build. Nvidia runc could be offered as an official plugin or baked in. That's what chbmb does, unpack unraid, bake in nvidia drivers and runc, and recompile. But because chbmb doesn't exactly know what may or may not have changed in unraid releases (not open source) he has to reverse engineer quite a bit. Qnap on the other hand bakes nvidia drivers and runc in their software.

From the command prompt, which python should return /usr/bin/python unless you installed python3 in which case you need to use #!/usr/bin/python3

I'm going to go out on a limb here and speak for @CHBMB. This plugin (and the DVB plugin) are built and maintained by him on a volunteer basis and it isn't always convenient for him (or anyone else) to continually keep up with every release as soon as it's released. There is significant time required to build and test each and every release which isn't always doable because of other commitments which are probably far more important. Cut him some slack. To be honest, at times I'm surprised due to the time required for this that he even bothers to support RC's.

For what it's worth, I was able to get 12.1 working with virtio NIC using TommyP's patch .

Just thought I would mention Diagnostics, since you're new and it wasn't mentioned in the thread. Tools - Diagnostics will let you download a zip file which contains many of your settings, SMART for all attached disks, syslog (since last boot), information about your shares, the results from running some simple commands, and other things which give a much more complete understanding of your situation. We usually prefer diagnostics instead of only syslog, but in cases of crash, it can also be useful to have syslogs from before reboot. And since diagnostics won't have those syslogs, Syslog Server is needed to get those for us.

Install the tweaks and tips plug-in and check what governor the system is running. You want on demand. I have a 2700x running with no issues, messing with c states fixed a issue with 1st Gen ryzen a long time ago but for your chip it's not needed.

Great plugin! I've made a Nord inspired theme with it. Imgur Album Theme Engine settings CSS File

The timeline is dictated by the sonarr developers, as soon as V3 comes out of beta and they produce a GitHub 'release' then it will be built. Sent from my CLT-L09 using Tapatalk

If you are parring through a GPU to a VM then it cannot be shared with another running VM. You can only use the sane GPU in two (or more) VMs if they will not be running at the same time. Hardware pass-through is always a bit of a hit-or-miss scenario as it is highly dependent on your exact hardware, BIOS, Linux kernel and KVM versions (most of which are outside Limetech's control) Until you actually try it you can never be sure if it will work for you.

This should be fixed in 6.8.1 release.

There was also corruption on the cache xfs filesystem, did you fix that? In any case probably a good idea to run memtest for a few hours.

@Sic79 i got now all running and talking together. The next thing is how to configure the webinterface.

Not necesarilly true - Previously, "Basic" was the name given to the free license limited to three disks. That was before the current license tiers were introduced.

just make a full backup of your unraid usb drive before upgrade. i see in the screenshot that you are using Unraid server basic, so there is a key? you can check this here: tools -> registration

You need to enable syslog server (in the settings) to save it your flash. That would allow you obtain log cross-boot. Your post-reboot log is pretty useless as any issue was logged in the pre-reboot.

https://github.com/jlesage/docker-qdirstat/blob/master/README.md#vnc-password

Unraid 6 and newer require a key to run. Are you perhaps running Unraid version 5?

There is no 'free' version of Unraid anymore so you will not be able to upgrade unless you are prepared to buy a key. Are you prepared for that? You should always have backup of any critical data, preferably with at least one off-site copy. Your comments imply you have no backups which is very risky as you can potentially lose data for all sorts of reasons.

Yes if plan to use SAS devices, SATA devices will still work with any SATA controller, including onboard.

Oh, you win! I lost it a long time ago in the unifi thread! And again in the letsencrypt thread with the Lua errors! Good thing I'm Norwegian and not American with an arsenal.... And I agree, we should be stopped!

Been a while since anyone asked about TLER on this forum. I believe the consensus is that Unraid is better used without TLER enabled. Unraid is not really RAID. https://forums.unraid.net/topic/1233-tler-time-limited-error-recovery/ https://forums.unraid.net/topic/32964-choosing-which-type-of-drives-to-use-for-what/?do=findComment&comment=317766 https://forums.unraid.net/topic/69564-most-basic-barebones-dirt-cheap-components-that-work-without-severe-limitations/?do=findComment&comment=635836 and others if you search

Open device manager You will see your unknown devices. Right click the unknown device and select "update driver". Select "Browse my computer for the driver software" Click browse Select the CDROM Drive virtio-win-x.x Then click next. Windows will scan the entire device for the location of the best-suited driver. It should find a RedHat network adapter driver, follow the prompts and you're in business. ** I never bothered to locate the actual subfolder of the driver on the virtio-win-1-1 image, I just let windows do it for me. ** Hope this helps.