• 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



    7 minutes ago, nuhll said:

    name changed and directory, mac adress changed also

    Weird. Not sure what happens if you setup a VM with a name that maybe already exists. Will unraid prevent you from doin this or will it mix things up? IDK. Did you restored the libvirt.img recently? It contains all the xml files.

    Link to comment

    Hi,

     

    for some reason it seems that in DockerMan i can't edit ports anymore.
    Container port field is missing.
     

    EDIT: after a reboot somehow it started working again.

    image.png

    Edited by dhstsw
    Link to comment

    Went from RC5 to RC1 and now my windows vm wont start?  I am getting this error "2019-11-04T16:51:21.930786Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region0+0xa2c5a0, 0x1baa5000f,8) failed: Cannot allocate memory"

     

    Any ideas?

    Link to comment
    26 minutes ago, sittingmongoose said:

    Went from RC5 to RC1 and now my windows vm wont start?  I am getting this error "2019-11-04T16:51:21.930786Z qemu-system-x86_64: vfio_region_write(0000:00:02.0:region0+0xa2c5a0, 0x1baa5000f,8) failed: Cannot allocate memory"

     

    Any ideas?

    Maybe due to qemu machine type.  Why downgrade to -rc1?

    Link to comment

    I am having reduced array performance on rc3/4/5 compared to rc1.  Specifically with streaming videos to Plex when mover and/or parity check are running.  Rc1 doesn’t have that problem.

     

    whats weird about the vm is after I downgraded, rebooted, the vm auto started fine.  This issue didn’t start until I stopped the vm, edited it to use a gpu and then started it again.  It throws this issue with the vmc and gpu which both worked previously.

    Link to comment
    1 minute ago, sittingmongoose said:

    I am having reduced array performance on rc3/4/5 compared to rc1.  Specifically with streaming videos to Plex when mover and/or parity check are running.  Rc1 doesn’t have that problem.

     

    whats weird about the vm is after I downgraded, rebooted, the vm auto started fine.  This issue didn’t start until I stopped the vm, edited it to use a gpu and then started it again.  It throws this issue with the vmc and gpu which both worked previously.

    I offered some suggestions in your other topic.  Sorry we can't troubleshoot an -rc downgrade issue.

     

    So look, I want to point something out: no disrespect intended but this issue is not high on the priority list at the moment.  Why? because there is a viable workaround: don't run mover or parity check while streaming video.  We will eventually get to this.

    Link to comment

    I wasn't trying to bring up the array performance issue again as its in a separate thread now.  My only thing about the performance issue is that it was fixed in RC1 then broken in later RCs.  So I was hoping you guys could isolated it more easily than normal.  Either way, Ill keep that component to the separate thread.

     

    I'll try to fix the windows vm by deleting it and re-adding it.  Maybe a reboot will fix it too.  I can update this post if anyone cares.

     

    Edit:  Didn't see your array comments until after I wrote this so just ignore that.  Im going back to RC5 and testing a few things as per your instructions.

    Edited by sittingmongoose
    Link to comment

    EDIT: This appears to be a firefox issue, rather than unraid as the terminal works on my phone. If it's still fine to leave it here, does anyone have any solutions? Can't seem to find anything to help online.

     

    Has anyone else had issues with the webterminal? I can no longer see any text displayed. Just updated from 6.7.2-rc2

     

    It appears I can still run commands, however. Screenshot attached of htop. After a second even that displayed text dissapears leaving just the colors.

     

    There is nothing out of the ordinary in the syslog.

    Screenshot_20191105_090940.png

    Edited by Dataone
    Link to comment
    38 minutes ago, Dataone said:

    EDIT: This appears to be a firefox issue, rather than unraid as the terminal works on my phone. If it's still fine to leave it here, does anyone have any solutions? Can't seem to find anything to help online.

     

    I suspect that this is more likely an issue with how you have configured Firefox.  My Firefox (ver. 70.0.1) is working fine with both top and htop.  If you google, you can find out how to reset Firefox back to its default configuration.

    Link to comment
    13 minutes ago, Frank1940 said:

    I suspect that this is more likely an issue with how you have configured Firefox.  My Firefox (ver. 70.0.1) is working fine with both top and htop.  If you google, you can find out how to reset Firefox back to its default configuration.

     

    Screenshot_20191105_095805.png.5353e58fc2669fe956d3cdcc57d25bff.png

     

    privacy.resistFingerprinting in about:config was the culprit. However, I really don't want to disable this and there's no way to add exceptions per domain.

     

    I assume that the upgrade of ttyd with the 6.8.0-rc series would be the cause? Is it possible to manually downgrade that specific package?

    Edited by Dataone
    Link to comment
    39 minutes ago, Dataone said:

    privacy.resistFingerprinting in about:config was the culprit. However, I really don't want to disable this and there's no way to add exceptions per domain.

    Is it a global setting or is it handled differently in a private window?

    Link to comment
    40 minutes ago, Dataone said:

    Is it possible to manually downgrade that specific package?

    Possible?  Yes.  Will we do it? No.  But we'll watch the development, eventually it'll probably get fixed.

    Link to comment
    16 minutes ago, Frank1940 said:

     

    Yes, I've already decided I'll use it and have been with no issues with unraid 6.7.2

    This is why I'm looking in this thread to see if anyone has a solution, as this is an issue I believed introduced with the tty package upgrade in the 6.8.0-rc series. My thinking is that I shouldn't have to disable privacy related settings to use the webterminal, as it was working fine before hand.

    7 minutes ago, limetech said:

    Possible?  Yes.  Will we do it? No.  But we'll watch the development, eventually it'll probably get fixed.

     

    That's a shame, but I understand. How would I manually downgrade it? Can't find any documentation on doing so. Thanks for responding

    Edited by Dataone
    Link to comment
    16 minutes ago, Dataone said:

     

    Yes, I've already decided I'll use it and have been with no issues with unraid 6.7.2

    This is why I'm looking in this thread to see if anyone has a solution, as this is an issue I believed introduced with the tty package upgrade in the 6.8.0-rc series. My thinking is that I shouldn't have to disable privacy related settings to use the webterminal, as it was working fine before hand.

     

    That's a shame, but I understand. How would I manually downgrade it? Can't find any documentation on doing so. Thanks for responding

    Why not just use a different browser until it's sorted?

    Link to comment
    7 minutes ago, limetech said:

    Why not just use a different browser until it's sorted?

    I've just been using ssh in the meantime, but it would be nice if I could fix it myself anyways and not have to think about it agian, at least until there's another update. (thanks for the corruption fix by the way, it's a lifesaver)

    Edited by Dataone
    Link to comment

    need to do more analysis but seems like I am having drive spindown issues with rc5 (as in not spinning down after XX minutes ) - anyone else?  Will look into it more but something doesn't seem quite right

    Edited by jjslegacy
    Link to comment
    Just now, jjslegacy said:

    need to do more analysis but seems like I am having drive spindown issues with rc5 (as in not spinning down after XX minutes ) - anyone else?  Will look into it more but something doesn't seem quite right

    Nothing here, spinning down on my end fine

    Link to comment

    I have been seeing a lot of NFS issues with my Fedora Server 30 VM on one unraid server hosting Sonarr and Radarr with missing root folders located on two other unraid servers the logs show this 

     

    NFS: (SERVER IP for NFS Mount) server error: fileid changed fsid 0:51: expected fileid 0x2800000c6b19ee, got 0x2800000c6e58b1

     

    I switched tunable to off as mentioned in the RC release notes on one server to see if this alleviates the issue as I have been seeing it pop up every few hours but only since 6.8RC1

    and before anyone asks I cant use SMB as the script a buddy created explicitly looks for the NFS mounts to map to the dockers running in fedora 

    Link to comment
    6 minutes ago, Can0nfan said:

    NFS: (SERVER IP for NFS Mount) server error: fileid changed fsid 0:51: expected fileid 0x2800000c6b19ee, got 0x2800000c6e58b1

     

    I also came across this today, however that was after modifying share setings for one I was mounted to. Tried to browse the share without re-mounting and saw that error. Hasn't appeared since.

    Edited by Dataone
    Link to comment
    8 minutes ago, Dataone said:

     

    I also came across this today, however that was after modifying share setings for one I was mounted to. Tried to browse the share without re-mounting and saw that error. Hasn't appeared since.

    mine is constantly showing in cockpit under logs. but once i stop the containers unmount and remount the NFS share then start the containers they are fine for a couple hours.  if i reboot fedora itself will correct it for maybe half a day or so

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