• 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



    15 hours ago, BoarAnt said:

    I'm using a Gigabyte MZ32-AR0, and I upgraded from the stable build (6.7.2).

     

    Thanks for the info.  Not sure what could be causing my issue then.  Even a fresh vanilla install on a new USB doesn't boot.  Maybe I'll try booting a different Linux distro using the same kernel to see if it is some issue with my board and the latest kernel.

    Edited by IamSpartacus
    Link to comment
    3 hours ago, IamSpartacus said:

     

    Thanks for the info.  Not sure what could be causing my issue then.  Even a fresh vanilla install on a new USB doesn't boot.  Maybe I'll try booting a different Linux distro using the same kernel to see if it is some issue with my board and the latest kernel.

    I'm not sure if you've done this yet, but have you added 'nomodeset' to the grub boot options yet? Most EPYC server boards have an aspeed bmc chip (mine is the ast2500) which interfered on boot. My unraid setup didn't boot until I added that in my grub configs.

    Link to comment
    17 minutes ago, BoarAnt said:

    I'm not sure if you've done this yet, but have you added 'nomodeset' to the grub boot options yet? Most EPYC server boards have an aspeed bmc chip (mine is the ast2500) which interfered on boot. My unraid setup didn't boot until I added that in my grub configs.

     

    I have not.  How exactly is that done?  Just add nomodeset in each of the Syslinux configs?

    Edited by IamSpartacus
    Link to comment
    15 minutes ago, limetech said:

    We're going to include this in 6.8-rc6 but it's not obvious all the "fixes" are there.  You can peruse the commit history:

    https://github.com/qemu/qemu/commits/stable-4.1

     

    If qcow2 corruption still exists then we will immediately revert back.  We have to get 6.8 'stable' release published asap.

    Ive sent an mail, but didnt got a reply until now.

     

    Whats about the Vm issue? Will this be corrected? In next RC? Are any new bug reports needed, or do you know whats wrong?

    Link to comment
    1 hour ago, IamSpartacus said:

     

    I have not.  How exactly is that done?  Just add nomodeset in each of the Syslinux configs?

    Correct. At the grub menu, press the Tab button to enable editing, and add nomodeset as an additional argument at the end of the linux line and press return to boot. Once unraid is up, be sure to go into the flash drive and edit those lines in your grub.cfg permanently.

    Link to comment

    I am currently running 6.7 RC5, as it is the last version that supported the patch detailed here: https://forums.unraid.net/topic/72036-nvme-m2-passthrough/. I am passingthrough a NVMW drive with the SM2262 controller that was having issues.

     

    I upgraded today to 6.8 RC.

     

    Getting this error, which is the same as other people were getting before the patch was applied and after the patch was removed:

    internal error: qemu unexpectedly closed the monitor: 2019-11-06T04:48:46.400809Z qemu-system-x86_64: -device vfio-pci,host=0000:01:00.0,id=hostdev2,bus=pci.0,addr=0x6: vfio 0000:01:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align

     

    Please help me resolve this issue. The solution should not be to buy new hardware. This was working perfectly with the patch implemented. The patch shouldn't have been removed before a solution was found. 

    Edited by zinkpro45
    Link to comment
    5 hours ago, limetech said:

    We're going to include this in 6.8-rc6 but it's not obvious all the "fixes" are there.  You can peruse the commit history:

    https://github.com/qemu/qemu/commits/stable-4.1

     

    If qcow2 corruption still exists then we will immediately revert back.  We have to get 6.8 'stable' release published asap.

    But linus is still 2 weeks out for LTS kernel 5.4 and QEMU 4.2 is 2 weeks out too

    https://wiki.qemu.org/Planning/4.2

     

    :)

    Link to comment
    6 hours ago, zinkpro45 said:

    Please help me resolve this issue. The solution should not be to buy new hardware. This was working perfectly with the patch implemented. The patch shouldn't have been removed before a solution was found. 

    This is a fairly extensive patch and not sure if it will apply against 5.3.x kernel and upcoming 5.4.x kernel.  I think the basic problem is that the silicon has a h/w defect which the patch is designed to workaround and while it seems to work with your device it doesn't work with others.  I don't know why the vm xml workaround doesn't work either.  There are 2 choices, either ask @aw_ nicely to generate a new patch for the latest kerne, or just go buy a device that works and use your current device for something else.

    Link to comment
    On 11/16/2019 at 7:21 AM, limetech said:

    This is a fairly extensive patch and not sure if it will apply against 5.3.x kernel and upcoming 5.4.x kernel.  I think the basic problem is that the silicon has a h/w defect which the patch is designed to workaround and while it seems to work with your device it doesn't work with others.  I don't know why the vm xml workaround doesn't work either.  There are 2 choices, either ask @aw_ nicely to generate a new patch for the latest kerne, or just go buy a device that works and use your current device for something else.

    How long you ignore my questions about the VM issues?


    If youre working on it fine, but just ignroing me?!?!?!?!

    Link to comment
    1 hour ago, nuhll said:

    How long you ignore my questions about the VM issues?

    It is already explained in the topic you reference to, that the current workaround is to separate VM and docker to different interfaces (or VLANs) to avoid the issue.

     

    Meanwhile we keep an eye at KVM/Qemu and Docker development to see if the issue gets resolved. This is out of control of Limetech.

     

    Oh, and you may want to try RC6

    Edited by bonienl
    • Thanks 1
    Link to comment
    On 11/17/2019 at 9:55 AM, bonienl said:

    It is already explained in the topic you reference to, that the current workaround is to separate VM and docker to different interfaces (or VLANs) to avoid the issue.

     

    Meanwhile we keep an eye at KVM/Qemu and Docker development to see if the issue gets resolved. This is out of control of Limetech.

     

    Oh, and you may want to try RC6

    I asked if it was possible to do it with a virtual nic, i cant use VLAN in my network.

    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.