Jump to content
  • Unraid OS version 6.7.0-rc8 available


    limetech

    Hopefully last release before 6.7.0 stable.

     

    Two notes:

    1. Added sdparm command in order to get SAS spin-up/down implemented properly.  If you have SAS controllers with SAS HDD's please send me PM if you are willing to help debug this.
    2. Removed kernel patch which was trying to work around problematic Silicon Motion SM2262/SM2263 NVMe controllers.  A different workaround is recommended.

     

    Version 6.7.0-rc8 2019-04-30

    Base distro:

    • at-spi2-core: version 2.32.1
    • bash: version 5.0.007
    • cifs-utils: version 6.9
    • dhcpcd: version 7.2.0
    • docker: version 18.09.5
    • glib2: version 2.60.1
    • glibc-zoneinfo: version 2019a
    • gtk+3: version 3.24.8
    • icu4c: version 64.2
    • kernel-firmware: version 20190424_4b6cf2b
    • libcap: version 2.27
    • libcroco: version 0.6.13
    • libdrm: version 2.4.98
    • libpng: version 1.6.37 (CVE-2018-14048 CVE-2018-14550 CVE-2019-7317)
    • libpsl: version 0.21.0
    • nano: version 4.2
    • ncurses: version 6.1_20190420
    • nghttp2: version 1.38.0
    • openssh: version 8.0p1
    • pcre2: version 10.33
    • pixman: version 0.38.4
    • samba: version 4.9.6
    • sdparm: version 1.10
    • sg3_utils: version 1.44
    • sqlite: version 3.28.0
    • util-linux: version 2.33.2
    • wget: version 1.20.3 (CVE-2019-5953)
    • zstd: version 1.4.0

    Linux kernel:

    • version: 4.19.37
    • remove patch: PCI: Quirk Silicon Motion SM2262/SM2263 NVMe controller reset: device 0x126f/0x2263

    Management:

    • docker: preserve container fixed IPv4 and IPv6 addresses across reboot/docker restart
    • emhttp: ignore *.key files that begin with "._"
    • networking: pass user-specified MAC address through to bridge
    • smartmontools: update drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt}
    • webgui: Allow optional notifications on background docker update checks
    • webgui: Dashboard: fixed hanging when no share exports are defined
    • webgui: Minor textual changes
    • webgui: Add GameServers to category for docker containers

     



    User Feedback

    Recommended Comments



    Sync on flash drives seems to happen before text is posted whilst doing the update so appears to hang, but then completes ok.

     

    Rebooted all running ok.

    Edited by SimonF
    • Upvote 1

    Share this comment


    Link to comment
    Share on other sites

    Anybody else? still having this issue with both rc7 and rc8 not sure whats up just updated my R710 that went without issue maybe someone will be able to read the tea leaves this diag is after reboot with rc8

    homenas-diagnostics-20190430-2127.zip

     

    b2bf3aaf-176f-4ec0-bce9-e94046a5fe77.thumb.png.1e055490634bd0d5d653c07ecf96a19f.png

    c7713930-dd72-4162-b225-b09941fff645.png

    Share this comment


    Link to comment
    Share on other sites

    You have three times a default gateway "192.168.1.1" defined (eth0, eth1, eth2). This leads to asymmetric data transfers, and likely your firewall blocking things.

     

    Make sure only eth0 has a default gateway.

    Share this comment


    Link to comment
    Share on other sites
    32 minutes ago, bonienl said:

    You have three times a default gateway "192.168.1.1" defined (eth0, eth1, eth2). This leads to asymmetric data transfers, and likely your firewall blocking things.

     

    Make sure only eth0 has a default gateway.

    Good eye sir that was the ticket!👍

    Edited by mrbilky

    Share this comment


    Link to comment
    Share on other sites

     

    Thanks for the update.

     

    "Hopefully last release before 6.7.0 stable. "

     

    Does LT ack low performance on some situation of disk operation ?

     

    e.g.

                  cat /mnt/disk'x'/xxxx > /dev/null

     

    I test by above, in 1 disk / 2 disk / 3 disk and got abnormal throughput, suffer this issue in whole 6.7RC but no problem on 6.6.7, thanks

    Edited by Benson

    Share this comment


    Link to comment
    Share on other sites

    I've been waiting for SAS spindown/up for absolutely ages! i've for 12 Dell SAS drives in an R510 that won't spin down, so this is fantastic news!

    Share this comment


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

    Sync on flash drives seems to happen before text is posted whilst doing the update so appears to hang, but then completes ok.

     

    Rebooted all running ok.

    I’m still seeing this as well. The “syncing—please wait” message doesn’t appear until after the sync has completed.

    • Upvote 1

    Share this comment


    Link to comment
    Share on other sites
    35 minutes ago, wgstarks said:

    I’m still seeing this as well. The “syncing—please wait” message doesn’t appear until after the sync has completed.

    Same here. Worried my server had freezed.

    Share this comment


    Link to comment
    Share on other sites

    Oddly enough I saw no delay this time on syncing. I was Chicken Little on the last RC: "The install has hung! The install has hung!". lol

    Share this comment


    Link to comment
    Share on other sites

    Thanks for the quick fix for my mac problem! :D Working fine.

    Share this comment


    Link to comment
    Share on other sites
    2 hours ago, Benson said:

    I test by above, in 1 disk / 2 disk / 3 disk and got abnormal throughput, suffer this issue in whole 6.7RC but no problem on 6.6.7, thanks

    Are you talking about having 3 or more devices being read in parallel?  If so you can try increasing

    Tunable (md_num_stripes)

    on Settings/Disk Settings if your use case requires this.

    Share this comment


    Link to comment
    Share on other sites
    3 hours ago, greg0986 said:

    I've been waiting for SAS spindown/up for absolutely ages! i've for 12 Dell SAS drives in an R510 that won't spin down, so this is fantastic news!

    The code is not in place to fix this yet, just the packages required for a fix.  I only have limited SAS h/w to test with and so far things not working correctly but I think it might be an issue with the enclosure I'm using.

    • Like 1

    Share this comment


    Link to comment
    Share on other sites
    2 hours ago, wgstarks said:

    I’m still seeing this as well. The “syncing—please wait” message doesn’t appear until after the sync has completed.

    Yeah we'll fix this for stable.  Actually those coming from pre-6.7 Unraid will not see this issue.  It's happening because of this change back in -rc6:

    • fstab: mount USB flash boot device with 'flush' keyword
    • Like 1

    Share this comment


    Link to comment
    Share on other sites
    Benson

    Posted (edited)

    31 minutes ago, limetech said:

    Are you talking about having 3 or more devices being read in parallel?  If so you can try increasing

    Tunable (md_num_stripes)

    on Settings/Disk Settings if your use case requires this.

    Actually problem not only happen on parallel read, performance also low even only 1 disk access at a time.

     

    In 6.7RC, I got slow problem on

    - Rsync file between 2 Unraid

    - Hash file by Checksum suit / FIP locally

    - .....

    Edited by Benson

    Share this comment


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

    Actually problem not only happen on parallel read, performance also low even only 1 disk access at a time.

    Need more info, for example what exactly are you doing?  Also diagnostics.zip.  Is this an issue isolated to 6.7-rc series only?

    Share this comment


    Link to comment
    Share on other sites

    Yes, issue only on 6.7-rc series, I have make bug-report for easy followup.

    Pls have check, this issue have reproduce at 3 different PC platform.

    Share this comment


    Link to comment
    Share on other sites
    6 hours ago, limetech said:

    The code is not in place to fix this yet, just the packages required for a fix.  I only have limited SAS h/w to test with and so far things not working correctly but I think it might be an issue with the enclosure I'm using.

    Do you need the SAS drives to be part of the array? I have some SAS drives laying around that I can add to my server they are just not part of the array (connected via an SAS expander to a Dell H330 SAS controller.)

    If this suffices for your test let me know and I will upgrade / run it tonight (EU time).

    Share this comment


    Link to comment
    Share on other sites

    Yes, SAS drives need to be tested as part of the array.

    Share this comment


    Link to comment
    Share on other sites

    No issues running RC8 on my threadripper system.

     

    Noticed PHP 7.2.17 is out to patch a CVE. If that could be included in Final!

     

    Bring on stable!

    Share this comment


    Link to comment
    Share on other sites
    3 hours ago, Dazog said:

    Noticed PHP 7.2.17 is out to patch a CVE. If that could be included in Final!

    Yes we'll get that into next release.

    Share this comment


    Link to comment
    Share on other sites
    5 hours ago, limetech said:

    Yes we'll get that into next release.

    Awesome! I open my big mouth and another CVE for PHP and 7.2.18 is out.

     

    I should just be quiet :0

    Share this comment


    Link to comment
    Share on other sites
    21 minutes ago, Dazog said:

    another CVE for PHP and 7.2.18 is out

    Where do you see that?

    Share this comment


    Link to comment
    Share on other sites



    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.