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



    Updated from rc5. All systems nominal. Nothing to report.

    Share this comment


    Link to comment
    Share on other sites

    Updated from rc5 no issues.

    Share this comment


    Link to comment
    Share on other sites

    Updated from rc5 without problems.

    Share this comment


    Link to comment
    Share on other sites

    No issues here from rc5 on 2 servers.

    Share this comment


    Link to comment
    Share on other sites
    Quote

    webgui: Open link under Unraid logo in new window

    Just got to the forum with a right click on and "open in new tab", and thought again how handy it'd be.  Little thing, but thank you for this :)

    Share this comment


    Link to comment
    Share on other sites

    Updated without issue from rc5. Among ALL the updates, thanks also for the intel 10Gb driver update!

    Edited by cybrnook

    Share this comment


    Link to comment
    Share on other sites

    Updated from RC5 and running since this morning without issues!

    Share this comment


    Link to comment
    Share on other sites

    Updated from rc5... no issues.  

    Share this comment


    Link to comment
    Share on other sites

    Any word on Linux Kernal 4.20?  Really hoping for 9900k support!!

    Share this comment


    Link to comment
    Share on other sites
    11 minutes ago, sittingmongoose said:

    Any word on Linux Kernal 4.20?  Really hoping for 9900k support!!

    4.20 is already EOL probably won't use that one.

    Share this comment


    Link to comment
    Share on other sites

    updated from rc5, no issues found

    Share this comment


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

    Any word on Linux Kernal 4.20?  Really hoping for 9900k support!!

    Next unraid depending on when it releases will uses Kernel 5.1 but my money is on 5.2

     

    Which MAY have wireguard kernel support.

     

    That will be around the same time Zen 2 launches and support that.

    Share this comment


    Link to comment
    Share on other sites

    Upgraded from 6.6.7 and now I can get to the web ui or ssh.  Currently running headless so I’m working to hook up a monitor to see where it is running in to problems....

     

    Well I was able to get it to boot in GUI mode, but when I try to load without the GUI it is getting stuck at "loading /bzroot...ok"  I was able to downgrade and tried to upgrade again (I'm apparently asking for trouble), but it is getting stuck at the same spot.

    Edited by SenorLoco

    Share this comment


    Link to comment
    Share on other sites

    There have been reports for some time about only being able to boot in GUI or non-GUI mode on some peoples systems, but I do not think anyone has tracked down the cause or even a clear pattern of when it occurs.   Since you can boot in GUI mode I would suggest just setting that as the default.   Booting into GUI mode will not be a problem even if normally running in 'headless' mode.

    Share this comment


    Link to comment
    Share on other sites

    Headless 6.6.7 upgrade to rc6 here. No issues at all. 

    Share this comment


    Link to comment
    Share on other sites

    I was able to get it working without booting in to GUI mode.  6.6.7 and 6.7.0 GUI were booting fine in Legacy mode, but I was able to change to UEFI in the bios and then it booted fine without the GUI.

    Share this comment


    Link to comment
    Share on other sites

    I may have spoke to soon for the 6.7.0 rc6 update I started having issues with dockers updating so I looked at fix common problems and it was complaining of these issues

    image.thumb.png.2743e7b220462bcf1613152541f0506f.pngScreen Shot 2019-03-27 at 6.32.29 PM

     

    so I rolled back to 6.7.0 rc5 and all seem to be good I updated dockers with no problem and FCP found no issue so I captured diags of before and after for those good at reading the tea leaves anyone else having anything like this? It actually affected Plex updating metadata thought that was weird I went so far as resetting my router but that was no help only rolling back corrected it

     

    homenas-diagnostics-20190327-2221.zip

    homenas-diagnostics-20190327-2228.zip

     

    Edited by mrbilky
    Corrected zip file links

    Share this comment


    Link to comment
    Share on other sites

    What do you have your dns settings set as?

    Share this comment


    Link to comment
    Share on other sites
    10 minutes ago, cybrnook said:

    What do you have your dns settings set as?

    google but I didn't change it from rc5 to rc6 so it works on rc5 was I supposed to change it due to the upgrade? Funny thing to my other server an R710 is working fine with rc6 but the DNS is the routers DNS

    Edited by mrbilky

    Share this comment


    Link to comment
    Share on other sites

    Upgraded from rc5 and diff compared the logs, all looks as it should. Nice work!

    Share this comment


    Link to comment
    Share on other sites
    8 minutes ago, mrbilky said:

    google but I didn't change it from rc5 to rc6 so it works on rc5 was I supposed to change it due to the upgrade? Funny thing to my other server an R710 is working fine with rc6 but the DNS is the routers DNS

    Sounds like a time out issue, maybe? Were DNS time out settings changed anywhere?

    Share this comment


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

    I may have spoke to soon for the 6.7.0 rc6 update I started having issues with dockers updating so I looked at fix common problems and it was complaining of these issues

    image.thumb.png.2743e7b220462bcf1613152541f0506f.pngScreen Shot 2019-03-27 at 6.32.29 PM

     

    so I rolled back to 6.7.0 rc5 and all seem to be good I updated dockers with no problem and FCP found no issue so I captured diags of before and after for those good at reading the tea leaves anyone else having anything like this? It actually affected Plex updating metadata thought that was weird I went so far as resetting my router but that was no help only rolling back corrected it

     

    homenas-diagnostics-20190327-2221.zip

    homenas-diagnostics-20190327-2228.zip

     

     

    Thanks for the diags.  There were a large number of base package updates in -rc6 and you have plugins that install a lot of packages.  My guess is that one of those plugins is reverting some package, making this issue happen.  Reboot in 'safe mode' and see if Plex metadata update works correctly.

    Share this comment


    Link to comment
    Share on other sites

    If they did it wasn't me I really thought it was my ISP so I took the drastic measure of resetting the router but then I rolled back to rc5 and all worked as normal then I updated again for shits and giggles to see if it was a hiccup but it went back to the errors reported I'm now on rc5 on my main server and rc6 on my other server with the only difference I see is the ip4 DNS server being google on the rc5 and the ip4 of the default gateway on rc6

    Share this comment


    Link to comment
    Share on other sites

    I want to add, I did see an anomaly today as well. I have my unraid server in the basement on a rack, and I have a KVM switch hooked up to all my servers. I always leave unraid up as my main display, and it's always just there.

     

    Today, however, I went into the basement and noticed that the display was in sleep mode. Not off, but basically no signal. I switched (on the KVM) over to my pfsense box, and that came right up. Switched back to unraid, and still nothing. So I rebooted, and as of now display is back to being active.

     

    I will watch it for another 24 hours and see if it does it again. If so I will post diags. Side note, webserver and all was up and running fine, and logs seemed to be okay between yesterday and today. It's as if the display output went to sleep mode.

    Edited by cybrnook

    Share this comment


    Link to comment
    Share on other sites



    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.