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



    I made a video on what the new 6.7.0 looks like etc. There is a mistake in this video where I talk about the webgui: VM manager: remove and rebuild USB controllers. What I thought it was, I found out after it was available in 6.6.6 as well so wasnt it !!

    Also shows how to upgrade to rc for those who don't know and downgrade again after if needs be. :)

     

    https://www.youtube.com/watch?v=qRD1qVqcyB8&amp;feature=youtu.be

     

    • Like 7

    Share this comment


    Link to comment
    Share on other sites

       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

    Share this comment


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

    I made a video on what the new 6.7.0 looks like etc. There is a mistake in this video where I talk about the webgui: VM manager: remove and rebuild USB controllers. What I thought it was, I found out after it was available in 6.6.6 as well so wasnt it !!

    Also shows how to upgrade to rc for those who don't know and downgrade again after if needs be. :)

     

    https://www.youtube.com/watch?v=qRD1qVqcyB8&amp;feature=youtu.be

     

    Thanks man, much appreciated!

    Share this comment


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

    I made a video on what the new 6.7.0 looks like etc. There is a mistake in this video where I talk about the webgui: VM manager: remove and rebuild USB controllers. What I thought it was, I found out after it was available in 6.6.6 as well so wasnt it !!

    Also shows how to upgrade to rc for those who don't know and downgrade again after if needs be. :)

     

    https://www.youtube.com/watch?v=qRD1qVqcyB8&amp;feature=youtu.be

     

    Very nice, thank you!  Added to original Announcement:

     

    • Like 1

    Share this comment


    Link to comment
    Share on other sites
    2 hours ago, 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

     

    yes, but when you aren't on the dashboard that banner info box is nice to have. so really the redundant one is in the dashboard but it does make it nice when you want to screen shot and you dont have to include all of the window just to include the stats. you can collapse the server info box and leave it like that where it only takes up a little room.

    Share this comment


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

    I made a video on what the new 6.7.0 looks like etc. There is a mistake in this video where I talk about the webgui: VM manager: remove and rebuild USB controllers. What I thought it was, I found out after it was available in 6.6.6 as well so wasnt it !!

    Also shows how to upgrade to rc for those who don't know and downgrade again after if needs be. :)

     

    https://www.youtube.com/watch?v=qRD1qVqcyB8&amp;feature=youtu.be

     

    man you have a lot of stuff going on your box.. whats the specs? (curious how whats needed for all those dockers/vm/etc)

    finally got to the part in the video where you are showing the dashboard and I can see the specs there :)

     

    I also agree about the blue color when the switch is toggled on (ex: dockers).

    Edited by zoggy

    Share this comment


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

    I made a video on what the new 6.7.0 looks like etc. There is a mistake in this video where I talk about the webgui: VM manager: remove and rebuild USB controllers. What I thought it was, I found out after it was available in 6.6.6 as well so wasnt it !!

    Also shows how to upgrade to rc for those who don't know and downgrade again after if needs be. :)

     

    https://www.youtube.com/watch?v=qRD1qVqcyB8&amp;feature=youtu.be

     

    Awesome video!

    Share this comment


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

    also agree about the blue color when the switch is toggled on

    By popular demand, I changed it back to blue ...

    • Like 2

    Share this comment


    Link to comment
    Share on other sites

    I would still like to see Bcache included as a kernel module:

     

    https://www.kernel.org/doc/Documentation/bcache.txt
     

    This is extremely useful for people that use unnasigned devices and can also be implemented with LVM.

    It has been considered stable and has been included within the Linux kernel source for a long time.

     

    In Unraid kernel .config
    # CONFIG_BCACHE is not set

    I struggle to recompile the unraid Linux kernel and would simply like to see this as a kernel module to make things easier (obviously the tools need not be included as not all users would ever need them).

    Thanks

    Share this comment


    Link to comment
    Share on other sites

    New UI Looks absolutely brilliant.

     

    So happy about the TimeMachine support over SMB :)

    Share this comment


    Link to comment
    Share on other sites

    Upgraded, all working perfectly. Happy to jump on a round of RC testing as I skipped the last few.

    Share this comment


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

    By popular demand, I changed it back to blue ...

     

    (I'm not trying to be awkward here, I swear, but:) wouldn't it make more sense, given the new theme, to change the colour to orange, or similar? Seems that's the accent colour you're going for. I think the complaint wasn't that it wasn't blue, but simply that it wasn't a different colour to the "off" state.

    Share this comment


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

    Seems that's the accent colour you're going for. I think the complaint wasn't that it wasn't blue, but simply that it wasn't a different colour to the "off" state.

    I think this is something we can try to take a closer look at. Maybe the switch itself should get a color change. 

    • Upvote 1

    Share this comment


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

    This is a possibility

    image.png.e8667cf721ee52c7685657bb70a38f88.png

    I think the blue color is the best.  The switches everywhere need to be included in the change to a color when on.

    Share this comment


    Link to comment
    Share on other sites

    Traditionally the ON state is green on these kinds of elements. But the way I see it we should just test and see what color works best on different backgrounds. I think the text-color should stay untouched for readability. The blue gets awfully dark on the black theme.

    Share this comment


    Link to comment
    Share on other sites
    37 minutes ago, Mex said:

    Traditionally the ON state is green on these kinds of elements. But the way I see it we should just test and see what color works best on different backgrounds. I think the text-color should stay untouched for readability. The blue gets awfully dark on the black theme.

    Looks pretty good to me.  No darker than the icons.

    1074621264_BlueSwitches.png.239329c83e586f01eb9cb81202aa712d.png

    Share this comment


    Link to comment
    Share on other sites

    Keep in mind that changes such as this causes me to have to do version checking in UD to determine which version of Unraid is running so I can determine the "On" color to use.  Between 6.6.6 and 6.7 there was a change in the drive used/free graphics that caused me to have to check the Unraid version to display the used/free graphics properly.  The LT team is always looking forward (this is a good thing), but I have to always look backwards to maintain compatibility with older versions of Unraid.  I don't mind some changes that make sense, but until the day that LT rolls UD into Unraid (probably not going to happen real soon) or I stop supporting older versions of Unraid (I really don't want to do this), I have to sort out backwards compatibility issues.  This takes time and I volunteer my efforts as do many others.

     

    For example.  This came from the drive used/free graphics change in 6.7 that I had to sort out yesterday.  It was quite confusing to me at first because I did not know there was a change.

    The font awesome icons are a good improvement in the UI experience and were backwards compatible to 6.4, so that was not a big deal.

     

    I agree that the switches should be highlighted, but they have been blue for as long as I can remember and now we have to change them?

     

    My point is try to minimize the changes just for change sake.  If a change really enhances Unraid, I will do what I can to accommodate.

    • Like 1
    • Upvote 1

    Share this comment


    Link to comment
    Share on other sites
    31 minutes ago, dlandon said:

    Looks pretty good to me.  No darker than the icons.

    1074621264_BlueSwitches.png.239329c83e586f01eb9cb81202aa712d.png

    This seems fine to me with regards to the switch itself, its the text I think is a bit to dark on black

    Share this comment


    Link to comment
    Share on other sites
    3 minutes ago, Mex said:

    This seems fine to me with regards to the switch itself, its the text I think is a bit to dark on black

    I understand.  Fortunately that is controlled by the style sheets built into Unraid and bonienl can tweak those and UD will follow.

    Share this comment


    Link to comment
    Share on other sites
    40 minutes ago, dlandon said:

    Looks pretty good to me.  No darker than the icons.

    1074621264_BlueSwitches.png.239329c83e586f01eb9cb81202aa712d.png

    The Problem with a darker shades of Blue on Black is the 'Brightness' setting of the individual monitor.  What is fine contrast on one monitor will be virtually black on another monitor.  Looking at the above screen capture, the "COMPLETE" lacks contrast and not easily read but the larger blue 'squares' are fine.  (Disclosure: I personally dislike black backgrounds.  I am 'old school' and want black ink on a white/off-white page!) 

    Share this comment


    Link to comment
    Share on other sites

    I think orange is a better choice of color over the blue. That's my 2 cents anyways. 😉

    Share this comment


    Link to comment
    Share on other sites

    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.

    Share this comment


    Link to comment
    Share on other sites
    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



    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.