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


    User Feedback

    Recommended Comments



    Just now, Frank1940 said:

    Go to   Tools   >>>   Update OS    Change 'Branch' from "Stable" to "Next"

    Amazing grace so sweet. thank you so much.

    Share this comment


    Link to comment
    Share on other sites

    My system is hard locking anywhere from 4 hours to ~12 after startup. I am unable to reach it via ssh or a browser so my only recourse is to do a hard restart. I have attached the log files below as well as a screen shot of the dashboard when it locked overnight. I left the dashboard up before i went to bed so i could see what was happening and when everything locked. I came from 6.5.3 and had no issues previously.

    Unraid.PNG

    FCPsyslog_tail.txt

    mediaserver-diagnostics-20190122-0245.zip

    Share this comment


    Link to comment
    Share on other sites

    Ok, I got the upgrade done, but after about 10-20 minutes the system lost network.  I've got a console hooked up now so if it happens again I can do some digging...but it looks like something went wonky in the network setup (Server could not ping anything, and nothing could ping server).

    Share this comment


    Link to comment
    Share on other sites

    I upgraded with no game breaking issues so far.
    1 small bug or weird issue I notice is the free & used space of unassigned devices.


    I'm sure my 2tb drives don't have 2 Petabytes of free space. or my 120gb ssd have 121 TB of free space. Any idea's?

    unassidevi.PNG

    Share this comment


    Link to comment
    Share on other sites

    Yes that appears to be a bug probably in the Unassigned Devices plugin. I see the same thing. It is displaying TBs free on a disk with only GBs capacity.

     

    Share this comment


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

    Yes that appears to be a bug probably in the Unassigned Devices plugin. I see the same thing. It is displaying TBs free on a disk with only GBs capacity.

     

    Oh ! Good to know it's not just me. I'm sure they'll get to fixing that little bug soon then. The devices seem to run fine as my VM is starting fine from the SSD & i'm copying files now to the unattached 2tb drive at full gigabit speed

    Share this comment


    Link to comment
    Share on other sites
    15 minutes ago, Tybio said:

    Ok, I got the upgrade done, but after about 10-20 minutes the system lost network.  I've got a console hooked up now so if it happens again I can do some digging...but it looks like something went wonky in the network setup (Server could not ping anything, and nothing could ping server).

    Just lost net again, nothing in the syslog.  Might have to revert back to 6.6.0, anyone have any ideas for information to gather from CLI before I do so?

     

    Edit: Odd, I have eth0 (10GB card) as my main interface, but I also have eth2 connected (IPMI is shared on this) but "down" in the network config.  It came up that way, but now I'm seeing eth2 as "UP".  That might explain things as now I have 2 ethernet ports active on the same segment and (perhaps?) with the bridge setup I'm creating a loop that is getting blocked.

    Edited by Tybio

    Share this comment


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

    @limetech 

    I have these 2 nics as part of the motherboard

    
    [8086:1539] 04:00.0 Ethernet controller:
    [8086:1539] 06:00.0 Ethernet controller:

    I was using in the syslinux configuration:

    
    xen-pciback.hide=(06:00.0)

    to stop Unraid from using that nic for itself as it had the same id as another nic on the motherboard as above.

     

    I have upgraded to 6.7 yet the nic is still hidden from the OS and it passes through fine to the vm.

    So the is this something that works now. But this kernel option will no longer work

    in future/final 6.7 so we are moving to the config/vfio-pci.cfg file in preparation?

     

    We had reports that xen-pciback was no longer working and looking into it confirmed same issue on one of our test systems. @eschultz can provide more details.  Hiding devices like this on the kernel command line always seemed "hacky" (is that a word?) to me and putting this into a config file is going to make creating a proper UI for it much easier.  Using the 'config/vfio-pci.cfg' file is an additional method of achieving the same result.

    Share this comment


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

    The new dashboard and icons are great!

     

    add telegram notifications

     

    The GUI is missing the input line for 'chatid'. The only way for it to work is to manually create a file 'chatid' in /boot/config/telegram/ with the chatid number inside this file. 

    Right, forgot to add in OP that was added by @realies - updated.  I'm sure he'll address this.

    Share this comment


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

    You have to switch from the Stable branch to the Next branch.  This new release is an RC.

    Also there are instructions:

     

    • Like 1

    Share this comment


    Link to comment
    Share on other sites
    4 hours ago, 1812 said:

    Is it just me, or is the web gui a little bit faster?

    Could be differences in how Spectre mitigation is implemented in Linux 4.19 kernel vs. earlier.  These mitigations are still very much a work-in-process.

    Share this comment


    Link to comment
    Share on other sites
    58 minutes ago, TechnoBabble28 said:

    My system is hard locking anywhere from 4 hours to ~12 after startup. I am unable to reach it via ssh or a browser so my only recourse is to do a hard restart. I have attached the log files below as well as a screen shot of the dashboard when it locked overnight. I left the dashboard up before i went to bed so i could see what was happening and when everything locked. I came from 6.5.3 and had no issues previously.

    Unraid.PNG

    FCPsyslog_tail.txt

    mediaserver-diagnostics-20190122-0245.zip

    Please create a separate bug report for this.

    Share this comment


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

    My system is hard locking anywhere from 4 hours to ~12 after startup. I am unable to reach it via ssh or a browser so my only recourse is to do a hard restart. I have attached the log files below as well as a screen shot of the dashboard when it locked overnight. I left the dashboard up before i went to bed so i could see what was happening and when everything locked. I came from 6.5.3 and had no issues previously.

    Unraid.PNG

    FCPsyslog_tail.txt

    mediaserver-diagnostics-20190122-0245.zip

    Are you running a windows 10 VM with GPU Passthrew?  If so, I had this problem going from 5.6.0 to 6.6.0 threw 6.6.6 and it was Windows 10 VM that was at fault.  Here is my bug report and what I did to fix it. 

     

    Edited by Rudder2

    Share this comment


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

    Correct.  I would be interested in your results doing exactly that and verify that everything works correctly.  re: the Signal processor: It is my understanding that for proper operation all the devices of an IOMMU group must be isolated (bound to vfio-pci) or none of them.  Maybe you can move that USB controller to another slot in order to put into its own IOMMU group?

    ok, i did it like described and all working fine here, both vm´s running smooth with nvidia and their usb controllers

     

    only thing not working seems tobe the openvpn server plugin but thats surely not related to this.

     

    about splitting, its one of the onboard ones ... so no chance to move into another slot ;) (i have 2, 1st for unraid usb key, 2nd for workstation vm) i cannot isolate it but i see all running here ...

     

    i attached my system log in case of interest ...

    alsserver-syslog-20190122-1831.zip

    Share this comment


    Link to comment
    Share on other sites

    Updated only issue so far SNMP plugin fails. Tries removing and installing and install fails. Have posted on the SNMP plugin.

     

    Nerd pack also having issues.

    Edited by SimonF

    Share this comment


    Link to comment
    Share on other sites
    Quote

    Are you running a windows 10 VM with GPU Passthrew?  If so, I had this problem going from 5.6.0 to 6.6.0 threw 6.6.6 and it was Windows 10 VM that was at fault.  Here is my bug report and what I did to fix it. 

     

    I don't run any VM's, this is purely just a media server running Plex and a couple supporting dockers.

     

     

    Edited by TechnoBabble28

    Share this comment


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

    ok, i did it like described and all working fine here, both vm´s running smooth with nvidia and their usb controllers

    Thank you for the report.

    Share this comment


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

     

    I don't run any VM's, this is purely just a media server running Plex and a couple supporting dockers.

     

     

    I noticed from your screenshot that you are running a Ryzen 1700.  These Ryzens are famous for hard locks since day 1.  I believe that the core problem was traced down to idle power use being so low that it causes a mismatch between different power rails on many power supplies, causing things get wonky and then the system locks up.  There have been multiple fixes, from disabling C-States, Unraid config file parameters, and the best solution being enabling the power supply compensation setting in your BIOS (if your BIOS has this - mine does not).  I am currently using the settings in my config file.

     

    Typically these Ryzen machines lock up only when idle, as that's when they can enter the lower power states that lead to the problem.  Your usage matches this.  Your time-frame to lockup is also very indicative of this issue.

     

    I have noticed that different Unraid releases seem more/less susceptible to this issue.  Perhaps the latest 6.7 release with 4.19 is more susceptible - maybe the new code is so efficient it is idling better.

     

    The fixes for this are outside the scope of this thread.  Just wanted to make sure you were aware - sorry if you already knew all this.  With a fix in place, the hard lock is completely resolved.

     

    Of course, this may not be your issue at all, and like Tom said you need to open a bug report.

     

    Paul

    Share this comment


    Link to comment
    Share on other sites

    Upgraded, Only issue is my VPN will not start, posted on the plugin page. New layout looks good!!

     

    openvpn: error while loading shared libraries: libcrypto.so.l: cannot open shared object file: No such file or directory

    openvpn: error while loading shared libraries: libcrypto.so.l: cannot open shared object file: No such file or directory

     

    Edited by clowrym

    Share this comment


    Link to comment
    Share on other sites

    Update on my Ryzen 1800X still runing fine. 

    The new look are really nice. GOOD work!

     

    One thing. 

    OpenVPN-as don't work after update. It can't find iptables. it get that from a modul on the host. Maybe there is coming a update of the images soon. 

     

    The openvpn dokumentation say i need the following on the host. 

    modprobe ipt_mark

    modprobe ipt_MARK

    modprobe tun

    i can't find the frist 2 (ipt_mark, ipt_MARK)

     

    *** Update after some trying. I got it to work. *** 

    Change in the Container

    Network Type: from HOST to Brigde

    INTERFACE:  from BOND0 to ETH0

    Hopes this helps somebody :)

    Edited by Stef-dk

    Share this comment


    Link to comment
    Share on other sites

    Apologies if this is the wrong place to ask but is SAS drive still not fully supported ( sleep not working). Just wondering if it's in the works, a workaround is available or just have to stick with leaving the drives on while the sata disks go to sleep. 
    Thank you

    Share this comment


    Link to comment
    Share on other sites

    Everything all good with my 2700x system after updating. Changed VMs to qemu 3.1 and its booted right up. usb pcie card passthrough still working along with all the other things. 

    Share this comment


    Link to comment
    Share on other sites
    Quote

    Array has 5 utilization warnings.

    any way to make to change that on the dashboard from 'warning'+'error' to just 'error' ?

    made me think oh crap something bad.. but no I just have a few drives over 70% because of split folders

    Share this comment


    Link to comment
    Share on other sites

    minor cosmetic bug:

     

    firefox_2019-01-22_13-50-14.png

     

    can see that on the dashboard it just displays the bios version but on the system info modal you incert "- v" before it.

    Share this comment


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

    any way to make to change that on the dashboard from 'warning'+'error' to just 'error' ?

    Sorry, it is not clear to me what you like to see.

    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.