• Unraid OS version 6.9.0-beta35 available


    limetech

    New in this release:


    GPU Driver Integration

    Unraid OS now includes selected in-tree GPU drivers: ast (Aspeed), i915 (Intel), amdgpu and radeon (AMD).  These drivers are blacklisted by default via 'conf' files in /etc/modprobe.d:

    /etc/modprobe.d/ast.conf
    /etc/modprobe.d/amdgpu.conf
    /etc/modprobe.d/i915.conf
    /etc/modprobe.d/radeon.conf

    Each of these files has a single line which blacklists the driver, preventing it from being loaded by the Linux kernel.

     

    However it is possible to override the settings in these files by creating the directory 'config/modprobe.d' on your USB flash boot device and then creating the same named-file in that directory.  For example, to unblacklist amdgpu type these commands in a Terminal session:

    mkdir /boot/config/modprobe.d
    touch /boot/config/modprobe.d/amdgpu.conf

    When Unraid OS boots, before the Linux kernel executes device discovery, we copy any files from /boot/config/modprobe.d to /etc/modprobe.d.  Since amdgpu.conf on the flash is an empty file, it will effectively cancel the driver from being blacklisted.

     

    This technique can be used to set boot-time options for any driver as well.

     

    Better Support for Third Party Drivers

    Recall that we distribute Linux modules and firmware in separate squashfs files which are read-only mounted at /lib/modules and /lib/firmware.  We now set up an overlayfs on each of these mount points, making it possible to install 3rd party modules at boot time, provided those modules are built against the same kernel version.  This technique may be used by Community Developers to provide an easier way to add modules not included in base Unraid OS: no need to build custom bzimage, bzmodules, bzfirmware and bzroot files.

     

    To go along with the other GPU drivers included in this release, we have created a separate installable Nvidia driver package.  Since each new kernel version requires drivers to be rebuilt, we have set up a feed that enumerates each driver available with each kernel.

     

    The easiest way to install the Nvdia driver, if you require it, is to make use of a plugin provided by Community member @ich777This plugin uses the feed to install the correct driver for the currently running kernel.  A big thank you! to @ich777 for providing assistance and coding up the the plugin:

     

    Linux Kernel

    This release includes Linux kernel 5.8.18.  We realize the 5.8 kernel has reached EOL and we are currently busy upgrading to 5.9.

     


     

    Version 6.9.0-beta35 2020-11-12 (vs -beta30)

    Base distro:

    • aaa_elflibs: version 15.0 build 25
    • brotli: version 1.0.9 build 2
    • btrfs-progs: version 5.9
    • ca-certificates: version 20201016
    • curl: version 7.73.0
    • dmidecode: version 3.3
    • ethtool: version 5.9
    • freetype: version 2.10.4
    • fuse3: version 3.10.0
    • git: version 2.29.1
    • glib2: version 2.66.2
    • glibc-solibs: version 2.30 build 2
    • glibc-zoneinfo: version 2020d
    • glibc: version 2.30 build 2
    • iproute2: version 5.9.0
    • jasper: version 2.0.22
    • less: version 563
    • libcap-ng: version 0.8 build 2
    • libevdev: version 1.10.0
    • libgcrypt: version 1.8.7
    • libnftnl: version 1.1.8
    • librsvg: version 2.50.1
    • libwebp: version 1.1.0 build 3
    • libxml2: version 2.9.10 build 3
    • lmdb: version 0.9.27
    • nano: version 5.3
    • ncurses: version 6.2_20201024
    • nginx: version 1.19.4
    • ntp: version 4.2.8p15 build 3
    • openssh: version 8.4p1 build 2
    • pam: version 1.4.0 build 2
    • rpcbind: version 1.2.5 build 2
    • samba: version 4.12.9 (CVE-2020-14318 CVE-2020-14318 CVE-2020-14318)
    • talloc: version 2.3.1 build 4
    • tcp_wrappers: version 7.6 build 3
    • tdb: version 1.4.3 build 4
    • tevent: version 0.10.2 build 4
    • usbutils: version 013
    • util-linux: version 2.36 build 2
    • vsftpd: version 3.0.3 build 7
    • xfsprogs: version 5.9.0
    • xkeyboard-config: version 2.31
    • xterm: version 361

    Linux kernel:

    • version 5.8.18
    • added GPU drivers:
    • CONFIG_DRM_RADEON: ATI Radeon
    • CONFIG_DRM_RADEON_USERPTR: Always enable userptr support
    • CONFIG_DRM_AMDGPU: AMD GPU
    • CONFIG_DRM_AMDGPU_SI: Enable amdgpu support for SI parts
    • CONFIG_DRM_AMDGPU_CIK: Enable amdgpu support for CIK parts
    • CONFIG_DRM_AMDGPU_USERPTR: Always enable userptr write support
    • CONFIG_HSA_AMD: HSA kernel driver for AMD GPU devices
    • kernel-firmware: version 20201005_58d41d0
    • md/unraid: version 2.9.16: correction recording disk info with array Stopped; remove 'superblock dirty' handling
    • oot: Realtek r8152: version 2.14.0

    Management:

    • emhttpd: fix 'auto' setting where pools enabled for user shares should not be exported
    • emhttpd: permit Erase of 'DISK_DSBL_NEW' replacement devices
    • emhtptd: track clean/unclean shutdown using file 'config/forcesync'
    • emhttpd: avoid unnecessarily removing mover.cron file
    • modprobe: blacklist GPU drivers by default, config/modprobe.d/* can override at boot
    • samba: disable aio by default
    • startup: setup an overlayfs for /lib/modules and /lib/firmware
    • webgui: pools not enabled for user shares should not be selectable for cache
    • webgui: Add pools information to diagnostics
    • webgui: vnc: add browser cache busting
    • webgui: Multilanguage: Fix unable to delete / edit users
    • webgui: Prevent "Add" reverting to English when adding a new user with an invalid username
    • webgui: Fix Azure / Gray Switch Language being cut-off
    • webgui: Fix unable to use top right icons if notifications present
    • webgui: Changed: Consistency between dashboard and docker on accessing logs
    • webgui: correct login form wrong default case icon displayed
    • webgui: set 'mid-tower' default case icon
    • webgui: fix: jGrowl covering buttons
    • webgui: New Perms: Support multi-cache pools
    • webgui: Remove WG from Dashboard if no tunnels defined
    • webgui: dockerMan: Allow readmore in advanced view
    • webgui: dockerMan: Only allow name compatible with docker

    Edited by limetech

    • Like 10
    • Thanks 5



    User Feedback

    Recommended Comments



    1 hour ago, trypowercycle said:

    Is anyone else having issues with their virtual machines disappearing from the dashboard after starting any of your VMs? 

    Known issue, see bug report

     

    Link to comment

    I've recently moved from stable to 6.9 beta 35 and found /dev/dri is missing. I've followed the instructions to un-blacklist the i915 driver but no luck. modprobe i915 command does nothing and I don't know what else to do, it was already working with Plex in ver 6.8.3... some details if may help to help:

     

    MOBO: ASUS ZPA10-D8 dual

    CPU: Dual XEON E5-2690 v.3 @ 2.6GHz

     

    Link to comment
    35 minutes ago, Koldo said:

    CPU: Dual XEON E5-2690

    i915 drivers are loaded and create /dev/dri for integrated GPUs

     

    Your CPUs do not have integrated GPUs and i915 /dev/dri is of no use to you.

     

    If you had hardware transcoding working with Plex (assuming that is what you are trying to accomplish), it was not through an iGPU with QuickSync Video support.

     

    You would need to use the Nvidia-Driver plugin and a discrete Nvidia GPU.

    Edited by Hoopster
    Link to comment

    Generally speaking is there an estimate on how long until 6.9.0 hits stable?

     

    I'm relatively new (6.8.3 was my first version) around here. I just happened to decide to install my unused 1060 into my Unraid server a couple of days after the major change to getting it working on Unraid. 

     

    I'm hesitant to go to the beta release but if 6.9.0 is likely a ways off from stable I may go ahead and do it. I just haven't gone through the upgrade process on Unraid yet ever and was planning to hold off on going to beta testing anything until I had gone through a stable upgrade at least once. 

    PS. I'm familiar enough with software dev release processes that I'm not asking for a firm date. Just a "probably a couple weeks" vs "couple months" vs "no way to know, could be a year" type of estimate. 

    Edited by Jahf
    Link to comment
    19 minutes ago, Jahf said:

    Generally speaking is there an estimate on how long until 6.9.0 hits stable?

    Before anyone else beats me to it:

     

    Soon™

    • Like 2
    • Haha 7
    Link to comment

    Next release of 6.9 will be on Linux 5.9 kernel, hopefully that will be it before we can go to 'stable' (because Linux 5.8 kernel was recently marked EOL).

    • Like 9
    Link to comment

    I've noticed I can't map directly to a pool disks.  I have a mirrored cache and a single ssd called system.  U used to be able to access them via \\tower\cache or \\tower\system.  Now I can't reach them,  Is this by design?  If so, is there anyway a user can revert back if they want too?  I have a few scripts and other setups throughout my network that look for the above paths that are now failing.

    Link to comment
    23 minutes ago, dalben said:

    I've noticed I can't map directly to a pool disks.  I have a mirrored cache and a single ssd called system.  U used to be able to access them via \\tower\cache or \\tower\system.  Now I can't reach them,  Is this by design?  If so, is there anyway a user can revert back if they want too?  I have a few scripts and other setups throughout my network that look for the above paths that are now failing.

    You would need to enable disk shares 

    • Thanks 3
    Link to comment
    3 hours ago, Squid said:

    You would need to enable disk shares 

    Thanks.  Found the setting, it was on Auto.  Set to Yes and all good now.

    • Thanks 1
    Link to comment
    6 hours ago, limetech said:

    Next release of 6.9 will be on Linux 5.9 kernel, hopefully that will be it before we can go to 'stable' (because Linux 5.8 kernel was recently marked EOL).

    Thanks. That's exactly the info I need to put "soon" in perspective :)

    Link to comment

    I must have missed it but was removing the Log column under Docker intentional? Now I have to click on the individual docker container to bring up the menu in order to view log. Still works but just annoying.

    Link to comment
    5 hours ago, nimaim said:

    I must have missed it but was removing the Log column under Docker intentional? Now I have to click on the individual docker container to bring up the menu in order to view log. Still works but just annoying.

    It was done to unify the interface between how the dashboard and the docker tab works

    • Like 1
    • Thanks 1
    Link to comment
    On 11/24/2020 at 12:13 AM, limetech said:

    Next release of 6.9 will be on Linux 5.9 kernel, hopefully that will be it before we can go to 'stable' (because Linux 5.8 kernel was recently marked EOL).

    Hopefully you fix the hdd temp problem for main view if a non standard driver is selected (or needed - automatically selected), as you stated in beta 25 i guess...xD

    Screenshot_20201125-091231_Chrome.thumb.jpg.621843ca2676d42292e541cf71696f7e.jpg

    Screenshot_20201125-090618_Chrome.thumb.jpg.8683e973fba2447e261dc40b202d9780.jpg

     

    Edited by DarkMan83
    • Like 1
    Link to comment
    11 hours ago, Squid said:

    It was done to unify the interface between how the dashboard and the docker tab works

    Is it also possible to add a entry in the popupmenu something like 'Force Update' so that you don't have to open the advanced view on the Docker page?

    Link to comment
    7 hours ago, DarkMan83 said:

    Hopefully you fix the hdd temp problem for main view if a non standard driver is selected (or needed - automatically selected), as you stated in beta 25 i guess...xD

    Please refresh my memory: what is the "hdd temp problem"?

    Link to comment
    6 hours ago, limetech said:

    Please refresh my memory: what is the "hdd temp problem"?

    Screenshot_20201125-230217_Chrome.thumb.jpg.a0c63a71eac91422c595c588d1f4758c.jpg

    But my HDD's in main view are still showing a "*" (Star) instead of the actual temp, temp in the ini file get's never updated.

    But as you can see, smart data has those temp values, but it is not standard controller type...

    Edited by DarkMan83
    Link to comment
    3 minutes ago, DarkMan83 said:

    my HDD's in main view are still showing a "*" (Star)

    According to your screenshot they are all spun down, so temp is unavailable. That is the way it has always worked for everyone.

    Link to comment
    56 minutes ago, trurl said:

    According to your screenshot they are all spun down, so temp is unavailable. That is the way it has always worked for everyone.

    i'm fully aware of my hdds in the Screenshot are in standby mode but this also applies for if non of the hdds are in standby...

    This was already discussed in another topic, so this was only a reminder that it's still not working...

    Before someone might ask again...

    Screenshot_20201125-234215_Chrome.thumb.jpg.a23b04d0ebf6bb83c3f1cd10eadfb128.jpg

    Edited by DarkMan83
    Link to comment
    2 hours ago, DarkMan83 said:

    but it is not standard controller type...

    If you click on the disk from Main, what are you selecting in "SMART Settings/SMART controller type"?

    Link to comment
    1 hour ago, limetech said:

    If you click on the disk from Main, what are you selecting in "SMART Settings/SMART controller type"?

    With my controller i can use "cciss" or "sat" ( where smartctl suggests "cciss" as you can see in the screen)...regardless which one i choose no temps in main. Smart data is working for me we with either of them.

     

    In another topic i can't remember it was already confirmed, that selecting a specific controller type (regardless which one) is ignored for the command that reads the temps, seems that the controller type value isn't properly used to build the command with the needed params...

    Edited by DarkMan83
    Link to comment
    15 minutes ago, DarkMan83 said:

    With my controller i can use "cciss" or "sat" ( where smartctl suggests "cciss" as you can see in the screen)...regardless which one i choose no temps in main. Smart data is working for me we with either of them.

     

    In another topic i can't remember it was already confirmed, that selecting a specific controller type (regardless which one) is ignored for the command that reads the temps, seems that the controller type value isn't properly used to build the command with the needed params...

    Ok, thank you.

    Link to comment

    I can confirm that in my mobo, upgrading from 6.8.3 everything is working flawlessly, the cpu governor and performance in general is better than ever and bluestacks is finally working in my VMs.

     

    Hardware: X470 GAMING PRO CARBON (MS-7B78) | AMD Ryzen 9 3900x NO OC  | Corsair Vengeance RGB Pro (4x16GB) DDR4 DRAM 2400MHz C16 | Geforce GTX 1060 3 GB, Intel 82576 Dual NIC
    Storage: Intel 660P NVME 1TB x 2 RAID-0 Cache | Seagate Barracuda 4 TB, 8 TB | Seagate IronWolf 4 TB
    Dockers: swag, Plex, Tautulli, NodeRed, MQTT, Wekan, Pydio, SageMath, Psono, ELK Stack, Sonarr, Radarr, Bazzar, TIG Stack
    VMs:  Windows 10, Windows Server 2019, MacOS Catalina, Ubuntu 20.0.4, pfSense

    • Thanks 1
    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • 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.