6.9.0-beta24 vs. -beta22 Summary:
- fixed several bugs
- added some out-of-tree drivers
- added ability to use xfs-formatted loopbacks or not use loopback at all for docker image layers. Refer to Docker section below for more details
- (-beta23 was an internal release)
Important: Beta code is not fully tested and not feature-complete. We recommend running on test servers only!
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
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: Let's say 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 let's say 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 pool. Now you have x2 1-device btrfs pools. Upon array Start user 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.
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.
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 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.
All updated to latest versions. In addition, Linux PAM has been integrated. This will permit us to install 2-factor authentication packages in a future release.
Updated to version 19.03.11
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.
In this release however, you must edit the 'config/docker.cfg' file directly to specify a directory, for example:
Finally, 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.
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.
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>
- AFP support has been removed.
- Numerous other Unraid OS and webGUI bug fixes and improvements.
Version 6.9.0-beta24 2020-07-08
- fix emhttpd crash expanding number of slots for an existing pool
- fix share protected/not protected status
- fix btrfs free space reporting
- fix pool spinning state incorrect
- curl: version 7.71.0
- fuse3: version 3.9.2
- file: version 5.39
- gnutls: version 3.6.14
- harfbuzz: version 2.6.8
- haveged: version 1.9.12
- kernel-firmware: version 20200619_3890db3
- libarchive: version 3.4.3
- libjpeg-turbo: version 2.0.5
- lcms2: version 2.11
- libzip: version 1.7.1
- nginx: version 1.19.0 (CVE-2019-9511, CVE-2019-9513, CVE-2019-9516)
- ntp: version 4.2.8p15
- openssh: version 8.3p1
- pam: version 1.4.0
- rsync: version 3.2.1
- samba: version 4.12.5 (CVE-2020-10730, CVE-2020-10745, CVE-2020-10760, CVE-2020-14303)
- shadow: version 4.8.1
- sqlite: version 3.32.3
- sudo: version 1.9.1
- sysvinit-scripts: version 2.1
- ttyd: version 20200624
- util-linux: version 2.35.2
- xinit: version 1.4.1
- zstd: version 1.4.5
- version 5.7.7
- out-of-tree driver: QLogic QLGE 10Gb Ethernet Driver Support (from staging)
- out-of-tree driver: RealTek r8125: version 9.003.05
- out-of-tree driver: HighPoint rr272x_1x: version v1.10.6-19_12_05
- cleanup passwd, shadow
- docker: support both btrfs and xfs backing filesystems
- loopbacks: permit xfs or btrfs based on filename
- mount_image: suppport bind-mount
- mount all btrfs volumes using 'space_cache=v2' option
- mount loopbacks with 'noatime' option; enable 'direct-io'
- non-rotational device partitions aligned on 1MiB boundary by default
- ssh: require passwords, disable non-root tunneling
- web terminal: inhibit warning pop-up when closing window
- webgui: Add log viewer for vfio-pci
- webgui: Allow different image types to upload with 512K max
- webgui: other misc. improvements
- webgui: vm manager: Preserve VNC port settings