• 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



    3 hours ago, S1dney said:

    Can't wait for this to reach a stable release.

    6.8.3 is a stable release and there's a prebuilt image with NVIDIA 450.66 available. Just copy an handful of files over to the stick and reboot. That's all.

     

     

    Edited by hawihoney
    Link to comment
    On 11/16/2020 at 5:13 AM, sir_storealot said:

    Hi, I want to use i915 IGPU acceleration in docker. Does it mean I should disable the stuff I have added to my go file before I upgrade to new beta:

     

    
    modprobe i915
    sleep 5
    chmod -R 777 /dev/dri
    chown -R nobody:users /dev/dri

     

    I'm also curious.

     

    This line in the release notes, best I can tell, does not suggest i915 wasn't included in previous releases, only that it's among those now included - otherwise the modprobe command wouldn't have worked in previous releases, right?

    Quote

    Unraid OS now includes selected in-tree GPU drivers: ast (Aspeed), i915 (Intel), amdgpu and radeon (AMD). 

    If so there's a new way to load it but the earlier way also works. I confirmed by upgrading, rebooting (without changing the go file) and testing the Emby docker.

    Link to comment
    Quote

    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.

     

    As an old computer user (1981 with a RS Color Computer) who has just enough exposure as to how operating systems function, I kinda understand what to do from this limited set of instructions.  (I also realize that the devil is always in the details. Installing the driver is probably only the first step to what must be done to fully utilize the driver.)  I am also presuming that these mentioned GPU drivers would normally be found in most Linux distributions and, if the hardware associated with one of these GPU drivers was detected when Linux is being installed, the appropriate driver would be installed and made ready for use.

     

    I realize that this a beta release and many features that could/(should) be included in the final release may not be there but I feel that you should be considering the person who wants a straightforward install of all the features he wants without resorting to the command line. 

     

    What I think is needed is a 'Video Setup' icon in the Settings menu which would allow the user to decide whether he wants to include a video driver in his Unraid setup.   If he decides to include a video driver, I would hope that on reboot, the install process would detect and install the proper driver.  If that can't be done, at least, allow the user to chose which driver to install and have a background script do the heavy lifting.  

     

    EDIT:  One more thing.  There should also be detailed information on exactly what GPU hardware each of these drivers support.  i915.conf does not really provide any information as to hardware is actually supported!

    Edited by Frank1940
    • Like 4
    Link to comment
    2 minutes ago, chocorem said:

    Could anybody help me to find out the reason ?

    Possibly unrelated but should be fixed anyway, you have an unassigned disk (WD40EFRX-68WT0N0 s/n WCC4E4JNHYEC) generating a lot of ATA errors, if it's not being used disconnect it, if it is replace cables, also the LSI is on a very old firmware, you should update it.

     

    Link to comment
    2 hours ago, Frank1940 said:

    As an old computer user (1981 with a RS Color Computer) who has just enough exposure as to how operating systems function, I kinda understand what to do from this limited set of instructions.  (I also realize that the devil is always in the details. Installing the driver is probably only the first step to what must be done to fully utilize the driver.)  I am also presuming that these mentioned GPU drivers would normally be found in most Linux distributions and, if the hardware associated with one of these GPU drivers was detected when Linux is being installed, the appropriate driver would be installed and made ready for use.

     

    I realize that this a beta release and many features that could/(should) be included in the final release may not be there but I feel that you should be considering the person who wants a straightforward install of all the features he wants without resorting to the command line. 

     

    What I think is needed is a 'Video Setup' icon in the Settings menu which would allow the user to decide whether he wants to include a video driver in his Unraid setup.   If he decides to include a video driver, I would hope that on reboot, the install process would detect and install the proper driver.  If that can't be done, at least, allow the user to chose which driver to install and have a background script do the heavy lifting.  

     

    EDIT:  One more thing.  There should also be detailed information on exactly what GPU hardware each of these drivers support.  i915.conf does not really provide any information as to hardware is actually supported!

    Good points all, but a couple of observations.....

     

    Typical (traditional?) software release schedules consider betas to be functionally complete, and are provided for testing and big fixes only. Limetech don't seem to follow this, and the beta cycle becomes more of an extended alpha with new bits being added all the time. This is likely the root cause of the often unfeasibly long beta cycles, and why they don't talk about release schedules - you cant predict them with this methodology. 

     

    I'd prefer to see scope-limited releases with fixed feature sets, tested efficiently and released on a more regular basis. I think this would also help grow adoption as new users see a healthy, vibrant platform with regular updates and new feature additions.

     

    The second point is, historically, unRaid tends to get new features in a rough & ready manner, something like this release. It works, but requires a degree of pfaffing about in config files and the like to get it set up. The UI tends to follow a release or 2 later when the feature & functionality settles down.

     

    I recall being about for the birth of VMs, when not only did we need to hand code all the VM XML files, but Limetech changed the VM engine very late in the day, and a lot of the knowledge and skill early adopters had built up had to be thrown out and re-learned. For such reasons, it makes sense that they don't focus on a smooth UI early on - if the underlying implementation needs to be re-factored, that would be a waste of work.

     

    Link to comment

    What happens to current setup after upgrading. I currently use Intel quicksinc and the go configuration file to have the gpu detected. I'm assuming I don't to make changes. 

     

    On a side note I've read the comments of what's going down. I hope it gets better, it would be bad to see how unraid has grown so much, to leave it for lack of support in certain apps. The community apps and the external plugins is what drove me to use it in the first place. Hope everything goes back to normal

    Link to comment
    5 minutes ago, meep said:

     

    Typical (traditional?) software release schedules consider betas to be functionally complete, and are provided for testing and big fixes only. Limetech don't seem to follow this, and the beta cycle becomes more of an extended alpha with new bits being added all the time. This is likely the root cause of the often unfeasibly long beta cycles, and why they don't talk about release schedules - you cant predict them with this methodology. 

     

    As I recall, this is the first time that LimeTech has released a beta to the general public.  In the past, they have putout a  release candidate (rc)  prior to the final release of a major update.  (The first rc release seems to be preceded in most cases by a closed beta cycle involving people who seem to have a NDA.)  This release cycle has often been long and involved (with sometimes much discussion about the process) but I will  not get into that here.  LimeTech is much better than many software companies today.  They seem to continue the development process on each stable release until every known bug has been squashed before that version is released!  This tends to make for very long release cycles with no insight as to its release date since that is determined by the point in time when bugs are gone. 

    Link to comment

    For some reason, my dockers are no longer "clickable" on the dashboard since this most recent beta. Also, my pfSense (FreeBSD) VM does not show up on my dashboard at all. My Windows 10 VM shows up, but not my running pfSense VM. They are accessible from the VM tab or Docker tab though. Both of these issues only show up in most recent update. 

    Link to comment
    1 minute ago, Haroldkidd said:

    So how do you upgrade, I'm not getting an update from tools on my unraid server. 

    In OS Update tool, switch branch from Stable to Next and the install option will appear.

    Link to comment
    3 hours ago, Psycho249 said:

    For some reason, my dockers are no longer "clickable" on the dashboard since this most recent beta. Also, my pfSense (FreeBSD) VM does not show up on my dashboard at all. My Windows 10 VM shows up, but not my running pfSense VM. They are accessible from the VM tab or Docker tab though. Both of these issues only show up in most recent update. 

    Just stop your VM's and all dockers clickable again...*joking*

    Try not to use the dashboard for this,until the bug is fixed, since this is a beta, it's expected to have bugs...

    Link to comment
    6 minutes ago, DarkMan83 said:

    Just stop your VM's and all dockers clickable again...*joking*

    Try not to use the dashboard for this,until the bug is fixed, since this is a beta, it's expected to have bugs...

    Or go to Settings - Display Settings and change "Show Dashboard apps" to "Docker only". Then Dockers on Dashboard work but you will have to go to VMS page to work with your VMs.

    Link to comment

    After upgrading to 6.9.0-b35, nothing is being logged or displayed in any of the system event logs.

    Edited by Holytoledo
    Link to comment
    11 hours ago, Frank1940 said:

    What I think is needed is a 'Video Setup' icon in the Settings menu which would allow the user to decide whether he wants to include a video driver in his Unraid setup.   If he decides to include a video driver, I would hope that on reboot, the install process would detect and install the proper driver.  If that can't be done, at least, allow the user to chose which driver to install and have a background script do the heavy lifting.  

     

    EDIT:  One more thing.  There should also be detailed information on exactly what GPU hardware each of these drivers support.  i915.conf does not really provide any information as to hardware is actually supported!

    Can't agree with you more, it's helpful to beginners of unraid.

    Edited by rallos_hoo
    Link to comment

    I haven't yet spun up a second server/instance to test the beta, but wanted to ask. Has the autostart VM issue been fixed from 6.8.3?

     

    I have no idea if this hasn't been addressed, or if it was fixed in this, or a previous beta, but on 6.8.3, "autostart" VMs don't actually autostart on boot. I have to manually start them.

    Link to comment
    20 minutes ago, TechGeek01 said:

    I haven't yet spun up a second server/instance to test the beta, but wanted to ask. Has the autostart VM issue been fixed from 6.8.3?

     

    I have no idea if this hasn't been addressed, or if it was fixed in this, or a previous beta, but on 6.8.3, "autostart" VMs don't actually autostart on boot. I have to manually start them.

    well, i dont think this was a general issue, autostart always worked here as sample and never been a issue lately.

    Link to comment
    40 minutes ago, TechGeek01 said:

    I have no idea if this hasn't been addressed, or if it was fixed in this, or a previous beta, but on 6.8.3, "autostart" VMs don't actually autostart on boot. I have to manually start them.

    No problem here with a Debian VM on beta35, start's just fine on boot.

    • Like 1
    Link to comment
    47 minutes ago, TechGeek01 said:

    I have no idea if this hasn't been addressed, or if it was fixed in this, or a previous beta, but on 6.8.3, "autostart" VMs don't actually autostart on boot. I have to manually start them.

    VMs only autostart if the array is also set to autostart, and that's done on purpose.

    Link to comment

    @limetech, any chance this is fixed in beta35? I can't chance it as I wont have a recourse back to nvidia drivers since the old plugins are dead in the water so I don't want to change bumping up to then have to go back without a way to go to the nvidia driver sets.

     

    "Thanks, yes that explains it.  Probably, with -beta25 and even earlier releases, if you click on the device from Main and then look at 'Partition format' it will say 'GPT: 4KiB-aligned (factory erased)' - that (factory erased) shouldn't be there.  Will fix for next release."

    Link to comment

    HI, I could use a little hand holding please, I've been left out in the cold

    How do i get the nVidia drivers installed

    I've seen this link mentioned 

     

    https://raw.githubusercontent.com/ich777/unraid-nvidia-driver/master/nvidia-driver.plg

     

    I've been searching but can't find any explanation (just a bunch of people arguing)

    I have been using the LinixServer.io nVidia builds for a while (now it's depreciated, no explanation just a "i quit" statement)

     

    I think a guide would be helpful somewhere either on the beta 35 build page or maybe a final post on the LinixServer.io page for plebs like me he are confused and left without a path.

     

    I'm a point and click pleb so if someone could tell me what to type and where that would be great

    (I'm sure there are a few of us in this position so I'm guessing these instructions should be somewhere easy to find.)

     

    Thank you in advance.

    Link to comment
    22 hours ago, hawihoney said:

    6.8.3 is a stable release and there's a prebuilt image with NVIDIA 450.66 available. Just copy an handful of files over to the stick and reboot. That's all.

     

     

    I know haha, but I'm waiting for the upgraded kernel ;)

    I'm still on the latest build that had the 5+ kernel included.

    Link to comment
    10 minutes ago, mdrodge said:

    HI, I could use a little hand holding please, I've been left out in the cold

    How do i get the nVidia drivers installed

    I've seen this link mentioned 

     

    https://raw.githubusercontent.com/ich777/unraid-nvidia-driver/master/nvidia-driver.plg

     

    I've been searching but can't find any explanation (just a bunch of people arguing)

    I have been using the LinixServer.io nVidia builds for a while (now it's depreciated, no explanation just a "i quit" statement)

     

    I think a guide would be helpful somewhere either on the beta 35 build page or maybe a final post on the LinixServer.io page for plebs like me he are confused and left without a path.

     

    I'm a point and click pleb so if someone could tell me what to type and where that would be great

    (I'm sure there are a few of us in this position so I'm guessing these instructions should be somewhere easy to find.)

     

    Thank you in advance.

    Could this be what you are looking for?  

     

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