Unraid OS 6.9.0-Beta25 is Now Available

Multiple Pools

This new feature 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.

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.

Multi-Language Support

Another exciting new feature in Unraid 6.9 is the ability to download language packs and use the Unraid OS in a number of different languages. Currently, English, Spanish, French, German and Dutch are available and several others are in the works.

A huge amount of work and effort has been implemented by @bonienl to provide multiple-language support in the Unraid OS webGUI. Likewise, thanks to @Squid, language packs are installed via the Community Applications plugin - look for a new "Language" Category or you can also search for specific language packs.

For more info on Multi-Language Support, please check out our guide here.

Note: Community Applications HAS to be up to date to install languages. Versions of CA prior to 2020.05.12 will not even load on this release. As of this writing, the current version of CA is 2020.06.13a. 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.

Also, a new Multi-Language Section of the Unraid forum is available for discussions in language specific forums.

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). For more details, please see the full forum release post linked at the bottom of the page.

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.

For more details, please see the full forum release post linked at the bottom of the page.

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 modified 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 more details, please see the full forum release post linked at the bottom of the page.

Other Updates

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