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



    I understand that the "on" state for buttons has always been blue but why not, in the new design style, use orange to keep everything consistent?

    Share this comment


    Link to comment
    Share on other sites

    Think the command text below should be white (black theme). 

    image.thumb.png.07089dd27c40ede560d821529338a8f5.png

    image.png

    Share this comment


    Link to comment
    Share on other sites

    Loving the progress, keep up the great work!

     

    Was the below fix supposed to sort wrapping of long names, like for VM's?:

    Quote

    webgui: Dashboard: fixed wrapping of long lines

    image.thumb.png.daa6ab37747a7ebd7714c3eeaa1de4eb.png

    Share this comment


    Link to comment
    Share on other sites

    The change in RC2 is for the dashboard.

    VMS page will have support for longer VM names in the next RC.

    • Like 1

    Share this comment


    Link to comment
    Share on other sites

    Thanks @bonienl

     

    You have any plans on updating the icons in the dynamix plugins to match the new themeing? I notice that stats, trim and temperature still have the more colorful icons.

    image.thumb.png.f4db0de266a8365fd706a23e46b693e6.png

     Just tell me if I am pushing it... 🙂

    Share this comment


    Link to comment
    Share on other sites

    main announcement thread needs to be updated to point to this RC instead of rc1

    Share this comment


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

    main announcement thread needs to be updated to point to this RC instead of rc1

    Good call, thank you.

    Share this comment


    Link to comment
    Share on other sites
    49 minutes ago, AnnabellaRenee87 said:

    Can you please add NUMAD? 

    I replied in the feature request board:

    Please quit spamming every other topic with this request. 😉

     

    Share this comment


    Link to comment
    Share on other sites

    How do you use the --allow-discards option?

    Edit: ah, it's already there :)

    "/usr/sbin/cryptsetup luksOpen /dev/sdb1 sdb1 --allow-discards --key-file /root/keyfile"

    root@s:~# fstrim -a -v
    /var/lib/docker: 23.8 GiB (25545605120 bytes) trimmed on /dev/loop2
    /mnt/cache: 352 GiB (377950724096 bytes) trimmed on /dev/mapper/sdb1
    Yaaay. Strange cache size but ok? ;)

    Edited by Niklas

    Share this comment


    Link to comment
    Share on other sites
    38 minutes ago, Niklas said:

    Yaaay. Strange cache size but ok? ;)

    What's strange about it?

    Share this comment


    Link to comment
    Share on other sites

    I see RC 2 fixed the on colour thank fro that but we lost the delay start up under dockers and presumably VM's

     

    could we get that back please????

    Screenshot 2019-01-25 15.47.55.png

    Share this comment


    Link to comment
    Share on other sites

    image.png.203e7e0becfb8e336831d313a81439ba.png

    Still there. Notice the difference between our two screenshots?

    Share this comment


    Link to comment
    Share on other sites

    Great progress!  So far so good...

    Share this comment


    Link to comment
    Share on other sites

    2 Unraid ( Intel / AMD ) update, both found array read performance drop, for example "cat <file> > /dev/null" ..... all disk relate operation slow down a lot, never got this before.

    Edited by Benson

    Share this comment


    Link to comment
    Share on other sites

    I notice on the new dashboard that 100% CPU usage on the overall state is a longer bar than 100% on individual CPU's.   Is this by design?

    Share this comment


    Link to comment
    Share on other sites
    42 minutes ago, itimpi said:

    I notice on the new dashboard that 100% CPU usage on the overall state is a longer bar than 100% on individual CPU's.   Is this by design?

    This is by design to accomodate for cpus with hyperthreading were core/ht pair is grouped together

    Share this comment


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

    This is by design to accomodate for cpus with hyperthreading were core/ht pair is grouped together

    OK - that makes sense.   My system does not have hyperthreading which will be why I am seeing this.

    Share this comment


    Link to comment
    Share on other sites

    My system is giving those warning :  Looking from past bug report, it was link to kernel bug.

     

     

    WARNING: CPU: 4 PID: 134 at net/netfilter/nf_conntrack_core.c:907 __nf_conntrack_confirm+0x96/0x675

    [11203.774527] Modules linked in: macvlan iptable_mangle xt_CHECKSUM ipt_REJECT ip6table_filter ip6_tables vhost_net tun vhost tap veth xt_nat ipt_MASQUERADE iptable_nat nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod ipmi_devintf sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd mpt3sas glue_helper i2c_i801 i2c_core intel_cstate ahci intel_uncore libahci intel_rapl_perf raid_class ixgbe(O) scsi_transport_sas wmi acpi_power_meter acpi_pad button ipmi_si pcc_cpufreq

    [11203.774568] CPU: 4 PID: 134 Comm: kworker/4:1 Tainted: G           O      4.19.17-Unraid #1

    [11203.774569] Hardware name: Supermicro Super Server/X10SRH-CLN4F, BIOS 2.0a 09/20/2016

    [11203.774574] Workqueue: events macvlan_process_broadcast [macvlan]

    [11203.774578] RIP: 0010:__nf_conntrack_confirm+0x96/0x675

    [11203.774580] Code: c1 ed 20 89 2c 24 e8 66 f9 ff ff 8b 54 24 04 89 ef 89 c6 41 89 c5 e8 96 fa ff ff 84 c0 75 b9 49 8b 86 80 00 00 00 a8 08 74 02 <0f> 0b 4c 89 f7 e8 04 ff ff ff 49 8b 86 80 00 00 00 0f ba e0 09 73

    [11203.774581] RSP: 0000:ffff88bf7f703d98 EFLAGS: 00010202

    [11203.774583] RAX: 0000000000000188 RBX: ffff88bf71607900 RCX: 00000000b5bbcdae

    [11203.774584] RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffffffff81e08f94

    [11203.774585] RBP: 0000000000009665 R08: 00000000df89ce78 R09: ffff88bec9167000

    [11203.774586] R10: 0000000000000098 R11: ffff88bee3dea800 R12: ffffffff81e8d3c0

    [11203.774587] R13: 000000000000ad62 R14: ffff88b3807d4780 R15: ffff88b3807d47d8

    [11203.774589] FS:  0000000000000000(0000) GS:ffff88bf7f700000(0000) knlGS:0000000000000000

    [11203.774590] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033

    [11203.774592] CR2: 000000000c531ff0 CR3: 0000000001e0a003 CR4: 00000000001606e0

    [11203.774593] Call Trace:

    [11203.774595] <IRQ>

    [11203.774599] ipv4_confirm+0xaf/0xb7

    [11203.774601] nf_hook_slow+0x37/0x96

    [11203.774605] ip_local_deliver+0xa7/0xd5

    [11203.774608] ? ip_sublist_rcv_finish+0x53/0x53

    [11203.774610] ip_rcv+0x9e/0xbc

    [11203.774613] ? ip_rcv_finish_core.isra.0+0x2e6/0x2e6

    [11203.774616] __netif_receive_skb_one_core+0x4d/0x69

    [11203.774620] process_backlog+0x7e/0x116

    [11203.774622] net_rx_action+0x10b/0x274

    [11203.774627] __do_softirq+0xce/0x1e2

    [11203.774630] do_softirq_own_stack+0x2a/0x40

    [11203.774631] </IRQ>

    [11203.774634] do_softirq+0x4d/0x59

    [11203.774637] netif_rx_ni+0x1c/0x22

    [11203.774641] macvlan_broadcast+0x10f/0x153 [macvlan]

    [11203.774644] ? __switch_to_asm+0x34/0x70

    [11203.774647] macvlan_process_broadcast+0xd5/0x131 [macvlan]

    [11203.774650] process_one_work+0x16e/0x24f

    [11203.774653] ? cancel_delayed_work_sync+0xa/0xa

    [11203.774655] worker_thread+0x1dc/0x2ac

    [11203.774658] kthread+0x10b/0x113

    [11203.774660] ? kthread_park+0x71/0x71

    [11203.774663] ret_from_fork+0x35/0x40

    [11203.774665] ---[ end trace af37fab765101c2b ]---

     

    My system:

    Model: SuperMicro

    M/B: Supermicro X10SRH-CLN4F Version 1.00A - s/n: NM154S007683

    BIOS: American Megatrends Inc. Version 2.0a. Dated: 09/20/2016

    CPU: Intel® Xeon® CPU E5-2650L v3 @ 1.80GHz

    HVM: Enabled

    IOMMU: Enabled

    Cache: 768 KiB, 3072 KiB, 30720 KiB

    Memory: 256 GiB DDR4 Multi-bit ECC (max. installable capacity 512 GiB)

    Network: eth0: 10000 Mbps, full duplex, mtu 9000

    Kernel: Linux 4.19.17-Unraid x86_64

    OpenSSL: 1.1.1a

     

    Is it useful to publish a diagnostic ? 

     

    tower-diagnostics-20190126-1345.zip

    Edited by Greatcoco
    Attached a diagnostic

    Share this comment


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

    Is it useful to publish a diagnostic ?

    It's not useful to not publish a diagnostic.

    Share this comment


    Link to comment
    Share on other sites

    The new vfio bind method is not working if multiple ID's are specified. Only one ID specified and it works. I'll create a bug report.

    Share this comment


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

    What's strange about it?

    I don't fully know how btrfs works yet. 352 GiB ~ 378 GB. I have two 250GB in RAID1 as cache.
    If it looks correct, I'm happy about it. :)

    Edit: Ok, so it is correct. Of course. 
    johnnie.black reminded me that it reports trimmed FREE space. Doh! ;-)

    Edited by Niklas

    Share this comment


    Link to comment
    Share on other sites
    5 minutes ago, Niklas said:

    I don't fully know how btrfs works yet. 352 GiB ~ 378 GB. I have two 250GB in RAID1 as cache.
    If it looks correct, I'm happy about it.

    That's not correct, please post the diagnostics: Tools -> Diagnostics, though likely unrelated to this release, so probably best to post in the general support forum.

    Share this comment


    Link to comment
    Share on other sites

    Loving the new look but not sure what is going on with the memory section on the dashboard. I have 24 of a possible 32 GiB of RAM installed but memory is reporting as 0 MiB with a usable size of 32.0 GiB and a maximum size of 16.0 ?

     

    Also a small issue with OpenVPN that was resolved on the relevant forum

     

    ram.jpg

    Share this comment


    Link to comment
    Share on other sites

    currently am not upgrading to the 6.7.0 RC because my build is a all-in-one system, but can someone tell me the well know reset bug of the Vega56/64 graphic cards is fixed with this 4.19 kernel?

    The build is a Threadripper 1950 system, wits controlling the network, multiple Docker containers and my desktop VM's,  so i feels a little bit curious for upgrading the system :S 

    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.