Jump to content


Popular Content

Showing content with the highest reputation since 01/18/18 in all areas

  1. 17 points
    I was wanting to do GPU Hardware Acceleration with a Plex Docker but unRAID doesn't appear to have the drivers for the GPUs loaded. would be nice to have the option to install the drivers so the dockers could use them.
  2. 12 points
    There are several things you need to check in your Unraid setup to help prevent the dreaded unclean shutdown. There are several timers that you need to adjust for your specific needs. There is a timer in the Settings->VM Manager->VM Shutdown time-out that needs to be set to a high enough value to allow your VMs time to completely shutdown. Switch to the Advanced View to see the timer. Windows 10 VMs will sometimes have an update that requires a shutdown to perform. These can take quite a while and the default setting of 60 seconds in the VM Manager is not long enough. If the VM Manager timer setting is exceeded on a shutdown, your VMs will be forced to shutdown. This is just like pulling the plug on a PC. I recommend setting this value to 300 seconds (5 minutes) in order to insure your Windows 10 VMs have time to completely shutdown. The other timer used for shutdowns is in the Settings->Disk Settings->Shutdown time-out. This is the overall shutdown timer and when this timer is exceeded, an unclean shutdown will occur. This timer has to be more than the VM shutdown timer. I recommend setting it to 420 seconds (7 minutes) to give the system time to completely shut down all VMs, Dockers, and plugins. These timer settings do not extend the normal overall shutdown time, they just allow Unraid the time needed to do a graceful shutdown and prevent the unclean shutdown. One of the most common reasons for an unclean shutdown is having a terminal session open. Unraid will not force them to shut down, but instead waits for them to be terminated while the shutdown timer is running. After the overall shutdown timer runs out, the server is forced to shutdown. If you have the Tips and Tweaks plugin installed, you can specify that any bash or ssh sessions be terminated so Unraid can be gracefully shutdown and won't hang waiting for them to terminate (which they won't without human intervention). If you server seems hung and nothing responds, try a quick press of the power button. This will initiate a shutdown that will attempt a graceful shutdown of the server. If you have to hold the power button to do a hard power off, you will get an unclean shutdown. If an unclean shutdown does occur because the overall "Shutdown time-out" was exceeded, Unraid will attempt to write diagnostics to the /log/ folder on the flash drive. When you ask for help with an unclean shutdown, post the /log/diagnostics.zip file. There is information in the log that shows why the unclean shutdown occurred.
  3. 12 points
    I took a stab at writing a How-To based on the feedback in the release thread. If this looks helpful, maybe it could be added to the top post? Edit: this warrants it's own topic, thank you! -tom ----- Upgrading from 6.4.x to 6.5.0 Nothing to it really: Read the first post in the 6.4.1 and 6.5.0 release notes threads Consider disabling mover logging, it just adds noise to diagnostics. New 6.4.1 installs have it disabled by default. Go to Settings -> Scheduler -> Mover Settings Install/Update the Fix Common Problems plugin, then go to Tools -> Update Assistant and click "Run Tests". Whereas the normal FCP checks for potential problems with your *current* version of unRAID, the Update Assistant checks for incompatibilities with the version of unRAID you are *about* to install. It is highly recommended that you resolve any issues before proceeding. If you choose not to run the Update Assistant, you'll want to perform these steps manually: Ensure your server name does not include invalid characters, or you will have problems in 6.5.x. Only 'A-Z', 'a-z', '0-9', dashes ('-'), and dots ('.') are allowed, and the name must be 15 characters or less. To fix this, go to Settings -> Identification and change the "Server name". (see this) Upgrade all your plugins Uninstall the Advanced Buttons plugin, it was newly discovered to be incompatible (see this). You may want to review the next section for other plugins that are known to have problems, if you skipped that when going to 6.4.0. Note that the S3 Sleep plugin works again, feel free to install it if you removed it when going to 6.4.0 (see this). Stop the array (this step is optional, but I like to do it before starting the upgrade) Go to Tools -> Update OS and update the OS. You may need to switch from Next to Stable to see the update. Reboot! Then check out the "Setting Up New Features" section below. Upgrading from 6.3.5 (or earlier?) to 6.5.0 Before you upgrade from 6.3.5 Read the first post in the 6.4.0, 6.4.1 and 6.5.0 release notes threads Consider disabling mover logging, it just adds noise to diagnostics. New 6.4.1 installs have it disabled by default. Go to Settings -> Scheduler -> Mover Settings Install/Update the Fix Common Problems plugin, then go to Tools -> Update Assistant and click "Run Tests". Whereas the normal FCP checks for potential problems with your *current* version of unRAID, the Update Assistant checks for incompatibilities with the version of unRAID you are *about* to install. It is highly recommended that you resolve any issues before proceeding. If you choose not to run the Update Assistant, you'll want to perform these steps manually: Ensure your server name does not include invalid characters, or you will have problems in 6.5.x. Only 'A-Z', 'a-z', '0-9', dashes ('-'), and dots ('.') are allowed, and the name must be 15 characters or less. To fix this, go to Settings -> Identification and change the "Server name". (see this) If you have VMs, go to Settings -> VM Manager, switch to Advanced View, and make sure all of the paths are valid. Here are the default settings, but make sure the paths below actually exist on your system. Without these paths, your VMs will not load under 6.4.1. For more info see this default VM storage path -> /mnt/user/domains/ (this is DOMAINDIR in \\tower\flash\config\domain.cfg) default ISO storage path -> /mnt/user/isos/ (this is MEDIADIR in \\tower\flash\config\domain.cfg) Delete this file from your flash drive: \\tower\flash\config\plugins\dynamix.plg This is an old version of the dynamix webgui. Depending on how old it is, it can prevent the new webgui from loading. (see this, this) Upgrade all your plugins (other than the main unRAID OS plugin) You must uninstall Advanced Buttons (see this) and the Preclear plugin (see this, this, this, this, this, this). Consider uninstalling unmenu (see this), the Pipework docker (see this), and any other plugins you no longer use. Note that the S3 Sleep plugin works again, just make sure you have updated to the latest (see this) Consider installing the Fix Common Problems plugin and resolving any issues it highlights Additional cleanup you may want to perform: Consider deleting all files from the \\tower\flash\extra folder and install them using Nerd Tools instead Review your \\tower\flash\config\go script and use a good editor (like Notepad++, not Notepad) to remove as much as possible. For instance, remove any references to "cache_dirs" and use the Dynamix Cache Directories plugin instead. Consider moving other customizations to the User Scripts plugin Remove any port assignments added on the /usr/local/sbin/emhttp line FYI, a completely stock go script looks like this: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & Consider Installing any BIOS updates that are available for your motherboard If you made any substantial changes in this section, reboot and test to make sure any problems are not the result of these changes. Performing the upgrade from 6.3.5 Stop the array (If 6.3.5 or earlier) Go to Plugins and update the unRAID OS plugin (but don't reboot yet) (If on 6.4.0 or one of the 6.4 rc's) Go to Tools -> Update OS and update the OS (but don't reboot yet). You may need to switch from Next to Stable to see the update. By default, the webgui in unRAID 6.4.1 will use port 80 and any customization you made to the port in your go script will be ignored. If you need to change the port(s) before booting into 6.4.1 for the first time, use a good editor (like Notepad++, not Notepad) and edit \\tower\flash\config\ident.cfg Add the following lines to the end of the file, substituting the ports you want to use: USE_SSL="auto" PORT="80" PORTSSL="443" NOTE: If you need to change the defaults, be sure to pick high values over 1024. i.e. 81 and 43 are *not* good options. Try 8080 and 8443 Once you have booted in 6.4.0, you should no longer edit this file by hand. Better to use the webgui: Settings -> Identification -> Management Access If you are running Ryzen: Edit your \\tower\flash\config\go script (using a good editor like Notepad++ (not Notepad)) and add the "zenstates" command right before "emhttp", like this: /usr/local/sbin/zenstates --c6-disable /usr/local/sbin/emhttp & Also, go into your BIOS and disable "Global C-state control" Reboot It may be helpful to clear your browsers cache --- Setting Up New Features unRAID now supports SSL! unRAID will automatically provision and maintain a Lets Encrypt certificate for you, along with the necessary dynamic DNS entries. To enable this, go to Settings -> Identification -> Management Access and click Provision. If you get an error about rebinding protection, wait 10 minutes and try again. If you still get the error, click Help to read how to adjust your router. Using these certificates will change your url to <some long number>.unraid.net. No it can't be changed without disabling all of the automation and switching to your own certificates. You don't need to remember the number, when you connect via IP or servername it will automatically redirect. If you are concerned about a theoretical DNS outage, know that you can override your DNS by adding an entry to your PC's hosts file. Or in a pinch you can edit \\tower\boot\config\ident.cfg and set USE_SSL="no" If you prefer to not use the fully automated Lets Encrypt certificates, you can set your own domain name and supply your own certificates or use self-signed certificates. In this mode, you are responsible for managing DNS and ensuring the certificates do not expire. Click the Help icon on the SSL Certificate Settings page for more details. Want to check out the new themes? Navigate to Settings -> Display Settings -> Dynamix color theme. You may need to change your banner when you change the theme Note that you can now use the webgui to assign unique IP addresses to your dockers. If you manually customized your macvlans under 6.3.5 you'll need to set them up again using the webgui. You can now disable the insecure telnet protocol. Go to Settings -> Identification -> Management Access and set "Use TELNET" to "No" 6.4.1 adds docker support links to the docker page. Any dockers you install in 6.4.1 or later will automatically get this functionality, to update your existing dockers follow this one-time process Solutions to Common Problems Are you looking for the "edit XML" option for your VMs? First Edit the VM, then click the button in the upper right corner to switch from "Form View" to "XML View" If your system hangs at "loading /bzroot", you need to switch from "legacy" booting to UEFI. The ASRock C236 WSI motherboard in particular needs this, others may as well. (see this, this) To do this: (If needed) rename the "EFI-" folder on the flash drive to "EFI" Go into the bios and set the boot priority #1 to "UEFI: {flash drive}" Starting wth 6.4.1, unRAID now monitors SMART attribute 199 (UDMA CRC errors) for you. If you get an alert about this right after upgrading, you can just acknowledge it, as the error probably happened in the past. If you get an alert down the road, it is likely due to a loose SATA cable. Reseat both ends, or replace if needed. (see this) If your VMs will not start after upgrading, go to Settings -> VM Manager, switch to Advanced View, and make sure all of the paths are valid. Here are the default settings, but make sure the paths actually exist on your system: default VM storage path -> /mnt/user/domains/ (this is DOMAINDIR in \\tower\flash\config\domain.cfg) default ISO storage path -> /mnt/user/isos/ (this is MEDIADIR in \\tower\flash\config\domain.cfg) For more info see this. (the Update Assistant could have warned you of this in advance) If you can't access the webgui after upgrading to 6.5.0, your server name may include characters that are invalid for NETBIOS names. Only 'A-Z', 'a-z', '0-9', dashes ('-'), and dots ('.') are allowed, and it must be 15 characters or less. (see this) To fix this, edit \\tower\flash\config\ident.cfg using a good editor (like Notepad++, not Notepad) and remove those characters from the "NAME" parameter, then reboot. (the Update Assistant could have warned you of this in advance) If you are unable to access the webgui after upgrading, you may have a really old version of the dynamix webgui plugin on your system. Delete \\tower\flash\config\plugins\dynamix.plg and reboot. (see this, this) (the Update Assistant could have warned you of this in advance) If you have problems booting after applying the upgrade, move your flash drive to a Windows or Mac machine and run checkdisk, fixing any problems it finds. If your cache disk has an "incompatible partition" after upgrading, it was probably created in an older version of the Unassigned Devices plugin. UD has been updated so this won't happen again. (the Update Assistant could have warned you of this in advance) This is a one-time fix. You'll need to downgrade to 6.3.5 and move the data off the cache drive, re-format the disk and move the data back. The procedure is outlined here If you have on-board Aspeed IPMI you may find that IPMI loses video or changes color during the boot process. To resolve this, go to Main -> Boot Device -> Flash -> Syslinux Config and add "nomodeset" to your "append" line (and reboot). It should look something like this: label unRAID OS kernel /bzimage append initrd=/bzroot nomodeset You'll probably want to repeat that on each of the other append lines in this file. If you don't see CPU load statistics on the dashboard, or if you can't use the new web-based terminal, switch to Chrome or Firefox instead of Safari. This is a shortcoming in Safari, not a bug in unRAID. Doesn't apply in 6.5.0 Are you having problems with your Lets Encrypt docker? First, make sure the webgui and docker aren't both trying to use the same port. Beyond that, Lets Encrypt recently made some changes that break things. These issues are not related to the unRAID upgrade, refer to the LE docker thread for help Speedtest complaining about Python? The timing is coincidental, but it is not related to the unRAID upgrade, see the Speedtest thread If you are unable to update your dockers, or if you see this error in the syslog: Feb 3 12:08:59 Unraid-Nas [6503]: The command failed. Error: sh: /usr/local/emhttp/usr/bin/docker: No such file or directory then you need to uninstall the Advanced Buttons plugin. It is not currently compatible with 6.4.1+ See this (the Update Assistant could have warned you of this in advance) If you get this error message when trying to install the preclear plugin: unRAID version (6.4.1 - GCC 7.3.0) not supported. please re-read the "before you upgrade" section of this post. The preclear plugin is not compatible with 6.4.1+ If you see this error message in your logs, please re-read the "before you upgrade" section of this post. rc.diskinfo is part of the preclear plugin, which is not compatible with 6.4.1 (the Update Assistant could have warned you of this in advance) Feb 6 06:21:30 Tower rc.diskinfo[17255]: PHP Warning: file_put_contents(): Only 0 of 2584 bytes written, possibly out of free disk space in /etc/rc.d/rc.diskinfo on line 499 Are you seeing a "wrong csrf_token" token in your logs? Close all your browser tabs (on all computers) that were pointed at unRAID prior to the last reboot. More info If you have severe errors (no lan, array won't start, webgui won't start) try installing on a new flash drive. If it works, that means the problem is with one of your customizations. You can either try to find and fix the problem (if you skipped the "before you upgrade" section, that would be a good place to start), or move forward with the clean flash drive. To continue with the clean drive, copy just the basics (/config/super.dat and your key file) from the old drive to the new one and then reconfigure as needed. Are you still having problems? Review the expanded "Before you upgrade" section above. If that doesn't help, grab your diagnostics (Tools -> Diagnostics) if you can, and reboot into Safe Mode. If your problems go away, then the problem is likely with a plugin. If the problems persist, you'll need additional help. Either way, grab your diagnostics again while in safe mode and attach both sets to a forum post where you clearly explain the issue.
  4. 12 points
    @tillkrueger @jenskolson @trurl @unrateable @jonathanm @1812 @Squid since all of you were active in this thread. I found a way to get the file transfer back. Bring up the Guacamole left panel menu (CTRL ALT SHIFT) Input Method = On Screen Keyboard In the On Screen Keyboard, use ALT (it'll stay on, 'pressed') then TAB, select it using TAB, then ALT again (to turn off) A tip I found too, is that anytime doing a copy or move, always best to use the 'queue' button in the pop-up confirmation dialog so that multiple transfers are sequentially handled. It's easy to get to the queue, I found using this it often mitigates much of my need to see the file transfer progress window. The 'Queue Manager' is easy to get back on the screen by using the top menu, Tools > Queue Manager
  5. 10 points
    Currently unRAID uses basic auth to enter credentials for the web gui, but many password managers don't support this. Would be great if we could get a proper login page. Examples This kind of login page always works with password managers. This does not
  6. 10 points
    Hi Everyone! In an effort to combat spammers that are flooding the forum with spam posts, we are putting a new requirement in place: the first post of any new member MUST be approved by the moderators before normal members can see it and before additional posts will be allowed. We apologize in advance for any inconvenience that this may cause folks wishing to post, but due to the sheer nature of the spammers hitting us, this is one of the better ways for us to combat the issue for the time being. Thank you in advance for your understanding. All the best, The Lime Technology Team
  7. 10 points
    @realies @pwm First let me start by saying that the implications that we are "just trying to look busy" and that we deliberately are trying to "fool" people by using versioning "trickery" is pure rubbish, and I would appreciate and in fact, insist, that you go back and edit your post to strike out those statements. The only thing you got right was indeed we are a small company without the resources to test a wide range of hardware and configurations for an extremely complex set of subsystems. However we never publicly release any software where we know we have introduced risk of data loss, except in rare cases where we clearly state the risk in release notes. As for use of "RC" designation, have you ever studied the linux kernel release methodology? I know your answer is No or else you would know that the "RC" series of a linux kernel is precisely for shaking out bugs and those releases are definitely not ready for any kind of production use. The choice made to promote a kernel from "RC" to "mainline" is also fairly arbitrary. Go take a look at any kernel change log and you will see all kinds of crazy bugs fixed by later patch releases. They typically don't even mark security-related patches as being security-related (because they don't want to give hints to would-be hackers, placing unpatched users at risk). Unless we are forced to, we also don't use the the ".0" release of a new kernel either because we know there will be wider usage with inevitable patch releases (up to 26 now for 4.14). We know from monitoring downloads that most of our user community doesn't update to a .0 unRaid release immediately either. This is the nature of software development and you guys should know better. As for introducing "new features" beyond -rc1 - ok you got me there! Usually we have one or two truly "new" features which require significant coding in each minor release, and usually most of that coding is in place by -rc1. Sometimes big chunks might be staged over several RC's. Sometimes it might take a few RC's to get the UI completely right or handle unexpected cases. Meanwhile, other developers are contributing code. I'm not going to tell those people, "Sorry don't give us those changes because we are still testing this other unrelated feature." Sometimes those features themselves might extend the RC series beyond what we wanted, but that's the price we are willing to pay for now. In the case of the linux kernel, there are thousands of developers which requires far more discipline and rigor to maintain sanity (hence the "merge window" concept). In contrast, we are a small team with good communication (usually) and don't need to be so pedantic. Finally, this stuff is hard. Every user thinks their feature request or bug fix should be the highest priority. Every user wants to see fast progress. Every user can find faults and bugs in any software release. And we have to be as responsive as possible to survive as a company. So how about you cut us a break?
  8. 9 points
    Please report only issues/bugs which are new in the prerelease. We've been holding back on this release a few days waiting for updated Intel ixgbe (10Gbit) OOT driver which builds correctly with 4.18 kernel. But no update yet so this release uses 4.17.19 kernel. Every major subsystem has been updated. In addition @bonienl has added some really cool features and update the default themes to match our new branding. Release notes: Version 6.6.0-rc1 2018-08-31 Base distro: aaa_base: version 14.2 (rev 5) aaa_elflibs: version 15.0 (rev 2) acl: version 2.2.53 acpid: version 2.0.29 adwaita-icon-theme: version 3.28.0 appres: version 1.0.5 (rev 2) at-spi2-atk: version 2.26.2 at-spi2-core: version 2.28.0 at: version 3.1.20 (rev 5) atk: version 2.28.1 attr: version 2.4.48 avahi: version 0.7 (rev2) bash: version 4.4.023 bin: version 11.1 (rev 2) bridge-utils: version 1.5 (rev 2) btrfs-progs: version v4.17 bzip2: version 1.0.6 (rev 3) ca-certificates: version 20180409 cairo: version 1.15.12 celt051: version (rev 2) cifs-utils: version 6.7 (rev 2) coreutils: version 8.29 (rev 2) cpio: version 2.12 (rev 2) cpufrequtils: version 08 (rev 2) cryptsetup: version 1.7.5 (rev 2) curl: version 7.61.0 (CVE-2018-1000300, CVE-2018-1000301, CVE-2018-0500) cyrus-sasl: version 2.1.27_rc8 db48: version 4.8.30 (rev 4) dbus: version 1.12.8 dcron: version 4.5 dejavu-fonts-ttf: version 2.37 (rev 4) dhcpcd: version 7.0.6 diffutils: version 3.6 (rev 2) dmidecode: version 3.1 (rev 2) dnsmasq: version 2.79 (rev 2) docker: version 18.06.1-ce e2fsprogs: version 1.44.2 ebtables: version 2.0.10 (rev 2) editres: version 1.0.7 (rev 2) elvis: version 2.2_0 (rev 4) encodings: version 1.0.4 (rev 2) etc: version 15.0 (rev 6) ethtool: version 4.17 eudev: version 3.2.5 (rev2) file: version 5.33 findutils: version 4.4.2 (rev 2) flex: version 2.6.4 (rev 3) floppy: version 5.5 (rev 2) fontconfig: version 2.12.6 (rev 2) freetype: version 2.9 (rev 2) fribidi: version 1.0.4 fuse: version 2.9.7 (rev3) gawk: version 4.2.1 (rev 2) gd: version 2.2.5 (rev2) gdbm: version 1.15 gdk-pixbuf2: version 2.36.12 genpower: version 1.0.5 (rev 3) getty-ps: version 2.1.0b (rev 4) glew: version 2.1.0 (rev 2) glib2: version 2.56.1 glibc-solibs: version 2.27 (rev 4) glibc-zoneinfo: version 2018e (rev 3) glibc: version 2.27 (rev 4) glu: version 9.0.0 (rev 2) gmp: version 6.1.2 (rev 2) gnome-themes-standard: version 3.22.3 (rev 2) gnupg: version 1.4.23 (CVE-2018-12020) gnutls: version 3.6.2 (rev 2) gptfdisk: version 1.0.3 (rev 2) grep: version 3.1 (rev 2) gtk+3: version 3.22.30 gzip: version 1.9 (rev 2) harfbuzz: version 1.8.1 haveged: version 1.9.2 hdparm: version 9.56 hicolor-icon-theme: version 0.17 (rev 2) hostname: version 3.18 (rev 2) htop: version 2.2.0 icu4c: version 61.1 imlib2: version 1.5.1 inetd: version 1.79s (rev 11) infozip: version 6.0 (rev 4) inotify-tools: version 3.14 (rev 2) intel-microcode: version 20180807 iproute2: version 4.17.0 iptables: version 1.6.2 (rev 2) iputils: version s20140519 (rev 2) kernel-firmware: version 20180814_f1b95fe keyutils: version 1.5.10 (rev 2) kmod: version 25 (rev 2) lbzip2: version 2.5 less: version 530 (rev 3) libaio: version 0.3.111 libarchive: version 3.3.2 (rev 3) libcap-ng: version 0.7.8 (rev 3) libcgroup: version 0.41 (rev 5) libcroco: version 0.6.12 (rev 2) libdaemon: version 0.14 (rev2) libdmx: version 1.1.4 libdrm: version 2.4.92 libedit: version 20180525_3.1 libee: version 0.4.1 (rev 2) libepoxy: version 1.4.3 (rev 2) libestr: version 0.1.10 (rev 2) libevdev: version 1.5.9 (rev 2) libevent: version 2.1.8 (rev 3) libfastjson: version 0.99.8 (rev2) libffi: version 3.2.1 (rev 2) libfontenc: version 1.1.3 (rev 2) libgcrypt: version 1.8.3 (CVE-2018-0495) libgpg-error: version 1.31 libgudev: version 232 (rev 2) libICE: version 1.0.9 (rev 3) libidn: version 1.35 libjpeg-turbo: version 1.5.3 (rev 2) liblogging: version 1.0.6 (rev2) libmnl: version 1.0.4 (rev 3) libnetfilter_conntrack: version 1.0.7 libnfnetlink: version 1.0.1 (rev 2) libnftnl: version 1.1.0 libnl3: version 3.4.0 (rev 2) libpcap: version 1.8.1 (rev 2) libpciaccess: version 0.14 (rev 2) libpng: version 1.6.34 (rev 2) libpthread-stubs: version 0.4 (rev 2) librsvg: version 2.42.5 libseccomp: version 2.3.3 (rev2) libSM: version 1.2.2 (rev 3) libssh2: version 1.8.0 (rev 3) libtasn1: version 4.13 (rev 2) libtirpc: version 1.0.3 (rev 2) libunistring: version 0.9.10 libunwind: version 1.2.1 libusb-compat: version 0.1.5 (rev2) libusb: version 1.0.22 libvirt-php: version 0.5.4 (rev3) libvirt: version 4.6.0 libwebsockets: version 2.4.2 libX11: version 1.6.5 (rev 2) libx86: version 1.1 (rev 3) libXau: version 1.0.8 (rev 3) libXaw: version 1.0.13 (rev 2) libxcb: version 1.13 (rev 2) libXcomposite: version 0.4.4 (rev 3) libXcursor: version 1.1.15 (rev 2) libXdamage: version 1.1.4 (rev 3) libXdmcp: version 1.1.2 (rev 3) libXevie: version 1.0.3 (rev 3) libXext: version 1.3.3 (rev 3) libXfixes: version 5.0.3 (rev 2) libXfont2: version 2.0.3 (rev 2) libXfontcache: version 1.0.5 (rev 3) libXft: version 2.3.2 (rev 4) libXi: version 1.7.9 (rev 2) libXinerama: version 1.1.3 (rev 3) libxkbfile: version 1.0.9 (rev 2) libxml2: version 2.9.8 (rev 2) libXmu: version 1.1.2 (rev 3) libXpm: version 3.5.12 (rev 2) libXrandr: version 1.5.1 (rev 2) libXrender: version 0.9.10 (rev 2) libXres: version 1.2.0 (rev 2) libxshmfence: version 1.3 (rev 2) libxslt: version 1.1.32 (rev 2) libXt: version 1.1.5 (rev 2) libXtst: version 1.2.3 (rev 2) libXxf86dga: version 1.1.4 (rev 3) libXxf86misc: version 1.0.3 (rev 3) libXxf86vm: version 1.1.4 (rev 3) listres: version 1.0.4 (rev 2) lm_sensors: version 3.4.0 (rev 2) logrotate: version 3.14.0 (rev 2) lsof: version 4.91 lsscsi: version 0.29 lvm2: version 2.02.177 lz4: version 1.8.2 mc: version 4.8.21 mesa: version 18.1.2 mkfontdir: version 1.0.7 (rev 2) mkfontscale: version 1.1.3 (rev 2) mozilla-firefox: version 61.0.2 (CVE-2018-12359, CVE-2018-12360, CVE-2018-12361, CVE-2018-12358, CVE-2018-12362, CVE-2018-5156, CVE-2018-12363, CVE-2018-12364, CVE-2018-12365, CVE-2018-12371, CVE-2018-12366, CVE-2018-12367, CVE-2018-12368, CVE-2018-12369, CVE-2018-12370, CVE-2018-5186, CVE-2018-5187, CVE-2018-5188) mpfr: version 4.0.1 (rev 2) mtdev: version 1.1.5 (rev 2) nano: version 2.9.8 ncompress: version (rev 2) ncurses: version 6.1_20180616 net-tools: version 20170208_479bb4a (rev 2) netatalk: version 3.1.11 (rev2) nettle: version 3.4 (rev 2) network-scripts: version 15.0 nghttp2: version 1.32.0 (CVE-2018-1000168) nginx: version 1.14.0 ntfs-3g: version 2017.3.23 (rev 2) ntp: version 4.2.8p12 (CVE-2016-1549, CVE-2018-12327) numactl: version 2.0.11 (rev2) openldap-client: version 2.4.46 openssh: version 7.7p1 openssl-solibs: version 1.1.0i openssl10-solibs: version 1.0.2o openssl: version 1.1.0i (CVE-2018-0732, CVE-2018-0737) p11-kit: version 0.23.12 pango: version 1.42.1 patch: version 2.7.6 (rev 3) (CVE-2018-1000156) pciutils: version 3.5.6 (rev 2) pcre: version 8.42 php: version 7.2.8 pixman: version 0.34.0 (rev 2) pkgtools: version 15.0 (rev 20) pm-utils: version 1.4.1 (rev 6) procps-ng: version 3.3.15 (CVE-2018-1124, CVE-2018-1126, CVE-2018-1125, CVE-2018-1123, CVE-2018-1122) qemu: version 3.0.0 reiserfsprogs: version 3.6.27 (rev2) rpcbind: version 0.2.4 (rev 4) rsync: version 3.1.3 (rev 2) rsyslog: version 8.36.0 samba: version 4.8.4 (CVE-2018-1139, CVE-2018-1140, CVE-2018-10858, CVE-2018-10918, CVE-2018-10919) sed: version 4.5 sessreg: version 1.1.1 (rev 2) setxkbmap: version 1.3.1 (rev 2) shadow: version 4.2.1 (rev 4) shared-mime-info: version 1.9 (rev 2) spice: version 0.14.0 (rev2) sqlite: version 3.24.0 ssmtp: version 2.64 (rev5) startup-notification: version 0.12 (rev 3) sudo: version 1.8.23 sysfsutils: version 2.1.0 (rev 2) sysvinit-scripts: version 2.1 (rev 12) sysvinit: version 2.90 talloc: version 2.1.13 tar: version 1.30 (rev 2) tcp_wrappers: version 7.6 (rev 2) tdb: version 1.3.15 (rev 2) telnet: version 0.17 (rev 4) tevent: version 0.9.36 (rev 2) traceroute: version 2.1.0 (rev 2) transset: version 1.0.2 (rev 2) tree: version 1.7.0 (rev 2) ttyd: version 1.4.0 (rev2) usbredir: version 0.7.1 (rev2) usbutils: version 010 utempter: version 1.1.6 (rev 3) util-linux: version 2.32 vala: version 0.28.1 (rev2) vbetool: version 1.2.2 (rev 2) vsftpd: version 3.0.3 (rev 5) vte3: version 0.44.3 (rev2) wget: version 1.19.5 (CVE-2018-0494) which: version 2.21 (rev 2) xauth: version 1.0.10 (rev 2) xcb-util: version 0.4.0 (rev 3) xclock: version 1.0.7 (rev 3) xdpyinfo: version 1.3.2 (rev 2) xdriinfo: version 1.0.6 (rev 2) xev: version 1.2.2 (rev 2) xf86-input-evdev: version 2.10.6 xf86-input-keyboard: version 1.9.0 (rev 3) xf86-input-mouse: version 1.9.3 xf86-input-synaptics: version 1.9.1 xf86-video-ast: version 1.1.5 (rev 5) xf86-video-mga: version 1.6.5 (rev 3) xf86-video-vesa: version 2.4.0 (rev 3) xfsprogs: version 4.16.1 xhost: version 1.0.7 (rev 2) xinit: version 1.4.0 (rev 2) xkbcomp: version 1.4.2 xkbevd: version 1.1.4 (rev 2) xkbutils: version 1.0.4 (rev 3) xkeyboard-config: version 2.22 (rev 2) xkill: version 1.0.5 (rev 2) xload: version 1.1.3 (rev 2) xlsatoms: version 1.1.2 (rev 2) xlsclients: version 1.1.4 (rev 2) xmessage: version 1.0.5 (rev 2) xmodmap: version 1.0.9 (rev 2) xorg-server: version 1.20.0 (rev 2) xprop: version 1.2.3 (rev 2) xrandr: version 1.5.0 (rev 2) xrdb: version 1.1.1 (rev 2) xrefresh: version 1.0.6 (rev 2) xset: version 1.2.4 (rev 2) xsetroot: version 1.1.2 (rev 2) xsm: version 1.0.4 (rev 2) xterm: version 333 xtrans: version 1.3.5 (rev 2) xwd: version 1.0.7 (rev 2) xwininfo: version 1.1.4 (rev 2) xwud: version 1.0.5 (rev 2) xz: version 5.2.4 zlib: version 1.2.11 (rev 2) Linux kernel: version 4.17.19 intel ixgbe: version 5.3.7 intel ixgbevf: version 4.3.5 highpoint r750: version 1.2.11 highpoint rr3740a: version 1.17.0 added per customer request: CONFIG_BLK_DEV_SKD: STEC S1120 Block Driver CONFIG_BNXT: Broadcom NetXtreme-C/E support CONFIG_CHR_DEV_ST: SCSI tape support changed from built-in to module: CONFIG_BLK_DEV_SR: SCSI CDROM support removed CONFIG_SENSORS_IT87: ITE IT87xx and compatibles it87: version 20180709 groeck Linux Driver for ITE LPC chips (https://github.com/groeck/it87) set CRYPTO_DEV_SP_PSP=N otherwise udev deadlocks on threadripper Management: Docker: add optional per-container wait before starting Enable IPv6 for NTP rc.cpufreq: For CPUs using intel_pstate, always use the performance governor. This also provides power savings on Intel processors while avoiding the ramp-up lag present when using the powersave governor (which is the default if ondemand is requested on these machines). restore docker custom networks upon docker start update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} webgui: docker: Correct docker container icon name generation webgui: docker: added cpu load and memory load display webgui: docker: added shell/bash selection for console webgui: docker: Make cpu-load and mem-load only visible in advanced mode webgui: Show accumulated encryption status webgui: Prevent openbox from clipping webgui: Plugins: Show support thread if present webgui: Remove control codes, and extended ascii characters from plugin urls on install webgui: Update link for privileged help text webgui: fix regex matching for unraid.net domain name validation when using new openssl1.1 webgui: docker: Prevent arbitrary bash execution or redirection on docker create/run commands webgui: Plugins: Preserve support link when updating plugin webgui: diagnostics: Replace consecutive repeated lines in syslog webgui: Remove empty entries when storing individual disk settings webgui: docker: fix connect container console to new window webgui: Use timeout in command execution of diagnostics webgui: Fixed 'Update All Containers' button sometimes hidden in docker list webgui: Added version control in docker API calls webgui: Show docker allocations in column format webgui: fix css help button in themes azure and gray webgui: Added docker autostart wait period webgui: Added CPU selection to docker container edit section webgui: Verify internet access using NCSI method NCSI = network connection status indicator. This method tries to access a specific Microsoft site to test internet access. The same method is used in Windows. webgui: Added docker autostart wait period webgui: New CPU pinning functionality webgui: Change wording on dashboard page "memory total usable" webgui: Include meminfo in diagnostics webgui: Docker containers page: show container starting up message Starting docker service and auto-starting containers has been decoupled. This lets the docker page return as soon as the service is ready. The container overview page shows a new message, and will automatically reload to update the status until all containers are auto-started webgui: VMs: preserve XML custom settings in VM config updates webgui: dockerMan: Avoid filename collisions on FAT32 webgui: Extract disk log from multiple rotated logs webgui: theme-match marketing site
  9. 9 points
    Can I manually create and use multiple btrfs pools? Work in progress. Multiple cache pools are not supported yet, though they are planned for the future, until then you can still use multiple btrfs pools with the help of the Unassigned Devices plugin. There are some limitations and most operations creating and maintaining the pool will need to be made using the command line, so if you're not comfortable with that wait for LT to add the feature. If you want to use the now, here's how: -If you don't have yet install the Unassigned Devices plugin. -Better to start with clean/wiped devices, so wipe them or delete any existing partitions. -Using UD format the 1st device using btrfs, choose the mount point name and optionally activate auto mount and share -Using UD mount the 1st device, for this example it will be mounted at /mnt/disks/yourpoolpath -Using UD format the 2nd device using btrfs, no need to change the mount point name, and leave auto mount and share disable. -Now on the console/SSH add the device to the pool by typing: btrfs dev add -f /dev/sdX1 /mnt/disks/yourpoolpath Replace X with correct identifier, note the 1 in the end. -Device will be added and you will see the extra space on the 1st disk free space graph, whole pool will be accessible in the original mount point, in this example: /mnt/disks/yourpoolpath -By default the disk is added in single profile mode, i.e., it will extend the existing volume, you can change that to other profiles, like raid0, raid1, etc, e.g., to change to raid1 type: btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/disks/yourpoolpath See here for the other available modes. -If you want to add more devices to that pool just repeat the process above Notes -Only mount the first device with UD, all other members will mount together despite nothing being shown on UD's GUI, same to unmount, just unmount the 1st device to unmount the pool. -It appears that if you mount the pool using the 1st device used/free space are correctly reported by UD, unlike if you mount using e.g. the 2nd device, still for some configurations the space might be incorrectly reported, you can always check it using the command line: btrfs fi usage /mnt/disks/yourpoolpath -You can have as many unassigned pools as you want, example how it looks on UD: sdb+sdc+sdd+sde are part of a raid5 pool, sdf+sdg are part of raid1 pool, sdh+sdi+sdn+sdo+sdp are another raid5 pool, note that UD sorts the devices by identifier (sdX), so if sdp was part of the first pool it would still appear last, UD doesn't reorder the devices based on if they are part of a specific pool. You can also see some of the limitations, i.e., no temperature is shown for the secondary pools members, though you can see temps for all devices on the dashboard page, still it allows to easily use multiple pools until LT adds multiple cache pools to Unraid. Remove a device: -to remove a device from a pool type (assuming there's enough free space): btrfs dev del /dev/sdX1 /mnt/disks/yourpoolpath Replace X with correct identifier, note the 1 in the end Note that you can't go below the used profile minimum number of devices, i.e., you can't remove a device from a 2 device raid1 pool, you can convert it to single profile first and then remove the device, to convert to single use: btrfs balance start -f -dconvert=single -mconvert=single /mnt/disks/yourpoolpath Then remove the device normally like above. Replace a device: To replace a device from a pool (if you have enough ports to have both old and new devices connected simultaneously): You need to partition the new device, to do that format it using the UD plugin, you can use any filesystem, then type: btrfs replace start -f /dev/sdX1 /dev/sdY1 /mnt/disks/yourpoolpath Replace X with source, Y with target, note the 1 in the end of both, you can check replacement progress with: btrfs replace status /mnt/disks/yourpoolpath If the new device is larger you need to resize it to use all available capacity, you can do that with: btrfs fi resize X:max /mnt/disks/yourpoolpath Replace X with the correct devid, you can find that with: btrfs fi show /mnt/disks/yourpoolpath
  10. 8 points
    I am starting a series of videos on pfSense. Both physical and VM instances will be used. Topics such as using a failover physical pfSense to work with a VM pfSense. Setting up OpenVPN (both an OpenVPN server and OpenVPN multiple clients). Using VLANs. Blocking ads. Setting up squid and squid guard and other topics. T This part is an introduction part gives an overview of the series of videos and talks about pfSense and its advantages. Second part of is on hardware and network equipment Part 3 install and basic config Part 4 customize backup and aupdate Part 5 DHCP, Interfaces and WIFI Part 6 Pfsense and DNS Part 7 - Firewall rules, Portforwarding/NAT, Aliases and UPnp Part 8 Open NAT for XBOX ONE and PS4
  11. 8 points
    This Docker is in BETA status. Some controllers may not be detected, there may be errors thrown. Please help in resolving these issues if this occurs if you use this beta version. Installation Via the Community Application: Search for "DiskSpeed" Manual Installation (The Community Applications plugin is having issues currently, here's a work around for now) Save the attached "my-DiskSpeed.xml" file to your NAS under \\tower\flash\config\plugins\dockerMan\templates-user View the Docker tab in your unRAID Administrator , click on "Add Container" Under "Select a template", pick "my-DiskSpeed" The defaults should work as-is unless you have port 18888 already in use. If so, change the Web Port & WebUI settings to a new port number. The Docker will create a directory called "DiskSpeed" in your appdata directory to hold persistent data. Note: Privileged mode is required so that the application can see the controllers & drives on the host OS. This docker will use up to 512MB of RAM. RAM optimization will happen in a later BETA. Running View the Docker tab in your unRAID Administrator and click on the icon next to "DiskSpeed" and select WebUI. A new window will open. On first time run (or after the Docker app is updated or you select to rescan hardware), the application will scan your system to locate drive controllers & the hard drives attached to them. Drive Images As of this post, the Hard Drive Database (HDDB) has 825 drive models in 20 brands. If you have one or more drives that do not have a predefined image in the HDDB, you have a couple options available - wait for me to add the image which will be displayed after you click "Rescan Controllers" or you can add the drive yourself by editing it and uploading a drive image for it. You can view drive images in the HDDB to see if there's an image that'll fit your drive and optionally upload it so others can benefit. Controller & Drive Identification Issues Some drives, notably SSD's, do not reveal the Vendor correctly or at all. If you view the Drive information and it has the same value for the vendor as the model or an incorrect or missing Vendor, please inform me so that I can manually add the drive to the database or add code to handle it. If you have a controller that is not detected, please notify me. Benchmarking Drives The current method of benchmarking the hard drives is to read the hard drive at certain percentages for 15 seconds and takes the average speed over each of those seconds except for the first 2 seconds which tend to trend high. Hard Drives report an optimal block size to use while reading but if not, a block size of 128K is used. Since Docker under unRAID requires the array to be running, SpeedGap detection was added to detect disk drive activity during the test by comparing the smallest & largest amount of bytes read over the 15 seconds. If a gap is detected over a given size which starts at 45MB, the gap allowed is increased by 5MB and the spot retested. If a drive keeps triggering the SpeedGap detection over each spot, you may need to disable the SpeedGap detection as the drive is very erratic in its read speeds. One drive per controller is tested at the same time. In the future, each drive will be tested to see it's maximum transfer rate and the system will be tested to see how much data each controller can transfer and how much data the entire system bus can handle. Then multiple drives over multiple controllers will be read simultaneously while keeping the overall bandwidth by controller & system under the maximum transfer rate. Contributing to the Hard Drive Database If you have a drive that doesn't have information in the Hard Drive Database other than the model or you've performed benchmark tests, a button will be displayed at the bottom of the page labeled "Upload Drive & Benchmark Data to the Hard Drive Database". The HDDB will display information given up by the OS for the drives and the average speed graphs for comparison. Application Errors If you get an error message, please post the error here and the steps you took to cause it to happen. There will be a long string of java diagnostics after the error message (java stack) that you do not need to include, just the error message details. If you can't get past the Scanning Hardware screen, change the URL from http://[ip]:[port]/ScanControllers.cfm to http://[ip]:[port]/isolated/CreateDebugInfo.cfm and hit enter. Note: The unRAID diagnostic file doesn't provide any help. If submitting a diagnostic file, please use the link at the bottom of the controllers in the Diskspeed GUI. Home Screen (click top label to return to this screen) Controller Information Drive Information Drive Editor my-DiskSpeed.xml
  12. 8 points
    I think Thanks should be directed at all those members that have been dealing with the mess the last few months. @dlandon and @Squid have been working behind the scenes to try and clean up, and obviously @Frank1940 has put a great deal of work in here. There are many others too. The unsung heroes imho.... This has highlighted how fragile things are, and those of us that maintain plugins/containers have to maintain these things and I feel we owe a responsibility to do so, or at least state that life has taken over as PhAzE did when he wound things down.
  13. 8 points
    This video is an overview and a quick tutorial on the newly released unRAID 6.4.0 stable. This video will compare side by side unRAID 6.4.0 with its predecessor 6.3.5 and see the differences and improvements. It shows how to safely upgrade from 6.3 to 6.4 then how to set up your SSL certificate for HTTPS access and then how to set up an encrypted drive for the array.
  14. 7 points
    Hi Guys. After many requests I have made a tutorial for setting up a docker container for pi-hole. This gives us network wide adblocking. Hope you find it useful
  15. 7 points
    Comically late to the party, but I'll throw these in here as a very simple concept. and It's just a simple logo that could be used to brand unraid, with the blocks representing parity, it would work at any size, and would be dead easy to render as a vector. At this point though I'm sure something much better has been designed, it just stuck in my head.
  16. 7 points
    Dontlookoverthere over on the unRAID subreddit figured out how to get the plugin running again with a simple edit to the plg: https://www.reddit.com/r/unRAID/comments/7wjpus/preclear_working_on_641/ Caveat emptor and all that. I'm testing it on a drive in my server presently, it seems to be working properly. ohlin5 in the same post has provided an installable version that works with 6.4.1 and should maintain backwards compatiblity here: https://raw.githubusercontent.com/dohlin/unRAID-plugins/master/plugins/preclear.disk.plg
  17. 6 points
    CA Mover Tuning A simple little plugin (mainly created for my own purposes) that will let you fine tune the operation of the mover script On scheduled runs of mover, only actually move file(s) if the the cache drive is getting full (selectable threshold) On scheduled runs of mover, optionally don't move if a parity check / rebuild is already in progress Ability to completely disable the scheduled runs of mover if so desired (Not sure if there's much demand for this) Manually executed runs of mover ("Move Now" button) can either follow the rules for schedules, or always move all files After installation (any guesses as to how to install the plugin?), the default settings are set so that there is no difference as to how unRaid normally handles things. You'll find it's settings within Settings - Scheduler
  18. 6 points
    I would love a progress bar/percentage thingy for mover
  19. 6 points
    It really is time for @limetech to incorporate the UD functionality. I do not have the time nor the interest in updating UD for the new GUI.
  20. 6 points
    To upgrade: If you are running any 6.4 stable release or any 6.4-rc/6.5-rc 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 Maybe we should have called this 6.4.2 because this is primarily a security update for Meltdown/Spectre and a base package update. However due to the length of the change log, and inclusion of a number of bug fixes and UI improvements, we decided to go ahead and publish this as the next minor release. Refer also to @ljm42 awesome 6.4 Update Notes which still are helpful if you are upgrading from a pre-6.4 release. Following are the Release Notes: Version 6.5.0 2018-03-13 The primary purpose of this release is to update the Linux kernel to the latest version which completes mitigation for Meltdown/Spectre vulnerabilities. In addtion we have updated a number of base packages, made several UI improvements, especially in the VM and Docker Managers, and fixed a number of bugs. Due to security updates all users are encouraged to update. Summary: For new installations, we now reference Google public NTP servers instead of pool.ntp.org. Updated linux kernel includes more patches related to Meltdown/Spectre. Refreshed base packages to latest versions. We added a workaround for Safari to display CPU Load Statistics correctly. Resident network guru bonienl continues to make networking refinements: Fixed default gateway with different metrics. Now same gateway with multiple metrics properly set up Fixed route_up and route_down functions. Now adding and removing routes handles IPv6 link local addresses and it is allowed to add the same route multiple times with different metric and interface. Routing table shows interface name too with default routes Network settings page is updated thru a websocket (/sub/dhcp), this ensures info is always present. Another nice advantage of websockets. Cleanup of network.cfg file. Only necessary settings are stored. This greatly reduces the number of entries. Some fixes in the network settings page itself, better user experience. IPv6 routes have their own metric value, can be set independently of IPv4 Docker fixes for custom networks Some code cleanup Another nice feature added by bonienl is the ability to downgrade to the previous unRAID-OS release. Upgraded noVNC. This is very much improved, give it a try! Other misc. bug fixes. Base distro: adwaita-icon-theme: version 3.26.1 appres: version 1.0.5 at-spi2-core: version 2.26.2 atk: version 2.26.1 bash: version 4.4.019 btrfs-progs: version v4.15.1 cairo: version 1.15.10 coreutils: version 8.29 cyrus-sasl: version 2.1.26 (rev3) dbus: version 1.12.6 dhcpcd: version 7.0.1 docker: version 17.12.1 e2fsprogs: version 1.43.9 editres: version 1.0.7 etc: version 15.0 ethtool: version 4.15 eudev: version 3.2.5 freetype: version 2.9 fuse: version 2.9.7 (inline_name size 64 patch) gawk: version 4.2.1 glib2: version 2.54.3 glibc-solibs: version 2.27 glibc-zoneinfo: version 2018c glibc: version 2.27 gnutls: version 3.6.2 gtk+3: version 3.22.28 guile: version 2.2.3 gzip: version 1.9 harfbuzz: version 1.7.6 hdparm: version 9.54 hostname: version 3.18 htop: version 2.1.0 icu4c: version 60.2 inetd: version 1.79s (rev10) iproute2: version 4.15.0 iptables: version 1.6.2 kernel-firmware: version 20180222_7344ec9 kmod: version 25 less: version 530 libXcursor: version 1.1.15 libXfont2: version 2.0.3 libXres: version 1.2.0 libdrm: version 2.4.91 libevdev: version 1.5.8 libfastjson: version 0.99.8 libgcrypt: version 1.8.2 libjpeg-turbo: version 1.5.3 libmnl: version 1.0.4 (rev2) libnftnl: version 1.0.9 libpciaccess: version 0.14 librsvg: version 2.42.3 libseccomp: version 2.3.3 libtasn1: version 4.13 libunistring: version 0.9.9 libvirt-php: version 0.5.4 (rev2) libvirt: version 4.0.0 libxcb: version 1.13 libxml2: version 2.9.7 libxshmfence: version 1.3 libxslt: version 1.1.32 listres: version 1.0.4 logrotate: version 3.13.0 lsof: version 4.90 lvm2: version 2.02.176 lxterminal: version 0.3.1 lz4: version mc: version 4.8.20 mesa: version 17.3.6 mkfontscale: version 1.1.3 mpfr: version 4.0.1 nano: version 2.9.3 net-tools: version 20170208_479bb4a nettle: version 3.4 network-scripts: version 15.0 (rev6) ntp: version 4.2.8p11 (CVE-2016-1549, CVE-2018-7182, CVE-2018-7170, CVE-2018-7184, CVE-2018-7185) openldap-client: version 2.4.45 p11-kit: version 0.23.10 pango: version 1.40.14 patch: version 2.7.6 pciutils: version 3.5.6 php: version 7.2.3 pkgtools: version 15.0 (rev5) qemu: version 2.11.1 rpcbind: version 0.2.4 (rev3) rsync: version 3.1.3 (CVE-2017-16548, CVE-2018-5764) rsyslog: version 8.33.0 samba: version 4.7.6 (CVE-2018-1050, CVE-2018-1057) shadow: version 4.2.1 (rev3) shared-mime-info: version 1.9 smartmontools: version 6.6 spice-protocol: version 0.12.13 spice: version 0.14.0 sqlite: version 3.22.0 sudo: version 1.8.22 sysvinit-scripts: version 2.1 (rev6) talloc: version 2.1.11 tar: version 1.30 tdb: version 1.3.15 tevent: version 0.9.36 traceroute: version 2.1.0 usbutils: version 009 util-linux: version 2.31.1 vte3: version 0.44.3 wget: version 1.19.4 (rev2) xdriinfo: version 1.0.6 xf86-video-vesa: version 2.4.0 xfsprogs: version 4.15.1 xkbcomp: version 1.4.1 xkeyboard-config: version 2.22 xorg-server: version 1.19.6 xterm: version 331 Linux kernel: version 4.14.26 with scsi rcu patch: https://patchwork.kernel.org/patch/10236213/ Management: accommodate buggy dhcp servers which hand out a single host IPv6 address fix desktop gui mode by re-enabling graphics compositing due to new mesa version hide php warnings for now since php 7.2 is more strict shfs: support run-time logging level change upon upgrade strip metric value from GATEWAY if present update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} webgui: noVNC: version 1.0.0 webgui: tablesorter: version v2.29.6 and fixed sorting issue in browser webgui: Miscellaneous corrections and optimizations webgui: Make "waiting" message consistent across all pages webgui: Corrected wrong menu references in Dashboard Apps webgui: Corrected memory display on Dashboard page webgui: Link to Schedule from Array Operations webgui: Prevent text overlapping input boxes on Edit Docker Page webgui: Don't show Template Dropdown in Add Container when referrer is Community Applications webgui: Update app icons container slidedown speed webgui: Load docker and vm lists in background to speed up rendering webgui: Update plugins table inline instead of rebuilding the complete list webgui: Disable buttons while containers/vms are started or stopped webgui: Rearrange buttons on Docker overview page webgui: Add ALL VMs start & stop operation webgui: Allow VM + Docker restart with animation webgui: Narrow LOG column in Docker list webgui: Increase VM wait for shutdown time to 20s webgui: Added user preference for VM list webgui: Plugin manager code optimization webgui: Standardize VM folder structure, other code cleanup webgui: Improved docker used ports and IPs list webgui: Enhancements to Docker settings and overview webgui: Fixed regression error in Docker settings webgui: Fixed version/date extraction in previous unRAID version webgui: Corrected PHP warnings webgui: dashboard cpu bar updates using Safari browser (now uses SSE instead of Websockets) webgui: Add ability for pluginMan to not install the .plg file webgui: Enhancements to Docker custom network settings webgui: enhancement to diagnostics: Don't anonymize system share names (such as appdata,domains,isos,system) webgui: Fixed container update hanging when network doesn't exist webgui: network refinements webgui: docker: support special characters in webGUI, Support and Project Context menus webgui: Add controls to enable/disable and specify custom ports for TELNET and SSH webgui: Permit up to 4 NTP servers to be configured. webgui: Add "Downgrade to previous version" selection webgui: Add "Start Page" selection webgui: vm manager: remove obsolete on-hover comment about Nvidia and Hyper-V on VM Edit page webgui: vm manager: VM Edit: Hide Cdrom bus dropdown if cdrom is blank webgui: vm manager: VM Edit: improve usb3 option prevention when windows 7/xp are detected webgui: vm manager: VM Edit: allow specifying ROM BIOS for Graphics Cards webgui: vm manager: VM Edit: added new qemu-xhci usb controller option; rearranged usb controller dropdown on vm edit page webgui: vm manager: VM Edit: basic/advanced view toggle replaced with form/xml view webgui: vm manager: VM Edit: removed help regarding usb hotplug not supported yet webgui: vm manager: VM Settings: added vm action upon host shutdown, either Shutdown VMs or Hibernate VMs
  21. 6 points
    Mainly because my keyboard is worn out from replying "Uninstall Advanced Buttons", today's update features an "Update Assistant" which sits on the Tools Menu (next to Update OS) This performs a couple of checks to see if you're going to have problems if you update your OS. In otherwords, you run it before hitting Update OS Problems it will catch: Plugins up to date Incompatible plugins with the updated unRaid OS At least 4G memory Any disabled disks present (doesn't actually hinder an update, but really something you'd be nuts not to take care of prior to an update) Cache drive partition starts on sector 64 (would catch all those "unmountable" cache drives after updating) Basic RW test to the flash drive Zenstates set up in the go file Any excess parameters on the emhttp line in the go file Tests are not definitive, there may be valid use cases if there's a failure, but it will at least hopefully save me from buying another keyboard again EDIT: More tests coming...
  22. 6 points
    for radarr "press enter to exit" loop try exec'ing in to the container and running cd /opt/radarr && curl -o - http://download.sonarr.tv/hotfixes/regression-mono-5.10/NLog.dll.gz | gunzip -c > NLog.dll and then restarting the container
  23. 5 points
    @Wisnaeme im shortly going to be releasing a krusader docker image which of course i will support, might be worth switching to as this one is no longer supported, and is an older version of krusader (and a beta at that!).
  24. 5 points
    Sorry for the delay, guys. I'm very short on time so I had to decrease the level of support dedicated to this plugin. If someone could verify if the script is working fine with v6.5 I do appreciate that.
  25. 5 points