• Unraid OS version 6.8.0-rc5 available


    limetech

    tldr:

    Updated kernel.

    Fixed sqlite db corruption issue.

    Removed "vega 10 reset" patch.

    Removed "navi reset" patch.

    Reverted qemu.

    Fixed shfs bug.

    Fixed handling of quotes in passwords.

    Misc. webGUI fixes.

    Other package updates.

    Announce /mnt/user0 is deprecated and will be removed in 6.9 release.

     

    Note: if your VM's won't start you need to click on Edit in the VM context page and then just click Update.  This is because of reverting qemu.

     

    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
    • 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.
    • 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-rc5 2019-11-01

    Base distro:

    • btrfs-progs: version 5.3.1
    • kernel-firmware: version 20191025_340e06e
    • libedit: version 20191025_3.1
    • librsvg: version 2.46.3
    • mozilla-firefox: version 70.0 (CVE-2018-6156, CVE-2019-15903, CVE-2019-11757, CVE-2019-11759, CVE-2019-11760, CVE-2019-11761, CVE-2019-11762, CVE-2019-11763, CVE-2019-11765, CVE-2019-17000, CVE-2019-17001, CVE-2019-17002, CVE-2019-11764)
    • php: version 7.3.11 (CVE-2019-11043)
    • qemu: version 4.0.1 [revert from 4.1.0]
    • samba: version 4.11.2 (CVE-2019-10218, CVE-2019-14833, CVE-2019-14847)
    • xkeyboard-config: version 2.28

    Linux kernel:

    • version 5.3.8
    • patch: fix_vega_reset [removed]
    • patch: navi_reset [removed]
    • oot: md/unraid: version 2.9.12 (do not fail read-ahead)

    Management:

    • emhttp: fix improper handling of embedded quote characters in a password
    • shfs: fix bug not accounting for device(s) not mounted yet
    • webgui: Fixed: undo cleanup of disk.png
    • webgui: Fixed typo in help text
    • webgui: Unraid fonts and cases update
    • webgui: Dashboard: fixed user write + read counts
    • webgui: Dashboard: WG tunnel handshake in days when longer than 24 hours

    Edited by limetech

    • Thanks 7



    User Feedback

    Recommended Comments



    2 minutes ago, paramehdic said:

    Array wont start, reverted to RC4 and working fine again.

    wierd...i have three server all running and array starting fine on rc5 you should update and run diagnostics and post them here

    Link to comment

    I know that nothing can be promised and I do not expect that. However, is it possible to predict based on the earlier releases when the first stable 3.8 will see daylight? That is, I am craving for updating to 3.8 (Intel 9th gen iGPU support and Wireguard support) but also need to minimize any risk of issues to the array as it is somewhat mission critical that I am running there.

     

    Any info appreciated!

     

    Link to comment

    For anyone interested about the array performance issues compared to RC1.  Setting the disk tuning scheduler from "mq-deadline" to "none" along with using the mover tuning plugin to set disk IO priority to "low" fixed my problems.  Now it performs like RC1 did. 

    Link to comment
    27 minutes ago, Ruato said:

    I know that nothing can be promised and I do not expect that. However, is it possible to predict based on the earlier releases when the first stable 3.8 will see daylight? That is, I am craving for updating to 3.8 (Intel 9th gen iGPU support and Wireguard support) but also need to minimize any risk of issues to the array as it is somewhat mission critical that I am running there.

     

    Any info appreciated!

     

    you mean 6.8?
    its pretty stable you should try it, you can always roll back if you have issues

    Link to comment
    3 hours ago, Can0nfan said:

    you mean 6.8?
    its pretty stable you should try it, you can always roll back if you have issues

    Yes, 6.8. I do not know what I was thinking when writing. OK, maybe I'll take a shot. Thank you for the reply!

    I was just wondering whether it will probably be days, weeks or months..

    Link to comment
    15 minutes ago, Ruato said:


    I was just wondering whether it will probably be days, weeks or months..

    Yes, probably days, weeks or months. All depends on how many more issues require a fix and how many more RC’s that takes. LT isn’t likely to commit to a schedule (totally understandable).
     

    The only other answer you might get is “soon”.

    Link to comment
    1 hour ago, wgstarks said:

    Yes, probably days, weeks or months. All depends on how many more issues require a fix and how many more RC’s that takes. LT isn’t likely to commit to a schedule (totally understandable).
     

    The only other answer you might get is “soon”.

    Yes, understood. As I wrote in the original post, I do not expect any guarantees. I was looking for "an educated guess" based on the earlier releases but I understand that each release has its individual properties/issues.

    Link to comment
    6 hours ago, paramehdic said:

    Array wont start, reverted to RC4 and working fine again.

    If you can't provide diagnostics please don't bother to post.

    • Thanks 1
    Link to comment
    6 hours ago, sittingmongoose said:

    For anyone interested about the array performance issues compared to RC1.  Setting the disk tuning scheduler from "mq-deadline" to "none" along with using the mover tuning plugin to set disk IO priority to "low" fixed my problems.  Now it performs like RC1 did. 

    Tested it, but it didn't work for me. I guess I'm going to disable the cache for now.

    Link to comment
    17 minutes ago, Racer said:

    Tested it, but it didn't work for me. I guess I'm going to disable the cache for now.

    You said you didnt try RC1 right?  How are you testing it?  Whats slow?

    Link to comment

    I did try your suggestion: disk scheduler set to none and disk IO priority set to low on 6.8 rc5.

    Array performance is not better with these settings.

    Link to comment
    Just now, Racer said:

    I did try your suggestion: disk scheduler set to none and disk IO priority set to low on 6.8 rc5.

    Array performance is not better with these settings.

    How are you testing array performance?

     

    Did you ever try RC1?

    • Thanks 1
    Link to comment
    19 hours ago, soana said:

    Running rc5 and for the second time after an array stop/start the system starts a parity check.

     

    tower-diagnostics-20191104-2353.zip 171.71 kB · 10 downloads

     

    Nov  3 10:21:43 Tower emhttpd: unclean shutdown detected
    

    The array stopped/started status is stored on flash. If for some reason flash can't be written when shutting down, or if power is removed before stopping the array, then you get an unclean shutdown which results in a parity check.

     

    Put flash in PC and let it checkdisk.

    Link to comment
    7 minutes ago, sittingmongoose said:

    How are you testing array performance?

     

    Did you ever try RC1?

    No, I didn't test it. What's the best way to do that? Maybe with reinstalling the last official version and move on from that?

     

    I start a videostream and open up my shares. After that I start mover.

    About 10-15 seconds after starting the mover my stream stops completely. Shares get unresponsive immediately.

    That's my test for the array. 

    Link to comment
    31 minutes ago, Racer said:

    No, I didn't test it. What's the best way to do that? Maybe with reinstalling the last official version and move on from that?

     

    I start a videostream and open up my shares. After that I start mover.

    About 10-15 seconds after starting the mover my stream stops completely. Shares get unresponsive immediately.

    That's my test for the array. 

    An easy way to install other versions is to install the Nvidia plugin, go into it, then select stock unraid builds on the right.  6.8.0 rc1 is in there.

    Link to comment
    3 minutes ago, sittingmongoose said:

    An easy way to install other versions is to install the Nvidia plugin, go into it, then select stock unraid builds on the right.  6.8.0 rc1 is in there.

    https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.8.0-rc1-x86_64.zip

     

    Just copy all the bz* images from this to the flash. I believe that's all that's needed for downgrading 6.8.0 . Worked that way for me downgrading 6.7.2

    Edited by Dataone
    Link to comment
    2 hours ago, Racer said:

    I did try your suggestion: disk scheduler set to none and disk IO priority set to low on 6.8 rc5.

    Array performance is not better with these settings.

    Just FYI, if you are having problems, then you should set the mover tuning plugin's parameters back to "normal"  Otherwise, it introduces another variable for @limetech to calculate, and he may/may not be aware of the plugin, so the disk IO priority option he may not have a clue about what you're talking about.

    • Like 1
    • Thanks 1
    Link to comment

    Thanks for your help. I'm on rc1 now. Streaming from another drive and running mover works.

    Before I streamed from one drive and also did write on that same drive with the mover because of my data layout.

    I have to test the same with sittingmongoose's settings on rc5 and I will report back.

     

     

    @Squid I'm running it at Normal at the moment on rc1.

    Edited by Racer
    Link to comment

    I see a problem with both of my Servers on RC5 to connect or ping to another device. Until RC4 everything worked perfect.

    Now on RC5 my smb Mountpoint is not connecting. A connection in Krusader and MidnightCommander to the other device is not possible. 

    Then I tried to ping the device and I tried to ping the unraid server from that device. Ping is not answering in both directions.

     

    The strange thing is, that the connection to that device an both unraid servers (including ping) works perfectly from my Macbook.

    I downgraded one of those servers, but it didn't work ether?!?
     

    Maybe just a coincidence or failure in the network? When not and I can help you out with diagnostics... I attached the diagnostics of both of them.

     

    The uni7 is the one I downgraded to RC4.

     

    kind regards

    Nils

     

     

     

    uni7-diagnostics-20191106-0700.zip unquad-diagnostics-20191106-0701.zip

    Link to comment

    I'm curious why /mnt/user0 is being removed?

     

    I use it directly a lot when organizing things. Will it be possible to add it back with a plugin?

    • Like 1
    Link to comment
    1 hour ago, rpj2 said:

    I'm curious why /mnt/user0 is being removed?

     

    I use it directly a lot when organizing things. Will it be possible to add it back with a plugin?

    I'm wondering the same thing. I'm using /mnt/user0 and /mnt/cache to ad hoc moving of data between cache and user shares without messing with share use cache configuration.

    Maybe it can be preserved for experienced user via system tunable?

    • Like 2
    Link to comment
    On 11/5/2019 at 2:02 PM, trurl said:

     

    
    Nov  3 10:21:43 Tower emhttpd: unclean shutdown detected
    

    The array stopped/started status is stored on flash. If for some reason flash can't be written when shutting down, or if power is removed before stopping the array, then you get an unclean shutdown which results in a parity check.

     

    Put flash in PC and let it checkdisk.

    Hmm, I did not perform a checkdisk yet but I did a array stop/start and then a reboot followed by another stop/start array and no more parity checks started. Will run a checkdisk next and keep an eye on it.

    Link to comment

    For the past two days now, my server has lost network connectivity at approximately 6pm.  A reboot has brought it back online both times.

     

    What appears to be the relevant part of the log is below.  Any idea what is causing this? 

     

    I plan on rolling back to rc3 to see if that stops this from occurring

     

    Quote

    Nov  7 17:54:52 UnRAID avahi-daemon[7727]: Withdrawing address record for 10.0.1.10 on eth0.
    Nov  7 17:54:52 UnRAID avahi-daemon[7727]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.1.10.
    Nov  7 17:54:52 UnRAID avahi-daemon[7727]: Interface eth0.IPv4 no longer relevant for mDNS.
    Nov  7 17:54:54 UnRAID ntpd[2542]: Deleting interface #6 eth0, 10.0.1.10#123, interface stats: received=69, sent=69, dropped=0, active_time=65526 secs
    Nov  7 17:54:54 UnRAID ntpd[2542]: 45.76.244.193 local addr 10.0.1.10 -> <null>
    Nov  7 18:03:03 UnRAID kernel: mdcmd (76): spindown 6
    Nov  7 18:03:04 UnRAID kernel: mdcmd (77): spindown 8
    Nov  7 18:03:04 UnRAID kernel: mdcmd (78): spindown 9
    Nov  7 18:03:05 UnRAID kernel: mdcmd (79): spindown 10
    Nov  7 18:03:05 UnRAID kernel: mdcmd (80): spindown 12
    Nov  7 18:03:20 UnRAID kernel: mdcmd (81): spindown 1
    Nov  7 18:08:01 UnRAID kernel: mdcmd (82): set md_write_method 0
    Nov  7 18:08:01 UnRAID kernel: 
    Nov  7 18:20:29 UnRAID kernel: mdcmd (83): spindown 4
    Nov  7 18:20:29 UnRAID kernel: mdcmd (84): spindown 5
    Nov  7 18:24:57 UnRAID wsdd[659]: udp_send: Failed to send udp packet with Network is unreachable
    Nov  7 18:24:57 UnRAID wsdd[659]: udp_send: Failed to send udp packet with Network is unreachable
    Nov  7 18:24:57 UnRAID wsdd[659]: udp_send: Failed to send udp packet with Network is unreachable
    Nov  7 18:24:58 UnRAID wsdd[659]: udp_send: Failed to send udp packet with Network is unreachable

     

    Edited by Peanutman85
    Link to comment

    Before you roll back or reboot, post your diagnostics.  From the command prompt, you can get them via

    diagnostics

     

    Edited by Squid
    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.