• Unraid OS version 6.8.0-rc3 available


    limetech
    • Closed

    Q: -rc3?  what happened to -rc2?

    A: we thought a setting resulted in disabling auto-logout but instead made it happen almost immediately - sorry about that.

     

    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-rc3 2019-10-17

    Management:

    • php: set very long session timeout

     

    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
    • Thanks 2



    User Feedback

    Recommended Comments



    3 hours ago, sittingmongoose said:

    I am testing the same way.  If I turn on parity check and mover, it’s completely unusable.  
     

    in rc1, pretty much nothing stoped streams from working.  It did slow down mover and parity checks but that’s expected.

     

    Make sure your CPU Scaling Governor is not set to Power Save if you're using the Tips and Tweaks plugin.  I found that while that setting is supposed to keep the CPU frequency at it's lowest setting regardless of load, in 6.7.x and earlier it was actually still ramping up the CPU frequency on demand.  Now in 6.8 is keeps the CPU at the minimum frequency.  I've since set the governor to On Demand and it's working as expected.  I've heard of other users with very power system performance in 6.8 with the CPU Scaling Governor set to Power Save and switching to On Demand fixed it.

    • Thanks 2
    Link to comment

    So no issues on RC1 with Nvidia.  Even running parity, mover and streaming 4 4k remux videos doesn't have issues.

     

    I don't know how to tune the settings in tunable.  Not sure what to change...

     

    Also, its not the cpu because on all versions I am running at all core 5GHZ.  I checked in all versions.

    Link to comment
    6 hours ago, sittingmongoose said:

    I don't know how to tune the settings in tunable.  Not sure what to change...

    With rc3 there's a setting for the scheduler, though is you didn't change it should remain the same as it was used with rc1, but check it, should be set to "mq-deadline"

     

    Settings -> Disk Settings -> Scheduler setting

    Edited by johnnie.black
    Link to comment
    3 hours ago, Johan1111 said:

    I did a fresh install of 6.8.0-rc3

    Diags posted are from v6.7.3.rc4

    Link to comment

    Hi,

    i tryed to update my Server to RC3. And then my problems starts...

     

    After rebooting the server i cant access the web gui. Tryed to wait about 2 hours but gui still not available.

    So i connected a monitor directly to the server and reboot it again. Start looks fine and unraid starts normally, but without get any ip (dhcp) from my router. So i looked into the network config file. Config file was totally messed up, so i manually edit the file for dhcp settings and reboot the server. The Server boots normal and i get access to the gui. But the web interface is absolutely unusable. So i tryed to rollback to 6.7.2.....server reboots and works normal. But Web interface is still unusable.

    any ideas?

    unraid.jpg

    Link to comment

    Yikes maybe my vanilla install was wrong. I’ll try it again afterwork.  Then post diags.

     

    either way, I know my original comments were about Nvidia rc3.

    Edited by sittingmongoose
    Link to comment
    51 minutes ago, sittingmongoose said:

    Yikes maybe my vanilla install was wrong.

    The v6.7.3.rc4 diags are from a reply to another user.

    Link to comment
    8 hours ago, TanteHorst said:

    But Web interface is still unusable.

    any ideas?

    Looks like a browser problem. Clear browser cache, try different browser, try from a different computer,...

    Link to comment
    8 hours ago, TanteHorst said:

     But Web interface is still unusable. any ideas?

    I have been encountering this for the past few days.  Hitting the <F5> key fixes it.  I am using Firefox (at the moment) and I suspect it is at the heart of this issue. (I have a couple of other websites behave the same way and using <F5> works there also.)

    Link to comment
    On 10/21/2019 at 7:19 AM, BRiT said:

    Also try adjusting the new Tunable in RC3 for the Scheduler. That's about the only bit that could have an impact.

     

    On 10/21/2019 at 8:28 AM, johnnie.black said:

    Oh yes, forgot about that, that can make a difference.

    May I ask how one knows if this should be adjusted and to what value?

     

    Thanks,

    craigr

    Link to comment
    5 minutes ago, craigr said:

    May I ask how one knows if this should be adjusted and to what value?

    I believe it should be left at the default "mq-deadline", users suffering form the SQL corruption issue were asked to select "none" to test but apparently it didn't solve the problem.

    Link to comment

    Bug on UI:

    When the browser window is maximised, the Docker Containers section used to display 3 columns of icons but now only displays 2, aligned to the left margin of the box. Perhaps each docker icon is a little wider or something?

    Link to comment
    26 minutes ago, testdasi said:

    Bug on UI:

    When the browser window is maximised, the Docker Containers section used to display 3 columns of icons but now only displays 2, aligned to the left margin of the box. Perhaps each docker icon is a little wider or something?

    Are you referring to the Dashboard page? Perhaps you need to give more detail because I'm seeing three columns, using the White theme.

     

    1330561096_ScreenShot2019-10-22at20_12_45.png.5b05be7b16ea735e4bd9523e709c839b.png

     

     

    Edited by John_M
    Added screenshot
    Link to comment
    4 minutes ago, John_M said:

    Are you referring to the Dashboard page? Pehaps you need to give more detail because I'm seeing three columns, using the White theme.

    Yes Dashboard page. A bit more details (all on Windows)

    • Chrome 1920px width - 3 columns
    • Chrome 1900px width - 2 columns
    • Firefox 1920px width - 2 columns

    Looks like you guys optimised really hard for 1920px width on Chrome.

    I have my taskbar on the side (blame it on Ubuntu habit) and I run Firefox so the width of the window is a certain number of pixels smaller than 1920px (closer to 1800 or so).

    Link to comment
    40 minutes ago, testdasi said:

    I run Firefox so the width of the window is a certain number of pixels smaller than 1920px (closer to 1800 or so).

    My screen grab was from Firefox on a 1280 pixel wide display (non-Retina 13-inch MacBook Pro) with a vertical scrollbar on the right of the window, so significantly narrower than 1920. Which theme are you using?

     

    EDIT: I switched temporarily to Gray theme and saw two columns, as you describe. Now back on White theme, with three columns.

     

    Edited by John_M
    Tried a different theme
    • Thanks 1
    Link to comment

    Ok so I went back to Vanilla RC3.  Still having the buffering issues.  CPU is at all core 5ghz.  Changed scheduler from auto to mq-deadline.  I ran my test with parity, mover and a few streams going and it crapped out again.  Here are my diags.  

     

    Through all this process I went back to RC1 Nvidia to confirm it was working as I thought and it was.  So the issue is new to RC3.

     

    Edit:  I will note it is better than it was in 6.7...Just not as good as RC1 was.

    9900k-diagnostics-20191022-2206.zip

    Edited by sittingmongoose
    Link to comment
    2 hours ago, John_M said:

    My screen grab was from Firefox on a 1280 pixel wide display (non-Retina 13-inch MacBook Pro) with a vertical scrollbar on the right of the window, so significantly narrower than 1920. Which theme are you using?

     

    EDIT: I switched temporarily to Gray theme and saw two columns, as you describe. Now back on White theme, with three columns.

     

    I think the scaling on your MacBook affects it too. When I zoom out to 90%, it's back to 3 columns.

    Anyhow, that is still probably a symptom that you guys are optimising too hard, leaving no leeway. The 6.7 layout was a bit more easy with differing display config.

     

    Edit: so looks like jbartlett also has the same issue.

    Edited by testdasi
    Link to comment
    6 hours ago, johnnie.black said:

    I believe it should be left at the default "mq-deadline", users suffering form the SQL corruption issue were asked to select "none" to test but apparently it didn't solve the problem.

    That's what gets me.  Mine is set to "auto" and I have never changed it :|

     

    Should I?

     

    Thanks,

    craigr

    Link to comment
    13 minutes ago, testdasi said:

    I think the scaling on your MacBook affects it too. When I zoom out to 90%, it's back to 3 columns.

    There isn't any scaling. It isn't a Retina display. It's 1:1.

    jbartlett says he's using -rc1. I'm using -rc3, which is the subject of this thread,

    Link to comment



    Guest
    This is now closed for further comments

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.