• Unraid OS version 6.8.0-rc7 available


    limetech

    -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
    • Like 3
    • Thanks 5


    User Feedback

    Recommended Comments



    Quote

     

    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".

    The "stripe pool" resource is automatically shared evenly between all active streams.

     

    Can confirm this feature works. however, is there possibly a method/setting to revert behaviour to work as before?

    i have situations where i want the mover to complete quicker rather than delay due to a single active stream (that uses Kb's odf data verus about 50MB's of transfer speed that is unavailable for the mover.

    Link to comment
    Share on other sites
    Quote

    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.

    Should this work regardless of what network protocol is being used?

     

    I had parity check running and streaming a movie was completely impossible via NFS (I believe this was even possible without this feature before...).

    Haven't tried via SMB yet, just wondering whether if this feature protocol dependent or not.

    Edited by olympia
    Link to comment
    Share on other sites
    13 hours ago, dgriff said:

    Still having strange IO problem writing to my array (through the cache).

     

    Downloading torrents and things slow to a crawl  (from ~10MB/sec on 6.7.2 to under 100k/sec, usually around 20k/sec with 6.8RC7), CPU usage hovering around 40% (not much happening on the array).

     

    Reverted to 6.7.2 and everything is back to normal and CPU usage <20%, usually <10%.  Diagnostics attached (remembered to pull them this time!).

    diagnostics-20191124-0522.zip 145.68 kB · 4 downloads

    I am having similar issues.  I will post a log next time.  If I am unpacking a large RAR file on the cache drive nothing else can happen on the array.  Netdata will even freeze and when it comes back there is no data (a blank section) on all the CPU charts for however long it froze while extracting the files.

     

    craigr

    Link to comment
    Share on other sites
    13 hours ago, dgriff said:

    Still having strange IO problem writing to my array (through the cache).

     

    Downloading torrents and things slow to a crawl  (from ~10MB/sec on 6.7.2 to under 100k/sec, usually around 20k/sec with 6.8RC7), CPU usage hovering around 40% (not much happening on the array).

     

    Reverted to 6.7.2 and everything is back to normal and CPU usage <20%, usually <10%.  Diagnostics attached (remembered to pull them this time!).

    diagnostics-20191124-0522.zip 145.68 kB · 5 downloads

     

    Try uninstalling the PreClear Disk plugin. It's doing bad things with libevent, replacing a newer version with a much older version [ 2.1.11 replaced with 2.1.8 ]

     

     

    +==============================================================================
    Nov 22 22:57:10 KizunaAi root: | Upgrading libevent-2.1.11-x86_64-1 package using /boot/config/plugins/preclear.disk/libevent-2.1.8-x86_64-3.txz
    Nov 22 22:57:10 KizunaAi root: +==============================================================================
    Nov 22 22:57:10 KizunaAi root: Pre-installing package libevent-2.1.8-x86_64-3...
    Nov 22 22:57:10 KizunaAi root: Removing package: libevent-2.1.11-x86_64-1-upgraded-2019-11-22,22:57:10
    Nov 22 22:57:10 KizunaAi root: Verifying package libevent-2.1.8-x86_64-3.txz.
    Nov 22 22:57:10 KizunaAi root: Installing package libevent-2.1.8-x86_64-3.txz:

     

     

    Link to comment
    Share on other sites

    This particular issue is being dealt with in this bug report

    It is specific to users who have configured docker containers with a custom network (macvlan) and VMs sharing the same interface. There exist several workarounds to mitigate the issue (see the dedicated topic above).

    In parallel we are investigating how to solve the issue.

     

    Please respond in the appropriate bug report if you have more information/findings which can help to resolve the issue.

    • Like 1
    • Thanks 1
    Link to comment
    Share on other sites

    Anyone have any issues with Q35 VMs breaking with each RC update? Becoming a bit of a pain but I manage to get it working each time... Need to get it working on RC7 still though. Essentially the VM starts but I get no screen output on my GPU passthrough.

    Edited by J89eu
    Link to comment
    Share on other sites
    37 minutes ago, J89eu said:

    Anyone have any issues with Q35 VMs breaking with each RC update? Becoming a bit of a pain but I manage to get it working each time... Need to get it working on RC7 still though. Essentially the VM starts but I get no screen output on my GPU passthrough.

    Are you talking about "every single RC" for 6.8? The Qemu version changed a couple times and with a downgrade from 4.1 to 4.0 is one of a reasons why maybe VMs broke for you if you have setup a Q35-4.1 and after a downgrade that version was above the highest suported Q35-4.0. I'am running my Win10 VM as Q35 for quite a while now and had no issues so far on all RCs. I think libvirt is downgraded in the current release, maybe this is causing it for you.

    Link to comment
    Share on other sites

    Simple request, I'd like a check box on the NEXT branch where I can ask for the system to not notify me until there is a stable 6.8 release.

     

    Additionally, an automatic polling request for updates would be nice. 

    Link to comment
    Share on other sites
    40 minutes ago, eagle470 said:

    Simple request, I'd like a check box on the NEXT branch where I can ask for the system to not notify me until there is a stable 6.8 release.

    If you are on the NEXT branch, you are expected to install updates as you can, and participate with diagnostics if you find an issue. If you don't want to be bugged until the a stable release, you need to be running the stable branch.

     

    I know there are valid reasons to not stay on 6.7.2, but it's not reasonable to expect to treat the NEXT branch as stable.

    Link to comment
    Share on other sites
    1 hour ago, eagle470 said:

    Additionally, an automatic polling request for updates would be nice.

    Already exists. See Settings -> Notification Settings -> Unraid OS update notification

    • Like 1
    • Haha 1
    Link to comment
    Share on other sites
    On 11/23/2019 at 9:45 AM, nuhll said:

    does vms finally work??? 

    my three are however my windows 10 is awwwfuly sluggish and slow..still trying to see if its the mac rdp client or vm itself

    Link to comment
    Share on other sites
    2 hours ago, jonathanm said:

    If you are on the NEXT branch, you are expected to install updates as you can, and participate with diagnostics if you find an issue. If you don't want to be bugged until the a stable release, you need to be running the stable branch.

     

    I know there are valid reasons to not stay on 6.7.2, but it's not reasonable to expect to treat the NEXT branch as stable.

    Its the holiday week and I have a snow storm coming...I'd rather not be troubleshooting while my users are bored and pissed at me...

    Link to comment
    Share on other sites
    3 minutes ago, eagle470 said:

    Its the holiday week and I have a snow storm coming...I'd rather not be troubleshooting while my users are bored and pissed at me...

    What are you talking about?

    Link to comment
    Share on other sites
    Just now, limetech said:

    What are you talking about?

    I don't want to patch this week as I expect I will need my system online full time starting Wednesday and I've found 6.8-rc6 to be stable enough for me. I just don't want the notification now that my system has found an update available. 

     

    Patching means a certain level of risk, while I'm understanding and generally prepared for that, I don't want to deal with a 1 year old and no Sesame Street and we can't leave the house...Also all my other users would be frustrated too.....

    Link to comment
    Share on other sites
    1 hour ago, bonienl said:

    Already exists. See Settings -> Notification Settings -> Unraid OS update notification

     

    6 minutes ago, eagle470 said:

     I just don't want the notification now that my system has found an update available. 

     

    Read the reply from bonienl.

     

    image.png.213c346db425c2cbccbb48d0170749ad.png

     

    Edited by BRiT
    Pics or it never happened ...
    Link to comment
    Share on other sites
    1 hour ago, Can0nfan said:

    my three are however my windows 10 is awwwfuly sluggish and slow..still trying to see if its the mac rdp client or vm itself

    Are you running an overclocked Threadripper? My Windows 10 VM's are extremely sluggish to the point of not even being viable even with a very modest OC but rock-solid on stock. Haven't identified a reason why yet.

    • Like 1
    Link to comment
    Share on other sites

    Edit: No issues with r7 except the macvlan issue which has been described by others.

     

    Is a linux kernel update to 5.4 planned for the 6.8 branch. As a gen 3 Ryzen user there are some useful improvements in there for me.

     

    Apologies if it has already been discussed, I tried searching without much luck. Either I failed or the parsing of '5.4' was tricky.

    Edited by nagelm
    context
    Link to comment
    Share on other sites

    Hopefully a new kernel will be reserved for a quick 6.9 RC series and 6.8 Stable can be released.

    Link to comment
    Share on other sites
    1 hour ago, Johan1111 said:

    Still with the same issue IPv4 address not set

     

    unRAID Server OS version: 6.8.0-rc7

    IPv4 address: not set

    IPv6 address: not set

     

    Tower login: 

    i'm attaching my log files

    tower-diagnostics-20191125-1611.zip 49.33 kB · 1 download

     

    I remember I have the same issue after I poweroff and restart the sever,  first time boot, all IP address is not set, then I reboot the server, this time system will have a IP of 169.x.x.x,  reboot again,  now system will get the correct IP

     

    I thought I was the only one have this issue since I never see anyone report similar issue, would you please try to reboot to see if you can duplicate my issue

    Link to comment
    Share on other sites
    5 hours ago, BRiT said:

    Hopefully a new kernel will be reserved for a quick 6.9 RC series and 6.8 Stable can be released.

    Pshhh.... think longer, I want Linux kernel 5.6 with wireguard support in kernel in the next RC.

     

    RC7 is stable for me.

     

    Enjoy Thanksgiving in the USA and then come back to us and our sesame street problems.

     

     

     

    Edited by Dazog
    • Haha 1
    Link to comment
    Share on other sites
    6 hours ago, nagelm said:

    Edit: No issues with r7 except the macvlan issue which has been described by others.

     

    Is a linux kernel update to 5.4 planned for the 6.8 branch. As a gen 3 Ryzen user there are some useful improvements in there for me.

     

    Apologies if it has already been discussed, I tried searching without much luck. Either I failed or the parsing of '5.4' was tricky.

    I read in other post that 6.9 RC1 will use 5.4

    Link to comment
    Share on other sites
    4 hours ago, trott said:

     

    I remember I have the same issue after I poweroff and restart the sever,  first time boot, all IP address is not set, then I reboot the server, this time system will have a IP of 169.x.x.x,  reboot again,  now system will get the correct IP

     

    I thought I was the only one have this issue since I never see anyone report similar issue, would you please try to reboot to see if you can duplicate my issue

    I restarted multiple times like 5 and still got the same all the time. never happened with 6.7.3-rc4.

    Link to comment
    Share on other sites



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • 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.