Jump to content
  • Unraid OS version 6.7.0-rc1 available


    limetech

    New in Unraid OS 6.7 release:

     

    New Dashboard layout, along with new Settings and Tools icons.  Designed by user @Mex and implemented in collaboration with @bonienl.  We think you will find this is a big step forward.

     

    Time Machine support via SMB.  To enable this feature it is necessary to first turn on Enhanced OS X interoperability on the Settings/SMB page.  Next, select a share to Export for Time Machine in the share SMB Security Settings section.  AFP support is deprecated.

     

    Linux kernel 4.19.  This is the latest Long Term Support kernel.  We will go with this for a while but anticipate
    updating to 4.20 or even 5.0 for Unraid 6.7.0 stable.  Here are some other kernel-related updates:

    • Added TCP "BBR Congestion control" and made it the default.  This should improve network throughput but probably not too many users will notice anything different.
    • Added Bluetooth support in the Linux kernel.  We did not add the user-space tools so this will be mostly useful to support Bluetooth in docker containers.
    • AMD firmware update for Threadripper.

     

    Ignore case in validating user share names.  If there are multiple top-level directories which differ only in case, then we use the first such share name encountered, checking in order: cache, disk1, disk2, ..., diskN.  Additional top-level directories encountered will be ignored.  For example, suppose we have:

    /mnt/cache/ashare
    /mnt/disk1/Ashare
    /mnt/disk2/ashare

    The name of the exported share will be 'ashare' and will consist of a union of /mnt/cache/ashare and /mnt/disk2/ashare.  The contents of /mnt/disk1/Ashare will not show up in /mnt/user/ashare.

     

    If you then delete the contents of /mnt/user/ashare followed by deleting the 'ashare' share itself, this will result in share 'Ashare' becoming visible.  Similar, if you delete the contents of /mnt/cache/ashare (or gets moved), then you will now see share 'Ashare' appear, and it will look like the contents of 'ashare' are missing!  Thankfully very few (if any) users should be affected by this, but handles a corner case in both the presentation of shares in windows networking and storage of share config data on the USB flash boot device.

     

    New vfio-bind method.  Since it appears that the xen-pciback/pciback kernel options no longer work, we introduced an alternate method of binding, by ID, selected PCI devices to the vfio-pci driver. This is accomplished by specifying the PCI ID(s) of devices to bind to vfio-pci in the file 'config/vfio-pci.cfg' on the USB flash boot device.  This file should contain a single line that defines the devices:

    BIND=<device> <device> ...

    Where <device> is a Domain:Bus:Device.Function string, for example,

    BIND=02:00.0

    Multiple device should be separated with spaces.

     

    The script /usr/local/sbin/vfio-pci is called very early in system start-up, right after the USB flash boot device is
    mounted but before any kernel modules (drivers) have been loaded.  The function of the script is to bind each specified device to the vfio-pci driver, which makes them available for assignment to a virtual machine, and also prevents the Linux kernel from automatically binding them to any present host driver.

     

    In addition, and importantly, this script will bind not only the specified device(s), but all other devices in the same IOMMU group as well.  For example, suppose there is an NVIDIA GPU which defines both a VGA device at 02:00.0 and an audio device at 02.00.1.  Specifying a single device (either one) on the BIND line is sufficient to bind both device to vfio-pci.  The implication is that either all devices of an IOMMU group are bound to vfio-pci or none of them are.

     

    Added 'telegram' notification agent support - thank you @realies

     

    Finally, we updated several base packages, including move to Samba 4.9 and docker 18.09, and fixed a number of minor bugs.

     

    Version 6.7.0-rc1 2019-01-21

    Base distro:

    • aaa_elflibs: version 15.0 (rev 3)
    • acpid: version 2.0.31
    • adwaita-icon-theme: version 3.30.1
    • at: version 3.1.23
    • at-spi2-atk: version 2.30.0
    • at-spi2-core: version 2.30.0
    • atk: version 2.30.0
    • bin: version 11.1 (rev 3)
    • bluez: version 4.101
    • bluez firmware: version 1.2
    • bridge-utils: version 1.6
    • btrfs-progs: version v4.19.1
    • ca-certificates: version 20181210
    • cairo: version 1.16.0
    • cifs-utils: version 6.8
    • coreutils: version 8.30 (rev 4)
    • curl: version 7.63.0
    • cyrus-sasl: version 2.1.27
    • dbus: version 1.12.12
    • dhcpcd: version 7.0.8
    • diffutils: version 3.7
    • dmidecode: version 3.2
    • dnsmasq: version 2.80
    • docker: version 18.09.1
    • e2fsprogs: version 1.44.5
    • etc: version 15.0 (rev 9)
    • ethtool: version 4.19
    • file: version 5.35
    • findutils: version 4.6.0
    • fribidi: version 1.0.5
    • gdbm: version 1.18.1
    • gdk-pixbuf2: version 2.38.0
    • git: version 2.20.1
    • glibc-zoneinfo: version 2018g
    • glib2: version 2.58.2
    • gnutls: version 3.6.5 (CVE-2018-16868)
    • gptfdisk: version 1.0.4
    • graphite2: version 1.3.13
    • grep: version 3.3
    • gtk+3: version 3.24.2
    • gzip: version 1.10
    • harfbuzz: version 2.3.0
    • haveged: version 1.9.4
    • hdparm: version 9.58
    • hostname: version 3.21
    • hwloc: version 1.11.11
    • icu4c: version 63.1
    • inotify-tools: version 3.20.1
    • intel-microcode: version 20180807a
    • iproute2: version 4.19.0
    • iptables: version 1.8.2
    • iputils: version s20180629
    • irqbalance: version 1.5.0
    • jansson: version 2.12
    • kernel-firmware: version 20181218_0f22c85
    • keyutils: version 1.6
    • libSM: version 1.2.3
    • libX11: version 1.6.7
    • libarchive: version 3.3.3
    • libcap-ng: version 0.7.9
    • libdrm: version 2.4.96
    • libedit: version 20181209_3.1
    • libepoxy: version 1.5.3
    • libestr: version 0.1.11
    • libevdev: version 1.6.0
    • libgcrypt: version 1.8.4
    • libgpg-error: version 1.33
    • libjpeg-turbo: version 2.0.1
    • libnftnl: version 1.1.2
    • libpcap: version 1.9.0
    • libpng: version 1.6.36
    • libpsl: version 0.20.2
    • libpthread-stubs: version 0.4 (rev 3)
    • librsvg: version 2.44.11
    • libtirpc: version 1.1.4
    • libvirt: version 4.10.0
    • libwebp: version 1.0.1
    • libxcb: version 1.13.1
    • lm_sensors: version 3.5.0
    • logrotate: version 3.15.0
    • lvm2: version 2.03.02
    • lzip: version 1.20
    • lz4: version 1.8.3
    • mc: version 4.8.22
    • mesa: version 18.3.0
    • miniupnpc version: 2.1
    • nano: version 3.2
    • ncurses: version 6.1_20181110
    • netatalk: version 3.1.12 (CVE-2018-1160)
    • nettle: version 3.4.1 (CVE-2018-16869)
    • nghttp2: version 1.35.1
    • nginx: version 1.14.2 (+ nchan 1.2.3) (CVE-2018-16843, CVE-2018-16844, CVE-2018-16845)
    • ntp: version 4.2.8p12 (rev 5)
    • openldap-client: version 2.4.47
    • pciutils: version 3.6.2
    • perc2: version 10.32
    • php: version 7.2.13
    • pixman: version 0.36.0
    • pkgtools: version 15.0 (rev 23)
    • pv: version 1.6.6
    • qemu: version 3.1.0
    • rpcbind: version 1.2.5
    • rsyslog: version 8.40.0
    • samba: version 4.9.4 (CVE-2018-14629, CVE-2018-16841, CVE-2018-16851, CVE-2018-16852, CVE-2018-16853, CVE-2018-16857)
    • sed: version 4.7
    • shadow: version 4.6
    • shared-mime-info: version 1.10
    • smartmontools: version 7.0
    • spice: version 0.14.1
    • spice-protocol: version 0.12.14
    • sqlite: version 3.26.0
    • sudo: version 1.8.26
    • sysvinit-scripts: version 2.1 (rev 24)
    • sysvinit: version 2.93
    • tar: version 1.30 (rev 3)
    • tree: version 1.8.0
    • ttyd: version 1.4.2
    • util-linux: version 2.33
    • wget: version 1.20
    • xauth: version 1.0.10 (rev 3)
    • xfsprogs: version 4.19.0
    • wget: version 1.20.1
    • xkeyboard-config: version 2.25
    • xterm: version 341
    • zstd: version 1.3.8

    Linux kernel:

    • version: 4.19.16
    • OOT Intel 10Gbps network driver: ixgbe: version 5.5.3
    • OOT Tehuti 10Gbps network driver: tn40xx: version 0.3.6.17
    • added drivers:
    • CONFIG_USB_SERIAL_CH341: USB Winchiphead CH341 Single Port Serial Driver
    • added TCP BBR congestion control kernel support and set as default:
    • CONFIG_NET_KEY: PF_KEY sockets
    • CONFIG_TCP_CONG_BBR: BBR TCP
    • CONFIG_NET_SCH_FQ: Fair Queue
    • CONFIG_NET_SCH_FQ_CODEL: Fair Queue Controlled Delay AQM (FQ_CODEL)
    • added Bluetooth kernel support:
    • CONFIG_BT: Bluetooth subsystem support
    • CONFIG_BT_BREDR: Bluetooth Classic (BR/EDR) features
    • CONFIG_BT_RFCOMM: RFCOMM protocol support
    • CONFIG_BT_RFCOMM_TTY: RFCOMM TTY support
    • CONFIG_BT_BNEP: BNEP protocol support
    • CONFIG_BT_BNEP_MC_FILTER: Multicast filter support
    • CONFIG_BT_BNEP_PROTO_FILTER: Protocol filter support
    • CONFIG_BT_HIDP: HIDP protocol support
    • CONFIG_BT_HS: Bluetooth High Speed (HS) features
    • CONFIG_BT_LE: Bluetooth Low Energy (LE) features
    • CONFIG_BT_HCIBTUSB: HCI USB driver
    • CONFIG_BT_HCIBTUSB_AUTOSUSPEND: Enable USB autosuspend for Bluetooth USB devices by default
    • CONFIG_BT_HCIBTUSB_BCM: Broadcom protocol support
    • CONFIG_BT_HCIBTUSB_RTL: Realtek protocol support
    • CONFIG_BT_HCIUART: HCI UART driver
    • CONFIG_BT_HCIUART_H4: UART (H4) protocol support
    • CONFIG_BT_HCIUART_BCSP: BCSP protocol support
    • CONFIG_BT_HCIUART_ATH3K: Atheros AR300x serial support
    • CONFIG_BT_HCIUART_AG6XX: Intel AG6XX protocol support
    • CONFIG_BT_HCIUART_MRVL: Marvell protocol support
    • CONFIG_BT_HCIBCM203X: HCI BCM203x USB driver
    • CONFIG_BT_HCIBPA10X: HCI BPA10x USB driver
    • CONFIG_BT_HCIVHCI: HCI VHCI (Virtual HCI device) driver
    • CONFIG_BT_MRVL: Marvell Bluetooth driver support
    • CONFIG_BT_ATH3K: Atheros firmware download driver
    • md/unraid: version 2.9.5 (kernel BUG if read phase of read/modify/write with FUA flag set fails on stripe with multiple read failures)
    • patch: PCI: Quirk Silicon Motion SM2262 NVMe controller reset
    • patch: support Mozart 395S chip

    Management:

    • add early vfio-bind utility
    • fix: docker log rotation
    • fix: inconsistent share name case
    • fix: terminal instances limited to 8 (now lifted)
    • restore PHP E_WARNING in /etc/php/php.ini
    • support Apple Time Machine via SMB
    • update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt}
    • webgui: New icon reference
    • webgui: Added new font icons
    • webgui: added new case icons
    • webgui: Revamped dashboard page
    • webgui: Replaced orb png icons by font-awesome
    • webgui: Position context menu always left + below icon
    • webgui: Do not capitalize path names in title of themes Azure and Gray
    • webgui: Allow plugins to use font awesome for icon
    • webgui: sort notification agents alphabetically, add telegram notifications
    • webgui: Dashboard: use disk thresholds for utlization bars
    • webgui: VM manager: remove and rebuild USB controllers
    • webgui: Fixed: slots selection always disabled after "New Config"
    • webgui: Fix Background color when installing container
    • webgui: Fixed share/disk size calculation when names include space
    • webgui: Add log-size and log-file options to docker run command
    • webgui: Escape quotes on a containers template
    • webgui: Prevent update notification if plugin is not compatible
    • webgui: other GUI enhancements

    Edited by limetech

    • Like 5
    • Upvote 6


    User Feedback

    Recommended Comments



    4 minutes ago, kizer said:

    Personally and I do mean Personally.

    Colors like Red and Orange signal an error or problem or something Critical like stopping the array or restarting.

    Colors like Green and Blue show normal or non critical system changes.

    The key for me is context. Overall theme wise, I'm ok with orange. Status indicators, not so much, unless it's an error condition.

    Share this comment


    Link to comment
    Share on other sites
    6 minutes ago, jonathanm said:

    The key for me is context. Overall theme wise, I'm ok with orange. Status indicators, not so much, unless it's an error condition.

    I agree totally.

     

    Back in the day we had Black and Blue. Lol

    UnRAIDscreen.jpg

    • Like 2

    Share this comment


    Link to comment
    Share on other sites

    LOL. You can't say goodbye to version 4?

    Share this comment


    Link to comment
    Share on other sites
    46 minutes ago, jonathanm said:

    The key for me is context. Overall theme wise, I'm ok with orange. Status indicators, not so much, unless it's an error condition.

    I am with you there.

    Share this comment


    Link to comment
    Share on other sites
    Just now, bonienl said:

    I am with you there.

    Agreed

    Share this comment


    Link to comment
    Share on other sites

    will there be a way to rearrange the new dashboard? because the new layout seems less useful to me.

    Share this comment


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

    will there be a way to rearrange the new dashboard? because the new layout seems less useful to me.

    something like how it's done in pfsense would be nice eventually, but we've just now taken a quantum leap forward.

    Share this comment


    Link to comment
    Share on other sites

    Great work. Compliments to all!!!!

    it would be very usefull and extremely beautifull  to be able to rearrange, add /remove  boxes (tiles) in Dashboard .

    (as 1812 posted,  pfsense like)  . That way every Unraid Dashboard could be personalized!!   

    Keep the good work . Thanks again

    Share this comment


    Link to comment
    Share on other sites

    image.png.296ec81be56a51dc90f19674868d9e09.png

    i am the only one missing the icon for "Global Share Setting" in Settings?

    Share this comment


    Link to comment
    Share on other sites

    Clear your browser's cache or try a different browser.

    image.thumb.png.e83ab3a367589b084cd0a8b554a1565b.png

    Edited by bonienl
    • Like 1

    Share this comment


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

    Clear your browser's cache or try a different browser.

     

    That was it!

     

    Frist i try in Internet explorer and it was there. then i clear cache og was also back in chrome.

     

    If i see the site in Internet explorer the top text is not the right place. 

     

    image.png.8ab59b0347b91b3eacc73c4abf4a290f.png

    But who use explorer anyway so no problem:  :D

     

    Share this comment


    Link to comment
    Share on other sites

    Internet Explorer doesn't support the latest standards which are used in the GUI.

    If you insist to use a Microsoft product, you'll need to switch to Edge.

    Share this comment


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

    Internet Explorer doesn't support the latest standards which are used in the GUI.

    If you insist to use a Microsoft product, you'll need to switch to Edge.

    Not planing on that :) 

    Edited by Stef-dk

    Share this comment


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

    will there be a way to rearrange the new dashboard? because the new layout seems less useful to me.

     

    I was thinking about this too. The new dashboard contains what almost appears like panels. Having the ability to drag and drop the panels where you would like them would be very cool. Better yet would be the ability to customize what gets displayed in each panel and then arrange the data and the panels however you'd like. I'm sure many of you have seen other webui's like this and have an idea of what I'm talking about. Grafana is one product that does this real well.

    Share this comment


    Link to comment
    Share on other sites

    Updated to RC-1. Wanted to play with the TM via SMB.😁

    Looks like the broken pipe errors are gone at boot now.👍

    • Like 1

    Share this comment


    Link to comment
    Share on other sites
    Quote

    New vfio-bind method.  

    ...

    The script /usr/local/sbin/vfio-pci is called very early in system start-up, right after the USB flash boot device is mounted but before any kernel modules (drivers) have been loaded.  The function of the script is to bind each specified device to the vfio-pci driver, which makes them available for assignment to a virtual machine, and also prevents the Linux kernel from automatically binding them to any present host driver.

    @limetech could this be leveraged to change the default GPU (and presenting another) for the unraid GUI console?

    Share this comment


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

    @limetech could this be leveraged to change the default GPU (and presenting another) for the unraid GUI console?

    No, it's started very early in system start-up, but not early enough.

    • Upvote 1

    Share this comment


    Link to comment
    Share on other sites

    I updated a few minutes ago, and had to revert. 3 of my Western Digital Drives started reporting errors. I admittedly panicked and reverted the update before collecting anything. Reverting did resolve the issue. The alert I got read this: 

     

    Event: Unraid Disk 9 error
    Subject: Alert [servername] - Disk 9 in error state (disk missing)
    Description: No device identification ()
    Importance: alert

     

    These are all WD 8TB Drives model: WDC_WD80EFAX-68LHPN0 and WDC_WD80EMAZ-00WJTA0

    Share this comment


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

    I updated a few minutes ago, and had to revert. 3 of my Western Digital Drives started reporting errors. I admittedly panicked and reverted the update before collecting anything. Reverting did resolve the issue. The alert I got read this: 

     

    
    Event: Unraid Disk 9 error
    Subject: Alert [servername] - Disk 9 in error state (disk missing)
    Description: No device identification ()
    Importance: alert

     

    These are all WD 8TB Drives model: WDC_WD80EFAX-68LHPN0 and WDC_WD80EMAZ-00WJTA0

    What controller are they attached to?

    Share this comment


    Link to comment
    Share on other sites

    Hello @limetechand @eschultz...New dash looks awesome wondering if this current rc has the Mellanox Infiniband drivers baked in yet? I sent 5 cards for testing to get integrated last year and Eric said it might have to wait for 6.7.x

    thanks cant wait to try this but I dont have a spare server that isnt mission critical at this time and reports of cache pool failure and docker failure scares me a bit too much for RC1

    Share this comment


    Link to comment
    Share on other sites
    48 minutes ago, limetech said:

    What controller are they attached to?

    @limetechIt's the onboard controller from this motherboard and also from this PCIe controller:
    https://www.newegg.com/Product/Product.aspx?Item=N82E16815158365
    https://www.newegg.com/Product/Product.aspx?Item=N82E16813182933

     

    Intel Corporation C610/X99 series

    and

    Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller

     

    Does that help? I'm willing to share w/e you need to see :) 

     

    Edited by shinta148

    Share this comment


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

    Does that help? I'm willing to share w/e you need to see :) 

    diagnostics.zip are useful, would reveal if only drives on the Marvell controller dropped out.  Could be same issue as:

     

    Share this comment


    Link to comment
    Share on other sites

    Looks good changing the background header and txt.

     

    image.thumb.png.a1b5a4cd2ceda50e08a33667144e48b2.png

    Share this comment


    Link to comment
    Share on other sites
    On 1/22/2019 at 9:33 PM, Jcloud said:

       Just installed and no issues with install.  From LimeTech's feature listing I like the "under-the-hood" changes, and while I'm getting used to the new dashboard I like it. 

     

      My only initial criticism would be the banner info (top right-hand corner) and the first cell of the new dashboard is redundant information - then again, I've notice people have removed their banner, so this makes sense.  And yes, I know I can minimize the cell.  Second small criticism, I think that initial panel should have the Unraid version listed since it is listing banner info.

     

    Thank you for all your work!

     

    Unraid dashboard.jpg

    Do you mind sharing your banner? Thanks!

     

    Share this comment


    Link to comment
    Share on other sites

    Marvell 88SE9230 controller is not recognized my 3 disk offline

    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.