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



    I attempted an upgrade from 6.8.3 ---> latest Unraid Beta 6.9.0 Beta 25. Update itself occurred just fine....but my BTRFS Cache Pool failed spectacularly.

    I boot into Beta 25 just fine. I try to start array. Array starts. I notice my Cache pool is marked as unmountable though! My Cache Pool is BTRFS x2 500GB....both drives are Samsung SSDs. I look in the syslog and see really nasty looking errors regarding the disks! I did a stop/start of array again...same thing happens. I verified both drives are correctly assigned to the right cache position too.....I revert back to 6.8.3.....and Everything is working again (including the cache pool).

    Below is what I believe are the relevant lines in my syslog...but I've also attached my diagnostics. Can someone give some advice?

     

    Sep 21 21:00:35 BEAST-UNRAID emhttpd: shcmd (172): mount -t btrfs -o noatime,space_cache=v2 -U 655fa096-89b6-4d8c-bc03-93f0bd3a6417 /mnt/cache
    Sep 21 21:00:35 BEAST-UNRAID kernel: BTRFS info (device sde1): enabling free space tree
    Sep 21 21:00:35 BEAST-UNRAID kernel: BTRFS info (device sde1): using free space tree
    Sep 21 21:00:35 BEAST-UNRAID kernel: BTRFS info (device sde1): has skinny extents
    Sep 21 21:00:35 BEAST-UNRAID kernel: BTRFS info (device sde1): enabling ssd optimizations
    Sep 21 21:00:35 BEAST-UNRAID kernel: BTRFS info (device sde1): creating free space tree
    Sep 21 21:00:35 BEAST-UNRAID kernel: BTRFS critical (device sde1): corrupt leaf: block=3222820274176 slot=29 extent bytenr=3222702620672 len=16384 invalid generation, have 72057081052587335 expect (0, 54760086]
    Sep 21 21:00:35 BEAST-UNRAID kernel: BTRFS error (device sde1): block=3222820274176 read time tree block corruption detected
    Sep 21 21:00:35 BEAST-UNRAID kernel: BTRFS critical (device sde1): corrupt leaf: block=3222820274176 slot=29 extent bytenr=3222702620672 len=16384 invalid generation, have 72057081052587335 expect (0, 54760086]
    Sep 21 21:00:36 BEAST-UNRAID kernel: BTRFS error (device sde1): block=3222820274176 read time tree block corruption detected
    Sep 21 21:00:36 BEAST-UNRAID kernel: BTRFS critical (device sde1): corrupt leaf: block=3222820274176 slot=29 extent bytenr=3222702620672 len=16384 invalid generation, have 72057081052587335 expect (0, 54760086]
    Sep 21 21:00:36 BEAST-UNRAID kernel: BTRFS error (device sde1): block=3222820274176 read time tree block corruption detected
    Sep 21 21:00:37 BEAST-UNRAID kernel: BTRFS critical (device sde1): corrupt leaf: block=3222820274176 slot=29 extent bytenr=3222702620672 len=16384 invalid generation, have 72057081052587335 expect (0, 54760086]
    Sep 21 21:00:37 BEAST-UNRAID kernel: BTRFS error (device sde1): block=3222820274176 read time tree block corruption detected
    Sep 21 21:00:37 BEAST-UNRAID kernel: BTRFS: error (device sde1) in btrfs_create_free_space_tree:1177: errno=-5 IO failure
    Sep 21 21:00:37 BEAST-UNRAID kernel: BTRFS warning (device sde1): failed to create free space tree: -5
    Sep 21 21:00:37 BEAST-UNRAID kernel: BTRFS error (device sde1): commit super ret -30
    Sep 21 21:00:37 BEAST-UNRAID root: mount: /mnt/cache: can't read superblock on /dev/sde1.
    Sep 21 21:00:37 BEAST-UNRAID emhttpd: shcmd (172): exit status: 32
    Sep 21 21:00:37 BEAST-UNRAID emhttpd: /mnt/cache mount error: No file system
    Sep 21 21:00:37 BEAST-UNRAID emhttpd: shcmd (173): umount /mnt/cache
    Sep 21 21:00:37 BEAST-UNRAID kernel: BTRFS error (device sde1): open_ctree failed
    Sep 21 21:00:37 BEAST-UNRAID root: umount: /mnt/cache: not mounted.
    Sep 21 21:00:37 BEAST-UNRAID emhttpd: shcmd (173): exit status: 32
    Sep 21 21:00:37 BEAST-UNRAID emhttpd: shcmd (174): rmdir /mnt/cache
    Sep 21 21:00:37 BEAST-UNRAID emhttpd: shcmd (175): sync

     

    beast-unraid-diagnostics-20200921-2135.zip

    Edited by Stupifier

    Share this comment


    Link to comment
    Share on other sites

    Oh boy.  I wonder if it's some new feature in a newer version of BTRFS?  Running btrfs --version for me results in btrfs-progs v5.6.1. You might like to compare that with what you've got to see if there's something listed in the changelog with parts of that error.

     

    Ultimately I've decided that a single drive xfs is more reliable than a btrfs mirror so I've stuck with that until something else comes around.  So, that kind of thinking would be one workaround for you - stop your array, copy your data on the current good version to some other storage.  Upgrade Unraid and format a new cache of your choosing e.g. XFS or btrfs so that it's a known good starting point.  Copy your data back and start the array.  Or along those lines.  You get my drift right?  Obviously kick start a move first.

     

    Also, pays to check for sure the hardware is not full of smart errors or something.  Could also make a copy now and run some btrfs repair tools before upgrading.  Someone else will probably have some better advice on that.

     

    Good luck!

     

     

    Share this comment


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

    I attempted an upgrade from 6.8.3 ---> latest Unraid Beta 6.9.0 Beta 25. Update itself occurred just fine....but my BTRFS Cache Pool failed spectacularly.

    This is the result of the improved tree checker on newer kernels, more info here, if if still mounts correctly with the older kernel easiest way is to backup and re-format the pool.

    Share this comment


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

    Oh boy.  I wonder if it's some new feature in a newer version of BTRFS?  Running btrfs --version for me results in btrfs-progs v5.6.1. You might like to compare that with what you've got to see if there's something listed in the changelog with parts of that error.

     

    Ultimately I've decided that a single drive xfs is more reliable than a btrfs mirror so I've stuck with that until something else comes around.  So, that kind of thinking would be one workaround for you - stop your array, copy your data on the current good version to some other storage.  Upgrade Unraid and format a new cache of your choosing e.g. XFS or btrfs so that it's a known good starting point.  Copy your data back and start the array.  Or along those lines.  You get my drift right?  Obviously kick start a move first.

     

    Also, pays to check for sure the hardware is not full of smart errors or something.  Could also make a copy now and run some btrfs repair tools before upgrading.  Someone else will probably have some better advice on that.

     

    Good luck!

     

     

     

    7 hours ago, JorgeB said:

    This is the result of the improved tree checker on newer kernels, more info here, if if still mounts correctly with the older kernel easiest way is to backup and re-format the pool.

    Thanks a bunch guys! I kinda figured this was the path forward and there was no magic "FIX" command.

    Well....then it sounds like I'll be backup and re-formatting in order to upgrade. Hope Unraid Devs figure out a way to address this when 6.9.0 goes stable.....cuz that is a nasty problem to face. They could address it as simply as telling people the upgrade will break old BTRFS pools.

    Edited by Stupifier

    Share this comment


    Link to comment
    Share on other sites

    reformatting is probably the best thing anyway so you can take advantage of the new alignment for SSDs.

     

    Be sure to read earlier in the thread about that.

    Share this comment


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

    . They could address it as simply as telling people the upgrade will break old BTRFS pools.

    This will only happen to very few users, and most of those cases the problem was already in the pool, just undetected.

    Share this comment


    Link to comment
    Share on other sites

    Are Unraid team alive? Last update 12 July. I understand all that covid etc... But beta 25 realy buggy and 6.8.3 didn't have QEMU 5.0

    Is there any estimates of release date stable 6.9

    • Like 1

    Share this comment


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

    Soon™

     

    6 hours ago, Squid said:

    Very soon(tm)

     

    • Haha 1

    Share this comment


    Link to comment
    Share on other sites

    I've been running 6.9beta25 now for a month and it's great guys. Thanks for all the hard work. Nothing bugging me. Look forward to the stable release.

    • Like 1

    Share this comment


    Link to comment
    Share on other sites

    same here, 6.9 beta25 is stable and no real issues ... besides my docker size point which i couldnt figure out yet ... but thats prolly not beta related.

     

    image.png.c39ba9e96c062f98908202e5653edc00.png

    • Like 1

    Share this comment


    Link to comment
    Share on other sites
    On 9/23/2020 at 5:01 AM, Squid said:

    Very soon(tm)

    Too late for that. No updates in 2 months <> soon. :)

     

    But it will be done when it's done, I guess. By definition.

     

    My data, and uptime on the system, is too important to me to run pre-RC betas. So I'm just getting impatient. Lol

    Edited by JasonJoel

    Share this comment


    Link to comment
    Share on other sites
    17 minutes ago, JasonJoel said:

    Too late for that.

    Depends on when you start counting.

     

    This post was yesterday

    On 9/23/2020 at 11:13 AM, jonathanm said:

    Soon™

    😉

    • Like 1

    Share this comment


    Link to comment
    Share on other sites

    I am encountering complete KVM/qemu freezes/crashes during backups which need to be fixed by a reboot.

     

    The issue seems to be triggered by the use of libvirt "virsh blockcommit" command.

     

    Apparently the issues has been fixed in libvirt 6.5.0, would be great if this could be integrated before the final 6.9.0 release is made.

     

    https://gitlab.com/libvirt/libvirt/-/issues/31

     

    Thank you.

    Share this comment


    Link to comment
    Share on other sites

    @limetech, could you please add a link to a download for this beta release to the first post in this thread.  The reason is that that have been several folks who have update their hardware and find that the new hardware has a NIC that is not supported in the staple releases but is supported in this beta release.  Without a link, it is a convoluted process to get the beta installed on their boot drive.

    • Like 2

    Share this comment


    Link to comment
    Share on other sites
    14 minutes ago, Frank1940 said:

    @limetech, could you please add a link to a download for this beta release to the first post in this thread.  The reason is that that have been several folks who have update their hardware and find that the new hardware has a NIC that is not supported in the staple releases but is supported in this beta release.  Without a link, it is a convoluted process to get the beta installed on their boot drive.

    X2

     

    I like to keep a local copy of any software / OS I am actively using just in case.

    Share this comment


    Link to comment
    Share on other sites
    On 9/23/2020 at 11:36 AM, disclaimer8 said:

    Are Unraid team alive? Last update 12 July. I understand all that covid etc... But beta 25 realy buggy and 6.8.3 didn't have QEMU 5.0

    Is there any estimates of release date stable 6.9

    Agreed. I can't stay with one of my servers on 6.8.3 because my cache SSDs are slowly but steady being killed by Unraid. Any update on the RC would be welcome.

    2020-09-29_15-27-32.png

    Share this comment


    Link to comment
    Share on other sites
    22 minutes ago, Crogge said:

    Any update on the RC would be welcome.

    New beta was just released:

     

    • Like 1

    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.