• 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, bastl said:

    So you only experiencing this with i440fx VMs? Maybe I have some time tomorrow to test i440 on 6.8 RC. I'am running all my VMs on Q35 for quiet some time now without any problems.

    Q35-4.0.1 + OVMF + Emulated CPU. I just started tinkering with i440fx VMs, haven't yet met some test scenarios yet to even try an OC.

    Link to comment

    @jbartlett Maybe you have set some cores which are not directly attached to the memory? Did you manualy changed the topology for the VM?

    <topology sockets='1' cores='8' threads='2'/>

    I always do this for all my VMs to match the actual core/thread count. Default is always all selected cores and 1 thread.

    Link to comment
    Just now, bastl said:

    @jbartlett Maybe you have set some cores which are not directly attached to the memory? Did you manualy changed the topology for the VM?

    
    <topology sockets='1' cores='8' threads='2'/>

    I always do this for all my VMs to match the actual core/thread count. Default is always all selected cores and 1 thread.

    I had the VM pinned directly to the two numa nodes that had the memory attached (all CPUs).

     

    Hrm, the emulatorpin'ed CPU was on one of the other numa nodes but it didn't pose any other issues if that is the root cause. The infinity fabric on the Threadripper 2 chips seems to be so fast that I couldn't find any degregation even pinning a VM off node forcing everything to go through the infinity fabric.

    Link to comment

    Meh, I've got something going on here. Tried OC'ing with SeaBios and got the same laggy thing. I'm going to wipe my hands of this and stick to stock speeds.

    Link to comment
    9 hours ago, bastl said:

    @jbartlett Which "CPU Scaling Governor" are u using?

    I don't really even know what that is other than I've seen it posted in the forums a few times. Did some searching, installed the Tips & Tweaks plugin. Governor was set to "On Demand". I set it to Performance, rebooted & restarted the VM to make sure it still loaded as intended, then OC'ed the CPU to 6% using it's wizard. It took a couple minutes before I saw the BIOS load and I could see the text outputting character by character, probably a quarter second per line. It reminds me of the old 2400 baud modem days.

     

    Did some tinkering around, creating a blank VM with no drives attached, 2 CPUs, and 2GB of RAM. It was all slow until I removed the Quadro P2000, the VNC client showed it booted real fast.

     

    I actually DO want to squeeze as much juice out of this as I can. I'm actually a little stoked because I found a combination that allowed my multiple Brio 4K cams to work without flickering. My goal with this build is to have a 32 cpu running Livestream Studio for my 24x7 Foster Kitten Cam on the two main numa nodes and smaller Ubuntu VM's running OBS on the off-nodes feeding other streams to YouTube (multi-cam viewing ya'll!).

     

    I'm going to dig up the MB manual and dig into the BIOS to see if I can see anything causing the slowdown on OC with video passthrough.

    Link to comment

    @jbartlett Just an idea: Switch the slot for your card. Maybe the one you are using is wired via the chipset to the cpu and limits the card. Other devices like usb or network cards often share the same x4 connection to the CPU. Maybe thats your bottleneck

    Link to comment
    7 hours ago, jbartlett said:

    I'll take this off-thread for any further notes and share it on my thread for this MB.

    Just to throw it out there.. I upgraded to RC5 and my VM wouldn't make it to the desktop. QC35 2990wx. Just saw your thread so didn't try turning off PDO but downgraded to RC4 and it worked properly again. I had downgraded the version to 4.0 in the XML but it would just crap out when it was starting. 

    Edited by Jerky_san
    Link to comment
    7 minutes ago, Peanutman85 said:

    I experienced the issue again.  Diagnostics are attached.

    unraid-diagnostics-20191111-2141.zip 237.57 kB · 0 downloads

     

    Your network issue is the least of your concerns. You have some sort of hardware issues with your drives or controllers, as evident by just a minor snippet from your syslog with different devices.

     

     

    Nov 10 01:55:09 UnRAID kernel: scsi target10:0:0: handle(0x0009), sas_address(0x4433221102000000), phy(2)
    Nov 10 01:55:09 UnRAID kernel: scsi target10:0:0: enclosure logical id(0x500605b00606fa40), slot(1) 
    Nov 10 01:55:09 UnRAID kernel: sd 10:0:0:0: task abort: SUCCESS scmd(0000000087ecd861)
    Nov 10 01:55:09 UnRAID kernel: sd 10:0:0:0: Power-on or device reset occurred
    Nov 10 01:55:09 UnRAID kernel: repair_io_failure: 80 callbacks suppressed
    Nov 10 01:55:09 UnRAID kernel: BTRFS info (device sdb1): read error corrected: ino 72659949 off 2019721216 (dev /dev/sdk1 sector 675100992)
    Nov 10 01:55:09 UnRAID kernel: BTRFS info (device sdb1): read error corrected: ino 72659949 off 2019688448 (dev /dev/sdk1 sector 675100928)
    Nov 10 01:55:09 UnRAID kernel: BTRFS info (device sdb1): read error corrected: ino 72659949 off 2019692544 (dev /dev/sdk1 sector 675100936)
    Nov 10 01:55:09 UnRAID kernel: BTRFS info (device sdb1): read error corrected: ino 72659949 off 2019696640 (dev /dev/sdk1 sector 675100944)
    Nov 10 01:55:09 UnRAID kernel: BTRFS info (device sdb1): read error corrected: ino 72659949 off 2019700736 (dev /dev/sdk1 sector 675100952)
    Nov 10 01:55:09 UnRAID kernel: BTRFS info (device sdb1): read error corrected: ino 72659949 off 2019708928 (dev /dev/sdk1 sector 675100968)
    Nov 10 01:55:09 UnRAID kernel: BTRFS info (device sdb1): read error corrected: ino 72659949 off 2019713024 (dev /dev/sdk1 sector 675100976)
    Nov 10 01:55:09 UnRAID kernel: BTRFS info (device sdb1): read error corrected: ino 72659949 off 2019704832 (dev /dev/sdk1 sector 675100960)
    Nov 10 01:55:09 UnRAID kernel: BTRFS info (device sdb1): read error corrected: ino 72659949 off 2017345536 (dev /dev/sdk1 sector 675096352)
    Nov 10 01:55:09 UnRAID kernel: BTRFS info (device sdb1): read error corrected: ino 72659949 off 2019717120 (dev /dev/sdk1 sector 675100984)

     

     

    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: attempting task abort! scmd(00000000a094335d)
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: [sdk] tag#3132 CDB: opcode=0x2a 2a 00 08 ae 28 40 00 04 80 00
    Nov 10 07:08:05 UnRAID kernel: scsi target10:0:0: handle(0x0009), sas_address(0x4433221102000000), phy(2)
    Nov 10 07:08:05 UnRAID kernel: scsi target10:0:0: enclosure logical id(0x500605b00606fa40), slot(1) 
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: task abort: SUCCESS scmd(00000000a094335d)
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: attempting task abort! scmd(00000000022195f4)
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: [sdk] tag#3131 CDB: opcode=0x2a 2a 00 08 ae 22 40 00 06 00 00
    Nov 10 07:08:05 UnRAID kernel: scsi target10:0:0: handle(0x0009), sas_address(0x4433221102000000), phy(2)
    Nov 10 07:08:05 UnRAID kernel: scsi target10:0:0: enclosure logical id(0x500605b00606fa40), slot(1) 
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: task abort: SUCCESS scmd(00000000022195f4)
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: attempting task abort! scmd(000000005160c730)
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: [sdk] tag#3130 CDB: opcode=0x2a 2a 00 08 ae 1e 40 00 04 00 00
    Nov 10 07:08:05 UnRAID kernel: scsi target10:0:0: handle(0x0009), sas_address(0x4433221102000000), phy(2)
    Nov 10 07:08:05 UnRAID kernel: scsi target10:0:0: enclosure logical id(0x500605b00606fa40), slot(1) 
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: task abort: SUCCESS scmd(000000005160c730)
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: attempting task abort! scmd(000000007b9169b7)
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: [sdk] tag#3129 CDB: opcode=0x2a 2a 00 08 ae 1a 40 00 04 00 00
    Nov 10 07:08:05 UnRAID kernel: scsi target10:0:0: handle(0x0009), sas_address(0x4433221102000000), phy(2)
    Nov 10 07:08:05 UnRAID kernel: scsi target10:0:0: enclosure logical id(0x500605b00606fa40), slot(1) 
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: task abort: SUCCESS scmd(000000007b9169b7)
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: attempting task abort! scmd(00000000a0c0c721)
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: [sdk] tag#3128 CDB: opcode=0x2a 2a 00 08 ae 16 40 00 04 00 00
    Nov 10 07:08:05 UnRAID kernel: scsi target10:0:0: handle(0x0009), sas_address(0x4433221102000000), phy(2)
    Nov 10 07:08:05 UnRAID kernel: scsi target10:0:0: enclosure logical id(0x500605b00606fa40), slot(1) 
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: task abort: SUCCESS scmd(00000000a0c0c721)
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: attempting task abort! scmd(0000000030675ffb)
    Nov 10 07:08:05 UnRAID kernel: sd 10:0:0:0: [sdk] tag#3127 CDB: opcode=0x2a 2a 00 08 ae 12 40 00 04 00 00
    Nov 10 07:08:05 UnRAID kernel: scsi target10:0:0: handle(0x0009), sas_address(0x4433221102000000), phy(2)

    Link to comment

    @limetech - I've been experiencing network drops on my 10G network card and from my investigation, it's due to a memory leak in the driver which was patched in the 1.6.13 version. It looks like unraid is loading 1.5.44.

     

    Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1499321 - The meat of the discussion is just a little past half way. Affects onboard NICs & PCIe cards.

     

    Nov 12 01:42:57 VM1 kernel: atlantic: link change old 10000 new 0
    Nov 12 01:42:57 VM1 kernel: br0: port 1(eth0) entered disabled state
    Nov 12 01:43:11 VM1 kernel: atlantic: link change old 0 new 10000
    Nov 12 01:43:11 VM1 kernel: br0: port 1(eth0) entered blocking state
    Nov 12 01:43:11 VM1 kernel: br0: port 1(eth0) entered forwarding state

     

    root@VM1:~# ethtool -i eth0
    driver: atlantic
    version: 5.3.8-Unraid-kern
    firmware-version: 1.5.44
    expansion-rom-version:
    bus-info: 0000:0a:00.0
    supports-statistics: yes
    supports-test: no
    supports-eeprom-access: no
    supports-register-dump: yes
    supports-priv-flags: no
    

     

     

    vm1-diagnostics-20191112-1903.zip

    Edited by jbartlett
    • Thanks 1
    Link to comment

    So I'm about to build a new server.

     

    And main use will be Plex, so with the SQL issues would it be worth running the beta instead of 6.7?

    Link to comment
    43 minutes ago, SavellM said:

    So I'm about to build a new server.

     

    And main use will be Plex, so with the SQL issues would it be worth running the beta instead of 6.7?

    last 3 years including 6.8 have all been stable for me with plex running on my cache drives, on two servers

    Link to comment
    7 hours ago, SavellM said:

    with the SQL issues would it be worth running the beta instead of 6.7?

    You can avoid the issues on any release if you have SSD cache drive(s).  Storing the appdata share on an SSD cache drive seems to have prevented the SQLite problems even with the 6.7.x releases.  I have run Plex and other apps with SQLite databases for years across all releases and have never had a corrupt SQLite database.

     

    If your appdata share is on spinning disk(s) on the array, you'll want to use either the 6.6.7 or 6.8.0-rc releases.  Avoid 6.7.x in this case

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

    You can avoid the issues on any release if you have SSD cache drive(s).  Storing the appdata share on an SSD cache drive seems to have prevented the SQLite problems even with the 6.7.x releases.  I have run Plex and other apps with SQLite databases for years across all releases and have never had a corrupt SQLite database.

     

    If your addsata share is on spinning disk(s) on the array, you'll want to use either the 6.6.7 or 6.8.0-rc releases.  Avoid 6.7.x in this case

    That makes sense and why I never had any corruption myself previously as my cache and appdata was on SSD's :)

    I thought it was affecting everyone

    Edited by SavellM
    Link to comment
    On 11/12/2019 at 9:24 AM, IamSpartacus said:

    If anyone successfully updates to RC5 using an EPYC 7002 series CPU please let me know.  I'm in a holding pattern.

    I'm using an EPYC 7452 on RC5 without issues.

    Link to comment
    On 11/13/2019 at 6:55 AM, SavellM said:

    So I'm about to build a new server.

     

    And main use will be Plex, so with the SQL issues would it be worth running the beta instead of 6.7?

    6.8.0-rc4 and rc5 have been stable, and the sqlite issues appear to have been fixed.  I'm running rc5 and it has been solid for several weeks.  I am NOT running on a cache drive. 

    Link to comment
    5 hours ago, BoarAnt said:

    I'm using an EPYC 7452 on RC5 without issues.

     

    With what motherboard?  And what version did you upgrade from?

    Edited by IamSpartacus
    Link to comment

    Can someone test FreeBSD 11.3+ on unRAID 6.8.0 RC5? 

     

    FreeBSD versions 11.3, 12, 12.1 on unRAID 6.7.2 are unable to detect network interface. Hoping the latest unRAID RC version will resolve the issue.

     

     

    Link to comment
    8 hours ago, IamSpartacus said:

     

    With what motherboard?  And what version did you upgrade from?

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

    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.