Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 02/21/17 in Reports

  1. 22 points
    Since I can remember Unraid has never been great at simultaneous array disk performance, but it was pretty acceptable, since v6.7 there have been various users complaining for example of very poor performance when running the mover and trying to stream a movie. I noticed this myself yesterday when I couldn't even start watching an SD video using Kodi just because there were writes going on to a different array disk, and this server doesn't even have a parity drive, so did a quick test on my test server and the problem is easily reproducible and started with the first v6.7 release candidate, rc1. How to reproduce: -Server just needs 2 assigned array data devices (no parity needed, but same happens with parity) and one cache device, no encryption, all devices are btrfs formatted -Used cp to copy a few video files from cache to disk2 -While cp is going on tried to stream a movie from disk1, took a long time to start and would keep stalling/buffering Tried to copy one file from disk1 (still while cp is going one on disk2), with V6.6.7: with v6.7rc1: A few times transfer will go higher for a couple of seconds but most times it's at a few KB/s or completely stalled. Also tried with all unencrypted xfs formatted devices and it was the same: Server where problem was detected and test server have no hardware in common, one is based on X11 Supermicro board, test server is X9 series, server using HDDs, test server using SSDs so very unlikely to be hardware related.
  2. 18 points
    tldr: If you require hardware support offered by the Linux 5.x kernel then I suggest you remain on 6.8.0-rc7 and wait until 6.9.0-rc1 is published before upgrading. The "unexpected GSO type" bug is looking to be a show stopper for Unraid 6.8 using Linux kernel 5.3 or 5.4 kernel. We can get it to happen easily and quickly simply by having any VM running and then also start a docker App where Network Type has been set to "Custom : br0" (in my case) and I've set a static IP for the container or toggle between setting static IP and letting docker dhcp assign one. There are probably a lot of users waiting for a stable release who will see this issue, and therefore, I don't think we can publish with this bug. The bug does not occur with any 4.19.x or 4.20.x Linux kernel; but does occur with all kernels starting with 5.0. This implies the bug was introduced with some code change in the initial 5.0 kernel. The problem is that we are not certain where to report the bug; it could be a kernel issue or a docker issue. Of course, it could also be something we are doing wrong, since this issue is not reported in any other distro AFAIK. We are continuing investigation and putting together a report to submit either to kernel mailing list or as a docker issue. In any case, an actual fix will probably take quite a bit more time, especially since we are heading into the holidays. Therefore this is what we plan to do: For 6.8: revert kernel to 4.19.87 and publish 6.8.0-rc8. Those currently running stable (6.7.2) will see no loss of functionality because that release is also on 4.19 kernel. Hopefully this will be last or next to last -rc and then we can publish 6.8 stable. Note: we cannot revert to 4.20 kernel because that kernel is EOL and has not had any updates in months. For 6.9: as soon as 6.8 stable is published we'll release 6.9.0-rc1 on next release branch. This will be exactly the same as 6.8 except that we'll update to latest 5.4 kernel (and "unexpected GSO type" bug will be back). We will use the next branch to try and solve this bug. New features, such as multiple pools, will be integrated into 6.10 release, which is current work-in-progress. We'll wait a day or two to publish 6.8-rc8 with reverted kernel in hopes those affected will see this post first.
  3. 10 points
    New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device. You will probably notice a slight difference in speed of extract messages. There is still a 'sync' command at the end, which causes each device to spin up serially as Linux kernel syncs each device (why does kernel do this serially? I have no idea). I am tempted to remove this because a Reboot of course spins everything up in parallel, but I'm concerned about users out there who might just hit Reset button and USB flash write data is not fully written. Forms based authentication If you have set a root password for your server, upon boot you'll now see a nice login form. There still is only one user for Unraid so for username enter root. This form should be compatible with all major password managers out there. We always recommend using a strong password. We have auto-logout set to 1 hour. Linux kernel 5.3 default scheduler now 'mq-deadline' enabled Huge Page support, though no UI control yet binfmt_misc support added "Vega 10 Reset bug" patch more device drivers Some out-of-tree (oot) drivers are currently omitted either because the source code doesn't compile or driver doesn't work with the 5.3 kernel: Intel ixgbe [does not build] (using in-tree driver) Highpoint r750 [does not work] Highpoint rr3740a [does not build] This is always the risk with including vendor-supplied drivers. Until the vendor fixes their code we must omit their driver. md/unraid driver Introduced "multi-stream" support: Reads on devices which are not being written should run at full speed. In addition, if you have set the md_write_method tunable to "reconstruct write", then while writing, if any read streams are detected, the write method is switched to "read/modifywrite". Parity sync/check should run at full speed by default. Parity sync/check can be throttled back in presence of other active streams. The "stripe pool" resource is automatically shared evenly between all active streams. As a result got rid of some Tunables: md_sync_window md_sync_thresh and added some tunables: md_queue_limit md_sync_limit Please refer to Settings/Disk Settings help text for description of these settings. Remaining issue: some users have reported slower parity sync/check rates for very wide arrays (20+ devices) vs. 6.7 and earlier releases - we are still studying this problem. WireGuard support - available as a plugin via Community Apps. Our WireGuard implementation and UI is still a work-in-process; for this reason we have made this available as a plugin, though the latest WireGuard module is included in our Linux kernel. Full WireGuard implementation will be merged into Unraid OS itself in a future release. I want to give special thanks to @bonienl who wrote the plugin with lots of guidance from @ljm42 - thank you! I also should give a shout out to @NAS who got us rolling on this. If you don't know about WireGuard it's something to look into! Guide here: WS-Discovery support - Finally you can get rid of SMBv1 and get reliable Windows network discovery. This feature is configured on the Settings/SMB Settings page and enabled by default. Also on same settings page is Enable NetBIOS setting. This is enabled by default, however if you no longer have need for NetBIOS discovery you can turn it off. When turned off, Samba is configured to accept only SMBv2 protocol and higher. Added mDNS client support in Unraid OS. This means, for example, from an Unraid OS terminal session to ping another Unraid OS server on your network you can use (e.g., 'tower'): ping tower.local instead of ping tower Note the latter will still work if you have NetBIOS enabled. User Share File System (shfs) changes: Integrated FUSE-3 - This should increase performance of User Share File System somewhat. Fixed bug with hard link support. Previously a 'stat' on two directory entries referring to same file would return different i-node numbers, thus making it look like two independent files. This has been fixed however there is a config setting on Settings/Global Share Settings called "Tunable (support hard links)". The default is Yes, but with certain very old media and DVD players which access shares via NFS, you may need to set this to No. Note: if you have custom config/extra.cfg file, get rid of it. Other improvements/bug fixes: Format - during Format any running parity sync/check is automatically Paused and then resumed upon Format completion. Encryption - an entered passphrase is not saved to any file. Also included an API for Unassigned devices plugin to open encrypted volumes. Fixed bug where multi-device btrfs pool was leaving metadata set to dup instead of raid1. Several other small bug fixes and improvements. Numerous base package updates. Finally - please note that AFP is now deprecated and we plan to remove in Unraid 6.9 release. Version 6.8.0-rc1 2019-10-11 Base distro: aaa_elflibs: version 15.0 build 11 acpid: version 2.0.32 at-spi2-atk: version 2.34.0 at-spi2-core: version 2.34.0 atk: version 2.34.1 bash: version 5.0.011 btrfs-progs: version 5.2.2 bzip2: version 1.0.8 ca-certificates: version 20190826 cifs-utils: version 6.9 cryptsetup: version 2.2.1 curl: version 7.66.0 dbus: version 1.12.16 dbus-glib: version 0.110 dhcpcd: version 8.0.6 docker: version 19.03.3 e2fsprogs: version 1.45.4 encodings: version 1.0.5 etc: version 15.0 ethtool: version 5.3 expat: version 2.2.9 file: version 5.37 findutils: version 4.7.0 freetype: version 2.10.1 fuse3: version 3.6.2 gdbm: version 1.18.1 gdk-pixbuf2: version 2.38.2 git: version 2.23.0 glib2: version 2.62.0 glibc-solibs: version 2.30 glibc-zoneinfo: version 2019c glibc: version 2.30 glu: version 9.0.1 gnutls: version 3.6.10 gtk+3: version 3.24.10 harfbuzz: version 2.6.0 haveged: version 1.9.8 hostname: version 3.22 hwloc: version 1.11.13 icu4c: version 64.2 intel-microcode: version 20190918 iproute2: version 5.3.0 iptables: version 1.8.3 iputils: version 20190709 irqbalance: version 1.6.0 less: version 551 libICE: version 1.0.10 libX11: version 1.6.8 libXi: version 1.7.10 libXt: version 1.2.0 libarchive: version 3.4.0 libcap-ng: version 0.7.10 libcroco: version 0.6.13 libdrm: version 2.4.99 libedit: version 20190324_3.1 libevdev: version 1.7.0 libevent: version 2.1.11 libgcrypt: version 1.8.5 libgudev: version 233 libjpeg-turbo: version 2.0.3 libnftnl: version 1.1.4 libnl3: version 3.5.0 libpcap: version 1.9.1 libpciaccess: version 0.16 libpng: version 1.6.37 libpsl: version 0.21.0 librsvg: version 2.44.14 libseccomp: version 2.4.1 libssh2: version 1.9.0 libtasn1: version 4.14 libusb: version 1.0.23 libvirt-php: version 0.5.5 libvirt: version 5.7.0 (CVE-2019-10161, CVE-2019-10166, CVE-2019-10167, CVE-2019-10168) libwebp: version 1.0.3 libzip: version 1.5.2 logrotate: version 3.15.1 lsof: version 4.93.2 lsscsi: version 0.30 lvm2: version 2.03.05 lz4: version 1.9.1 mkfontscale: version 1.2.1 mozilla-firefox: version 68.0.2 (CVE-2019-11751, CVE-2019-11746, CVE-2019-11744, CVE-2019-11742, CVE-2019-11736, CVE-2019-11753, CVE-2019-11752, CVE-2019-9812, CVE-2019-11741, CVE-2019-11743, CVE-2019-11748, CVE-2019-11749, CVE-2019-5849, CVE-2019-11750, CVE-2019-11737, CVE-2019-11738, CVE-2019-11747, CVE-2019-11734, CVE-2019-11735, CVE-2019-11740, CVE-2019-11754, CVE-2019-9811, CVE-2019-11711, CVE-2019-11712, CVE-2019-11713, CVE-2019-11714, CVE-2019-11729, CVE-2019-11715, CVE-2019-11716, CVE-2019-11717, CVE-2019-1 1718, CVE-2019-11719, CVE-2019-11720, CVE-2019-11721, CVE-2019-11730, CVE-2019-11723, CVE-2019-11724, CVE-2019-11725, CVE-2019-11727, CVE-2019-11728, CVE-2019-11710, CVE-2019-11709) nano: version 4.5 ncurses: version 6.1_20190720 net-tools: version 20181103_0eebece nettle: version 3.5.1 nghttp2: version 1.39.2 nginx: version 1.16.1 (CVE-2019-9511, CVE-2019-9513, CVE-2019-9516) nodejs: version 10.16.3 nss-mdns: version 0.14.1 ntp: version 4.2.8p13 openldap-client: version 2.4.48 openssh: version 8.0p1 openssl-solibs: version 1.1.1d openssl: version 1.1.1d p11-kit: version 0.23.18.1 pcre2: version 10.33 php: version 7.2.23 (CVE-2019-11042, CVE-2019-11041) pixman: version 0.38.4 pkgtools: version 15.0 procps-ng: version 3.3.15 qemu: version 4.1.0 (CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091) qrencode: version 4.0.2 rpcbind: version 1.2.5 rsyslog: version 8.1908.0 samba: version 4.10.8 (CVE-2019-10197) sdparm: version 1.10 sessreg: version 1.1.2 setxkbmap: version 1.3.2 sg3_utils: version 1.44 shadow: version 4.7 shared-mime-info: version 1.12 sqlite: version 3.29.0 sysvinit-scripts: version 2.1 sysvinit: version 2.96 talloc: version 2.3.0 tdb: version 1.4.2 tevent: version 0.10.1 ttyd: version 1.5.2 usbutils: version 012 util-linux: version 2.34 wget: version 1.20.3 wireguard: version 0.0.20190913 wsdd: version 20180618 build 2 xauth: version 1.1 xclock: version 1.0.9 xfsprogs: version 5.2.1 xkeyboard-config: version 2.27 xorg-server: version 1.20.5 xrandr: version 1.5.1 xterm: version 348 xwininfo: version 1.1.5 zstd: version 1.4.3 Linux kernel: version 5.3.6 default scheduler now mq-deadline CONFIG_BINFMT_MISC: Kernel support for MISC binaries CONFIG_DEBUG_FS: Debug Filesystem CONFIG_HUGETLBFS: HugeTLB file system support CONFIG_ICE: Intel(R) Ethernet Connection E800 Series Support CONFIG_IGC: Intel(R) Ethernet Controller I225-LM/I225-V support CONFIG_MLX5_CORE_IPOIB: Mellanox 5th generation network adapters (connectX series) IPoIB offloads support CONFIG_SCSI_SMARTPQI: Microsemi PQI Driver CONFIG_WIREGUARD: IP: WireGuard secure network tunnel patch: fix_vega_reset (user request) patch: increase BLK_MAX_REQUEST_COUNT from 16 to 32 oot: LimeTech md/unraid: version 2.9.10 (multi-stream support) oot: Highpoint rsnvme: version v1.2.16_19_05_06 oot: Tehuti tn40xx: version 0.3.6.17.2 oot: omitted: Intel ixgbe [does not build] (using in-tree driver) oot: omitted: Highpoint r750 [does not work] oot: omitted: Highpoint rr3740a [does not build] Management: fix btrfs bug where converting from single to multiple pool did not balance metadata to raid1, and converting from multiple to single did not balance metadata back to single. auto-mount hugetlbfs to support kernel huge pages emhttpd: do not write /root/keyfile if encryption passphrase provided via webGUI fstab: mount USB flash boot device with root-only access nginx.conf: configure all nginx worker threads to run as 'root'. start/stop WireGuard upon server start/shutdown support forms-based authentication shfs: support FUSE3 API changes; hard links report same st_ino; hard link support configurable support disabling NetBIOS, and set Samba 'min server procotol' and 'min client protocol' to SMB2 if disabled support WS-Discovery method support mDNS local name resolution via avahi extract OS upgrade directly to USB flash webgui: Revamp Banner Warning System webgui: Fix custom case png not surviving reboot webgui: Enhanced display of network settings webgui: Open banner system to 3rd party apps webgui: Modified notify script to allow overriding email recipients in notification settings webgui: Allow Safari to use websockets webgui: Select case correction + replace MD1510 for AVS-10/4 webgui: Font, Icon and image cleanup webgui: Added AFP deprecated notice webgui: Changed config folder of TELEGRAM webgui: Add share access to user edit webgui: Added cache and disk type to shares page webgui: Aligned management page layout webgui: Added conditional UPnP setting on Management page webgui: Support wireguard plugin in download.php webgui: Added UPnP to access script (to support WireGuard plugin) webgui: Made notify script compatible with 6.8 new security scheme webgui: Fixed misalignment of absent disk on Main page webgui: Update ArrayDevices.page help text webgui: show warning on login page when browser cookies are disabled webgui: Fixed docker container update state webgui: Added VM XML files to diagnostics webgui: Telegram notification agent: enable group chat IDs, update helper description webgui: Integrate CAs Plugin Helper webgui: Switch download routine to be PHP Curl webgui: Change PluginHelpers download to be PHP Curl webgui: dockerMan - Deprecate TemplateURL webgui: Fixed: footer always on foreground webgui: Plugin Helpers: Follow redirects on downloads webgui: dockerMan: Redownload Icon if URL changes webgui: If a page is loaded via https, prevent it from loading resources via http (ie, block mixed content) webgui: Ensure spinner always ontop webgui: Allow outside click to close popups webgui: Use complete HTML documents in popups webgui: Standardize on lang="en" webgui: Added 'F1' key to toggle help text webgui: Main page: consolidate spin up/down action and device status into one webgui: support changed tunables on Disk Settings page
  4. 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 0.5.1.3 (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 4.2.4.4 (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
  5. 8 points
    -rc7 tldr: Updated kernel and Intel microcode which was released just after -rc6. Revert libvirt from 5.9.0 to 5.8.0 because 5.9.0 has bug where 'libvirt_list_domains()' returns an empty string when all domains are started instead of a list of domains. Fixed md/unraid crash resulting when bringing cleared array device online (bug introduced in multi-stream support). Don't let backslash be included in share names and vdisk paths. Misc. webGUI fixes. Other package updates. Specific changes in [-rcN] are indicated in bold below. New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device. You will probably notice a slight difference in speed of extract messages. [-rc2] The 'sync' command at the end has been replaced with 'sync -f /boot'. Forms based authentication If you have set a root password for your server, upon boot you'll now see a nice login form. There still is only one user for Unraid so for username enter root. This form should be compatible with all major password managers out there. We always recommend using a strong password. [-rc2] There is no auto-logout implemented yet, please click Logout on menu bar or completely close your browser to logout. Linux kernel 5.3 [-rc6/-rc7] include latest Intel microcode for yet another hardware vulnerability mitigation. default scheduler now 'mq-deadline' [-rc2] but this can be changed via Settings/Disk Settings/Scheduler setting. enabled Huge Page support, though no UI control yet binfmt_misc support added "Vega 10 Reset bug" [-rc2] and 'navi-reset' patches removed [-rc5] [-rc2] added oot: Realtek r8125: version 9.002.02 [-rc3] additional md/unraid changes and instrumentation [-rc6] fix chelsio missing firmware more device drivers Some out-of-tree (oot) drivers are currently omitted either because the source code doesn't compile or driver doesn't work with the 5.3 kernel: Intel ixgbe [does not build] (using in-tree driver) Highpoint r750 [does not work] Highpoint rr3740a [does not build] This is always the risk with including vendor-supplied drivers. Until the vendor fixes their code we must omit their driver. md/unraid driver Introduced "multi-stream" support: Reads on devices which are not being written should run at full speed. In addition, if you have set the md_write_method tunable to "reconstruct write", then while writing, if any read streams are detected, the write method is switched to "read/modifywrite". Parity sync/check should run at full speed by default. Parity sync/check is throttled back in presence of other active streams. The "stripe pool" resource is automatically shared evenly between all active streams. As a result got rid of some Tunables: md_sync_window md_sync_thresh and added some tunables: md_queue_limit md_sync_limit [-rc2] md_scheduler Please refer to Settings/Disk Settings help text for description of these settings. WireGuard support - available as a plugin via Community Apps. Our WireGuard implementation and UI is still a work-in-process; for this reason we have made this available as a plugin, though the latest WireGuard module is included in our Linux kernel. Full WireGuard implementation will be merged into Unraid OS itself in a future release. I want to give special thanks to @bonienl who wrote the plugin with lots of guidance from @ljm42 - thank you! I also should give a shout out to @NAS who got us rolling on this. If you don't know about WireGuard it's something to look into! Guide here: WS-Discovery support - Finally you can get rid of SMBv1 and get reliable Windows network discovery. This feature is configured on the Settings/SMB Settings page and enabled by default. Also on same settings page is Enable NetBIOS setting. This is enabled by default, however if you no longer have need for NetBIOS discovery you can turn it off. When turned off, Samba is configured to accept only SMBv2 protocol and higher. Added mDNS client support in Unraid OS. This means, for example, from an Unraid OS terminal session to ping another Unraid OS server on your network you can use (e.g., 'tower'): ping tower.local instead of ping tower Note the latter will still work if you have NetBIOS enabled. User Share File System (shfs) changes: Integrated FUSE-3 - This should increase performance of User Share File System. Fixed bug with hard link support. Previously a 'stat' on two directory entries referring to same file would return different i-node numbers, thus making it look like two independent files. This has been fixed however there is a config setting on Settings/Global Share Settings called "Tunable (support hard links)". [-rc2 ] Fixed the default value Yes, but with certain very old media and DVD players which access shares via NFS, you may need to set this to No. [-rc5] Fixed not accounting for devices not mounted yet. Note: if you have custom config/extra.cfg file, get rid of it. Other improvements/bug fixes: Format - during Format any running parity sync/check is automatically Paused and then resumed upon Format completion. Encryption - an entered passphrase is not saved to any file. Fixed bug where multi-device btrfs pool was leaving metadata set to dup instead of raid1. Several other small bug fixes and improvements. [-rc5] Fixed bug where quotes were not handled properly in passwords. Numerous base package updates [-rc2] including updating PHP to version 7.3.x, Samba to version 4.11.x. Known Issues and Other Errata Some users have reported slower parity sync/check rates for very wide arrays (20+ devices) vs. 6.7 and earlier releases - we are still studying this problem. [-rc6] this is fixed: If you are using Unassigned Devices plugin with encrypted volumes, you must use the file method of specifying the encryption passphrase. Note that a file containing your passphrase must consist of a single null-terminated string with no other line ending characters such as LF or CR/LF. In another step toward better security, the USB flash boot device is configured so that programs and scripts residing there cannot be directly executed (this is because the 'x' bit is set now only for directories). Commands placed in the 'go' file still execute because during startup, that file is copied to /tmp first and then executed from there. If you have created custom scripts you may need to take a similar approach. AFP is now deprecated and we plan to remove support in Unraid 6.9 release. The /mnt/user0 mount point is now deprecated and we plan to remove in Unraid 6.9 release. A note on password strings Password strings can contain any character however white space (space and tab characters) is handled specially: all leading and trailing white space is discarded multiple embedded white space is collapsed to a single space character. By contrast, encryption passphrase is used exactly as-is. Version 6.8.0-rc7 2019-11-22 Base distro: aaa_elflibs: version 15.0 dhcpcd: version 8.1.2 glib2: version 2.62.3 intel-microcode: version 20191115 kernel-firmware: version 20191118_e8a0f4c libidn2: version 2.3.0 libvirt: version 5.8.0 [reversion from 5.9.0] nghttp2: version 1.40.0 php: version 7.3.12 xfsprogs: version 5.3.0 xterm: version 351 Linux kernel: version 5.3.12 md/unraid: version 2.9.13 (fix crash bringing cleared device online) Management: webgui: Do not display error if docker log files manually deleted webgui: Warning alert for Format operations webgui: Docker and VM settings: validate path and name input webgui: Add shares: slashes are not allowed in share name
  6. 5 points
    Please open a new report for each issue/bug you find unique to this version. Bug fixes, improvements, and moving to linux 4.18 kernel. Release notes: Version 6.6.0-rc2 2018-09-06 Management: rc.nginx: added locations for robots.txt and js/css versioning this plugin: if legacy dynamix.plg file exists, delete it Linux kernel: version 4.18.6 removed OOT Intel ixgbe and ixgbevf, restored in-tree drivers: CONFIG_IXGBE: Intel(R) 10GbE PCI Express adapters support CONFIG_IXGBEVF: Intel(R) 10GbE PCI Express Virtual Function Ethernet support removed OOT groeck Linux Driver for ITE LPC chips, restored in-tree driver: CONFIG_SENSORS_IT87: ITE IT87xx and compatibles Management: webgui: vm manager: update unraid template logo webgui: Update virtio iso download links webgui: VM Manager: add 'virtio-win-0.1.160-1' to VirtIO-ISOs list webgui: IE: loads.txt is not being generated correctly on 6.6-rc1 webgui: Wrap all CSS/JS calls in autov() webgui: Set robots "noindex, nofollow" metatag on all pages, in case a user opens their system up to the internet. webgui: Added CPU isolation Both CPU pinning and CPU isolation is possible thru the GUI webgui: Make buttons a bit more narrow webgui: Fixed VM disk driver overwriting to default webgui: Fixed primary graphics card selection Note: this solution isn't complete. Removing a 2nd card doesn't work webgui: Fixed: VM settings Apply button not working in basic mode webgui: Fixed: no wrapping of help text in Docker settings webgui: Improved position of notifications webgui: Fixed: table height in fixed mode webgui: Fixed: VM creation error (parser error on attribute 'function') webgui: More specific removal of driver type to prevent 'qcow2' revert to 'raw' webgui: Robots protection webgui: Added SWAL message for CPU isolation webgui: Fixed: XML -- array conversion for "disk" elements webgui: CPU pinning: make notice to reboot permanent and inline with other pages webgui: VM settings: updated ACS Override and new Unsafe Interrupts option webgui: VM settings: align title capitalization webgui: VM settings: added help text webgui: CPU pinning: separate tabs for VM and Docker webgui: CPU pinning: individual notice message for VM and Docker webgui: Fixed: regression error in docker "check for updates" webgui: Docker containers: list adjustment to fit better smaller screens webgui: Docker containers: imrpoved table spacing webgui: CPU pinning: updated page structure webgui: VM edit: rebuild correctly graphic cards webgui: Prohibit CPU isolation in safe mode webgui: CPU pinning: updated help text for containers and isolated cores webgui: Docker: Suppress error if no volumes present in template
  7. 4 points
    -rc6 tldr: Updated kernel and Intel microcode for yet another hardware vulnerability. Update to latest qemu stable patch release: 4.1.1 Support UD passphrase-encrypted volumes. Misc. webGUI fixes. Other package updates. Specific changes in [-rcN] are indicated in bold below. New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device. You will probably notice a slight difference in speed of extract messages. [-rc2] The 'sync' command at the end has been replaced with 'sync -f /boot'. Forms based authentication If you have set a root password for your server, upon boot you'll now see a nice login form. There still is only one user for Unraid so for username enter root. This form should be compatible with all major password managers out there. We always recommend using a strong password. [-rc2] There is no auto-logout implemented yet, please click Logout on menu bar or completely close your browser to logout. Linux kernel 5.3 default scheduler now 'mq-deadline' [-rc2] but this can be changed via Settings/Disk Settings/Scheduler setting. enabled Huge Page support, though no UI control yet binfmt_misc support added "Vega 10 Reset bug" [-rc2] and 'navi-reset' patches removed [-rc5] [-rc2] added oot: Realtek r8125: version 9.002.02 [-rc3] additional md/unraid changes and instrumentation [-rc6] fix chelsio missing firmware more device drivers Some out-of-tree (oot) drivers are currently omitted either because the source code doesn't compile or driver doesn't work with the 5.3 kernel: Intel ixgbe [does not build] (using in-tree driver) Highpoint r750 [does not work] Highpoint rr3740a [does not build] This is always the risk with including vendor-supplied drivers. Until the vendor fixes their code we must omit their driver. md/unraid driver Introduced "multi-stream" support: Reads on devices which are not being written should run at full speed. In addition, if you have set the md_write_method tunable to "reconstruct write", then while writing, if any read streams are detected, the write method is switched to "read/modifywrite". Parity sync/check should run at full speed by default. Parity sync/check is throttled back in presence of other active streams. The "stripe pool" resource is automatically shared evenly between all active streams. As a result got rid of some Tunables: md_sync_window md_sync_thresh and added some tunables: md_queue_limit md_sync_limit [-rc2] md_scheduler Please refer to Settings/Disk Settings help text for description of these settings. WireGuard support - available as a plugin via Community Apps. Our WireGuard implementation and UI is still a work-in-process; for this reason we have made this available as a plugin, though the latest WireGuard module is included in our Linux kernel. Full WireGuard implementation will be merged into Unraid OS itself in a future release. I want to give special thanks to @bonienl who wrote the plugin with lots of guidance from @ljm42 - thank you! I also should give a shout out to @NAS who got us rolling on this. If you don't know about WireGuard it's something to look into! Guide here: WS-Discovery support - Finally you can get rid of SMBv1 and get reliable Windows network discovery. This feature is configured on the Settings/SMB Settings page and enabled by default. Also on same settings page is Enable NetBIOS setting. This is enabled by default, however if you no longer have need for NetBIOS discovery you can turn it off. When turned off, Samba is configured to accept only SMBv2 protocol and higher. Added mDNS client support in Unraid OS. This means, for example, from an Unraid OS terminal session to ping another Unraid OS server on your network you can use (e.g., 'tower'): ping tower.local instead of ping tower Note the latter will still work if you have NetBIOS enabled. User Share File System (shfs) changes: Integrated FUSE-3 - This should increase performance of User Share File System. Fixed bug with hard link support. Previously a 'stat' on two directory entries referring to same file would return different i-node numbers, thus making it look like two independent files. This has been fixed however there is a config setting on Settings/Global Share Settings called "Tunable (support hard links)". [-rc2 ] Fixed the default value Yes, but with certain very old media and DVD players which access shares via NFS, you may need to set this to No. [-rc5] Fixed not accounting for devices not mounted yet. Note: if you have custom config/extra.cfg file, get rid of it. Other improvements/bug fixes: Format - during Format any running parity sync/check is automatically Paused and then resumed upon Format completion. Encryption - an entered passphrase is not saved to any file. Fixed bug where multi-device btrfs pool was leaving metadata set to dup instead of raid1. Several other small bug fixes and improvements. [-rc5] Fixed bug where quotes were not handled properly in passwords. Numerous base package updates [-rc2] including updating PHP to version 7.3.x, Samba to version 4.11.x. Known Issues and Other Errata Some users have reported slower parity sync/check rates for very wide arrays (20+ devices) vs. 6.7 and earlier releases - we are still studying this problem. [-rc6] this is fixed: If you are using Unassigned Devices plugin with encrypted volumes, you must use the file method of specifying the encryption passphrase. Note that a file containing your passphrase must consist of a single null-terminated string with no other line ending characters such as LF or CR/LF. In another step toward better security, the USB flash boot device is configured so that programs and scripts residing there cannot be directly executed (this is because the 'x' bit is set now only for directories). Commands placed in the 'go' file still execute because during startup, that file is copied to /tmp first and then executed from there. If you have created custom scripts you may need to take a similar approach. AFP is now deprecated and we plan to remove support in Unraid 6.9 release. The /mnt/user0 mount point is now deprecated and we plan to remove in Unraid 6.9 release. A note on password strings Password strings can contain any character however white space (space and tab characters) is handled specially: all leading and trailing white space is discarded multiple embedded white space is collapsed to a single space character. By contrast, encryption passphrase is used exactly as-is. Version 6.8.0-rc6 2019-11-15 Base distro: aaa_elflibs: version 15.0 adwaita-icon-theme: version 3.34.3 cpio: version 2.13 cryptsetup: version 2.2.2 curl: version 7.67.0 docker: version 19.03.5 git: version 2.24.0 harfbuzz: version 2.6.4 hostname: version 3.23 intel-microcode: version 20191113 kernel-firmware: version 20191108_f1100d libvirt: version 5.9.0 libxml2: version 2.9.10 libxslt: version 1.1.34 lvm2: version 2.03.06 mkfontscale: version 1.2.1 mozilla-firefox: version 70.0.1 ncurses: version 6.1_20191026 qemu: version 4.1.1 (CVE-2019-14378, CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-12068, CVE-2019-11091) shared-mime-info: version 1.15 sudo: version 1.8.29 ttyd: version 20191025 xorg-server: version 1.20.5 xterm: version 350 zstd: version 1.4.4 Linux kernel: version 5.3.11 Management: add missing chelsio firmware emhttpd: properly handle encoded passwords emhttpd: correct footer notifications emhttpd: solve deadlock issue with 'emcmd' called from a plugin webgui: Submit passphrases and passwords in base64 format webgui: Fixed typo in shares settings webgui: Change dashbord link for mb/mem webgui: Fixed diagnostics errors when array was never started webgui: Docker: fixed multi container updates display oddity webgui: Rename docker repositories tab to template repositories webgui: Syslog: allow up to 5 digits port numbers
  8. 4 points
    This is continuation of this original issue report. There is some conflicting information in that topic and, therefore, with your help, we want to try and get to the bottom of this. We have several test servers running trying to reproduce this problem, so far hasn't happened. The first thing we want to definitively establish is whether the problem is isolated to only those cases where /config inside the container is mapped to: /mnt/user/appdata vs. /mnt/cache/appdata or /mnt/diskN/appdata Note: it does not matter what the "Default appdata storage location" is set to on Settings/Docker page. Of interest is the actual path used by an individual container. What I'd like to ask is this: For those of you who have seen this DB corruption occur after updating from Unraid 6.6.x to 6.7.x, please note the placement of your 'appdata' folder and how it's mapped to your problematic container. Then update to 6.7.2 and run normally until you see corruption. At that point, please capture diagnostics and report how appdata is being mapped. If this is a huge PITA for you, then bow out of this testing - we are not trying to cause big disruptions for you. Finally I want to make clear: we are not "blaming" this issue on any other component, h/w or s/w, and also not "admitting" this is our problem. We have not changed any code we're responsible for that would account for this, which doesn't mean we don't have a bug somewhere - probably we do, and a change in the kernel or some other component might simply be exposing some long hidden issue. We are only interested in identifying and fixing the problem.
  9. 4 points
    Hello, I have some cron jobs running during the night and morning every day. None of my cron job has run over the night, upgraded to 6.6.4 yesterday. No mover, no added backup script (using User Scripts), no daily trim and no Backup / Restore from CA. cat /etc/cron.d/root # Generated docker monitoring schedule: 10 */6 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 0 3 * * * /usr/local/sbin/mover |& logger # Generated plugins version check schedule: 10 */6 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated Unraid OS update check schedule: 11 */6 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null # Generated ssd trim schedule: 5 4 * * * /sbin/fstrim -a -v | logger &> /dev/null # Generated system data collection schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null root@Server:/etc# cd cron.daily/ root@Server:/etc/cron.daily# v total 12 -rwxrwxrwx 1 root root 76 Nov 8 00:08 fix.common.problems.sh* -rwxr-xr-x 1 root root 129 Apr 13 2018 logrotate* -rwxrwxrwx 1 root root 76 Nov 8 00:08 user.script.start.daily.sh* root@Server:/etc/cron.daily# cd .. root@Server:/etc# cd cron.hourly/ root@Server:/etc/cron.hourly# v total 4 -rwxrwxrwx 1 root root 77 Nov 8 00:08 user.script.start.hourly.sh* root@Server:/etc/cron.hourly# cd ../cron.weekly/ root@Server:/etc/cron.weekly# v total 4 -rwxrwxrwx 1 root root 77 Nov 8 00:08 user.script.start.weekly.sh* root@Server:/etc/cron.weekly# cd ../cron.monthly/ root@Server:/etc/cron.monthly# v total 4 -rwxrwxrwx 1 root root 78 Nov 8 00:08 user.script.start.monthly.sh* root@Server:/etc/cron.monthly# Just added my own backup script using "User Scripts" lately. No more, no less. Stuff supposed to be running here, nothing, except for fix common problems but that might be because of reboot after upgrade to .4. My added script: Contents: #!/bin/bash cd /mnt/user/AppdataBackup /usr/local/bin/duplicacy prune -keep 0:5 /usr/local/bin/duplicacy prune /usr/local/bin/duplicacy backup -stats -hash
  10. 4 points
    Can I please ask everyone when you mark an issue as "urgent" to obey these conditions: 1) The problem is reproduceable 2) Diagnostics and other relevant information are attached in the post We (the receiving side) get alarm bells ringing and act asap, but need info as much as possible to find and resolve the issue. Thank you.
  11. 3 points
    Oct 12 03:35:17 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1357, hdr_len 1411 Oct 12 03:35:17 Storage kernel: tun: 13 e4 3d f7 10 86 b8 9e 87 b1 5f 81 d9 7a 98 c9 ..=......._..z.. Oct 12 03:35:17 Storage kernel: tun: 26 fa 2d 78 50 03 f2 b2 22 55 bc 68 29 75 83 46 &.-xP..."U.h)u.F Oct 12 03:35:17 Storage kernel: tun: 04 35 d4 e4 71 d8 5c 04 e3 e2 a2 6d 4e 1f 22 9d .5..q.\....mN.". Oct 12 03:35:17 Storage kernel: tun: 6f 97 72 60 c9 63 2b dc f4 ec c7 4f 68 60 66 9e o.r`.c+....Oh`f. Getting the above message repeated over and over again in the log whenever a docker tries to access the NIC. storage-diagnostics-20191012-0237.zip
  12. 3 points
    Likely related to this bug but this one is more serious, any new multi device pools created on v6.7+ will be created with raid1 profile for data but single (or DUP if HDDs are used) profile for metadata, so if one of the devices fails pool will be toast.
  13. 2 points
    Hey Guys, First of all, I know that you're all very busy on getting version 6.8 out there, something I'm very much waiting on as well. I'm seeing great progress, so thanks so much for that! Furthermore I won't be expecting this to be on top of the priority list, but I'm hoping someone of the developers team is willing to invest (perhaps after the release). Hardware and software involved: 2 x 1TB Samsung EVO 860, setup with LUKS encryption in BTRFS RAID1 pool. ### TLDR (but I'd suggest to read on anyway 😀) The image file mounted as a loop device is causing massive writes on the cache, potentially wearing out SSD's quite rapidly. This appears to be only happening on encrypted caches formatted with BTRFS (maybe only in RAID1 setup, but not sure). Hosting the Docker files directory on /mnt/cache instead of using the loopdevice seems to fix this problem. Possible idea for implementation proposed on the bottom. Grateful for any help provided! ### I have written a topic in the general support section (see link below), but I have done a lot of research lately and think I have gathered enough evidence pointing to a bug, I also was able to build (kind of) a workaround for my situation. More details below. So to see what was actually hammering on the cache I started doing all the obvious, like using a lot of find commands to trace files that were written to every few minutes and also used the fileactivity plugin. Neither was able trace down any writes that would explain 400 GBs worth of writes a day for just a few containers that aren't even that active. Digging further I moved the docker.img to /mnt/cach/system/docker/docker.img, so directly on the BTRFS RAID1 mountpoint. I wanted to check whether the unRAID FS layer was causing the loop2 device to write this heavy. No luck either. This gave me a situation I was able to reproduce on a virtual machine though, so I started with a recent Debian install (I know, it's not Slackware, but I had to start somewhere ☺️). I create some vDisks, encrypted them with LUKS, bundled them in a BTRFS RAID1 setup, created the loopdevice on the BTRFS mountpoint (same of /dev/cache) en mounted it on /var/lib/docker. I made sure I had to NoCow flags set on the IMG file like unRAID does. Strangely this did not show any excessive writes, iotop shows really healthy values for the same workload (I migrated the docker content over to the VM). After my Debian troubleshooting I went back over to the unRAID server, wondering whether the loopdevice is created weirdly, so I took the exact same steps to create a new image and pointed the settings from the GUI there. Still same write issues. Finally I decided to put the whole image out of the equation and took the following steps: - Stopped docker from the WebGUI so unRAID would properly unmount the loop device. - Modified /etc/rc.d/rc.docker to not check whether /var/lib/docker was a mountpoint - Created a share on the cache for the docker files - Created a softlink from /mnt/cache/docker to /var/lib/docker - Started docker using "/etc/rd.d/rc.docker start" - Started my BItwarden containers. Looking into the stats with "iotstat -ao" I did not see any excessive writing taking place anymore. I had the containers running for like 3 hours and maybe got 1GB of writes total (note that on the loopdevice this gave me 2.5GB every 10 minutes!) Now don't get me wrong, I understand why the loopdevice was implemented. Dockerd is started with options to make it run with the BTRFS driver, and since the image file is formatted with the BTRFS filesystem this works at every setup, it doesn't even matter whether it runs on XFS, EXT4 or BTRFS and it will just work. I my case I had to point the softlink to /mnt/cache because pointing it /mnt/user would not allow me to start using the BTRFS driver (obviously the unRAID filesystem isn't BTRFS). Also the WebGUI has commands to scrub to filesystem inside the container, all is based on the assumption everyone is using docker on BTRFS (which of course they are because of the container 😁) I must say that my approach also broke when I changed something in the shares, certain services get a restart causing docker to be turned off for some reason. No big issue since it wasn't meant to be a long term solution, just to see whether the loopdevice was causing the issue, which I think my tests did point out. Now I'm at the point where I would definitely need some developer help, I'm currently keeping nearly all docker container off all day because 300/400GB worth of writes a day is just a BIG waste of expensive flash storage. Especially since I've pointed out that it's not needed at all. It does defeat the purpose of my NAS and SSD cache though since it's main purpose was hosting docker containers while allowing the HD's to spin down. Again, I'm hoping someone in the dev team acknowledges this problem and is willing to invest. I did got quite a few hits on the forums and reddit without someone actually pointed out the root cause of issue. I missing the technical know-how to troubleshoot the loopdevice issues on a lower level, but have been thinking on possible ways to implement a workaround. Like adjusting the Docker Settings page to switch off the use of a vDisk and if all requirements are met (pointing to /mnt/cache and BTRFS formatted) start docker on a share on the /mnt/cache partition instead of using the vDisk. In this way you would still keep all advantages of the docker.img file (cross filesystem type) and users who don't care about writes could still use it, but you'd be massively helping out others that are concerned over these writes. I'm not attaching diagnostic files since they would probably not point out the needed. Also if this should have been in feature requests, I'm sorry. But I feel that, since the solution is misbehaving in terms of writes, this could also be placed in the bugreport section. Thanks though for this great product, have been using it so far with a lot of joy! I'm just hoping we can solve this one so I can keep all my dockers running without the cache wearing out quick, Cheers!
  14. 2 points
    Hi, I've posted this already, but into an incorrect forum where it remained unnoticed. So sorry for the x-post. Symptoms: Plex HW transcoding does not work with Docker on unRAID 6.7.x (0 through 2), although it is working fine when downgrading to 6.6.7 without any change in unRAID or Docker container configuration. go file: #!/bin/bash #Setup drivers for hardware transcoding in Plex modprobe i915 chmod -R 777 /dev/dri #Start the Management Utility /usr/local/sbin/emhttp & syslinux.cfg untouched as i915 support is included OOB for some time now, however during my troubleshooting attempts, I've tried to force i915 support by modifying the aforementioned config file like this (with no effect of course): label Unraid OS menu default kernel /bzimage append pci=realloc=off initrd=/bzroot i915.alpha_support=1 /dev/dri is being passed to the Plex docker container as a device and is visible to the container: root@532cd6092721:/# ls -la /dev/dri total 0 drwxr-xr-x 2 root root 80 Jun 19 11:05 . drwxr-xr-x 6 root root 360 Jun 19 11:05 .. crw-rw---- 1 root video 226, 0 Jun 19 11:05 card0 crwxrwxrwx 1 99 users 226, 128 Jun 19 11:05 renderD128 Plex transcoder does appear to see the iGPU device, Plex dashboard shows that a HW transcode session is ongoing, however video keeps buffering and playback is never initiated. I've checked Plex log quite extensively and they do IMO confirm what I've stated above - the transcoder sees the iGPU, transcode session starts, but there is no video being output. Jun 19, 2019 15:38:32.248 [0x15102bbfd700] DEBUG - TPU: hardware transcoding: using hardware decode accelerator vaapi Jun 19, 2019 15:38:32.248 [0x15102bbfd700] DEBUG - [Universal] Using local file path instead of URL: /movies/Captain Marvel (2019)/Captain Marvel (2019) - Bluray-1080p.mkv Jun 19, 2019 15:38:32.249 [0x15102bbfd700] DEBUG - HTTP requesting GET http://127.0.0.1:32400/library/streams/181?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx Jun 19, 2019 15:38:32.249 [0x151093dfe700] DEBUG - Auth: authenticated user 1 as obfuscated Jun 19, 2019 15:38:32.249 [0x15102b1f8700] DEBUG - Request: [127.0.0.1:34844 (Loopback)] GET /library/streams/181 (14 live) GZIP Signed-in Token (obfuscated) Jun 19, 2019 15:38:32.252 [0x15102b1f8700] DEBUG - Content-Length of /movies/Captain Marvel (2019)/Captain Marvel (2019) - Bluray-1080p.en.srt is 91753. Jun 19, 2019 15:38:32.253 [0x151093dfe700] DEBUG - Completed: [127.0.0.1:34844] 200 GET /library/streams/181 (14 live) GZIP 3ms 91753 bytes Jun 19, 2019 15:38:32.253 [0x15102bbfd700] DEBUG - HTTP 200 response from GET http://127.0.0.1:32400/library/streams/181?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx Jun 19, 2019 15:38:32.253 [0x15102bbfd700] DEBUG - Detected character set of UTF-8. Jun 19, 2019 15:38:32.254 [0x15102bbfd700] DEBUG - Downloaded stream from [http://127.0.0.1:32400/library/streams/181?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx] (codec: srt) to temporary file [/transcode/Transcode/Sessions/plex-transcode-jk19rtdgc5dtot7fu88d8gsy-ef1b128f-4370-4808-a01d-07825b462435/temp-0.srt] Jun 19, 2019 15:38:32.254 [0x15102bbfd700] DEBUG - TPU: hardware transcoding: zero-copy support present Jun 19, 2019 15:38:32.254 [0x15102bbfd700] DEBUG - TPU: hardware transcoding: using zero-copy transcoding Jun 19, 2019 15:38:32.254 [0x15102bbfd700] DEBUG - TPU: hardware transcoding: final decoder: vaapi, final encoder: vaapi Jun 19, 2019 15:38:32.255 [0x15102bbfd700] DEBUG - Job running: EAE_ROOT='/tmp/pms-85736070-8352-49fb-956e-d7be9ba4a099/EasyAudioEncoder' FFMPEG_EXTERNAL_LIBS='/config/Library/Application\ Support/Plex\ Media\ Server/Codecs/21b5515-2321-linux-x86_64/' XDG_CACHE_HOME='/config/Library/Application Support/Plex Media Server/Cache' XDG_DATA_HOME='/usr/lib/plexmediaserver/Resources' X_PLEX_TOKEN='xxxxxxxxxxxxxxxxxxxx' '/usr/lib/plexmediaserver/Plex Transcoder' '-codec:0' 'h264' '-hwaccel:0' 'vaapi' '-hwaccel_fallback_threshold:0' '10' '-hwaccel_output_format:0' 'vaapi' '-codec:1' 'dca' '-analyzeduration' '20000000' '-probesize' '20000000' '-i' '/movies/Captain Marvel (2019)/Captain Marvel (2019) - Bluray-1080p.mkv' '-analyzeduration' '20000000' '-probesize' '20000000' '-i' '/transcode/Transcode/Sessions/plex-transcode-jk19rtdgc5dtot7fu88d8gsy-ef1b128f-4370-4808-a01d-07825b462435/temp-0.srt' '-filter_complex' '[0:0]hwupload[0];[0]scale_vaapi=w=1278:h=538:format=nv12[1];[1]hwupload[2]' '-filter_complex' '[0:1] aresample=async=1:ocl='\''stereo'\'':osr=48000[3]' '-map' '[2]' '-metadata:s:0' 'language=eng' '-codec:0' 'h264_vaapi' '-b:0' '2717k' '-maxrate:0' '3623k' '-bufsize:0' '7246k' '-r:0' '23.975999999999999' '-force_key_frames:0' 'expr:gte(t,0+n_forced*5)' '-map' '[3]' '-metadata:s:1' 'language=eng' '-codec:1' 'aac' '-b:1' '148k' '-f' 'dash' '-min_seg_duration' '5000000' '-skip_to_segment' '1' '-time_delta' '0.0625' '-manifest_name' 'http://127.0.0.1:32400/video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/manifest' '-avoid_negative_ts' 'disabled' '-map_metadata' '-1' '-map_chapters' '-1' 'dash' '-map' '1:s:0' '-metadata:s:0' 'language=eng' '-codec:0' 'ass' '-f' 'segment' '-segment_format' 'ass' '-segment_time' '1' '-segment_header_filename' 'sub-header' '-segment_start_number' '0' '-segment_list' 'http://127.0.0.1:32400/video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/seglist?stream=subtitles' '-segment_list_type' 'csv' '-segment_list_size' '2147483647' '-segment_list_separate_stream_times' '1' '-segment_format_options' 'ignore_readorder=1' 'sub-chunk-%05d' '-start_at_zero' '-copyts' '-vsync' 'cfr' '-y' '-vaapi_device' '/dev/dri/renderD128' '-nostats' '-loglevel' 'quiet' '-loglevel_plex' 'error' '-progressurl' 'http://127.0.0.1:32400/video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress' Jun 19, 2019 15:38:32.256 [0x15102bbfd700] DEBUG - Jobs: Starting child process with pid 586 Jun 19, 2019 15:38:32.281 [0x15102adf6700] DEBUG - Request: [127.0.0.1:34846 (Loopback)] PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress?status=startup (15 live) Signed-in Token (obfuscated) Jun 19, 2019 15:38:32.282 [0x151093dfe700] DEBUG - Completed: [127.0.0.1:34846] 204 PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress?status=startup (15 live) 0ms 203 bytes (pipelined: 1) (range: bytes=0-) Jun 19, 2019 15:38:32.282 [0x1510916b8700] DEBUG - Request: [127.0.0.1:34846 (Loopback)] PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress?status=opening (15 live) Signed-in Token (obfuscated) Jun 19, 2019 15:38:32.282 [0x151093dfe700] DEBUG - Completed: [127.0.0.1:34846] 204 PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress?status=opening (15 live) 0ms 203 bytes (pipelined: 2) (range: bytes=0-) Jun 19, 2019 15:38:32.284 [0x15102aff7700] DEBUG - Request: [127.0.0.1:34846 (Loopback)] PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress?status=opened (15 live) Signed-in Token (obfuscated) Jun 19, 2019 15:38:32.284 [0x151093fff700] DEBUG - Completed: [127.0.0.1:34846] 204 PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress?status=opened (15 live) 0ms 203 bytes (pipelined: 3) (range: bytes=0-) Jun 19, 2019 15:38:32.284 [0x15102b9fc700] DEBUG - Request: [127.0.0.1:34846 (Loopback)] PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress/stream?index=0&id=0&codec=h264&type=video (14 live) Signed-in Token (obfuscated) Jun 19, 2019 15:38:32.285 [0x151093fff700] DEBUG - Completed: [127.0.0.1:34846] 206 PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress/stream?index=0&id=0&codec=h264&type=video (14 live) 0ms 256 bytes (pipelined: 4) (range: bytes=0-) Jun 19, 2019 15:38:32.285 [0x15102adf6700] DEBUG - Request: [127.0.0.1:34846 (Loopback)] PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress/stream?index=1&id=0&codec=dts&type=audio (14 live) Signed-in Token (obfuscated) Jun 19, 2019 15:38:32.285 [0x151093fff700] DEBUG - Completed: [127.0.0.1:34846] 206 PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress/stream?index=1&id=0&codec=dts&type=audio (14 live) 0ms 256 bytes (pipelined: 5) (range: bytes=0-) Jun 19, 2019 15:38:32.340 [0x1510916b8700] DEBUG - Request: [127.0.0.1:34846 (Loopback)] PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress/streamDetail?index=0&id=0&codec=h264&type=video&profile=High&language=eng&width=1920&height=808&interlaced=0&level=41&frameRate=23.9 Affected systems: As evidenced by other users, it appears only 7th gen Intel processors including UHD600 iGPU are affected, namely Celeron J4105 (Gemini Lake) Thanks in advance for looking into this.
  15. 2 points
    So, after getting into RC2, I was trying to optimize my pinning using the new interface. I looked up my NUMA boundaries in the process: numactl --hardware available: 2 nodes (0-1) node 0 cpus: 0 1 2 3 4 5 6 7 16 17 18 19 20 21 22 23 node 0 size: 32040 MB node 0 free: 256 MB # <<< Make note of this value node 1 cpus: 8 9 10 11 12 13 14 15 24 25 26 27 28 29 30 31 node 1 size: 32243 MB node 1 free: 19974 MB node distances: node 0 1 0: 10 16 1: 16 10 I'm currently running two VMs as of this command. VM 1: 16gb RAM, CPUs 4-7, 20-23 (So, numa node 0, in CPU pairs) VM 2: 16gb RAM, CPUs 8-11, 24-27 (Numa node 1) But as you'll note, all the RAM is being allocated to node 0. Uh oh. Let's check: numastat qemu Per-node process memory usage (in MBs) PID Node 0 Node 1 Total ----------------------- --------------- --------------- --------------- 13479 (qemu-system-x86) 16473.43 0.25 16473.68 27148 (qemu-system-x86) 13259.18 3204.48 16463.66 ----------------------- --------------- --------------- --------------- Total 29732.60 3204.74 32937.34 Well, crap. That's no good. I then tried to force it using the <numatune> tags. This works fine for VM 1, which is completely in it's own node, but for VM 2, this makes it take forever to start up, because it tries to force the second qemu instance onto node 1 (where it should be) and you get a bunch of numa misses when the memory is allocated to node 0 anyway. This can also cause some NVRAM corruption in combination with other numa-optimizations and xml configuration settings, though I'm not able to remember exactly which one borked up the VM so bad I had to restore the .img file, nvram and xml to get nvidia drivers working again. I imagine this will be extra important for 2990 users as two of the cores have significantly better memory access than the others and you'd want to keep VMs nicely in line with these boundaries for optimum performance. Obviously we don't want this boundary crossing to happen with other processors (like my 1950) for performance reasons as well. Bonus bug: WebTerminal is really slow this release once you have some text in the window compared to last release. Bonus question: Any chance of getting 'numad' baked in so we can use "auto" in numatune?
  16. 2 points
    Changes in [-rc2] are indicated in bold below. New in Unraid OS 6.8 release: The unRAIDServer.plg file (update OS) still downloads the new release zip file to RAM but then extracts directly to USB flash boot device. You will probably notice a slight difference in speed of extract messages. [-rc2] The 'sync' command at the end has been replaced with 'sync -f /boot'. Forms based authentication If you have set a root password for your server, upon boot you'll now see a nice login form. There still is only one user for Unraid so for username enter root. This form should be compatible with all major password managers out there. We always recommend using a strong password. [-rc2] There is no auto-logout implemented yet, please click Logout on menu bar or completely close your browser to logout. Linux kernel 5.3 default scheduler now 'mq-deadline' [-rc2] but this can be changed via Settings/Disk Settings/Scheduler setting. enabled Huge Page support, though no UI control yet binfmt_misc support added "Vega 10 Reset bug" [-rc2] and 'navi-reset' patches [-rc2] added oot: Realtek r8125: version 9.002.02 more device drivers Some out-of-tree (oot) drivers are currently omitted either because the source code doesn't compile or driver doesn't work with the 5.3 kernel: Intel ixgbe [does not build] (using in-tree driver) Highpoint r750 [does not work] Highpoint rr3740a [does not build] This is always the risk with including vendor-supplied drivers. Until the vendor fixes their code we must omit their driver. md/unraid driver Introduced "multi-stream" support: Reads on devices which are not being written should run at full speed. In addition, if you have set the md_write_method tunable to "reconstruct write", then while writing, if any read streams are detected, the write method is switched to "read/modifywrite". Parity sync/check should run at full speed by default. Parity sync/check can be throttled back in presence of other active streams. The "stripe pool" resource is automatically shared evenly between all active streams. As a result got rid of some Tunables: md_sync_window md_sync_thresh and added some tunables: md_queue_limit md_sync_limit [-rc2] md_scheduler Please refer to Settings/Disk Settings help text for description of these settings. Remaining issue: some users have reported slower parity sync/check rates for very wide arrays (20+ devices) vs. 6.7 and earlier releases - we are still studying this problem. WireGuard support - available as a plugin via Community Apps. Our WireGuard implementation and UI is still a work-in-process; for this reason we have made this available as a plugin, though the latest WireGuard module is included in our Linux kernel. Full WireGuard implementation will be merged into Unraid OS itself in a future release. I want to give special thanks to @bonienl who wrote the plugin with lots of guidance from @ljm42 - thank you! I also should give a shout out to @NAS who got us rolling on this. If you don't know about WireGuard it's something to look into! Guide here: WS-Discovery support - Finally you can get rid of SMBv1 and get reliable Windows network discovery. This feature is configured on the Settings/SMB Settings page and enabled by default. Also on same settings page is Enable NetBIOS setting. This is enabled by default, however if you no longer have need for NetBIOS discovery you can turn it off. When turned off, Samba is configured to accept only SMBv2 protocol and higher. Added mDNS client support in Unraid OS. This means, for example, from an Unraid OS terminal session to ping another Unraid OS server on your network you can use (e.g., 'tower'): ping tower.local instead of ping tower Note the latter will still work if you have NetBIOS enabled. User Share File System (shfs) changes: Integrated FUSE-3 - This should increase performance of User Share File System somewhat. Fixed bug with hard link support. Previously a 'stat' on two directory entries referring to same file would return different i-node numbers, thus making it look like two independent files. This has been fixed however there is a config setting on Settings/Global Share Settings called "Tunable (support hard links)". [-rc2 ] Fixed the default value Yes, but with certain very old media and DVD players which access shares via NFS, you may need to set this to No. Note: if you have custom config/extra.cfg file, get rid of it. Other improvements/bug fixes: Format - during Format any running parity sync/check is automatically Paused and then resumed upon Format completion. Encryption - an entered passphrase is not saved to any file. Also included an API for Unassigned devices plugin to open encrypted volumes. Fixed bug where multi-device btrfs pool was leaving metadata set to dup instead of raid1. Several other small bug fixes and improvements. Numerous base package updates [-rc2] including updating PHP to version 7.3.x and Samba to version 4.11.x. Finally - please note that AFP is now deprecated and we plan to remove in Unraid 6.9 release. Version 6.8.0-rc2 2019-10-17 Base distro: aaa_elflibs: version 15.0 build 15 at-spi2-atk: version 2.34.1 binutils: version 2.33.1 gdk-pixbuf2: version 2.40.0 glib2: version 2.62.1 harfbuzz: version 2.6.2 icu4c: version 65.1 kernel-firmware: version 20191008_aa95e90 libX11: version 1.6.9 librsvg: version 2.46.1 libvirt-php: version 20190803 openssh: version 8.1p1 php: version 7.3.10 pkgtools: version 15.0 build 25 samba: version 4.11.0 (CVE-2019-10197) sqlite: version 3.30.1 ttyd: version 20191001 wireguard: version 0.0.20191012 xfsprogs: version 5.2.1 Linux kernel: change schedulers from modules to built-ins patch: navi_reset (user request) oot: Realtek r8125: version 9.002.02 Management: add 'scheduler' tunable for array devices fix shfs hard link initially reported as enabled but not actually enabled nginx: disable php session expiration unRAIDServer.plg (update OS) now executes 'sync -f /boot' instead of full sync at end of update webgui: Improve Use Cache option webgui: other minor text corrections webgui: Dashboard: add up/down arrows to VPN tunnel traffic Version 6.8.0-rc1 2019-10-11 Base distro: aaa_elflibs: version 15.0 build 11 acpid: version 2.0.32 at-spi2-atk: version 2.34.0 at-spi2-core: version 2.34.0 atk: version 2.34.1 bash: version 5.0.011 btrfs-progs: version 5.2.2 bzip2: version 1.0.8 ca-certificates: version 20190826 cifs-utils: version 6.9 cryptsetup: version 2.2.1 curl: version 7.66.0 dbus: version 1.12.16 dbus-glib: version 0.110 dhcpcd: version 8.0.6 docker: version 19.03.3 e2fsprogs: version 1.45.4 encodings: version 1.0.5 etc: version 15.0 ethtool: version 5.3 expat: version 2.2.9 file: version 5.37 findutils: version 4.7.0 freetype: version 2.10.1 fuse3: version 3.6.2 gdbm: version 1.18.1 gdk-pixbuf2: version 2.38.2 git: version 2.23.0 glib2: version 2.62.0 glibc-solibs: version 2.30 glibc-zoneinfo: version 2019c glibc: version 2.30 glu: version 9.0.1 gnutls: version 3.6.10 gtk+3: version 3.24.10 harfbuzz: version 2.6.0 haveged: version 1.9.8 hostname: version 3.22 hwloc: version 1.11.13 icu4c: version 64.2 intel-microcode: version 20190918 iproute2: version 5.3.0 iptables: version 1.8.3 iputils: version 20190709 irqbalance: version 1.6.0 less: version 551 libICE: version 1.0.10 libX11: version 1.6.8 libXi: version 1.7.10 libXt: version 1.2.0 libarchive: version 3.4.0 libcap-ng: version 0.7.10 libcroco: version 0.6.13 libdrm: version 2.4.99 libedit: version 20190324_3.1 libevdev: version 1.7.0 libevent: version 2.1.11 libgcrypt: version 1.8.5 libgudev: version 233 libjpeg-turbo: version 2.0.3 libnftnl: version 1.1.4 libnl3: version 3.5.0 libpcap: version 1.9.1 libpciaccess: version 0.16 libpng: version 1.6.37 libpsl: version 0.21.0 librsvg: version 2.44.14 libseccomp: version 2.4.1 libssh2: version 1.9.0 libtasn1: version 4.14 libusb: version 1.0.23 libvirt-php: version 0.5.5 libvirt: version 5.7.0 (CVE-2019-10161, CVE-2019-10166, CVE-2019-10167, CVE-2019-10168) libwebp: version 1.0.3 libzip: version 1.5.2 logrotate: version 3.15.1 lsof: version 4.93.2 lsscsi: version 0.30 lvm2: version 2.03.05 lz4: version 1.9.1 mkfontscale: version 1.2.1 mozilla-firefox: version 68.0.2 (CVE-2019-11751, CVE-2019-11746, CVE-2019-11744, CVE-2019-11742, CVE-2019-11736, CVE-2019-11753, CVE-2019-11752, CVE-2019-9812, CVE-2019-11741, CVE-2019-11743, CVE-2019-11748, CVE-2019-11749, CVE-2019-5849, CVE-2019-11750, CVE-2019-11737, CVE-2019-11738, CVE-2019-11747, CVE-2019-11734, CVE-2019-11735, CVE-2019-11740, CVE-2019-11754, CVE-2019-9811, CVE-2019-11711, CVE-2019-11712, CVE-2019-11713, CVE-2019-11714, CVE-2019-11729, CVE-2019-11715, CVE-2019-11716, CVE-2019-11717, CVE-2019-1 1718, CVE-2019-11719, CVE-2019-11720, CVE-2019-11721, CVE-2019-11730, CVE-2019-11723, CVE-2019-11724, CVE-2019-11725, CVE-2019-11727, CVE-2019-11728, CVE-2019-11710, CVE-2019-11709) nano: version 4.5 ncurses: version 6.1_20190720 net-tools: version 20181103_0eebece nettle: version 3.5.1 nghttp2: version 1.39.2 nginx: version 1.16.1 (CVE-2019-9511, CVE-2019-9513, CVE-2019-9516) nodejs: version 10.16.3 nss-mdns: version 0.14.1 ntp: version 4.2.8p13 openldap-client: version 2.4.48 openssh: version 8.0p1 openssl-solibs: version 1.1.1d openssl: version 1.1.1d p11-kit: version 0.23.18.1 pcre2: version 10.33 php: version 7.2.23 (CVE-2019-11042, CVE-2019-11041) pixman: version 0.38.4 pkgtools: version 15.0 procps-ng: version 3.3.15 qemu: version 4.1.0 (CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091) qrencode: version 4.0.2 rpcbind: version 1.2.5 rsyslog: version 8.1908.0 samba: version 4.10.8 (CVE-2019-10197) sdparm: version 1.10 sessreg: version 1.1.2 setxkbmap: version 1.3.2 sg3_utils: version 1.44 shadow: version 4.7 shared-mime-info: version 1.12 sqlite: version 3.29.0 sysvinit-scripts: version 2.1 sysvinit: version 2.96 talloc: version 2.3.0 tdb: version 1.4.2 tevent: version 0.10.1 ttyd: version 1.5.2 usbutils: version 012 util-linux: version 2.34 wget: version 1.20.3 wireguard: version 0.0.20190913 wsdd: version 20180618 build 2 xauth: version 1.1 xclock: version 1.0.9 xfsprogs: version 5.2.1 xkeyboard-config: version 2.27 xorg-server: version 1.20.5 xrandr: version 1.5.1 xterm: version 348 xwininfo: version 1.1.5 zstd: version 1.4.3 Linux kernel: version 5.3.6 default scheduler now mq-deadline CONFIG_BINFMT_MISC: Kernel support for MISC binaries CONFIG_DEBUG_FS: Debug Filesystem CONFIG_HUGETLBFS: HugeTLB file system support CONFIG_ICE: Intel(R) Ethernet Connection E800 Series Support CONFIG_IGC: Intel(R) Ethernet Controller I225-LM/I225-V support CONFIG_MLX5_CORE_IPOIB: Mellanox 5th generation network adapters (connectX series) IPoIB offloads support CONFIG_SCSI_SMARTPQI: Microsemi PQI Driver CONFIG_WIREGUARD: IP: WireGuard secure network tunnel patch: fix_vega_reset (user request) patch: increase BLK_MAX_REQUEST_COUNT from 16 to 32 oot: LimeTech md/unraid: version 2.9.10 (multi-stream support) oot: Highpoint rsnvme: version v1.2.16_19_05_06 oot: Tehuti tn40xx: version 0.3.6.17.2 oot: omitted: Intel ixgbe [does not build] (using in-tree driver) oot: omitted: Highpoint r750 [does not work] oot: omitted: Highpoint rr3740a [does not build] Management: fix btrfs bug where converting from single to multiple pool did not balance metadata to raid1, and converting from multiple to single did not balance metadata back to single. auto-mount hugetlbfs to support kernel huge pages emhttpd: do not write /root/keyfile if encryption passphrase provided via webGUI fstab: mount USB flash boot device with root-only access nginx.conf: configure all nginx worker threads to run as 'root'. start/stop WireGuard upon server start/shutdown support forms-based authentication shfs: support FUSE3 API changes; hard links report same st_ino; hard link support configurable support disabling NetBIOS, and set Samba 'min server procotol' and 'min client protocol' to SMB2 if disabled support WS-Discovery method support mDNS local name resolution via avahi extract OS upgrade directly to USB flash webgui: Revamp Banner Warning System webgui: Fix custom case png not surviving reboot webgui: Enhanced display of network settings webgui: Open banner system to 3rd party apps webgui: Modified notify script to allow overriding email recipients in notification settings webgui: Allow Safari to use websockets webgui: Select case correction + replace MD1510 for AVS-10/4 webgui: Font, Icon and image cleanup webgui: Added AFP deprecated notice webgui: Changed config folder of TELEGRAM webgui: Add share access to user edit webgui: Added cache and disk type to shares page webgui: Aligned management page layout webgui: Added conditional UPnP setting on Management page webgui: Support wireguard plugin in download.php webgui: Added UPnP to access script (to support WireGuard plugin) webgui: Made notify script compatible with 6.8 new security scheme webgui: Fixed misalignment of absent disk on Main page webgui: Update ArrayDevices.page help text webgui: show warning on login page when browser cookies are disabled webgui: Fixed docker container update state webgui: Added VM XML files to diagnostics webgui: Telegram notification agent: enable group chat IDs, update helper description webgui: Integrate CAs Plugin Helper webgui: Switch download routine to be PHP Curl webgui: Change PluginHelpers download to be PHP Curl webgui: dockerMan - Deprecate TemplateURL webgui: Fixed: footer always on foreground webgui: Plugin Helpers: Follow redirects on downloads webgui: dockerMan: Redownload Icon if URL changes webgui: If a page is loaded via https, prevent it from loading resources via http (ie, block mixed content) webgui: Ensure spinner always ontop webgui: Allow outside click to close popups webgui: Use complete HTML documents in popups webgui: Standardize on lang="en" webgui: Added 'F1' key to toggle help text webgui: Main page: consolidate spin up/down action and device status into one webgui: support changed tunables on Disk Settings page
  17. 2 points
    For those who keep local syslogs and want them to be included in the 'regular' log rotation scheme, you can create a settings file, e.g. rsyslog_local with content similar to the below. Copy this file to the folder /etc/logrotate.d /mnt/user/syslog/*.log { su nobody users missingok create 0666 nobody users size 1M rotate 2 sharedscripts postrotate /bin/kill -HUP `cat /var/run/rsyslogd.pid 2>/dev/null` 2>/dev/null || true endscript } /mnt/user/syslog/*.log refers to the location where the log files are stored.
  18. 2 points
    I wrote a very basic test program to verify this: #include <stdint.h> #include <unistd.h> #include <fcntl.h> int main() { uint32_t val = 0; int fd0 = open("test1", O_RDWR | O_CREAT); write(fd0, &val, sizeof(val)); close(fd0); while (val < 100000) { uint32_t val2 = 0; int fd1 = open("test1", O_RDWR | O_CREAT); int fd2 = open("test2", O_RDWR | O_CREAT); read(fd1, &val2, sizeof(val2)); close(fd1); val++; val2++; fd1 = open("test1", O_RDWR | O_CREAT); write(fd1, &val2, sizeof(val2)); write(fd2, &val, sizeof(val)); close(fd1); close(fd2); } return 0; } On a normal disk, the resulting "test1" and "test2" files will always contain identical 4-byte integers (100000). We can see this with a hex dump: $ cat test1 test2 | hexdump -C 00000000 a0 86 01 00 a0 86 01 00 |........| However, if the move program is run on test1 while the program runs, we can desynchronize: $ echo /mnt/cache/[path]/test1 | move -d 2 $ cat test1 test2 | hexdump -C 00000000 9f 86 01 00 a0 86 01 00 |........| Note that the two files now differ by 1. Losing writes can result in a lot of unexpected behaviors; I think it might be responsible for corruption I've seen in files downloaded by Transmission, as well as in sqlite databases (I saw corruption in my Plex Media Server database last night that appears consistent with lost writes, and happened about the same time as I ran the mover script). I'm not sure what the best solution for this problem is, as I'm not familiar with the internals of the mover program or the shfs ioctl it uses. One route could be to do the copy to a tmp file on the destination drive, then while holding an internal lock on the file as exposed by fuse, verify that it hasn't changed since the copy started, and only then take the place of the source. Alternately, while a file is being moved, shfs could expose it to userspace such that reads come from the source file, but writes go to both the source and the destination.
  19. 2 points
    Please open a new report for each issue/bug you find unique to this version. Version 6.6.0-rc4 2018-09-16 Linux kernel: version 4.18.8 Management: webgui: System devices: fixed display of ACS override warning message webgui: Correction in custom parity schedule webgui: VM edit corrections create image when new vdisk is added keep sound card selection included fix add/remove of network interfaces webgui: CPU pinning: preserve "emulatorpin" entry
  20. 1 point
    I have a issue with "br0". Everytime when I restart my unRAID Server and want to start the docker containers I'll get an error. I checked the log file but I can't find anything. Also I checked the container and if I check "Network Type" I can't choice "custom br0" it's gone. The solution to make it working again is going to the setting page the the Docker tab and disable and enable Docker. Now everything is returned to the normal situation. If I check the Docker container "Network type" is now "custom br0". I think I reported this before. So I think it's a bug whats exists for a longer time period.
  21. 1 point
    I created a new Win10 VM, first one on RC6, passing through a Logitech receiver/mouse and a Corsair keyboard (1b1c:1b20) and video card. Standard procedure, same process I've done three times on RC5 when setting up a new VM. After starting the VM, the keyboard becomes unresponsive on the unraid console, as expected as it's being passed through to the VM. Roughly 25 seconds later, the keyboard becomes responsive again on the console and not responding in the VM. I expect this issue to go away on RC7 with the rollback but logging for posterity. vm1-diagnostics-20191118-2155.zip
  22. 1 point
    So I appear to be having a problem with dockers, Specifically Linuxserver ones, but they said to me it is an unRAID issue and it is "not just us." I chatted with someone from Linuxserver in private and they said it is an issue with "Update all containers." The dockers will say there is an update ready, but when updated, it does not do anything. Tried manually updating a docker, same result. gibson-diagnostics-20190829-1841.zip
  23. 1 point
    Very often I see people marking their issue as "urgent" because it has impact on the operation of their system. Please consider carefully when to use the "urgent" priority. Using this level implies a serious bug affecting a large group of people. Make sure it is not related to the specific set up of your system. At minimum the issue must be reproduceable in safe mode. Any issue marked as "urgent" gets high attention at Limetech, but this gives a lot more burdon to investigate. If uncertain start with marking as "minor", if it turns out to be a serious issue its priority can always be raised.
  24. 1 point
    I am having two minor visual issues. The first has been around since 6.7.2 maybe 6.7.1 but definitely was correct in 6.7.0. When the "Display array utilization indicator" is turned on it sits above everything like the Z-index is incorrect. The second issue is when loading the dashboard the docker containers box has a very large gap where a third column of icons could be. I am running the Gray theme.
  25. 1 point
    I installed RC1 and it booted fine. Dockers & VM's running. Hit the Stop button to bring down the array so I could change a SMB setting to disable netbios. The status bar kept reporting that it was retrying to unmount. Unable to pull up the syslog via the GUI so I telnetted in and tailed the syslog. Received the following over & over. Oct 15 01:17:30 NAS emhttpd: Retry unmounting disk share(s)... Oct 15 01:17:35 NAS emhttpd: Unmounting disks... Oct 15 01:17:35 NAS emhttpd: shcmd (250): umount /mnt/cache Oct 15 01:17:35 NAS root: umount: /mnt/cache: target is busy. Oct 15 01:17:35 NAS emhttpd: shcmd (250): exit status: 32 lsof didn't report any files on /mnt/cache open. "mount -l" reported: /mnt/cache/system/docker/docker.img on /var/lib/docker type btrfs (rw) I entered "umount /var/lib/docker" and the unraid "Stop" function was able to complete. Seems like the unmount order needs to be adjusted. nas-diagnostics-20191015-0819.zip
  26. 1 point
    I noticed this back on RC3 but since RC5 came out, I updated and waited to see if it happened again. Back on RC3, it happened to CPU 0 which was assigned to UNRAID. Now it's showing up with CPU 14 which is the last core assigned to a Win10 VM. Task manager in Win10 shows no activity. Remoting into the server, htop does not show 100% utilization. I see it updating at the same rate as the other CPUs. nas-diagnostics-20190302-0815.zip
  27. 1 point
    I've seen several people reporting slower network speeds (tests and real work performance) are slower after upgrading to 6.7.0 I've seen this with the Speedtest plugin and a Win 10 VM going to speedtest.net. Speed is about 200Mbps slower than in version 6.5.4 (in my case). Others have seen the same issue of speed difference between 6.6.7 (normal expected speeds) and 6.7.0 (slower speeds by 200-300Mbps).
  28. 1 point
    when you change the setting Tunable (enable NCQ) to yes in disk setup and click apply, and it will do nothing to enable NCQ, I have to manually change the queue_depth to 31 in CLI startArray=yes&spindownDelay=0&spinupGroups=no&defaultFormat=2&defaultFsType=xfs&shutdownTimeout=90&poll_attributes=600&queueDepth=0&nr_requests=128&md_num_stripes=4096&md_sync_window=2048&md_sync_thresh=2000&md_write_method=0&changeDisk=Apply&csrf_token=**************** Aug 22 17:09:51 Tower emhttpd: shcmd (9335): echo 128 > /sys/block/sdf/queue/nr_requests Aug 22 17:09:51 Tower emhttpd: shcmd (9336): echo 128 > /sys/block/sde/queue/nr_requests Aug 22 17:09:51 Tower emhttpd: shcmd (9337): echo 128 > /sys/block/sdb/queue/nr_requests Aug 22 17:09:51 Tower emhttpd: shcmd (9338): echo 128 > /sys/block/sdd/queue/nr_requests Aug 22 17:09:52 Tower emhttpd: shcmd (9339): echo 128 > /sys/block/sdc/queue/nr_requests Aug 22 17:09:52 Tower kernel: mdcmd (95): set md_num_stripes 4096 Aug 22 17:09:52 Tower kernel: mdcmd (96): set md_sync_window 2048 Aug 22 17:09:52 Tower kernel: mdcmd (97): set md_sync_thresh 2000 Aug 22 17:09:52 Tower kernel: mdcmd (98): set md_write_method 0 Aug 22 17:09:52 Tower kernel: mdcmd (99): set spinup_group 0 0 Aug 22 17:09:52 Tower kernel: mdcmd (100): set spinup_group 1 0 Aug 22 17:09:52 Tower kernel: mdcmd (101): set spinup_group 2 0 Aug 22 17:09:52 Tower kernel: mdcmd (102): set spinup_group 3 0 Aug 22 17:09:52 Tower kernel: mdcmd (103): set spinup_group 4 0
  29. 1 point
    Have a thread going with 13 reports of AMD motherboards that, after upgrade to the latest BIOS, get the following error for Windows 10 VMs with GPU pass-through: vfio: Unable to power on device, stuck in D3 It affects the x300, X400, and the new X570 series mobos. This has been an issue since March 2019 when AMD motherboard manufacturers began preparing for the AMD 3000 CPUs. In the thread, I noted during some early research that the same issue plagued the AMD TheadRipper on x399 motherboards back in 2018(??), and I think the final solution came in the form of a Linux Kernel upgrade. This is my first report. Let me know if I need to change anything, or if it's not applicable here. Thank you!
  30. 1 point
    Please see this thread for more information. I've seen the same behavior since 6.6 and now on to 6.7. Also with 2 completely different servers (completely different hardware).
  31. 1 point
    This bug likely exists for some time, guess it's a corner case, but an user ran into it today. How to reproduce: Say you have all 2TB data disks, upgrade parity to a larger disk, e.g. 3TB, start the array and cancel the parity sync, stop the array and replace the 3TB parity with a 2TB disk, start array and parity sync will start again but will still show the old 3TB size for total parity size (not the disk itself), then it will error out during the sync when it runs past the actual parity size with an error similar to this one: May 28 19:04:44 Tower9 kernel: attempt to access beyond end of device May 28 19:04:44 Tower9 kernel: sdc: rw=1, want=976773176, limit=976773168 May 28 19:04:44 Tower9 kernel: md: disk0 write error, sector=976773104 May 28 19:04:44 Tower9 kernel: attempt to access beyond end of device May 28 19:04:44 Tower9 kernel: sdc: rw=1, want=976773184, limit=976773168 May 28 19:04:45 Tower9 kernel: md: disk0 write error, sector=976773112 May 28 19:04:45 Tower9 kernel: md: recovery thread: exit status: -4 This will result in parity disk being disabled, and the user will need to sync it again. I guess there will also be a problem if a small disk is used first and then replaced with a larger one, likely parity will say valid but it won't be synced past the end of the smaller device.
  32. 1 point
    I use papertrail and their remote server address has a 5 digit port - the field on the page only allows for 4 digits
  33. 1 point
    Hey, so i wanna update all my dockers and plugins every day, without notice, i just press them away anyway... and if something goes wrong, i have daily backups. I asked here for support, but i guess, the options i did were correct and it shoudl work that way: Here are some screenshots, still it comes up.
  34. 1 point
    Hi team I've tried upgrading to 6.6.x a couple of times now with both times having random lock ups as if none of the AMD teams had been done. Both times were able to switch back to 6.5.7 without a problem.
  35. 1 point
    When the array is stopped there are cron entries that could be problematic. When the array is stopped the following is in the crontab and /etc/cron.d/root. # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system. If a script fails, run-parts will # mail a notice to root. # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: 30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: 20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null # Generated docker monitoring schedule: 10 0 * * 1 /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated parity check schedule: 0 9 1 * * /usr/local/sbin/mdcmd check &> /dev/null || : # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated unRAID OS update check schedule: 11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null # Generated ssd trim schedule: 30 5 * * * /sbin/fstrim -a -v | logger &> /dev/null I don't know if any of these items running while the array is stopped would cause any issues. If the timing was right during a shutdown, I could see come issues.
  36. 1 point
    Docker port conflicts are no longer highlighted to the user in template editor. Previously port numbers would be highlighted in red on the docker allocations drop-down, when template default port conflicted with existing port allocations... signifying an issue to be rectified. If a user doesn't pickup the conflict manually, the result is a failed container creation.
  37. 1 point
    Version: 6.6.6 Problem: Unable to update a VM. After clicking "update," the button simply changes to "updating..." and never finishes. Replication Steps: 1. Select VM and click "Edit" 2. Change Name (or toggle "autostart"... just to test some kind of change😞 3. Click "Update". Other Notes: If it helps to diagnose the problem, toggling "auto start" from the "Virtual Machines" main menu works perfectly (see image below). However, clicking into a specific VM via "edit", and then choosing "update", as mentioned above, does not.
  38. 1 point
    https://fedorapeople.org/groups/virt/virtio-win/CHANGELOG * Mon Feb 04 2019 Cole Robinson <crobinso@redhat.com> - 0.1.164-1 - Update to virtio-win-prewhql-0.1-164 - Update to qemu-ga-win-100.0.0.0-3.el7ev - Add win10 arm64 experimental drivers Driver is still considered "Latest", since the "Stable" branch is still on 0.1.141-1 https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/virtio-win.iso
  39. 1 point
    As the new Dashboard is amazing, I would prefer it if Unraid would take me to that by default when I access the web UI. Is there an option to do this?
  40. 1 point
    I just enabled ACS PCIe Override for the first time after using unRAID for 2 years. Even though I've learnt in my time as a novice user what it does, I didn't know there were options available - downstream, multifunction or both. The current help text says: It'd be more useful given the warning if the text had a bit on what each option did, and maybe a link to a FAQ.
  41. 1 point
    Tagging @limetech because of recent discussions. With respect and no sarcasm (seriously) I request that you read this post, if you see your name tagged. I want to help fix this since unRAID is currently unusable for me. It's why I've tagged this as Urgent. Upgraded to 6.6.3 to try and diagnose issues, if they came back. The SFTP issues I logged in another post relating to 6.6.0 are still there (the other post is at the bottom of this one). I use a variety of tools/utilities to carry out various things over SFTP. - Backups with Duplicati. Connection is established, but all file transfers fail. - File transfers with FileZilla. Connection is established and I can login and browse, but can't transfer anything. The transfer all sits there on 0% and never get any further. - File transfers with gFTP. Works. All 3 of the above methods were faultless on 6.5.3 and nothing has changed on the client ends. Logic dictates that it's something on the unRAID side. That was before. In the post linked further down, @limetech suggested to do the following: wget http://slackware.cs.utah.edu/pub/slackware/slackware64-current/slackware64/n/openssh-7.9p1-x86_64-1.txz upgradepkg openssh-7.9p1-x86_64-1.txz I did that and now I can't login to my unRAID server *AT ALL* over SSH. From the client perspective, this is what I got at first, when trying to SSH into the server. ~ » ssh root@192.168.1.85 ssh_exchange_identification: read: Connection reset by peer I restarted sshd using the following, thinking that maybe something didn't get reloaded properly. /etc/rc.d/rc.sshd restart That didn't fix it. So I then disabled SSH from the GUI, then re-enabled SSH from the GUI. Now I get this when I try to login via SSH: ~ » ssh root@192.168.1.85 ssh: connect to host 192.168.1.85 port 22: Connection refused Looks to me like sshd isn't even listening anymore. It's worth nothing that SSH *excluding* SFTP was fine until I upgraded OpenSSH as per above. I can still open a terminal from the GUI, however. Trying to restart sshd from the GU terminal, now, shows this: OpenSSL version mismatch. Built against 1010100f, you have 1010009f OpenSSL version mismatch. Built against 1010100f, you have 1010009f I can Google and fix that, I'm sure, but why would that even happen? Honestly, I'm at a bit of a loss here. I thought I was doing the right thing by upgrading to 6.6.3 in order to diagnose issues and provide feedback/logs, but now I have an unRAID system I can't use. I can't even login to it to get logs or diagnostics issues. It is a headless box that has no monitor or keyboard attached. I know that's nobody's problem but mine, but it is a problem, nonetheless. Can anyone help? Please?
  42. 1 point
    Throughout all of the releases, I have grown used to the low 1024x768 limit of gui, and not the desired 1920x1080. However this new release has gone back in time to 800x600 and I can't use it at all. Through previous troubleshooting I have 1920x1080 dummy plugs in all ports not in use. This is limited to this release and no others so far have limited to less than 1024x768. Can this be corrected easily/rapidly? I would love to test the new RC but can't without gui boot. nas-diagnostics-20180902-1650.zip
  43. 1 point
    A NFS share of a user share /mnt/user/Test 192.168.2.0/24(rw,async,wdelay,hide,no_subtree_check,fsid=110,sec=sys,secure,root_squash,no_all_squash) can be mounted by a client for rw access, but completely ignores the permissions. [root@centos user]# mount mediastore:/mnt/user/Test /mnt/user/Test [root@centos user]# ls -ld Test drwxrwx---. 1 nobody users 20 Jun 20 08:27 Test [root@centos user]# cd Test [root@centos Test]# touch a [root@centos user]# ls -l a -rw-r--r--. 1 nfsnobody nfsnobody 0 Jun 20 08:27 a [root@centos Test]#
  44. 1 point
    Welcome to the new experimental Prerelease Support board! We have added the ability to tag issues/bugs with a Priority and mark when solved. Please report only issues/bugs which are new in the prerelease. Attention Intel 10Gbit Ethernet users: in this release we replaced the linux in-tree kernel drivers (ixgbe/ixgbevf) with the latest available from Intel. This change should be considered experimental. That is, for those of you having issues with Intel 10Gbit adapters, please report if this change solves the issues. Likewise, please report if you have successfully been using an Intel 10Gbit adapter and now you are having issues. If new problems arise or the old problems are not solved we will revert to in-tree drivers in the next release. Version 6.5.1-rc6 2018-04-14 Management: webgui: Add missing csrf_token when adding new container webgui: Added next parity schedule indicator on dashboard page webgui: Update cron when removing a plugin webgui: Nchan/Nginx: Use long polling for Safari and websockets for all other browsers Version 6.5.1-rc5 2018-04-08 Base distro: nginx: version 1.13.11 (with nchan: version 1.1.14) Linux kernel: version 4.14.33 out-of-tree drivers: intel ixgbe: version 5.3.6 intel ixgbevf: version 4.3.4 Management: samba: set 'allocation roundup size = 4096' in /etc/samba/smb.conf (fix inaccurate file usage vs. disk usage reporting)
  45. 1 point
    I ran the update from rc5 to rc6, shutdown the machine, and then booted it again. Everything went pretty fast and it seemed normal, but when RC6 booted it complained about an unclean shutdown and started a parity-check for no reason (?). htpc-diagnostics-20180416-1032.zip syslog-20180416-101745.txt Edit: I attached an additional log-file that should show the shutdown.
  46. 1 point
    Welcome to the new experimental Prerelease Support board! We have added the ability to tag issues/bugs with a Priority and mark when solved. Please report only issues/bugs which are new in the prerelease. Attention Intel 10Gbit Ethernet users: in this release we replaced the linux in-tree kernel drivers (ixgbe/ixgbevf) with the latest available from Intel. This change should be considered experimental. That is, for those of you having issues with Intel 10Gbit adapters, please report if this change solves the issues. Likewise, please report if you have successfully been using an Intel 10Gbit adapter and now you are having issues. If new problems arise or the old problems are not solved we will revert to in-tree drivers in the next release. Version 6.5.1-rc5 2018-04-08 Base distro: nginx: version 1.13.11 (with nchan: version 1.1.14) Linux kernel: version 4.14.33 out-of-tree drivers: intel ixgbe: version 5.3.6 intel ixgbevf: version 4.3.4 Management: samba: set 'allocation roundup size = 4096' in /etc/samba/smb.conf (fix inaccurate file usage vs. disk usage reporting)
  47. 1 point
    Welcome to the new experimental Prerelease Support board! We have added the ability to tag issues/bugs with a Priority and mark when solved. Please report only issues/bugs which are new in the prerelease. Too many issues with docker 17.12.x release, and we haven't had enough internal testing with 18.03.x release, so we are reverting back to 17.09.1. We are anticipating moving to 18.03.x in unRAID OS 6.6. Also: got rid of the "wont fix" tag and replaced with "Retest". If you see this on your bug report it means that you should see if the latest release fixes the problem. This might seem odd that we, the developers, might not know this; but, often we cannot reproduce many issues that are reported. Some issues end up being solved by a newer kernel release. Some issues we may have developed a theory why it might be happening and then put a change in the code to address it. Version 6.5.1-rc3 2018-03-30 Summary: Security updates, bug fixes and UI improvements. Base distro: docker: version 17.09.1 (downgrade from version 17.12.1) openssl: version 1.0.2o (CVE-2018-0739) openssl-solibs: version 1.0.2o (CVE-2018-0739) Linux kernel: version 4.14.31 with tcp_reset_sk_send_head_in_tcp_write_queue_purge patch with tehuti pci-id [1fc9:3015] patch (experimental) Management: Ensure hostname contains only valid NETBIOS characters Yet another mover logging fix webgui: Fixed display of error codes in SWAL webgui: VMmachine updates changed DETACH is available when VM is running default bus to VirtIO minor layout changes webgui: Docker only remove icons when container/image is deleted webgui: DockerClient: sort container names alphabetically and port numbers numerically webgui: Sort unassigned devices by disk size, disk model, disk name This groups disks together by size, followed by same model, and lastly their assigned name (sdX) webgui: Dokcer combine used ports and ips in single list webgui: Fixed: dashboard apps, properly initialize menu variable webgui: Reduced container list to one call to docker only for all containers at once webgui: Fixed VM 'detach' button webgui: Add short delay in array list update after spin up/spin down of disk webgui: Fix Create Docker php warning webgui: Diagnostic improvements webgui: Fixed false "next" announcement when on "stable " release webgui: Fixed removal of container and updating of json file webgui: Restore Apply button to previous behavior
  48. 1 point
    Doesn't matter if the setting is enabled or disabled, mover will always log the files being moved. servera-diagnostics-20180327-2040.zip
  49. 1 point
    Welcome to the new experimental Prerelease Support board! We have added the ability to tag issues/bugs with a Priority and mark when solved. Please report only issues/bugs which are new in the prerelease. This release mainly consists of security patches and bug fixes. We want to again, thank @bonienl for his continued amazing work with the .webGUI. We also want to acknowledge significant contributions from @Squid and valuable input from @realies - thank you! Version 6.5.1-rc2 2018-03-23 Summary: Security updates, bug fixes and UI improvements. Base distro: dmidecode: version 3.1 dnsmasq: version 2.79 e2fsprogs: version 1.44.0 fontconfig: version 2.12.6 hdparm: version 9.55 libevdev: version 1.5.9 libtirpc: version 1.0.3 libxml2: version 2.9.8 logrotate: version 3.14.0 mozilla-firefox: version 59.0.1 (CVE-2018-5127, CVE-2018-5128, CVE-2018-5129, CVE-2018-5130, CVE-2018-5131, CVE-2018-5132, CVE-2018-5133, CVE-2018-5134, CVE-2018-5135, CVE-2018-5136, CVE-2018-5137, CVE-2018-5138, CVE-2018-5140, CVE-2018-5141, CVE-2018-5142, CVE-2018-5143, CVE-2018-5126, CVE-2018-5125, CVE-2018-5146, CVE-2018-5147) nano: version 2.9.4 sysvinit-scripts: version 2.1 (rev7) transset: version 1.0.2 xinit: version 1.4.0 xkill: version 1.0.5 xload: version 1.1.3 xlsclients: version 1.1.4 xmessage: version 1.0.5 xprop: version 1.2.3 xrdb: version 1.1.1 xrefresh: version 1.0.6 xset: version 1.2.4 xsetroot: version 1.1.2 xsm: version 1.0.4 xwd: version 1.0.7 xwininfo: version 1.1.4 xwud: version 1.0.5 Linux kernel: version 4.14.29 with tcp_reset_sk_send_head_in_tcp_write_queue_purge patch Management: webgui: Docker add/edit: corrected list of exposed ports and assigned IPs webgui: Docker: unrestricted edit in authoring mode webgui: VM manager: fix increasing vdisk size webgui: Added "Update all Plugins" button to plugins page webgui: Execute docker commands with timeout webgui: Do version checking on source file loading webgui: Set vertical scroll bar only in VM dropdown file lists webgui: Fixed disk share cycling webgui: Made "spinner" consistent in every display theme Version 6.5.1-rc1 2018-03-20 Summary: Security updates, bug fixes and UI improvements. Base distro: curl: version 7.59.0 (CVE-2018-1000120, CVE-2018-1000121, CVE-2018-1000122) kernel-firmware: version 20180222_7344ec9 intel-microcode: version 20180312 Linux kernel: version 4.14.28 Management: mover: Regression: fix "mover: started/finished" message not output when mover logging enabled webgui: Plug Security Hole In Docker Template PostArgs webgui: Wording change on a error returned by plugin manager webgui: Docker: remove BOND members from custom network list webgui: DockerClient: improved caching webgui: Show zero source address when container is stopped webgui: Regression: fix network mode in container list webgui: Regression: fix container sorting webgui: Regression: return LOG display as before in docker list webgui: Add "reset sorting" to docker and VM list webgui: Allow user sorting preference for containers and VMs Sorting preference also dictates the sequence in which containers and VMs are started and stopped (reversed) webgui: Fixed regression error in plugin updates webgui: Fixed port mapping of user defined networks webgui: Fixes and improvements for Docker fixed deletion of orphan images inline list update when removing container or image fixed list updating after execution error added animation when removing container or image delete old xml file when container is renamed fixed IP assignment with multiple containers based on the same image webgui: Fixed VM list updating when VM is deleted webgui: Added ability to remove downloaded virtio iso files from the VM Settings page webgui: Allow concurrent virtio iso downloads on VM Settings page; fix progress display upon page refresh webgui: Docker: Don't automatically update webUI entry on templates webgui: Make disk spin up/down inline without refresh of complete page webgui: Docker Security: Remove any present script and iframe tags from all elements in a template webgui: Docker: Don't automatically update webUI entry on templates webgui: VM manager: replace pause icon for refresh when updating webgui: Change animation to spinning "refresh" webgui: Minor correction: let container list start in basic view with collapsed rows when no cookie is set yet webgui: Fix "Schedule" reference in tabbed/non-tabbed mode and return to Main page webgui: Do Clear Statistics inline without complete page refresh webgui: Fixed wrong cpu references in popup window in VM list 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 1.8.1.2 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
  50. 1 point
    Welcome to the new experimental Prerelease Support board! We have added the ability to tag issues/bugs with a Priority and mark when solved. Please report only issues/bugs which are new in the prerelease. This release mainly consists of security patches and bug fixes. We want to again, thank @bonienl for his continued amazing work with the .webGUI. We also want to acknowledge significant contributions from @Squid and valuable input from @realies - thank you! Version 6.5.1-rc1 2018-03-20 Summary: Security updates, bug fixes and UI improvements. Base distro: curl: version 7.59.0 (CVE-2018-1000120, CVE-2018-1000121, CVE-2018-1000122) kernel-firmware: version 20180222_7344ec9 intel-microcode: version 20180312 Linux kernel: version 4.14.28 Management: mover: Regression: fix "mover: started/finished" message not output when mover logging enabled webgui: Plug Security Hole In Docker Template PostArgs webgui: Wording change on a error returned by plugin manager webgui: Docker: remove BOND members from custom network list webgui: DockerClient: improved caching webgui: Show zero source address when container is stopped webgui: Regression: fix network mode in container list webgui: Regression: fix container sorting webgui: Regression: return LOG display as before in docker list webgui: Add "reset sorting" to docker and VM list webgui: Allow user sorting preference for containers and VMs Sorting preference also dictates the sequence in which containers and VMs are started and stopped (reversed) webgui: Fixed regression error in plugin updates webgui: Fixed port mapping of user defined networks webgui: Fixes and improvements for Docker fixed deletion of orphan images inline list update when removing container or image fixed list updating after execution error added animation when removing container or image delete old xml file when container is renamed fixed IP assignment with multiple containers based on the same image webgui: Fixed VM list updating when VM is deleted webgui: Added ability to remove downloaded virtio iso files from the VM Settings page webgui: Allow concurrent virtio iso downloads on VM Settings page; fix progress display upon page refresh webgui: Docker: Don't automatically update webUI entry on templates webgui: Make disk spin up/down inline without refresh of complete page webgui: Docker Security: Remove any present script and iframe tags from all elements in a template webgui: Docker: Don't automatically update webUI entry on templates webgui: VM manager: replace pause icon for refresh when updating webgui: Change animation to spinning "refresh" webgui: Minor correction: let container list start in basic view with collapsed rows when no cookie is set yet webgui: Fix "Schedule" reference in tabbed/non-tabbed mode and return to Main page webgui: Do Clear Statistics inline without complete page refresh webgui: Fixed wrong cpu references in popup window in VM list