• Unraid OS version 6.7.0-rc6 available


    limetech

    Lots of base package updates, other fixes.  Hopefully one of the last -rc's before stable release.

     

    Version 6.7.0-rc6 2019-03-25

    Base distro:

    • adwaita-icon-theme: version 3.32.0
    • at-spi2-atk: version 2.32.0
    • at-spi2-core: version 2.32.0
    • atk: version 2.32.0
    • bash: version 5.0.003
    • ca-certificates: version 20190308
    • coreutils: version 8.31
    • curl: version 7.64.0 (CVE-2019-8907, CVE-2019-3822, CVE-2019-3823)
    • dhcpcd: version 7.1.1
    • dnsmasq: version 2.80
    • docker: version 18.09.3
    • e2fsprogs: version 1.45.0
    • ethtool: version 5.0
    • file: version 5.36 (CVE-2019-8906, CVE-2019-8907)
    • freetype: version 2.10.0
    • git: version 2.21.0
    • glib2: version 2.60.0
    • glibc: version 2.29
    • glibc-solibs: version 2.29
    • glibc-zoneinfo: version 2018i-noarch-1
    • gnutls: version 3.6.6
    • gtk+3: version 3.24.7
    • infozip: version 6.0 (CVE-2014-8139, CVE-2014-8140, CVE-2014-8141, CVE-2016-9844, CVE-2018-18384, CVE-2018-1000035)
    • iproute2: version 4.20.0
    • iputils: version 20180629
    • jemalloc: version 4.5.0
    • jq: version 1.6 (rev2)
    • kernel-firmware: version 20190314_7bc2464
    • kmod: version 26
    • libaio: version 0.3.112
    • libcap-ng: version 0.7.9
    • libgpg-error: version 1.36
    • libjpeg-turbo: version 2.0.2
    • libpsl: version 0.20.2
    • libssh2: version 1.8.1 (CVE-2019-3855, CVE-2019-3856, CVE-2019-3857, CVE-2019-3858, CVE-2019-3859, CVE-2019-3860, CVE-2019-3861, CVE-2019-3862, CVE-2019-3863)
    • libvirt: version 5.1.0
    • libwebp: version 1.0.2
    • libwebsockets: version 3.1.0
    • libxkbfile: version 1.1.0
    • libxml2: version 2.9.9
    • libxslt: version 1.1.33
    • libzip: version 1.5.2
    • libXcomposite: version 0.4.5
    • libXcursor: version 1.2.0
    • libXdamage: version 1.1.5
    • libXdmcp: version 1.1.3
    • libXext: version 1.3.4
    • libXft: version 2.3.3
    • libXmu: version 1.1.3
    • libXrandr: version 1.5.2
    • libXxf86dga: version 1.1.5
    • lvm2: version 2.02.177
    • lzip: version 1.21
    • mcelog: version 162
    • mozilla-firefox: version 66.0 (CVE-2018-18500, CVE-2018-18504, CVE-2018-18505, CVE-2018-18503, CVE-2018-18506, CVE-2018-18502, CVE-2018-18501, CVE-2018-18356, CVE-2019-5785, CVE-2018-18511, CVE-2019-9790, CVE-2019-9791, CVE-2019-9792, CVE-2019-9793, CVE-2019-9794, CVE-2019-9795, CVE-2019-9796, CVE-2019-9797, CVE-2019-9798, CVE-2019-9799, CVE-2019-9801, CVE-2019-9802, CVE-2019-9803, CVE-2019-9804, CVE-2019-9805, CVE-2019-9806, CVE-2019-9807, CVE-2019-9809, CVE-2019-9808, CVE-2019-9789, CVE-2019-9788)
    • mpfr: version 4.0.2
    • ncompress: version 4.2.4.5
    • ncurses: version 6.1_20190223
    • nghttp2: version 1.37.0
    • ntp: version 4.2.8p13 (CVE-2019-8936)
    • oniguruma: version 6.9.1 (CVE-2017-9224, CVE-2017-9225, CVE-2017-9226, CVE-2017-9227, CVE-2017-9228, CVE-2017-9229)
    • openssl: version 1.1.1b (CVE-2019-1559)
    • openssl-solibs: version 1.1.1b (CVE-2019-1559)
    • p11-kit: version 0.23.15
    • pcre: version 8.43
    • php: version 7.2.15
    • pixman: version 0.38.0
    • rsyslog: version 8.1903.0
    • sqlite: version 3.27.2
    • sudo: version 1.8.27
    • sysvinit: version 2.94
    • sysvinit-scripts: version 2.1-noarch-26
    • talloc: version 2.1.16
    • tar: version 1.32
    • tdb: version 1.3.18
    • tevent: version 0.9.39
    • ttyd: version 20190223
    • util-linux: version 2.33.1
    • wget: version 1.20.1
    • xprop: version 1.2.4
    • xtrans: version 1.4.0

    Linux kernel:

    • version: 4.19.31
    • CONFIG_X86_MCELOG_LEGACY: Support for deprecated /dev/mcelog character device
    • OOT Intel 10Gbps network driver: ixgbe: version 5.5.5

    Management:

    • fstab: mount USB flash boot device with 'flush' keyword
    • rc.sshd: only copy new key files to USB flash boot device
    • rc.nginx: implement better status wait loop - thanks ljm42
    • smartmontools: update drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt}
    • webgui: Per Device Font Size Setting
    • webgui: Syslog: add '' entry in local folder selection
    • webgui: Syslog: included rsyslog.d conf files and chmod 0666
    • webgui: Syslog: added log rotation settings
    • webgui: Open link under Unraid logo in new window
    • webgui: Use cookie for display setting font size
    • webgui: prevent dashboard bar animations from queuing up on inactive browser tab
    • webgui: Replace string "OS X" with "macOS"
    • webgui: Updated Unraid icons
    • webgui: Switch plugins to a compressed download
    • Like 2
    • Upvote 1



    User Feedback

    Recommended Comments



    20 minutes ago, Duggie264 said:

    I just find it strange that I have had no issues under 6.6.7  and below?

     

    26 minutes ago, johnnie.black said:

    Likely a kernel issue

     

    Link to comment
    1 hour ago, Duggie264 said:

    Is that an unraid kernel issue, or  a controller kernel issue?

    It's likely a problem with the Linux kernel and/or the driver included with that kernel, a newer kernel/driver might fix it, might not.

    Link to comment

    > Each device (including the local) can have it's own font-size set via Display Settings.  Try changing the font-size.

     

    I tried changing the font setting...  It doesn't seem to help as it is the main log in page before I even get to the web interface...  It is at least twice as big as the earlier version...  When I open the web interface, it's so big I have to reduce it to 37% just so I can see the log off, etc options...

     

    Link to comment
    On 3/30/2019 at 8:23 AM, RGauld said:

    The console font appears to have changed.  In GUI mode with my monitor attached directly to the server, the web interface font is so large I have to reduce the screen to 30% to get the icons to appear for logoff, reboot, etc...

     

     

    20190330_061406.jpg

    This is probably an attempt to fix this

    Dunno how that's going to be solved. Either some people have fonts that are tiny, or others have huge fonts.

    Link to comment

    has setting a share floor always been honored on the cache drive as well?

    IE: Video Share Min Free Space 200GB, Use Cache

     

    so my 1tb cache drive is now 800gb, can the share floor be excluded from the cache drive?

    Link to comment
    1 hour ago, spl147 said:

    has setting a share floor always been honored on the cache drive as well?

    IE: Video Share Min Free Space 200GB, Use Cache

     

    so my 1tb cache drive is now 800gb, can the share floor be excluded from the cache drive?

    The Min Free Space for the cache drive is not set at the User Share Level.    instead you set it under Settings => Global Share Settings.

    Link to comment
    16 minutes ago, itimpi said:

    The Min Free Space for the cache drive is not set at the User Share Level.    instead you set it under Settings => Global Share Settings.

    And you would set it to be larger than the largest file you ever expect to write to cache, similarly to what you would set it to for a user share. It is perhaps even more important that you don't allow your cache to fill as that may corrupt docker image, appdata, or anything else you have that lives on cache.

     

    Min Free on cache will only have an effect on cache-yes or cache-prefer user shares, where it will cause additional files to overflow to the array.

    Link to comment

    on 6.6.7 and I get this when trying to update to this version here is my output:
     

    plugin: installing: /var/tmp/unRAIDServer.plg
    plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.7.0-rc6-x86_64.zip ... done
    plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.7.0-rc6-x86_64.md5 ... done
    wrong md5
    plugin: run failed: /bin/bash retval: 1

    I've attached my diagonostics. Probably something dumb I am forgetting

    tower-diagnostics-20190404-0041.zip

    Link to comment
    11 hours ago, gltovar said:

    on 6.6.7 and I get this when trying to update to this version here is my output:

    No I messed something up trying to publish -rc7.

    Link to comment



    Guest
    This is now closed for further comments

  • 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.