• 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



    On 11/24/2019 at 11:05 AM, BRiT said:

     

    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 ]

    Gave it a shot, but unfortunately no luck, same deal, almost no network thoroughput when writing, works fine again after revering to 6.7.2.  Wondering if it has something to do with the network driver as opposed to the filesystem.  New diagnostics attached.

     

    diagnostics-20191126-0523.zip

    Edited by dgriff
    Link to comment
    1 hour ago, Johan1111 said:

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

    then I might have different problem, I will grab the log when I upgrade my unraid next time

    Link to comment
    7 hours 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

    Check LAN cable:

     

    Link detected: no

     

     

    Link to comment
    1 hour ago, johnnie.black said:

    Check LAN cable:

     

    
    Link detected: no

     

     

    just rolled back to 6.7.3-rc4 without touching any cables and it works fine. it's been this way from first release 6.8.0-rc1 

    Link to comment
    21 minutes ago, Johan1111 said:

    just rolled back to 6.7.3-rc4 without touching any cables and it works fine. it's been this way from first release 6.8.0-rc1 

    That's very strange, for some reason with the new driver link is not detected, don't remember seeing that before.

     

    Is it linking at gigabit speed with v6.7?

    Link to comment
    2 minutes ago, johnnie.black said:

    That's very strange, for some reason with the new driver link is not detected, don't remember seeing that before.

     

    Is it linking at gigabit speed with v6.7?

    yes gigabit speed on a openwrt router works fine on 6.7.3-rc4 not on 6.8.0-rc

    Link to comment
    3 minutes ago, Johan1111 said:

    here are the diagnostics of 6.7.3-rc4

    Ok, I see the problem, you're using the realtek NIC with v6.7, after upgrading to v6.8 change the cable to the Intel NIC or if you prefer keep using the Realtek NIC go to Settings -> Network Settings -> Interface Rules and make the Realtek eth0, reboot required for changes to take effect.

    Link to comment
    20 hours ago, jbartlett said:

    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.

    nope same system as pre-6.7...Dual Xeon E5-2680 v1's the VM's are on a cache array od dual 1TB SSD's and i have plenty of ram for unRAID and the VM's 94GB ram with 16GB allocated to Windows, 16GB to one Fedora 30 Server and 1GB to another Fedora server

    it does seem most likely to be an issue introduced in unRAID 6.7 RC'S and the microsfot beta RDP client for my 27" 5K iMac, while still sluggish via a windows 10 laptop i have its not nearly as bad as when i use the RDP for my iMac.

    Link to comment
    8 hours ago, johnnie.black said:

    Ok, I see the problem, you're using the realtek NIC with v6.7, after upgrading to v6.8 change the cable to the Intel NIC or if you prefer keep using the Realtek NIC go to Settings -> Network Settings -> Interface Rules and make the Realtek eth0, reboot required for changes to take effect.

    just did that upgrade it and changed the cable to the other lan port of my MB still the same issue. I think is something else this never happened with any other older version.

    Link to comment
    2 hours ago, Can0nfan said:

    it does seem most likely to be an issue introduced in unRAID 6.7 RC'S and the microsfot beta RDP client for my 27" 5K iMac, while still sluggish via a windows 10 laptop i have its not nearly as bad as when i use the RDP for my iMac.

    I've concurrently remoted in using RDP (from Windows) to seven Win10 VM's on RC8 with no lagging at all on any of them. Same with using NoVNC. The difference in my case is that the VMs are running on two off-array SSD's.

     

    Is it sluggish using NoVNC? Any crossed pinned CPU's (don't even know if it allows it)? Try creating a new VM template with the same settings & drives using the GUI to rule out some kind of XML issue.

    Link to comment
    8 minutes ago, Johan1111 said:

    just did that upgrade it and changed the cable to the other lan port of my MB still the same issue. I think is something else this never happened with any other older version.

    It's happened before swapping eth0 and eth1, for example, though yours only showed eth0 hence why I didn't detect the issue with the first diags, if it's still not working with the cable on the Intel NIC we need new diags, or swap the NICs on the interface rules like mentioned above.

     

     

    Link to comment
    21 hours ago, johnnie.black said:

    It's happened before swapping eth0 and eth1, for example, though yours only showed eth0 hence why I didn't detect the issue with the first diags, if it's still not working with the cable on the Intel NIC we need new diags, or swap the NICs on the interface rules like mentioned above.

     

     

    just tried again with 6.7.3-rc4 and when i go to Interface Rules and swap eth0 and eth1 and then restart I get same issue as when I upgrade it not ip address set, change the cable to the other MB lan port same issue restart and change the cable same issue.

    Link to comment
    2 minutes ago, Johan1111 said:

    just tried again with 6.7.3-rc4 and when i go to Interface Rules and swap eth0 and eth1 and then restart I get same issue as when I upgrade it not ip address set, change the cable to the other MB lan port same issue restart and change the cable same issue.

     

    21 hours ago, johnnie.black said:

    we need new diags

     

    Link to comment
    On 11/24/2019 at 3:31 PM, Neo_x said:
    Quote

    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.

     

    Was going to reply to this earlier but forgot, I also don't really like this write method auto switch, not when write mode is set to "reconstruct write", why not use the "auto" setting for this? That would be fine, but when set to "rw" I would prefer that "rw" would always be used.

     

     

    • Like 1
    • Thanks 1
    Link to comment
    3 hours ago, johnnie.black said:

     

    Was going to reply to this earlier but forgot, I also don't really like this write method auto switch, not when write mode is set to "reconstruct write", why not use the "auto" setting for this? That would be fine, but when set to "rw" I would prefer that "rw" would always be used.

     

     

    Excellent suggestion.  I would quite like to see this way of controlling the adaptive write method behaviour implemented at some point (even if not at 6.8).

    Link to comment

    I've noticed my disks no longer spin down with this RC.  Is anyone else experiencing this?  If so I'll start a separate thread, but if no one else has seen it then it's got to be my local problem.

    Link to comment
    4 minutes ago, dalben said:

    I've noticed my disks no longer spin down with this RC.  Is anyone else experiencing this?  If so I'll start a separate thread, but if no one else has seen it then it's got to be my local problem.

    All mine are peacefully asleep at the moment 🙂 - no fuss

     

    image.png.d838e24e73eb5775c3158bd38e2a2700.png

    Link to comment
    4 minutes ago, cybrnook said:

    All mine are peacefully asleep at the moment 🙂 - no fuss

    OK, thanks.  Might have to look at what settings I played with.  Only thing I did was enable reconstruct write so I'll disable that and have a look.

    Link to comment
    6 hours ago, dalben said:

    OK, thanks.  Might have to look at what settings I played with.  Only thing I did was enable reconstruct write so I'll disable that and have a look.

    That could easily have that effect as a write to any drive will require all disks to be spinning.

    Link to comment
    30 minutes ago, itimpi said:

    That could easily have that effect as a write to any drive will require all disks to be spinning.

    OK, that does make sense.  I've been meaning to find out whats been keeping my Disk 4 from spinning down for a while.  Looks like enabling RW when Disk 4 never spins down will keep them all up.

     

    Cheers.

    Link to comment
    8 hours ago, dalben said:

    I've noticed my disks no longer spin down with this RC.  Is anyone else experiencing this?  If so I'll start a separate thread, but if no one else has seen it then it's got to be my local problem.

    Same for me. Im currently investigating it with "files open" plugin.

     

    I see e.g. drive 1 is spin up, plugin says, last access was 8am, now its after 12 spindown was set to 1hour or 30min... so

     

    disk2, last thing was 12, so thats ok.

     

    disk3 7, not ok.

     

    disk4 8, not ok.

     

    disk5 4, not ok.

     

    disk6 7, not ok.

     

    disk7 7, not ok.

     

    disk8 12, ok.

     

    Yo, if that plugin is right, there is another bug. First thing im gonna do (i remember it helped at some point) is goin to each disk and save the settings again.

    Link to comment

    I tried changing the scheduler in the disk settings page to `bfq`, but even after a reboot, when SSHing in to confirm the scheduler has not changed, I get:

     

    Quote

    root@Tower:~# cat /sys/block/sdc/queue/scheduler 
    [mq-deadline] kyber bfq none

     

    Edited by Kaveh
    Link to comment



    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.