Jump to content
  • 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



    Trying via VPN so I'll play around when I get home, but my VMs didn't start (coming from rc1) so I am trying to update but it's hanging on Updating...

     

    I also am seeing the previously reported "Array Stopped" message in the footer of the web gui.

     

    I'll open/post to specific reports if I can't seem to figure this out.

    Share this comment


    Link to comment
    Share on other sites

    Updated.  So far all good.

     

    The status bar showing  Array Stopped•Starting services... despite the array having started is still there though, but thats just cosmetic

    Share this comment


    Link to comment
    Share on other sites
    2 minutes ago, dalben said:

    Updated.  So far all good.

     

    The status bar showing  Array Stopped•Starting services... despite the array having started is still there though, but thats just cosmetic

    Right, I never see that happen so have to investigate further.

    Share this comment


    Link to comment
    Share on other sites
    24 minutes ago, dalben said:

    despite the array having started is still there though, but thats just cosmetic

    I'm curious.  Do you have any scripts via User Scripts set to start at Array Start?  I only see the message not go away on my first start, never on a subsequent stop / start.  And I have a script set to run at 1st array start only.  Just haven't had time to investigate further.

    Share this comment


    Link to comment
    Share on other sites
    9 minutes ago, Squid said:

    I'm curious.  Do you have any scripts via User Scripts set to start at Array Start?  I only see the message not go away on my first start, never on a subsequent stop / start.  And I have a script set to run at 1st array start only.  Just haven't had time to investigate further.

    I don't have any scripts that run at array start and I found the exact condition that you did.  Stopping and restarting array fixed the issue.

    Share this comment


    Link to comment
    Share on other sites

    I am running a VM as a Q35-4.1 machine in RC4. Do I need to do anything to the VM prior to moving to RC5?

     

    What was the reason to reverting to qemu 4.01?

     

    Thank you!

    Share this comment


    Link to comment
    Share on other sites
    1 minute ago, Michael Woodson said:

    I am running a VM as a Q35-4.1 machine in RC4. Do I need to do anything to the VM prior to moving to RC5?

     

    What was the reason to reverting to qemu 4.01?

     

    Thank you!

    You'll have to switch it to machine type q35-4.01

    Share this comment


    Link to comment
    Share on other sites
    56 minutes ago, limetech said:

    Right, I never see that happen so have to investigate further.

    I see it as well.  I never updated to rc4 but that is where it was first reported.  I just went from rc3 (in which the Array Stopped ..Starting Services message was not stuck on screen and Array Started appeared as it should) to rc5 in which I see the stuck message.

     

    For whatever it is worth, my server has been running on rc5 for 1 hour 20 minutes and two minutes ago, the Array Started message appeared at the bottom of the screen

     

    To @Squid's point, I have no users scripts set to run at array start.

    Share this comment


    Link to comment
    Share on other sites

    I also experienced the 'Array Stopped...Starting Services' message in RC4.  If I disabled or enabled either Dockers or VMs in settings then the status would immediately go to 'Array Started' as soon as I selected either option.  Since re-creating the docker and libvirt image files, I no longer see this issue.  Even when I had the issue with the Array Stopped message, all of my dockers, vms and array operated as normal.  

    Share this comment


    Link to comment
    Share on other sites
    41 minutes ago, Squid said:

    I'm curious.  Do you have any scripts via User Scripts set to start at Array Start?  I only see the message not go away on my first start, never on a subsequent stop / start.  And I have a script set to run at 1st array start only.  Just haven't had time to investigate further.

    Yes. I have a script running at array start via User Scripts that I needed to install when the flash drive got locked down. 

     

    When I'm home I can try disabling that

    Share this comment


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

    Updated.  So far all good.

     

    The status bar showing  Array Stopped•Starting services... despite the array having started is still there though, but thats just cosmetic

    I also had this issue.

     

    Also my unifi docker lost its network setting (none) and failed to start. I had to change it back to Custom:br0 and applied its static IP. I upgraded from rc1 to rc5.

     

    Errors:

    Nov 1 19:02:23 Frank-Server rc.docker: unifi-controller: Error response from daemon: user specified IP address is supported on user defined networks only
    Nov 1 19:02:23 Frank-Server rc.docker: Error: failed to start containers: unifi-controller.

    Share this comment


    Link to comment
    Share on other sites
    34 minutes ago, isaac.olsen94 said:

    Why did you remove the fix for Vega/nvidia cards?

    Because the "fix" worked for one group of users, but caused complete host crash for others.  If someone develops a reliable patch we will certainly incorporate it.

    • Like 2

    Share this comment


    Link to comment
    Share on other sites
    25 minutes ago, limetech said:

    Because the "fix" worked for one group of users, but caused complete host crash for others.  If someone develops a reliable patch we will certainly incorporate it.

    https://lists.freedesktop.org/archives/dri-devel/2019-October/239455.html

     

    We will have to see if any of this is backported to 5.4 LTS kernel once it hits 5.5.

     

    Usually the GPU vendors don't do those sorts of things, but not saying Limetech can't for its kernel ;)

    Share this comment


    Link to comment
    Share on other sites

    hi can someone please help me, i have a lot of folders on my /mnt/user0 , where should i move this folders to be safe for the future, thanks

    Share this comment


    Link to comment
    Share on other sites

    I have been backing up shares with /mnt/user0 for years, so that it wont have any file like *.partial~ or incomplete download. Now that it is deprecated, is there any alternative we can use?

    Share this comment


    Link to comment
    Share on other sites
    32 minutes ago, mata7 said:

    hi can someone please help me, i have a lot of folders on my /mnt/user0 , where should i move this folders to be safe for the future, thanks

    Not quite sure what you mean by this?    The /mnt/user0 location is just a view that is a sub-set of /mnt/user that omits any files/folders that are on the cache.   As such you have no files in that location that need moving.

    • Thanks 1

    Share this comment


    Link to comment
    Share on other sites

    So trying out the RC branch for the first time.  Went to setup wiregaurd with the Dynamix plugin.  Ran into a show stopper up front.  I use a DDNS with a .network FQDN.  When I entered my .network domain in the local endpoint input box it generates an error that my .network domain is not a true FQDN.  I assume someone just hard coded the vanilla .com / .net / .org in the error checking for that field.  Can we get that fixed?

    Share this comment


    Link to comment
    Share on other sites
    Quote

    Not quite sure what you mean by this?    The /mnt/user0 location is just a view that is a sub-set of /mnt/user that omits any files/folders that are on the cache.   As such you have no files in that location that need moving.

    oh ok, i dint know that, so those folders that are inside the user0 they are no really there thas what you mean? sorry english is no my first language  

    Share this comment


    Link to comment
    Share on other sites

    What's with removal of user0? Where am I supposed to point my deluge and nzb? 

    Share this comment


    Link to comment
    Share on other sites

    Looks like a lot of great additions n the RC.  As soon as I can reboot I'll apply it!

     

    Thanks,

    craigr

    Share this comment


    Link to comment
    Share on other sites
    9 hours ago, kaiguy said:

    Trying via VPN so I'll play around when I get home, but my VMs didn't start (coming from rc1) so I am trying to update but it's hanging on Updating...

     

    I also am seeing the previously reported "Array Stopped" message in the footer of the web gui.

     

    I'll open/post to specific reports if I can't seem to figure this out.

    I have this problem as well coming from RC3.

     

    craigr

    Share this comment


    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.