Jump to content
  • Unraid OS version 6.7.0-rc2 available


    limetech

    Mainly bug fixes, webGUI tweaks.

     

    Other highlights:

    • Added the '--allow-discards' option to LUKS open.  This should only have any effect when using encrypted Cache device/pool with SSD devices.  It allows a file system to notice if underlying device supports TRIM and if so, passes TRIM commands down.
    • Fixed issue where files created through OS X had improper permission set.

     

    Version 6.7.0-rc2 2019-01-24

    Linux kernel:

    • version: 4.19.17
    • patch: btrfs: prevent failed readahead from spamming syslog
    • patch: PCI: Quirk Silicon Motion SM2262/SM2263 NVMe controller reset

    Management:

    • emhttpd: Add --allow-discard luksOpen option
    • emhttpd: Increase number of queued inotify IN_MOVED_TO events from 16 to 1024 for /var/local/emhttp directory.
    • firmware:
      added BCM20702A0-0a5c-21e8.hcd
      added BCM20702A1-0a5c-21e8.hcd
    • smb: when Enhanced OS X interoperability set, include "fruit:nfs_aces = no" to be compatible with Unraid security model
    • webgui: Dashboard: fixed display of Wattage in UPS load
    • webgui: Fixed version display in system information
    • webgui: Dashboard: fixed wrapping of long lines
    • webgui: Docker: textual update
    • webgui: Switch button: use blue color in ON state
    • webgui: File browser: force download of files

     



    User Feedback

    Recommended Comments



    Just noticed this in the logs during a mover operation.  Don't know that this is RC related.

     

    Feb 7 08:39:17 SPE-UNRAID01 nginx: 2019/02/07 08:39:17 [error] 24097#24097: *2517925 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.10.50, server: , request: "POST /webGui/include/Notify.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.0.10.30:4443", referrer: "https://10.0.10.30:4443/Dashboard"
    Feb 7 08:39:18 SPE-UNRAID01 nginx: 2019/02/07 08:39:18 [error] 24097#24097: *2517925 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.10.50, server: , request: "POST /webGui/include/DashUpdate.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.0.10.30:4443", referrer: "https://10.0.10.30:4443/Dashboard"
    Feb 7 08:39:22 SPE-UNRAID01 nginx: 2019/02/07 08:39:22 [error] 24097#24097: *2517925 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.10.50, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.0.10.30:4443", referrer: "https://10.0.10.30:4443/Dashboard"

     

    Edited by IamSpartacus

    Share this comment


    Link to comment
    Share on other sites
    29 minutes ago, IamSpartacus said:

    Just noticed this in the logs during a mover operation.  Don't know that this is RC related.

     

    
    Feb 7 08:39:17 SPE-UNRAID01 nginx: 2019/02/07 08:39:17 [error] 24097#24097: *2517925 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.10.50, server: , request: "POST /webGui/include/Notify.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.0.10.30:4443", referrer: "https://10.0.10.30:4443/Dashboard"
    Feb 7 08:39:18 SPE-UNRAID01 nginx: 2019/02/07 08:39:18 [error] 24097#24097: *2517925 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.10.50, server: , request: "POST /webGui/include/DashUpdate.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.0.10.30:4443", referrer: "https://10.0.10.30:4443/Dashboard"
    Feb 7 08:39:22 SPE-UNRAID01 nginx: 2019/02/07 08:39:22 [error] 24097#24097: *2517925 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.10.50, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "10.0.10.30:4443", referrer: "https://10.0.10.30:4443/Dashboard"

     

    Do you have any other browsers (including tabs on the same browser, or mobile apps such as ControlR) open to your server?

    Share this comment


    Link to comment
    Share on other sites
    1 minute ago, trurl said:

    Do you have any other browsers (including tabs on the same browser, or mobile apps such as ControlR) open to your server?

     

    Only one Chrome tab open on my PC (10.0.10.50).

    Share this comment


    Link to comment
    Share on other sites

    Could be a plugin. Test your system in safe mode.

    Share this comment


    Link to comment
    Share on other sites

     

    On 2/6/2019 at 7:27 AM, John_M said:

    the CA Backup/Restore Appdata plugin appears as a "three dimensional" grey safe on the Plugins page, as it always has

    Your plugins are not up to date then.

    Share this comment


    Link to comment
    Share on other sites

    Reporting in after two weeks of heavy use of rc2. Stable and no surprises in the logs.

     

    Thanks team! 🙂

     

    Share this comment


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

    Reporting in after two weeks of heavy use of rc2. Stable and no surprises in the logs.

    Thank you!  Good to get this feedback.

    Share this comment


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

     

    Your plugins are not up to date then.

     

    Apparently, they are (I can't update the Dynamix System Stats one because it needs a later Unraid than 6.6.6): 

     

    1840668605_ScreenShot2019-02-07at21_38_01.thumb.png.6a90891dcc0b1a14780049ba0da06da4.png

    Share this comment


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

    Reporting in after two weeks of heavy use of rc2. Stable and no surprises in the logs.

     

    Thanks team! 🙂

     

    What about the icons? ffs, man, this shit really matters!

    Share this comment


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

    Apparently, they are

    From how you were talking, I thought you were already on 6.7

    Share this comment


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

    What about the icons? ffs, man, this shit really matters!

     

    That's why it's important we report 'what IS working' so that the rc process can move forward.

     

    If the majority of issues are very minor, 'annoyance' presentation layer issues, which @bonienl has been very responsive too, then that's a great sign of forward progress.

     

    Maybe the next rc resolves them all, maybe we get some new ones to discover. That's the fun of the rc process, embrace it 😁

     

    Share this comment


    Link to comment
    Share on other sites
    9 minutes ago, Squid said:

    From how you were talking, I thought you were already on 6.7

     

    From my first post on the subject

     

    Quote

    I'm posting this here because it seems to be a 6.7 "thing" even though I'm still using 6.6.6.

     

    though in a later post I said

     

    Quote

    I've just installed -rc2 on one server so I can have a play with it.

     

    My (first) point being that the changes that have been made to accommodate the new style in 6.7 have adversely affected 6.6.6, which is unfortunate because it is the current stable release. My second point was to question the choice of flat, minimalistic monochrome icons going forward.

    Share this comment


    Link to comment
    Share on other sites

    Can anybody confirm if Unraid GUI works fine with the Quadro NVS cards ?

    Share this comment


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

    Can anybody confirm if Unraid GUI works fine with the Quadro NVS cards ?

    Are you asking this question regarding this specific release of Unraid, 6.70rc2? I am guessing not since you already posted this question here:

    The proper way to get attention to a thread you have already started is to "bump" that same thread by making another post in it.

    Share this comment


    Link to comment
    Share on other sites

    I'm running version 6.7.0-rc2 and  pass through an NVME drive to the machine but I keep getting this error: 

     

    internal error: qemu unexpectedly closed the monitor: 2019-02-07T17:55:09.769688Z qemu-system-x86_64: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.3,addr=0x0: vfio 0000:05:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align

     

    The problem  occur with NVMe's using the Silicon Motion SM2263XT (different from SM2263) controller. In my case the HP EX900 250G

     

    IOMMU group 51:[126f:2263] 05:00.0 Non-Volatile memory controller: Silicon Motion, Inc. Device 2263 (rev 03)

    IOMMU group 52:[126f:2263] 06:00.0 Non-Volatile memory controller: Silicon Motion, Inc. Device 2263 (rev 03)

    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.