Jump to content
  • Unraid OS version 6.9.0-beta25 available


    limetech

    6.9.0-beta25 vs. -beta24 Summary:

    • fixed emhttpd crash resulting from having NFS exported disk shares
    • fixed issue where specifying 1 MiB partition alignment was being ignored (see 1 MiB Partition Alignment below)
    • fixed spin-up/down issues
    • ssh improvements (see SSH Improvements below)
    • kernel updated from 5.7.7 to 5.7.8
    • added UI changes to support new docker image file handling - thank you @bonienl.  Refer also to additional information re: docker image folder, provided by @Squid under Docker below.
    • known issue: "Device/SMART Settings/SMART controller type" is ignored, will be fixed in next release

     

    Important: Beta code is not fully tested and not feature-complete.  We recommend running on test servers only!

     

    Multiple Pools

    This features permits you to define up to 35 named pools, of up to 30 storage devices/pool.  The current "cache pool" is now simply a pool named "cache".  Pools are created and managed via the Main page.

     

    Note: When you upgrade a server which has a cache pool defined, a backup of config/disk.cfg will be saved to config/disk.cfg.bak, and then cache device assignment settings are moved out of disk.cfg and into a new file, config/pools/cache.cfg.  If later you revert back to a pre-6.9 Unraid OS release you will lose your cache device assignments and you will have to manually re-assign devices to cache.  As long as you reassign the correct devices, data should remain intact.

     

    When you create a user share, or edit an existing user share, you can specify which pool should be associated with that share.  The assigned pool functions identically to current cache pool operation.

     

    Something to be aware of: when a directory listing is obtained for a share, the unRAID array disk volumes and all pools which contain that share are merged in this order:

      pool assigned to share

      disk1

      :

      disk28

      all the other pools in strverscmp() order.

     

    As with the current "cache pool", a single-device pool may be formatted with either xfs, btrfs, or reiserfs.  A multiple-device pool may only be formatted with btrfs.  A future release will include support for multiple "unRAID array" pools.  We are also considering zfs support.

     

    Something else to be aware of: Suppose you have a 2-device btrfs pool. This will be what btrfs calls "raid1" and what most people would understand to be "mirrored disks". Well this is mostly true in that the same data exists on both disks but not necessarily at the block-level.  Now suppose you create another pool, and what you do is unassign one of the devices from the existing 2-device btrfs pool and assign it to this new pool - now you have x2 single-device btrfs pools.  Upon array Start you might understandably assume there are now x2 pools with exactly the same data.  However this is not the case. Instead, when Unraid OS sees that a btrfs device has been removed from an existing multi-device pool, upon array Start it will do a 'wipefs' on that device so that upon mount it will not be included in the old pool.  This of course effectively deletes all the data on the moved device.

     

    1 MiB Partition Alignment

    We have added another partition layout where the start of partition 1 is aligned on 1 MiB boundary. That is, for devices which present 512-byte sectors, partition 1 will start in sector 2048; for devices with 4096-byte sectors, in sector 256.  This partition type is now used for all non-rotational storage (only).

     

    It is not clear what benefit 1 MiB alignment offers.  For some SSD devices, you won't see any difference; others, perhaps big performance difference.  LimeTech does not recommend re-partitioning an existing SSD device unless you have a compelling reason to do so (or your OCD just won't let it be).

     

    To re-partition a SSD it is necessary to first wipe out any existing partition structure on the device.  Of course this will erase all data on the device.  Probably the easiest way to accomplish this is, with array Stopped, identify the device to be erased and use the 'blkdiscard' command:

    blkdiscard /dev/xxx  # for exmaple /dev/sdb or /dev/nvme0n1 etc)

            WARNING: be sure you type the correct device identifier because all data will be lost on that device!

     

    Upon next array Start the device will appear Unformatted, and since there is now no partition structure, Unraid OS will create it.

     

    Language Translation

    A huge amount of work and effort has been implemented by @bonienl to provide multiple-language support in the Unraid OS Management Utility, aka, webGUI.  There are several language packs now available, and several more in the works.  Thanks to @Squid, language packs are installed via the Community Applications plugin - look for a new category entitled Language.

     

    Note: Community Applications must be up to date to install languages.  See also here.

     

    Each language pack exists in public Unraid organization github repos.  Interested users are encouraged to clone and issue Pull Requests to correct translations errors.  Language translations and PR merging is managed by @SpencerJ.

     

    Linux Kernel

    Upgraded to 5.7.

     

    These out-of-tree drivers are currently included:

    • QLogic QLGE 10Gb Ethernet Driver Support (from staging)
    • RealTek r8125: version 9.003.05 (included for newer r8125)
    • HighPoint rr272x_1x: version v1.10.6-19_12_05 (per user request)

    Note that as we update the Linux kernel, if an out-of-tree driver no longer builds, it will be omitted.

     

    These drivers are currently omitted:

    • Highpoint RocketRaid r750 (does not build)
    • Highpoint RocketRaid rr3740a (does not build)
    • Tehuti Networks tn40xx (does not build)

    If you require one of these drivers, please create a Bug Report and we'll spend some time looking for alternatives.  Better yet, pester the manufacturer of the controller and get them to update their drivers.

     

    Base Packages

    All updated to latest versions.  In addition, Linux PAM has been integrated.  This will permit us to implement 2-factor authentication in a future release.

     

    Docker

    Updated to version 19.03.11

     

    It's now possible to select different icons for multiple containers of the same type.  This change necessitates a re-download of the icons for all your installed docker applications.  A delay when initially loading either the dashboard or the docker tab while this happens is to be expected prior to the containers showing up.

     

    We also made some changes to add flexibility in assigning storage for the Docker engine.  First, 'rc.docker' will detect the filesystem type of /var/lib/docker.  We now support either btrfs or xfs and the docker storage driver is set appropriately.

     

    Next, 'mount_image' is modifed to support loopback formatted either with btrfs or xfs depending on the suffix of the loopback file name.  For example, the file name ends with ".img", as in "docker.img" then we use mkfs.btrfs.  If file name ends with "-xfs.img", as in "docker-xfs.img" then we use mkfs.xfs.


    We also added the ability to bind-mount a directory instead of using a loopback.  If file name does not end with ".img" then code assumes this is the name of directory (presumably on a share) which is bind-mounted onto /var/lib/docker.

     

    For example, if "/mnt/user/system/docker/docker" then we first create, if necessary the directory "/mnt/user/system/docker/docker".  If this path is on a user share we then "dereference" the path to get the disk path which is then bind-mounted onto /var/lib/docker.  For exmaple, if "/mnt/user/system/docker/docker" is on "disk1", then we would bind-mount "/mnt/disk1/system/docker/docker".  Caution: the share should be cache-only or cache-no so that 'mover' will not attempt to move the directory, but the script does not check this.

     

    Additional information from user @Squid:

     

    Quote

    Just a few comments on the ability to use a folder / share for docker

     

    If you're one of those users who continually has a problem with the docker image filling up, this is the solution, as the "image" will be able to expand (and shrink) to the size of the asigned share.  Just be aware though that this new feature is technically experimental.  (I have however been running this on an XFS formatted cache drive for a while now, and don't see any problems at all)

     

    I would recommend that you use a share that is dedicated to the docker files, and not a folder from another existing share (like system as show in the OP).  

     

    My reasoning for this is that:

    1. If you ever have a need to run the New Permissions tool against the share that you've placed the docker folder into, then that tool will cause the entire docker system to not run.  The folder will have to be removed (via the command line), and then recreated.

    2. All of the folders contained within the docker folder are not compatible with being exported over SMB, and you cannot gain access to them that way.  Using a separate share will also allow you to not export it without impacting the other shares' exporting.  (And there are no "user-modifiable" files in there anyways.  If you do need to modify a file within that folder, (ie: a config file for a container and that config isn't available within appdata), you should be doing it via going to the container's shell)

    You definitely want the share to be cache-only or cache-no (although cache-prefer should probably be ok).  Setting it to cache:yes will undoubtedly cause you problems if mover winds up relocating files to the array for you.

     

    I did have some "weirdness" with using a Unassigned Device as the drive for the docker folder.  This may however been a glitch in my system.

     

    Fix Common Problems (and the Docker Safe New Permissions Tool) will wind up getting updated to let you know of any problems that it detects with how you've configured the folder.

     

    Virtualization

    libvirt updated to version 6.4.0

    qemu updated to version 5.0.0

     

    In addition, integrated changes to System Devices page by user @Skitals with modifications by user @ljm42.  You can now select PCI devices to isolate from Linux upon boot simply by checking some boxes.  This makes it easier to reserve those devices for assignment to VM's.

     

    Note: If you had the VFIO-PCI Config plugin installed, you should remove it as that functionality is now built-in to Unraid OS 6.9.  Refer also @ljm42's excellent guide.

     

    In a future release we will include the NVIDIA and AMD GPU drivers natively into Unraid OS.  The primary use case is to facilitate accelerated transcoding in docker containers.  For this we require Linux to detect and auto-install the appropriate driver.  However, in order to reliably pass through an NVIDIA or AMD GPU to a VM, it's necessary to prevent Linux from auto-installing a GPU driver for those devices upon boot, which can be easily done now through System Devices page.  Users passing GPU's to VM's are encouraged to set this up now.

     

    "unexpected GSO errors"

    If your system log is being flooded with errors such as:

    Jun 20 09:09:21 Tower kernel: tun: unexpected GSO type: 0x0, gso_size 31, hdr_len 66

    You need to edit each VM and change the model type for the Ethernet bridge from "virtio" to "virtio-net".  In most cases this can be accomplished simply by clicking Update in "Form View" on the VM Edit page.  For other network configs it may be necessary to directly edit the xml.  Example:

    <interface type='bridge'>
          <mac address='xx:xx:xx:xx:xx:xx'/>
          <source bridge='br0'/>
          <model type='virtio-net'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>

     

    SSH Improvements

    There are changes in /etc/ssh/sshd_conf to improve security (thanks to @Mihai and @ljm42 for suggestions):

    • only root user is permitted to login via ssh (remember: no traditional users in Unraid OS - just 'root')
    • non-null password is now required
    • non-root tunneling is disabled

     

    In addition, upon upgrade we ensure the 'config/ssh/root' directory exists on the USB flash boot device; and, we have set up a symlink: /root/.ssh to this directory.  This means any files you might put into /root/.ssh will be persistent across reboots.

     

    Note: if you examine the sshd startup script (/etc/rc.d/rc.sshd), upon boot all files from the 'config/ssh' directory are copied to /etc/ssh (but not subdirs).  The purpose is to restore the host ssh keys; however, this mechanism can be used to define custom ssh_conf and sshd_conf files (not recommended).

     

    Other

    • AFP support has been removed.
    • Numerous other Unraid OS and webGUI bug fixes and improvements.

     


    Version 6.9.0-beta25 2020-07-12

    Linux kernel:

    • version 5.7.8

    Management:

    • fix emhttpd crash resulting from exporting NFS disk share(s)
    • fix non-rotational device partitions were not actually being 1MiB aligned
    • dhcpcd: ipv6: use slaac hwaddr instead of slaac private
    • docker: correct storage-driver assignemnt logic
    • ssh: allow only root user, require passwords, disable non-root tunneling
    • ssh: add /root/.ssh symlink to /boot/config/ssh/root directory
    • syslog: configure to also listen on localhost udp port 514
    • webgui: Added btrfs info for all pools in diagnostics
    • webgui: Docker: allow BTRFS or XFS vdisk, or folder location
    • webgui: Multi-language: Fixed regression error: missing indicator for required fields
    • webgui: Dashboard: fix stats of missing interface
    • Like 2
    • Thanks 3


    User Feedback

    Recommended Comments



    Exact same situation for me with a Windows 10 VM!

    Hope Qemu 5.1 will fix this

    Edited by SA3285

    Share this comment


    Link to comment
    Share on other sites
    On 7/20/2020 at 8:17 AM, ctab579 said:

    Today I attempted to upgrade to Beta25, and unfortunately, the only VM I run would not start. The VM is a Ubuntu server 18.04.4. This VM has my iGPU from my 8700K passed through used for jellyfin.

    23 minutes ago, SA3285 said:

    Exact same situation for me with a Windows 10 VM!

    Make sure you have updated machine type in VM settings to latest version.

    I had to do this before my win10 VM created in 6.8.3 would start.

    Share this comment


    Link to comment
    Share on other sites

    Not sure if its been raised but I'm still having to do this mod to xml to get windows 10 vm to boot without a BSOD kernal error. Found a random thread with a solution to the BSOD.

    I don't know what this does or why its needed? Seems like it might be a ZEN 2 issue? has been there since beta22

     

    From This

     <cpu mode='host-passthrough' check='none'>
        <topology sockets='1' dies='1' cores='4' threads='2'/>
        <cache mode='passthrough'/>
        <feature policy='require' name='topoext'/>
      </cpu>

     

     

    To This

     <cpu mode='host-model' check='none'>
        <topology sockets='1' dies='1' cores='4' threads='2'/>
        <feature policy='require' name='topoext'/>
      </cpu>

     

    Share this comment


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

    Not sure if its been raised but I'm still having to do this mod to xml to get windows 10 vm to boot without a BSOD kernal error. Found a random thread with a solution to the BSOD.

    I don't know what this does or why its needed? Seems like it might be a ZEN 2 issue? has been there since beta22

     

    From This

     <cpu mode='host-passthrough' check='none'>
        <topology sockets='1' dies='1' cores='4' threads='2'/>
        <cache mode='passthrough'/>
        <feature policy='require' name='topoext'/>
      </cpu>

     

     

    To This

     <cpu mode='host-model' check='none'>
        <topology sockets='1' dies='1' cores='4' threads='2'/>
        <feature policy='require' name='topoext'/>
      </cpu>

     

    Thanks for your help, but didn't solve the problem for me.

    Share this comment


    Link to comment
    Share on other sites
    On 7/18/2020 at 5:26 PM, TheOriginalBox said:

    I updated to 6.9.0b25 and I can successfully passthrough [AMD] Starship/Matisse HD Audio Controller without the FLR reboot issue. I have yet to test USB as my motherboard only has 1 USB controller (which just happens to have unraid on it). If anyone can validate USB works as well that would be awesome.

     

    Yup it's solved for me too. Passing my USB/Audio to Win10VM no without any issues on 69beta25. 

     

    It looks like it was resolved in Linux Kernel 5.7.5 and beta25 uses 5.7.8

    ChangeLog-5.7.5

    See sections:

    PCI: Avoid FLR for AMD Starship USB 3.0

    PCI: Avoid FLR for AMD Matisse HD Audio & USB 3.0

     

    Thank you Kevin Buettner Marcos Scriven!

    • Like 2

    Share this comment


    Link to comment
    Share on other sites
    21 minutes ago, bubbl3 said:

    See no cache options

    That setting is no longer there, it's set on a share by share basis:

     

    imagem.thumb.png.d9ec327943f0fcfb10ab249426d726fa.png

    Share this comment


    Link to comment
    Share on other sites
    24 minutes ago, johnnie.black said:

    That setting is no longer there, it's set on a share by share basis:

     

    imagem.thumb.png.d9ec327943f0fcfb10ab249426d726fa.png

    I have it enabled there for appdata, then why the mover doesn't it enabled? also, how does one move all the existing data to the cache drive without the mover? Hopefully not manually...

    Edited by bubbl3

    Share this comment


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

    I have it enabled there for appdata, then why the mover doesn't it enabled?

    Possibly a bug, unless the enable cache setting is now also on another place, edit /boot/config/shares.cfg and change:

     

    shareCacheEnabled="no" to "yes"

    • Like 1

    Share this comment


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

    I have it enabled there for appdata, then why the mover doesn't it enabled? also, how does one move all the existing data to the cache drive without the mover? Hopefully not manually...

    If you want mover to move files from array to cache then the Use Cache setting needs to be set to Prefer.   The GUI built-in help describes how the various settings affect mover. Also mover will not move any files that are open so you may need to disable the docker and/or VM services while such a move is in progress.

    Share this comment


    Link to comment
    Share on other sites
    56 minutes ago, johnnie.black said:

    Possibly a bug, unless the enable cache setting is now also on another place, edit /boot/config/shares.cfg and change:

     

    shareCacheEnabled="no" to "yes"

    That was it, the value was set to "no":

    image.png.8453e3c44d5f8a4cea2d8e0169485b0a.png

     

    After changing that and rebooting I can use the mover:

    image.png.06e80e91ba3d9f1183a2abe331857e6f.png

     

    And the cache drive is not empty anymore:

    image.png.00c324d0097267c050eb4a145f9ac117.png

     

    Thanks @johnnie.black

     

    • Like 1

    Share this comment


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

    If you want mover to move files from array to cache then the Use Cache setting needs to be set to Prefer.   The GUI built-in help describes how the various settings affect mover. Also mover will not move any files that are open so you may need to disable the docker and/or VM services while such a move is in progress.

    Yep, I could just not use the mover, the appdata share was set to cache only but that didn't enable the use of the cache in share.cfg, doing that manually fixed all my issues.

    Share this comment


    Link to comment
    Share on other sites

    Actually thinking about it where can one now set the Minimum Free Space value for a cache pool?   It used to be on the 

    global settings.   The setting on the Shares tab applies I thought to array disks?

    Share this comment


    Link to comment
    Share on other sites
    35 minutes ago, itimpi said:

    Actually thinking about it where can one now set the Minimum Free Space value for a cache pool?   It used to be on the 

    global settings.   The setting on the Shares tab applies I thought to array disks?

    I can't find any of those options in the UI, but they are in share.cfg and they do work if manually edited.

    Share this comment


    Link to comment
    Share on other sites
    1 hour ago, johnnie.black said:

    Possibly a bug, unless the enable cache setting is now also on another place, edit /boot/config/shares.cfg and change:

     

    shareCacheEnabled="no" to "yes"

    Yup a bug.  Will be per-pool.

    Share this comment


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

    I can't find any of those options in the UI, but they are in share.cfg and they do work if manually edited.

    Part of same bug:  shareCacheFloor in share.cfg is not used anymore at all.  An individual floor setting for a pool can be set by editing the pools/<pool name>.cfg file and specify value for 'diskFloor'.

    • Like 1

    Share this comment


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

    Part of same bug:  shareCacheFloor in share.cfg is not used anymore at all.  An individual floor setting for a pool can be set by editing the pools/<pool name>.cfg file and specify value for 'diskFloor'.

    Also the mover didn't move all files to the cache drive once the cache share was set to use only the cache, all worked fine once I disabled docker and moved all appdata folders into the cache drive.

    Share this comment


    Link to comment
    Share on other sites
    2 minutes ago, bubbl3 said:

    Also the mover didn't move all files to the cache drive once the cache share was set to use only the cache, all worked fine once I disabled docker and moved all appdata folders into the cache drive.

    By design the mover will not move files that are "in use" - meaning open by some process or loopback mounted.

    Share this comment


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

    Also the mover didn't move all files to the cache drive once the cache share was set to use only the cache, all worked fine once I disabled docker and moved all appdata folders into the cache drive.

    Mover ignores cache-only and cache-no shares. To get files moved to cache you must set the share to cache-prefer.

    • Like 1
    • Thanks 1

    Share this comment


    Link to comment
    Share on other sites

    Upgraded from 6.8.3 ~6 days ago without any issues so far.  Only running containers (br interface), no VMs to report on.

     

    I am using multiple pool devices and it's pretty slick.

    • Thanks 1

    Share this comment


    Link to comment
    Share on other sites

    So, I upgraded to try to set up 2 cache pools, but when I set up my shares with the cache pool I wanted each share to use, it moved EVERYTHING to my cache drives, or tried to.

     

    Is this just a bug, or am I missing something.

    Share this comment


    Link to comment
    Share on other sites
    29 minutes ago, jcarroll said:

    So, I upgraded to try to set up 2 cache pools, but when I set up my shares with the cache pool I wanted each share to use, it moved EVERYTHING to my cache drives, or tried to.

     

    Is this just a bug, or am I missing something.

    There are lots of ways to configure, please post diagnostics.zip - that'll tell the tale.

    Tools/Diagnostics

    Share this comment


    Link to comment
    Share on other sites
    14 hours ago, jcarroll said:

    So, I upgraded to try to set up 2 cache pools, but when I set up my shares with the cache pool I wanted each share to use, it moved EVERYTHING to my cache drives, or tried to.

     

    Is this just a bug, or am I missing something.

     

    That's very interesting.  Say or example I have a share that's 'cache only' and i change which pool device i want it to use, unraid will move the data from one pool device to the other?  That would be highly useful for me in my IO testing.

     

    Quote

    There are lots of ways to configure

    @limetechcan you provide more details please?

    Edited by Dephcon

    Share this comment


    Link to comment
    Share on other sites
    30 minutes ago, Dephcon said:

     

    That's very interesting.  Say or example I have a share that's 'cache only' and i change which pool device i want it to use, unraid will move the data from one pool device to the other?  That would be highly useful for me in my IO testing.

    No, Unraid will not move the data to the new pool.      It will just start using that pool for any new files belonging to the share.      Note that for read purposes ALL drives are checked for file under a rip level folder named for the share (and thus logically belongs to the share).   The files on the previous pool will therefore still be visible under that share even though all new files are going to the new share.

    • Like 1

    Share this comment


    Link to comment
    Share on other sites



    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.