Leaderboard

The 6.12.5-rc1 release mainly contains bug fixes and security updates that we'd like feedback on before releasing it as 6.12.5. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the NVIDIA and Realtek plugins in particular. If the system is currently running 6.12, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (issues related to Docker not stopping should be resolved in this release.) Go to Tools -> Update OS. Change to the "Next" branch and click "Check for Updates". Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip. Upgrade notes This release includes bug fixes and security updates. All users are encouraged to upgrade. Known issues Please see the 6.12.0 release notes for general known issues. Rolling back If rolling back earlier than 6.12.4, also see the 6.12.4 release notes. Changes vs. 6.12.4 Bug fixes and improvements Replace very old 'MemTest86+' with Memtest86+ version: 6.20 There are also Boot Options available. When 'mirror syslog to flash' is enabled, view syslog-previous at Tools -> Syslog, and in diagnostics Docker: Docker containers were not always stopping, preventing docker from unmounting Docker containers using IPv6 on custom networks were unable to start emhttpd: if User Shares not enabled, update_cron was not called during array Start sequence rc.nginx stop - force nginx to stop shfs: Allocation method was not working correctly if 6 or more disks were specified in the 'include' mask webgui: Downgrade.php was not updated for 6.12 always show ipvlan / macvlan setting ZFS: use 'zfs import -f' to ensure pools from other systems get imported prevent auto-spindown of unformatted devices Package updates curl: version 8.4.0 (CVE-2023-38546 CVE-2023-38545 CVE-2023-38039) firefox: 119.0.r20231019122658 (AppImage) intel-microcode: version 20231114 kernel-firmware: 20231024_4ee0175 qemu: version 7.2.0 samba: version 4.17.12 (CVE-2023-3961 CVE-2023-4091 CVE-2023-4154 CVE-2023-42669 CVE-2023-42670) smartmontools: version 7.4 zfs: version 2.1.13 Linux kernel version 6.1.63 CONFIG_USB_NET_CDC_NCM: CDC NCM support CONFIG_NFS_V4_1: NFS client support for NFSv4.1 CONFIG_NFS_V4_1_MIGRATION: NFSv4.1 client support for migration CONFIG_NFS_V4_2: NFS client support for NFSv4.2 CONFIG_NFS_V4_2_READ_PLUS: NFS: Enable support for the NFSv4.2 READ_PLUS operation CONFIG_NFSD_V4_2_INTER_SSC: NFSv4.2 inter server to server COPY

Thank you for the feedback on the previous rc release, we have one more small set of updates to test before releasing 6.12.4. Highlights include: Resolved an issue with VMs on the macvtap interface not being able to connect to the Internet Additional IPv6 improvements The delay before auto-closing notifications is now configurable (see Settings/Notification Settings) Fix the custom network DHCP subnet options on the Settings/Docker Settings page If you are already on 6.12.4-rc18 this should be a simple update, no need to change any settings. If you are coming from an earlier release please see the 6.12.4-rc18 announce post for info on how to solve macvlan issues and other changes. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.2, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (This issue was resolved with 6.12.3) Go to Tools -> Update OS, change the Branch to "Next". If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot Known Issues Please see the 6.12.4-rc18 release notes Rolling Back Please see the 6.12.4-rc18 release notes Changes vs. 6.12.4-rc18 docker: add routing when shim or macvtap network is used docker: fix routing when "host access" is enabled docker: remove IPv6 from shim/vhost interface (some routers are incompatible) New notification option: auto-closure time New notification option: notification life time Set default notifications life time to 5 seconds network: print public ipv6 address network: shim interface gets MAC address of parent, no need to generate one Docker settings: fix subnet sizes CSS: set overflow-x to 'auto' Helptext: fix typo Linux kernel version 6.1.47

Please refer to the 6.12.0-rc1 topic for a general overview. Version 6.12.0-rc7 2023-06-05 Changes vs. 6.12.0-rc6 Share "exclusive mode": Added "Settings/Global Share Settings/Permit exclusive shares" [Yes/No] default: No. Fix issue marking share exclusive when changing Primary storage to a pool but share does not exist there yet. Make exclusive share symnlinks relative. Disable exclusive share mode if the share NFS-exported. Networking: Fix issue where/etc/resolve.conf can get deleted when switching DNS Server between auto/static. Support custom interfaces (e.g. Tailscale VPN tunnel or zerotier L2 tunnel) Web Terminal: Change renderer from webgl to canvas to mitigate issue with latest Chrome update. For better readability, changed background color on directory listings where 'w+o' is set. Docker: Fix issue detecting proper shutdown of docker. rc.docker: Fix multiple fixed IPs VM Manager: Fix issues with VM page loads if users have removed vcpu pinning. ovmf-stable: version 202305 (build 3) Other: Fix issue mounting emulated encrypted unRAID array devices. Fix ntp drift file save/restore from persistent USB flash 'config' directory. Remove extraneous /root/.config/remmina file Misc. changes to accommodate webGui repo reorganizaion. webGUI: Fixed regression error in disk critical / warning coloring & monitoring Linux kernel version 6.1.32 CONFIG_FANOTIFY: Filesystem wide access notification

Please refer to the 6.12.0-rc1 topic for a general overview. Anticipating stable release in a couple of days. Version 6.12.0-rc5 2023-05-01 Bug fixes/improvements: Auto-mount all nested ZFS datasets upon array Start. Fix bug in bind-mount when share names contain spaces. Restrict avahidaemon to primary interface. Restrict 'newperms' script to operate on /mnt/ only. Fixed typos in help text. Linux kernel Fixes bug in bind-mount when share names contain spaces. version: 6.1.27 Version 6.12.0-rc4 2023-04-27 New in this release is a conceptual change in the way storage is assigned to shares. Normally such a change would not happen in an -rc series; however, in this case the under-the-hood coding was minimal. The concept outlined below is something we planned on introducing in the Unraid OS 6.13 cycle. We decided to introduce this change now because of increased interest in Unraid OS now that ZFS is supported. The old concept of main storage being the unRAID array with an optional "Cache" is confusing to many new users, especially since cache has a specific meaning in ZFS. Also outlined below, we introduced the concept of an exclusive share. This is simply a share where all the data exists in a single named pool. In this case we set up a bind-mount, bypassing the FUSE-based User Share file system. This feature is primarily aimed at maximizing I/O for large fast ZFS pools accessed via a fast network Share storage conceptual change Configuring the storage options for a share is specified using two inputs: Primary storage Secondary storage Primary storage is where new files/folders are created. If Primary storage is below the Minimum Free Space setting then new files and folders will be created in Secondary storage, if configured. Each input presents a drop-down which lists "array", "none", and each named pool as a selection according to some configuration rules: For the Primary storage drop-down: the "none" option is omitted, ie, Primary storage must be selected any named pool can be selected "Array" can be selected (meaning the unRAID array) For the Secondary storage drop-down: the "none" option is included, ie, Secondary storage is optional if Primary storage is a pool name, then the only options are "none" and "Array" if Primary storage is "Array", then only "none" appears as an option When "Array" is selected for either Primary or Secondary storage, a set of additional settings slide in: Allocation method Included disk(s) Excluded disk(s) Split level When a btrfs named pool is selected for either Primary or Secondary storage, an additional setting slides in: Enable Copy-on-write When a ZFS named pool is selected for either Primary or Secondary storage, there are no additional settings at this time but there could be some in the future. For example, since a share is created as a ZFS dataset, it could have a different compression setting than the parent pool if we need to implement this. Mover action When there is Secondary storage configured for a share the "Mover action" setting becomes enabled, letting the user select the transfer direction of the mover: Primary to Secondary (default) Secondary to Primary Exclusive shares If Primary storage for a share is a pool and Secondary storage is set to "none", then we can set up a bind-mount in /mnt/user/ directly to the pool share directory. (An additional check is made to ensure the share also does not exist on any other volumes.) There is a new status flag, 'Exclusive access' which is set to 'Yes' when a bind-mount is in place; and, 'No' otherwise. Exclusive shares are also indicated on the Shares page. The advantage of setting up a bind-mount is that I/O bypasses FUSE-based user share file system (shfs) which can significantly increase performance. There are some restrictions: Both the share Min Free Space and pool Min Free Space settings are ignored when creating new files on an exclusive share. If there are any open files, mounted loopback images, or attached VM vdisk images on an exclusive share, no settings for the share can be changed. If the share directory is manually created on another volume, files are not visible in the share until after array restart, upon which the share is no longer exclusive. Change Log vs. 6.12.0-rc3 Linux kernel version: 6.1.26 Misc avahi: enable/disable IPv4/IPv6 based on network settings webgui: DeviceInfo: show shareFloor with units webgui: DeviceInfo: added automatic floor calculation webgui: Added autosize message webgui: Shares: added info icon webgui: Updated DeviceInfo and Shares page [explain] webgui: Fix network display aberration. webgui: Auto fill-in minimum free space for new shares webgui: feat(upc): update to v3 for connect webgui: Share/Pool size calculation: show and allow percentage values webgui: VM manager: Make remote viewer and web console options selectable. webgui: VM manager: Option to download .vv file and start remote viewer is browser set to open file .vv when downloaded. webgui: VM manager: Add remote viewer console support webgui: VM manager: Remove-lock-posix='on'-flock='on'/- Base Distro openzfs: version 2.1.11 Version 6.12.0-rc3 2023-04-14 Upgrade notes If you created any zpools using 6.12.0-beta5 please Erase those pools and recreate. If you revert back from 6.12 to 6.11.5 or earlier, you have to force update all your Docker containers and start them manually after downgrading. This is necessary because of the underlying change to cgroup v2 in 6.12.0-rc1. Upon boot, if all PCI devices specified in 'config/vfio-pci.cfg' file do not properly bind, VM Autostart is prevented. You may still start individual VMs. This is to prevent Unraid host crash if hardware PCI IDs changed because of a kernel update or physical hardware change. To restore VM autostart, examine '/var/log/vfio-pci-error' and remove offending PCI IDs from 'config/vfio-pci.cfg' file and reboot. Linux Multi-Gen LRU is a relatively new feature now included but not enabled by default. You can enable by adding this line to your 'config/go' file: echo y > /sys/kernel/mm/lru_gen/enabled If you revert back from 6.12 to 6.11.5 or earlier you many need to remove that line. Obsolete/Broken Plugins There are a few plugins which are known to be incompatible with Unraid 6.12, and upon boot will not be installed. You will get a notification for each plugin that is affected, and can review the list by going to Plugins/Plugin File Install Errors. disklocation-master version 2022.06.18 (Disk Location by olehj, breaks the dashboard) plexstreams version 2022.08.31 (Plex Streams by dorgan, breaks the dashboard) corsairpsu version 2021.10.05 (Corsair PSU Statistics by Fma965, breaks the dashboard) gpustat version 2022.11.30a (GPU Statistics by b3rs3rk, breaks the dashboard) ipmi version 2021.01.08 (IPMI Tools by dmacias72, breaks the dashboard) nut version 2022.03.20 (NUT - Network UPS Tools by dmacias72, breaks the dashboard) NerdPack version 2021.08.11 (Nerd Tools by dmacias72) upnp-monitor version 2020.01.04c (UPnP Monitor by ljm42, not PHP 8 compatible) ZFS-companion version 2021.08.24 (ZFS-Companion Monitor by campusantu, breaks the dashboard) Some of the affected plugins have been taken over by different developers, we recommend that you go to the Apps page and search for replacements. Please ask plugin-specific questions in the support thread for that plugin. ZFS Pools New in this release is the ability to create a ZFS file system in a user-defined pool. In addition you may format any data device in the unRAID array with a single-device ZFS file system. We are splitting full ZFS implementation across two Unraid OS releases. Initial support in this release includes: Support raid0, mirror, raidz1, raidz2 and raidz3 root profiles. Up to 4-way mirror in a mirror vdev. Multiple vdev groups. Support removing single device: if device still present in server, 'wipefs' is used to clear the partition table. Support replacing single missing device with a new device of same or larger size. Support scheduled trimming of ZFS pools. Support pool rename. Pool names must begin with a lowercase letter and only contain lowercase letters, digits, the underscore and dash. Pool names must not end with a digit. Non-root vdev cannot be configured in this release, however, they can be imported. Note: imported hybrid pools may not be expanded in this release. Pools created on other systems may or may not import depending on how the the pool was created. A future update will permit importing pools from any system. A ZFS pool has three variables: profile - the root data organization: raid0, mirror (up to 4-way), raidz1, raidz2, raidz3 width - the number of devices per root vdev groups - the number of root vdevs in the pool At time of ZFS pool creation, the webGUI will present all topology options based on the number of devices assigned to the pool. Special treatment for root single-vdev mirrors: A single-device ZFS pool can be converted to multiple-device mirror by adding up to 3 additional devices in one operation. A 2-device mirror can be increased to 3-device by adding a single device; similarly a 3-device mirror can be increased to 4-device mirror by adding a single device. To add an additional root vdev, you must assign 'width' number of new devices to the pool at the same time. The new vdev will be created with the same 'profile' as the existing vdevs. Additional flexibility in adding/expanding vdevs will be provided in a future update. Pools created with the steini84 plugin can be imported as follows: First create a new pool with the number of slots corresponding to the number of devices in the pool to be imported. Next assign all the devices to the new pool. Upon array Start the pool should be recognized, though certain zpool topologies may not be recognized (please report). Mixed topologies are not supported. For example, a pool with both a mirror root vdev and a raidz root vdev is not recognized. Autotrim can be configured as on or off (except for single-device ZFS volumes in the unRAID array). Compression can be configured as on or off, where on selects lz4. Future update will permit specifying other algorithms/levels. When creating a new ZFS pool you may choose zfs - encrypted, which, like other encrypted volumes, applies device-level encryption via LUKS. ZFS native encryption is not supported at this time. During system boot, the file /etc/modprobe.d/zfs.conf is auto-generated to limit the ZFS ARC to 1/8 of installed memory. This can be overridden if necessary by creating a custom 'config/modprobe.d/zfs.conf' file. Future update will include ability to configure the ARC via webGUI, including auto-adjust according to memory pressure, e.g., VM start/stop. Top-level user shares in a ZFS pool are created as datasets instead of ordinary directories. btrfs pools Autotrim can be configured as on or off when used in a pool. Compression can be configured as on or off. on selects zstd. Future update to permit specifying other algorithms/levels. xfs Autotrim can be configured as on or off when used as a single-slot pool. Docker It is possible to configure the Docker data-root to be placed in a directory on a ZFS storage pool. In this case Docker will use the 'zfs' storage driver. This driver creates a separate dataset for each image layer. Because of this, here is our recommendation for setting up Docker using directory: First, create a docker user share configured as follows: Share name: docker Use cache pool: Only Select cache pool: name of your ZFS pool Next, on Docker settings page: Enable docker: Yes Docker data-root: directory Docker directory: /mnt/user/docker If you ever need to delete the docker persistent state, then bring up the Docker settings page and set Enable docker to No and click Apply. After docker has shut down click the Delete directory checkbox and then click Delete. This will result in deleting not only the various files and directories, but also all layers stored as datasets. Before enabling Docker again, be sure to first re-create the docker share as described above. Other changes: CreateDocker: changed label Docker Hub URL to Registry URL because of GHCR and other new container registries becoming more and more popular. Honor user setting of stop time-out. Accept images in OCI format. Add option to disable readmore-js on container table Fix: Docker Containers console will not use bash if selected VM Manager If you enable copy/paste for virtual consoles you need to install additional software on the client in addition to the QEMU agent if that has been installed. Here is the location for spice-vdagent for both Windows and Linux. Note copy/paste function will not work with web spice viewer you need to use virt-viewer. Add Serial option to vdisk. Spice Bug fix for users with non standard GUI ports defined. OVMF for QEMU: version stable202302 Fix for bus text. Enable copy paste option for virtual consoles Update Memory Backup processing for Virtiofs. Fix lockup when no VMs are present Add support for rtl8139 network model. fix translation omission added lock/unlock for sortable items Fix for Spice Mouse if Copy paste enabled. Dashboard The webGUI Dashboard has been redesigned and it is now possible to move elements (tiles) up and down and between columns. This allows the user to organize the tiles in any way they desire. There is a small lock icon on the menu bar which must be clicked to enable this function. Note: The lock icon also appears on the Docker and VM pages and must be clicked to rearrange the startup order. Release bz file differences Unraid OS is comprised of a set of 5 so-called bz files in the root of the USB Flash boot device: bzimage - the Linux kernel bzroot - the root file system, sans console desktop bzroot-gui - additional files needed for console desktop bzmodules - modules (drivers) associated with the Linux kernel bzfirmware - device firmware required by certain modules Starting with 6.12 release, the content of these files has been rearranged: bzimage - the Linux kernel (same as before) bzroot - the root file system excluding the /usr directory tree bzroot-gui - a single file which auto-starts the console desktop (for compatibility) bzmodules - modules (drivers) associated with the Linux kernel and device firmware required by certain modules bzfirmware - the /usr directory and all files contained therein, including console desktop The results of this change is to speed up the boot process and free up nearly 1G of RAM. It also permits us to add more "stuff" to Unraid OS in the future without requiring more RAM. Finally, when booted in non-GUI mode, the desktop can be started by logging in at the console and typig the 'slim' command. The files bzfirmware and bzmodules are squashfs images mounted using overlayfs at /usr and /lib respectively. Since these files are loopback-mounted, care must be taken if ever you want to perform a manual update. What is a manual update? This is a method of updating Unraid OS on your USB flash boot device without using the Tools/Update OS function. Typically one would either: open a Terminal window, wget the release zip file, unzip the release, and then 'cp' the bz files to root of the boot device. or export the 'flash' share on your network and drag the bz files from a PC directly to the flash. Either method, starting with 6.12 can fail because the bzfirmware file will be overwritten while it is still mounted - not good. To get around this, you must first create a temp directory on the flash device and then 'mv' (or drag) all the bz files to this temp directly. Now you can copy the new bz files in place and reboot. Linux kernel version 6.1.23 md/unraid: version 2.9.27 CONFIG_FS_DAX: File system based Direct Access (DAX) support CONFIG_VIRTIO_FS: Virtio Filesystem CONFIG_ZONE_DEVICE: Device memory (pmem, HMM, etc...) hotplug support CONFIG_USBIP_HOST: Host driver CONFIG_INTEL_MEI: Intel Management Engine Interface CONFIG_INTEL_MEI_ME: ME Enabled Intel Chipsets CONFIG_INTEL_MEI_GSC: Intel MEI GSC embedded device CONFIG_INTEL_MEI_PXP: Intel PXP services of ME Interface CONFIG_INTEL_MEI_HDCP: Intel HDCP2.2 services of ME Interface CONFIG_INTEL_PMC_CORE: Intel PMC Core driver CONFIG_DRM_I915_PXP: Enable Intel PXP support CONFIG_SCSI_FC_ATTRS: FiberChannel Transport Attributes CONFIG_FUSION_SPI: Fusion MPT ScsiHost drivers for SPI CONFIG_FUSION_FC: Fusion MPT ScsiHost drivers for FC CONFIG_FUSION_CTL: Fusion MPT misc device (ioctl) driver CONFIG_FUSION_LOGGING: Fusion MPT logging facility CONFIG_X86_AMD_PSTATE: AMD Processor P-State driver CONFIG_LRU_GEN: Multi-Gen LRU CONFIG_SERIAL_8250_NR_UARTS=32: Maximum number of 8250/16550 serial ports CONFIG_SERIAL_8250_RUNTIME_UARTS=4: Number of 8250/16550 serial ports to register at runtime Misc cgroup2 now the default loopback images no longer mounted using directio upgradepkg patched to prevent replacing existing package with older version. current PCI bus/device information saved in file '/boot/previous/hardware' upon Unraid OS upgrade. NFS: enable UPD transport emhttp: fix cache pool (null) syslog strings emhttp: fix cache pool display wrong device size for selected replacement device networking: fix nginx recognizing IP address from slow dhcp servers mover: fix: improper handling of symlinks mover: fix: Mover logging syslog entries format different from previous releases plugin: Display Run command retval in error message shfs: igonore top-level hidden directoris (names beginning with '.') terminal: OpenTerminal: change termination signal (hard stop) upgrade Unraid OS: check for earlier upgrade without reboot VM Manager: let page load even when PCI devices appear missing or are misassigned wireguard: add SSL support for WG tunnel IP addresses (myunraid.net wildcard certs only) webgui: support PHP8, increase PHP max memory from 128M to 256M webgui: ManagementAccess: Disable Provision/Renew/Upgrade buttons when no IP on eth0 webgui: ManagementAccess: Support wireguard local IP addresses in combination with myservers.unraid.net SSL cert webgui: Move "view" icon on Main and Shares page to the left webgui: Dashboard: fix regression error in "select case" webgui: Dashboard: make items moveable between columns webgui: Keep dismissed banners hidden for a month webgui: Dashboard: API for adding custom tiles webgui: Dashboard: rearrange processor information webgui: Dashboard: rearrange UPS info webgui: Dashboard: rearrange memory info webgui: Dashboard: VPN header rearrangement webgui: Dashboard: header rearrangements webgui: Add jqueryUI touch punch for mobile devices webgui: Changed ID to CLASS for elements occurring more than once webgui: Make header in white and black themes scrollable When more items are present than screen space, the user can now scroll through them (previously these items were invisible) webgui: Dashboard and Docker: introduce lock button for sortable items By default sortable items are locked, which allows mobile devices to scroll the page. Upon request items can be made sortable webgui: Users: add icon to title bar webgui: Tools: new function -> PHP Settings View PHP info Configure error reporting Open LOG to see errors in real-time webgui: System info: fix reading inactive ports webgui: Plugin: Include the actual command, being executed webgui: System info: cache enhancement webgui: System info: memory enhancement webgui: DeviceInfo: disable buttons when erase operation is running webgui: Docker: filetree corrections webgui: Fixed: Dashboard: show heat alarm per pool webgui: Notifications: revised operation Autoclose new notifications after 3 seconds Fix notifications reappearing after closure webgui: DeviceList: add FS type in offline state webgui: Add notification agent for Bark webgui: Main: hide browse icon when disk is not mounted webgui: Diagnostics: add additional btrfs and zfs info webgui: Dashboard: add ZFS memory usage webgui: Revised New Permissions Select either disks or shares (not both) webgui: Add testparm to diagnostics webgui: Support new UD reserved mount point of /mnt/addons webgui: fix issue displaying Attributes when temperature display set to Fahrenheit webgui: Dashboard changes: lock the Dashboard completely: Editing/moving only becomes possible when unlocking the page An empty column is refilled when the respective tiles are made visible again, no need to reset everything added a visual "move indicator" on the Docker and VM page, to make clearer that rows can be moved now. change cursor shape when moving is enabled use tile title as index webgui: fix: Local Firefox account pop-up postmessages not working webgui: VM Manager: fix VM marked as Autostart not starting following manual array Start webgui: SMART test cannot be run on a UD disk because there is no spin down delay selection webgui: status footer stuck on "Starting services" when applying share config setting chagnes. webgui: Fix table layout for orphan images webgui: Plugin: Do not show update button if incompatible webgui: OpenTerminal: limit clients webgui: Context menu: automatic triangle placement webgui: Dashboard: fix pool warnings webgui: Allow SMART long test for UD webgui: Read processor type from /proc/cpuinfo webgui: CSS: solve scrollbar issue in firefox webgui: plugin: Make wget percentage detection more robust webgui: Add share: fix hidden share name check webgui: Display settings: add missing defaults webgui: Array Operation: prevent double clicking of Start button wireguard: fix nginx issue when partial WireGuard config Base Distro aaa_glibc-solibs: version 2.37 adwaita-icon-theme: version 43 at-spi2-core: version 2.46.0 bash: version 5.2.015 bind: version 9.18.12 btrfs-progs: version 6.2.1 ca-certificates: version 20221205 cryptsetup: version 2.6.1 curl: version 7.88.1 dbus: version 1.14.6 diffutils: version 3.9 dnsmasq: version 2.89 docker: version 20.10.23 e2fsprogs: version 1.47.0 encodings: version 1.0.7 file: version 5.44 firefox: version 111.0 (AppImage) freetype: version 2.13.0 fuse3: version 3.12.0 gawk: version 5.2.1 git: version 2.39.2 glib2: version 2.74.6 glibc: version 2.37 glibc-zoneinfo: version 2022g gnutls: version 3.7.9 gptfdisk: version 1.0.9 gtk+3: version 3.24.37 harfbuzz: version 7.1.0 htop: version 3.2.2 iproute2: version 6.2.0 iptables: version 1.8.9 iputils: version 20221126 less: version 612 libICE: version 1.1.1 libSM: version 1.2.4 libX11: version 1.8.4 libXau: version 1.0.11 libXcomposite: version 0.4.6 libXdamage: version 1.1.6 libXdmcp: version 1.1.4 libXpm: version 3.5.15 libXrandr: version 1.5.3 libXres: version 1.2.2 libXxf86dga: version 1.1.6 libarchive: version 3.6.2 libdrm: version 2.4.115 libfontenc: version 1.1.7 libglvnd: version 1.6.0 libjpeg-turbo: version 2.1.5.1 libpcap: version 1.10.3 libpng: version 1.6.39 libpsl: version 0.21.2 liburcu: version 0.14.0 libwebp: version 1.3.0 libxkbcommon: version 1.5.0 libxkbfile: version 1.1.2 libxshmfence: version 1.3.2 lmdb: version 0.9.30 logrotate: version 3.21.0 lsof: version 4.98.0 lz4: version 1.9.4 lzlib: version 1.13 mc: version 4.8.29 mcelog: version 191 mpfr: version 4.2.0 nano: version 7.2 ncurses: version 6.4 nginx: version 1.23.3 nghttp2: version 1.52.0 openssh: version 9.2p1 openssl: version 1.1.1t openssl-solibs: version 1.1.1t openzfs: version 2.1.9 pango: version 1.50.14 pciutils: version 3.9.0 pcre2: version 10.42 php: version 8.2.4 php-libvirt: version 0.5.7 php-markdown: version 2.0.0 samba: version 4.17.7 sqlite: version 3.41.0 sudo: version 1.9.13p2 sysstat: version 12.7.2 tdb: version 1.4.8 tevent: version 0.14.1 traceroute: version 2.1.2 transset: version 1.0.3 tree: version 2.1.0 usbutils: version 015 xcb-util: version 0.4.1 xdriinfo: version 1.0.7 xf86-video-vesa: version 2.6.0 xfsprogs: version 6.1.1 xhost: version 1.0.9 xinit: version 1.4.2 xkbcomp: version 1.4.6 xkeyboard-config: version 2.38 xorg-server: version 21.1.7 xprop: version 1.2.6 xrandr: version 1.5.2 xset: version 1.2.5 xterm: version 379 xz: version 5.4.1 zstd: version 1.5.4

The Unraid 6.12.7-rc1/rc2 releases contain bug fixes and security updates that we'd like feedback on before releasing 6.12.7. If you installed rc1, please upgrade to rc2 as it fixes problems related to installing license keys. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.6, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (this release takes another stab at preventing issues related to Docker not stopping properly) If you have the Connect plugin installed and updated to the latest version Open the dropdown in the top-right of the Unraid webgui and click Check for Update. More details in this blog post If you don't have the Connect plugin installed Go to Tools -> Update OS and switch to the "Next" branch. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip. Upgrade notes This release has two very important fixes. First, we updated Docker to incorporate fixes for their recent security advisory. Second, we fixed a corner case bug which can lead to data loss if a newly added array drive has a non-standard partition layout. If you add one of these drives, the second time you start the array the drive will show as unformatted. If this happens please contact support and we can help you with data recovery. Even if you have not encountered this issue, we recommend upgrading so that you will not be affected when adding drives in the future. This release also includes some nice fixes in networking, Docker containers, Time Machine support, and VMs as well as fix for a slowdown some systems were having on the Dashboard. We have also improved the SMART attribute handling for NVME and SSD drives. Details below. Known issues Out of date plugins Out of date plugins can cause problems, we recommend they be kept current. Call traces and crashes related to macvlan If you are getting call traces related to macvlan (or any unexplained crashes, really), as a first step we recommend navigating to Settings > Docker, switching to advanced view, and changing the Docker custom network type from macvlan to ipvlan. This is the default configuration that Unraid has shipped with since version 6.11.5 and should work for most systems. Note that some users have reported issues with port forwarding from certain routers (Fritzbox) and reduced functionality with advanced network management tools (Ubiquity) when in ipvlan mode. If this affects you, see the alternate solution available since Unraid 6.12.4. Network problems due to jumbo frames If you are having network issues of any kind, confirm that you have not enabled jumbo frames. Navigate to Settings > Network Settings > eth0 and confirm the Desired MTU is 1500. For more information see the Fix Common Problems warning for jumbo frames. Problems due to Realtek network cards Upgraded kernel fixes the deadlock issue with jumbo frames and the in-tree Realtek 8125 driver. However, we still recommend following the advice above regarding jumbo frames. If you continue to have network stability issues and Tools > System Devices shows that you have a Realtek ethernet controller, grab the part number shown and search Community Apps to see if there is a Realtek vendor-supplied driver plugin for that device. For more information, see the support page for Realtek driver plugins. Other issues? We highly recommend installing the Fix Common Problems plugin as it will warn you of common configuration problems. If you are having other crashes or stability issues, navigate to Settings > Syslog Server and enable Mirror syslog to flash. This will cause additional wear and tear on you USB flash boot device but is useful in the short term for gathering logs after a crash. After the next reboot, navigate to Tools > Diagnostics and download your anonymized diagnostics (as of 6.12.5, diagnostics automatically include logs that were mirrored to the flash drive). Finally, start a new topic and provide all the details of the issue. Once the issue is resolved, be sure to disable Mirror syslog to flash. Rolling back Be aware that rolling back to an earlier release will make your system vulnerable to the Docker security issues and potential data loss scenario mentioned in Upgrade notes. If rolling back earlier than 6.12.6, also see the 6.12.6 release notes. Changes vs. 6.12.6 Bug fixes and improvements Docker: Fix WG routes added to the correct interface (br0 or eth0 or bond0) Use "lazy unmount" unmount of docker image to prevent blocking array stop Updated to address multiple security issues (CVE-2024-21626, CVE-2024-24557) Networking improvements: Boot faster by checking for carrier before assigning DHCP addresses Remove leading zeros from IPv4 and IPv6 addresses New '/etc/rc.d/rc.inet1 status' and '/etc/rc.d/rc.inet1 status ip' commands to aid with network troubleshooting from the command line Notifications: Add ntfy.sh to notification agents SMART improvements: Fix NVME Selftest Fix display of 'Accumulated power on time, hours:minutes xxxxx:yy' SMART attribute Display KB/MB/GB/TB written in SMART Attributes for SSDs Add 'SSD endurance remaining' SMART Attribute System logging: By default, syslog is copied to USB boot flash on shutdown, see Settings > Syslog Server to disable Logs from the above and Mirror syslog to flash are now available the next boot on Tools > Syslog and in diagnostics VM Manager: Fix for downgrade: if the VM template has been updated to the latest QEMU machine type it will not be found upon downgrade. This change finds latest current version for a given machine type. ZFS: Use zpool import "-f" flag to permit import of foreign pools Other: Enable EFI boot by default for fresh installations Fix slowdown on Dashboard and Docker pages (and reduces flash device writes) Formatting: do not initialize device partition layout if already valid. Update OS: redesigned Update OS and Downgrade OS pages, refer to blog post Fix MacOS unable to write 'flash' share and restore Time Machine compatibility (fruit changes) Allow Community Apps (if installed) to automatically start containers when doing a multi-install Feedback form: change DONE button to CANCEL Package updates docker: version 24.0.9 kernel-firmware: version 20231226_abfcad8 Linux kernel version 6.1.74 CONFIG_USB_SERIAL_XR: USB MaxLinear/Exar USB to Serial driver CONFIG_CAN: CAN bus subsystem support CONFIG_CAN_NETLINK: CAN device drivers with Netlink support CONFIG_CAN_GS_USB: Geschwister Schneider UG and candleLight compatible interfaces CONFIG_SCSI

The 6.12.3-rc3 release is a bug fix release that we'd like feedback on before releasing it as 6.12.3. This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.2, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (This issue is resolved with this release) Go to Tools -> Update OS, change the Branch to "Next". If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot Networking This release has fixes for networking, particularly as it relates to IPv6. A side effect is that this will resolve an issue where the webgui won't load in certain instances. Note: If you have code in your go script to disable IPv6, remove that and disable it via the Settings -> Network Settings page instead. Disabling IPv6 by manually running commands will cause conflicts. Docker This release resolves an issue where Docker doesn't properly stop when the array stops, which can result in an unclean shutdown. Known Issues Please review the known issues for 6.12: https://docs.unraid.net/unraid-os/release-notes/6.12.0#known-issues If Docker containers have issues starting after a while, and you are running Plex, go to your Plex Docker container settings, switch to advanced view, and add this to the Extra Params --no-healthcheck Feedback / bugs This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip. Changes vs. 6.12.2 Bug fixes and improvements rc.docker: revised docker daemon running check rc.library: code optimization for ipv6 max/min support ipv4 mapped addresses rc.nginx: explicit ipv4/ipv6 selection on lo interface shfs: correct share size calculation when zfs is one of the volumes webgui: VM settings page: fixed typo webgui: Share Edit page: make minimum free space settings always available Linux kernel Added support to monitor and also limit power on Intel Core (2nd Gen+) CPU models. version 6.1.38 CONFIG_POWERCAP: Generic powercap sysfs driver CONFIG_INTEL_RAPL: Intel RAPL Support via MSR Interface CONFIG_IDLE_INJECT: Idle injection framework Base Distro firefox: version 115.0.r20230710165010 (AppImage)

This release has a fix for macvlan call traces(!) along with other bug fixes, security patches, and one new feature. We'd like your feedback before releasing it as 6.12.4 This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.2, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (This issue was resolved with 6.12.3) Go to Tools -> Update OS, change the Branch to "Next". If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot Add Tools/System Drivers page This new page gives you visibility into the drivers available/in use on your system. 3rd party drivers installed by plugins (such as NVIDIA and Realtek) have an icon that links to the support page for that driver. And you can now add/modify/delete the modeprobe.d config file for any driver without having to find that file on your flash drive. Thanks to @SimonF for adding this functionality! Fix for macvlan call traces! The big news in this test release is that we believe we have resolved the macvlan issues that have been plaguing us recently! We'd appreciate your help confirming the changes. Huge thanks to @bonienl for tracking this down! The root of the problem is that macvlan used for custom Docker networks is unreliable when the parent interface is a bridge (like br0), it works best on a physical interface (like eth0). We believe this to be a longstanding kernel issue and have posted a bug report. If you are getting call traces related to macvlan, as a first step we'd recommend navigating to Settings/Docker, switch to advanced view, and change the "Docker custom network type" from macvlan to ipvlan. This is the default configuration that Unraid has shipped with since version 6.11.5 and should work for most systems. However, some users have reported issues with port forwarding from certain routers (Fritzbox) and reduced functionality with advanced network management tools (Ubiquity) when in ipvlan mode. For those users, in this rc we have a new method that reworks networking to avoid this. Simply tweak a few settings and your Docker containers, VMs, and WireGuard tunnels will automatically adjust to use them: Settings -> Network Settings -> eth0 -> Enable Bridging = No Settings -> Docker -> Host access to custom networks = Enabled Note: if you previously used the two-nic method for docker segregation, you'll also want to revert that: Settings -> Docker -> custom network on interface eth0 (i.e. make sure eth0 is configured for the custom network, not eth1) When you start the array, the host, VMs, and Docker containers will all be able to communicate, and there should be no more call traces! Troubleshooting If your Docker containers with custom IPs aren't starting, edit them and change the "Network type" to "Custom: eth0". We attempted to do this automatically, but depending on how things were customized you might need to do it manually. If your VMs are having network issues, edit them and set the Network Source to "vhost0". Also, ensure there is a MAC address assigned. If your WireGuard tunnels won't start, make a dummy change to each tunnel and save. If you are having issues port forwarding to Docker containers (particularly on a Fritzbox) delete and recreate the port forward in your router. To get a little more technical... After upgrading to this release, if bridging remains enabled on eth0 then everything works as it used to. You can attempt to work around the call traces by disabling the custom Docker network, or using ipvlan instead of macvlan, or using the two-nic Docker segmentation method with containers on eth1. Starting with this release, when you disable bridging on eth0 we create a new macvtap network for Docker containers and VMs to use. It has a parent of eth0 instead of br0, which is how we avoid the call traces. A side benefit is that macvtap networks are reported to be faster than bridged networks, so you may see speed improvements when communicating with Docker containers and VMs. FYI: With bridging disabled for the main interface (eth0), then the Docker custom network type will be set to macvlan and hidden unless there are other interfaces on your system that have bridging enabled, in which case the legacy ipvlan option is available. To use the new fix being discussed here you'll want to keep that set to macvlan. Other Bug Fixes This release resolves corner cases in networking, Libvirt, Docker, WireGuard, NTP, NGINX, NFS and RPC. And includes an improvement to the VM Manager so it retains the VNC password during an update. And has a change to the shutdown process to allow the NUT plugin to shut the system down. A small change is that packages in /boot/extra are now treated more like packages installed by plugins, and the installation is logged to syslog rather than to the console. Known Issues Please see this page for information on crashes related to the i915 driver: https://docs.unraid.net/unraid-os/release-notes/6.12.0#known-issues If Docker containers have issues starting after a while, and you are running Plex, go to your Plex Docker container settings, switch to advanced view, and add this to the Extra Params --no-healthcheck This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip. Rolling Back Before rolling back to an earlier version, it is important to first change this back to yes: Settings -> Network Settings -> eth0 -> Enable Bridging = Yes And then start the array (along with the Docker and VM services) to update your Docker containers, VMs, and WireGuard tunnels back to their previous settings which should work in older releases. Once in the older version, confirm these settings are correct for your setup: Settings -> Docker -> Host access to custom networks Settings -> Docker -> Docker custom network type Changes vs. 6.12.3 Networking New vhost network for both containers and VMs. When bridging enabled: Create shim interface which is attached to bridge interface Copy parent address to shim interface with lower metric to allow host access More specific routes are no longer created When bridging disabled: Copy parent address to vhost interface with lower metric to allow host access Bug fixes and improvements create_network_ini: fixed dhcp hook improved IP address collection diagnostics: Add previous Unraid version to diagnostics version txt file. Add ntp.conf, sshd.config, and servers.conf (with anonymized URLs) anonymize IP addresses libvirt, nginx, nfs, rpc: changed running process detection nfsclient: start negotiation with v4, turn off atime modification rc.6: leave /usr and /lib mounted during shutdown rc.docker: create same IPv6 network for containers and services add more logging when stopping dockerd rc.inet1: do not use promiscuous mode for bridging add persistent option to dhcpcd rc.library: interfaces always listed in the same order, fix show ipv6 rc.libvirt: remove 'itco' watchdog from XML if present rc.local: annotate auto-generated /etc/modprobe.d/zfs.conf file rc.services: add logging exclude WireGuard "VPN tunneled access for docker" tunnels from services exclude WireGuard tunnels for ntp (code optimization) webgui: Update monitor_nchan Feedback: refactor feedback script Shares and Pools: show "Minimum free space" as absolute number instead of percentage Pools: minimum free space: only enabled when array is stopped VM Manager: Retain VNC password during update. VM Manager: Remove downloaded '.vv' files. Dashboard: hide ZFS bar when no ZFS is used Network settings: fix DNS settings sometimes disappear Translations: trim key and value in language files add System Drivers page Linux kernel version 6.1.46 (CVE-2023-20593) CONFIG_SCSI_MPI3MR: Broadcom MPI3 Storage Controller Device Driver Base Distro btrfs-progs: 6.3.3 curl: version 8.2.0 (CVE-2023-32001) kernel-firmware: version 20230724_59fbffa krb5: version 1.19.2 (CVE-2023-36054) openssh: version 9.3p2 (CVE-2023-38408) openssl: version 1.1.1v (CVE-2023-3817 CVE-2023-3446) samba: version 4.17.10 (CVE-2023-3496 CVE-2022-2127 CVE-2023-34968 CVE-2023-3496 CVE-2023-3347)

Please refer to the 6.12.0-rc1 topic for a general overview. For exclusive shares we made an implementation change. We found issues using bind-mounts with ZFS pools with internal nested child datasets. To overcome this problem, symlinks are created in /mnt/user instead. For example, for an exclusive share named "myshare" which exists only on "mypool" this symlink is generated: /mnt/user/myshare -> /mnt/mypool/myshare This implementation is actually a little cleaner and provides the same benefits of faster throughput. Version 6.12.0-rc6 2023-05-17 Changes vs. 6.12.0-rc5 Use symlinks instead of bind-mounts for exclusive shares. Fix share rename when share contains space and located on zfs pool. Share Edit: allow 1 letter names Network improvements: rc.docker - suppress ipv6 link-local address for docker0 and shim interfaces when set as ipv4 only rc.avahidaemon - let service listen on regular interfaces only which have an IP address, this includes the primary interface + set ipv4 / ipv6 support rc.samba - let smb, nmb service listen on regular interfaces only which have an IP address, this includes the primary interface + set ipv4 / ipv6 support (also for wsdd2) rc.ssh - listen on regular interfaces only which have an IP address, this includes the primary interface + set ipv4 / ipv6 support rc.inet1 - add iptables processing to bridge interfaces to make them operate similarly as macvlan interfaces create_network_ini - restart smb when network changes are done VMs: fixed notification subject TRIM: fix operation when ZFS is not active Network settings: fix bug in description field bash_completion: version 2.11 docker: version 23.0.6 Use 'zfs set atime=off' Upon root dataset mount; child datasets should inherit this setting. Continue format if blkdiscard command fails. Add Pushbits Agent for Matrix/Synapse integration https://github.com/pushbits/server Share Edit: warn when invalid zfs name is used Lock / unlock button: switch green / red color Green is normal state (page is locked) Red is attention state (page is unlocked) Linux kernel version: 6.1.29 Version 6.12.0 (Consolidated) Upgrade notes General If you created any zpools using 6.12.0-beta5 please Erase those pools and recreate. If you revert back from 6.12 to 6.11.5 or earlier, you have to force update all your Docker containers and start them manually after downgrading. This is necessary because of the underlying change to cgroup v2 in 6.12.0-rc1. Upon boot, if all PCI devices specified in 'config/vfio-pci.cfg' file do not properly bind, VM Autostart is prevented. You may still start individual VMs. This is to prevent Unraid host crash if hardware PCI IDs changed because of a kernel update or physical hardware change. To restore VM autostart, examine '/var/log/vfio-pci-errors' and remove offending PCI IDs from 'config/vfio-pci.cfg' file and reboot. Linux Multi-Gen LRU is a relatively new feature now included but not enabled by default. You can enable by adding this line to your 'config/go' file: echo y > /sys/kernel/mm/lru_gen/enabled If you revert back from 6.12 to 6.11.5 or earlier you many need to remove that line. Obsolete/Broken Plugins There are a few plugins which are known to be incompatible with Unraid 6.12, and upon boot will not be installed. You will get a notification for each plugin that is affected, and can review the list by going to Plugins/Plugin File Install Errors. disklocation-master version 2022.06.18 (Disk Location by olehj, breaks the dashboard) plexstreams version 2022.08.31 (Plex Streams by dorgan, breaks the dashboard) corsairpsu version 2021.10.05 (Corsair PSU Statistics by Fma965, breaks the dashboard) gpustat version 2022.11.30a (GPU Statistics by b3rs3rk, breaks the dashboard) ipmi version 2021.01.08 (IPMI Tools by dmacias72, breaks the dashboard) nut version 2022.03.20 (NUT - Network UPS Tools by dmacias72, breaks the dashboard) NerdPack version 2021.08.11 (Nerd Tools by dmacias72) upnp-monitor version 2020.01.04c (UPnP Monitor by ljm42, not PHP 8 compatible) ZFS-companion version 2021.08.24 (ZFS-Companion Monitor by campusantu, breaks the dashboard) Some of the affected plugins have been taken over by different developers, we recommend that you go to the Apps page and search for replacements. Please ask plugin-specific questions in the support thread for that plugin. Known issues We are aware that some 11th gen Intel Rocket Lake systems are experiencing crashes related to the i915 iGPU. If your Rocket Lake system crashes under Unraid 6.12.0, open a web terminal and run: echo "options i915 enable_dc=0" >> /boot/config/modprobe.d/i915.conf then reboot. Using this parameter will result in higher power use but it may resolve this issue for these GPUs. When Unraid 6.13 is released it will have a newer Linux kernel with better i915 support, we anticipate that at that point you can revert this tweak with: rm /boot/config/modprobe.d/i915.conf If "Docker custom network type" is set to "macvlan" you may get call traces and crashes on 6.12 even if you did not on 6.11. If so, we recommend changing to "ipvlan", or if you have two network cards you can avoid the issue completely: https://forums.unraid.net/topic/137048-guide-how-to-solve-macvlan-and-ipvlan-issues-with-containers-on-a-custom-network/ ZFS Pools For a good overview of ZFS, see https://arstechnica.com/information-technology/2020/05/zfs-101-understanding-zfs-storage-and-performance/ New in this release is the ability to create a ZFS file system in a user-defined pool. In addition you may format any data device in the unRAID array with a single-device ZFS file system. We are splitting full ZFS implementation across two Unraid OS releases. Initial support in this release includes: Support raid0, mirror, raidz1, raidz2 and raidz3 root profiles. Up to 4-way mirror in a mirror vdev. Multiple vdev groups. Support removing single device: if device still present in server, 'wipefs' is used to clear the partition table. Support replacing single missing device with a new device of same or larger size. Support scheduled trimming of ZFS pools. Support pool rename. Pool names must begin with a lowercase letter and only contain lowercase letters, digits, the underscore and dash. Pool names must not end with a digit. Non-root vdev cannot be configured in this release, however, they can be imported. Note: imported hybrid pools may not be expanded in this release. Pools created on other systems may or may not import depending on how the the pool was created. A future update will permit importing pools from any system. A ZFS pool has three variables: profile - the root data organization: raid0, mirror (up to 4-way), raidz1, raidz2, raidz3 width - the number of devices per root vdev groups - the number of root vdevs in the pool At time of ZFS pool creation, the webGUI will present all topology options based on the number of devices assigned to the pool. Special treatment for root single-vdev mirrors: A single-device ZFS pool can be converted to multiple-device mirror by adding up to 3 additional devices in one operation. A 2-device mirror can be increased to 3-device by adding a single device; similarly a 3-device mirror can be increased to 4-device mirror by adding a single device. To add an additional root vdev, you must assign 'width' number of new devices to the pool at the same time. The new vdev will be created with the same 'profile' as the existing vdevs. Additional flexibility in adding/expanding vdevs will be provided in a future update. Pools created with the steini84 plugin can be imported as follows: First create a new pool with the number of slots corresponding to the number of devices in the pool to be imported. Next assign all the devices to the new pool. Upon array Start the pool should be recognized, though certain zpool topologies may not be recognized (please report). Mixed topologies are not supported. For example, a pool with both a mirror root vdev and a raidz root vdev is not recognized. Autotrim can be configured as on or off (except for single-device ZFS volumes in the unRAID array). Compression can be configured as on or off, where on selects lz4. Future update will permit specifying other algorithms/levels. When creating a new ZFS pool you may choose zfs - encrypted, which, like other encrypted volumes, applies device-level encryption via LUKS. ZFS native encryption is not supported at this time. During system boot, the file /etc/modprobe.d/zfs.conf is auto-generated to limit the ZFS ARC to 1/8 of installed memory. This can be overridden if necessary by creating a custom 'config/modprobe.d/zfs.conf' file. Future update will include ability to configure the ARC via webGUI, including auto-adjust according to memory pressure, e.g., VM start/stop. Top-level user shares in a ZFS pool are created as datasets instead of ordinary directories. Share storage conceptual change New in this release is a conceptual change in the way storage is assigned to shares. The old concept of main storage being the unRAID array with an optional "Cache" is confusing to many new users, especially since cache has a specific meaning in ZFS. Also outlined below, we introduced the concept of an exclusive share. This is simply a share where all the data exists in a single named pool. In this case the FUSE-based User Share file system returns a symlink to the actual share directory in the pool. All operations within the share, including data transfer, therefore bypass FUSE, resulting in greater performance. This feature is primarily aimed at maximizing I/O for large fast ZFS pools accessed via a fast network This is front-end change only; existing shares will be viewed with this new structure automatically upon upgrading, and will automatically revert to the previous style if you revert to an earlier version. Configuring the storage options for a share is specified using two inputs: Primary storage Secondary storage Primary storage is where new files/folders are created. If Primary storage is below the Minimum Free Space setting then new files and folders will be created in Secondary storage, if configured. Each input presents a drop-down which lists "array", "none", and each named pool as a selection according to some configuration rules: For the Primary storage drop-down: the "none" option is omitted, ie, Primary storage must be selected any named pool can be selected "Array" can be selected (meaning the unRAID array) For the Secondary storage drop-down: the "none" option is included, ie, Secondary storage is optional if Primary storage is a pool name, then the only options are "none" and "Array". In the future other pools will be listed here as well. if Primary storage is "Array", then only "none" appears as an option When "Array" is selected for either Primary or Secondary storage, a set of additional settings slide in: Allocation method Included disk(s) Excluded disk(s) Split level When a btrfs named pool is selected for either Primary or Secondary storage, an additional setting slides in: Enable Copy-on-write When a ZFS named pool is selected for either Primary or Secondary storage, there are no additional settings at this time but there could be some in the future. For example, since a share is created as a ZFS dataset, it could have a different compression setting than the parent pool if we need to implement this. Mover action When there is Secondary storage configured for a share the "Mover action" setting becomes enabled, letting the user select the transfer direction of the mover: Primary to Secondary (default) Secondary to Primary Exclusive shares If Primary storage for a share is a pool and Secondary storage is set to "none", then a symlink is returned in /mnt/user/ pointing directly to the pool share directory. (An additional check is made to ensure the share also does not exist on any other volumes.) There is a new status flag, 'Exclusive access' which is set to 'Yes' when a symlink is in place; and, 'No' otherwise. Exclusive shares are also indicated on the Shares page. The advantage of setting up symlinks is that I/O bypasses FUSE-based user share file system (shfs) which can significantly increase performance. There are some restrictions: Both the share Min Free Space and pool Min Free Space settings are ignored when creating new files on an exclusive share. If there are any open files, mounted loopback images, or attached VM vdisk images on an exclusive share, no settings for the share can be changed. As a workaround, create a directory for the share on another volume and restart the array to disable exclusive access and make the necessary changes to the share settings. If the share directory is manually created on another volume, files are not visible in the share until after array restart, upon which the share is no longer exclusive. Clean Up button Appearing on the Shares page, a button called CLEAN UP, when enabled indicates there are config/share/.cfg files for shares that do not exist. Clicking this button will remove those files. Other Improvements btrfs pools Autotrim can be configured as on or off when used in a pool. Compression can be configured as on or off. on selects zstd. Future update to permit specifying other algorithms/levels. xfs Autotrim can be configured as on or off when used as a single-slot pool. Docker It is possible to configure the Docker data-root to be placed in a directory on a ZFS storage pool. In this case Docker will use the 'zfs' storage driver. This driver creates a separate dataset for each image layer. Because of this, here is our recommendation for setting up Docker using directory: First, create a docker user share configured as follows: Share name: docker Use cache pool: Only Select cache pool: name of your ZFS pool Next, on Docker settings page: Enable docker: Yes Docker data-root: directory Docker directory: /mnt/user/docker If you ever need to delete the docker persistent state, then bring up the Docker settings page and set Enable docker to No and click Apply. After docker has shut down click the Delete directory checkbox and then click Delete. This will result in deleting not only the various files and directories, but also all layers stored as datasets. Before enabling Docker again, be sure to first re-create the docker share as described above. Other changes: CreateDocker: changed label Docker Hub URL to Registry URL because of GHCR and other new container registries becoming more and more popular. Honor user setting of stop time-out. Accept images in OCI format. Add option to disable readmore-js on container table Fix: Docker Containers console will not use bash if selected VM Manager If you enable copy/paste for virtual consoles you need to install additional software on the client in addition to the QEMU agent if that has been installed. Here is the location for spice-vdagent for both Windows and Linux. Note copy/paste function will not work with web spice viewer you need to use virt-viewer. Other changes: Add Serial option to vdisk. Spice Bug fix for users with non standard GUI ports defined. OVMF for QEMU: version stable202302 Fix for bus text. Enable copy paste option for virtual consoles Update Memory Backup processing for Virtiofs. Fix lockup when no VMs are present Add support for rtl8139 network model. fix translation omission added lock/unlock for sortable items Fix for Spice Mouse if Copy paste enabled. let page load even when PCI devices appear missing or are misassigned Make remote viewer and web console options selectable. Option to download .vv file and start remote viewer is browser set to open file .vv when downloaded. Add remote viewer console support Remove-lock-posix='on'-flock='on'/- fix VM marked as Autostart not starting following manual array Start Fix for Max memory > 1TB Dashboard The webGUI Dashboard has been redesigned and it is now possible to move elements (tiles) up and down and between columns. This allows the user to organize the tiles in any way they desire. There is a small lock icon on the menu bar which must be clicked to enable this function. Note: The lock icon also appears on the Docker and VM pages and must be clicked to rearrange the startup order. Release bz file differences Unraid OS is comprised of a set of 5 so-called bz files in the root of the USB Flash boot device: bzimage - the Linux kernel bzroot - the root file system, sans console desktop bzroot-gui - additional files needed for console desktop bzmodules - modules (drivers) associated with the Linux kernel bzfirmware - device firmware required by certain modules Starting with 6.12 release, the content of these files has been rearranged: bzimage - the Linux kernel (same as before) bzroot - the root file system excluding the /usr directory tree bzroot-gui - a single file which auto-starts the console desktop (for compatibility) bzmodules - modules (drivers) associated with the Linux kernel and device firmware required by certain modules bzfirmware - the /usr directory and all files contained therein, including console desktop The results of this change is to speed up the boot process and free up nearly 1G of RAM. It also permits us to add more "stuff" to Unraid OS in the future without requiring more RAM. Finally, when booted in non-GUI mode, the desktop can be started by logging in at the console and typig the 'slim' command. The files bzfirmware and bzmodules are squashfs images mounted using overlayfs at /usr and /lib respectively. Since these files are loopback-mounted, care must be taken if ever you want to perform a manual update. What is a manual update? This is a method of updating Unraid OS on your USB flash boot device without using the Tools/Update OS function. Typically one would either: open a Terminal window, wget the release zip file, unzip the release, and then 'cp' the bz files to root of the boot device. or export the 'flash' share on your network and drag the bz files from a PC directly to the flash. Either method, starting with 6.12 can fail because the bzfirmware file will be overwritten while it is still mounted - not good. To get around this, you must first create a temp directory on the flash device and then 'mv' (or drag) all the bz files to this temp directly. Now you can copy the new bz files in place and reboot. Change Log Base Distro aaa_glibc-solibs: version 2.37 adwaita-icon-theme: version 43 at-spi2-core: version 2.46.0 bash: version 5.2.015 bash_completion: version 2.11 bind: version 9.18.12 btrfs-progs: version 6.2.1 ca-certificates: version 20221205 cryptsetup: version 2.6.1 curl: version 7.88.1 dbus: version 1.14.6 diffutils: version 3.9 dnsmasq: version 2.89 docker: version 23.0.6 e2fsprogs: version 1.47.0 encodings: version 1.0.7 file: version 5.44 firefox: version 111.0 (AppImage) freetype: version 2.13.0 fuse3: version 3.12.0 gawk: version 5.2.1 git: version 2.39.2 glib2: version 2.74.6 glibc: version 2.37 glibc-zoneinfo: version 2022g gnutls: version 3.7.9 gptfdisk: version 1.0.9 gtk+3: version 3.24.37 harfbuzz: version 7.1.0 htop: version 3.2.2 iproute2: version 6.2.0 iptables: version 1.8.9 iputils: version 20221126 less: version 612 libICE: version 1.1.1 libSM: version 1.2.4 libX11: version 1.8.4 libXau: version 1.0.11 libXcomposite: version 0.4.6 libXdamage: version 1.1.6 libXdmcp: version 1.1.4 libXpm: version 3.5.15 libXrandr: version 1.5.3 libXres: version 1.2.2 libXxf86dga: version 1.1.6 libarchive: version 3.6.2 libdrm: version 2.4.115 libfontenc: version 1.1.7 libglvnd: version 1.6.0 libjpeg-turbo: version 2.1.5.1 libpcap: version 1.10.3 libpng: version 1.6.39 libpsl: version 0.21.2 liburcu: version 0.14.0 libwebp: version 1.3.0 libxkbcommon: version 1.5.0 libxkbfile: version 1.1.2 libxshmfence: version 1.3.2 lmdb: version 0.9.30 logrotate: version 3.21.0 lsof: version 4.98.0 lz4: version 1.9.4 lzlib: version 1.13 mc: version 4.8.29 mcelog: version 191 mpfr: version 4.2.0 nano: version 7.2 ncurses: version 6.4 nginx: version 1.23.3 nghttp2: version 1.52.0 openssh: version 9.2p1 openssl: version 1.1.1t openssl-solibs: version 1.1.1t openzfs: version 2.1.11 pango: version 1.50.14 pciutils: version 3.9.0 pcre2: version 10.42 php: version 8.2.4 php-libvirt: version 0.5.7 php-markdown: version 2.0.0 samba: version 4.17.7 sqlite: version 3.41.0 sudo: version 1.9.13p2 sysstat: version 12.7.2 tdb: version 1.4.8 tevent: version 0.14.1 traceroute: version 2.1.2 transset: version 1.0.3 tree: version 2.1.0 usbutils: version 015 xcb-util: version 0.4.1 xdriinfo: version 1.0.7 xf86-video-vesa: version 2.6.0 xfsprogs: version 6.1.1 xhost: version 1.0.9 xinit: version 1.4.2 xkbcomp: version 1.4.6 xkeyboard-config: version 2.38 xorg-server: version 21.1.7 xprop: version 1.2.6 xrandr: version 1.5.2 xset: version 1.2.5 xterm: version 379 xz: version 5.4.1 zstd: version 1.5.4 Linux kernel version 6.1.29 md/unraid: version 2.9.27 CONFIG_FS_DAX: File system based Direct Access (DAX) support CONFIG_VIRTIO_FS: Virtio Filesystem CONFIG_ZONE_DEVICE: Device memory (pmem, HMM, etc...) hotplug support CONFIG_USBIP_HOST: Host driver CONFIG_INTEL_MEI: Intel Management Engine Interface CONFIG_INTEL_MEI_ME: ME Enabled Intel Chipsets CONFIG_INTEL_MEI_GSC: Intel MEI GSC embedded device CONFIG_INTEL_MEI_PXP: Intel PXP services of ME Interface CONFIG_INTEL_MEI_HDCP: Intel HDCP2.2 services of ME Interface CONFIG_INTEL_PMC_CORE: Intel PMC Core driver CONFIG_DRM_I915_PXP: Enable Intel PXP support CONFIG_SCSI_FC_ATTRS: FiberChannel Transport Attributes CONFIG_FUSION_SPI: Fusion MPT ScsiHost drivers for SPI CONFIG_FUSION_FC: Fusion MPT ScsiHost drivers for FC CONFIG_FUSION_CTL: Fusion MPT misc device (ioctl) driver CONFIG_FUSION_LOGGING: Fusion MPT logging facility CONFIG_X86_AMD_PSTATE: AMD Processor P-State driver CONFIG_LRU_GEN: Multi-Gen LRU CONFIG_SERIAL_8250_NR_UARTS=32: Maximum number of 8250/16550 serial ports CONFIG_SERIAL_8250_RUNTIME_UARTS=4: Number of 8250/16550 serial ports to register at runtime Misc avahi: enable/disable IPv4/IPv6 based on network settings and restrict avahidaemon to primary interface. cgroup2 now the default loopback images no longer mounted using directio newperms script restricted to operate on /mnt/ only. upgradepkg patched to prevent replacing existing package with older version. current PCI bus/device information saved in file '/boot/previous/hardware' upon Unraid OS upgrade. NFS: enable UPD transport emhttp: fix cache pool (null) syslog strings emhttp: fix cache pool display wrong device size for selected replacement device networking: fix nginx recognizing IP address from slow dhcp servers mover: fix: improper handling of symlinks mover: fix: Mover logging syslog entries format different from previous releases plugin: Display Run command retval in error message shfs: igonore top-level hidden directoris (names beginning with '.') terminal: OpenTerminal: change termination signal (hard stop) upgrade Unraid OS: check for earlier upgrade without reboot webgui: support PHP8, increase PHP max memory from 128M to 256M webgui: ManagementAccess: Disable Provision/Renew/Upgrade buttons when no IP on eth0 webgui: ManagementAccess: Support wireguard local IP addresses in combination with myservers.unraid.net SSL cert webgui: Move "view" icon on Main and Shares page to the left webgui: Dashboard: fix regression error in "select case" webgui: Dashboard: make items moveable between columns webgui: Keep dismissed banners hidden for a month webgui: Dashboard: API for adding custom tiles webgui: Dashboard: rearrange processor information webgui: Dashboard: rearrange UPS info webgui: Dashboard: rearrange memory info webgui: Dashboard: VPN header rearrangement webgui: Dashboard: header rearrangements webgui: Add jqueryUI touch punch for mobile devices webgui: Changed ID to CLASS for elements occurring more than once webgui: Make header in white and black themes scrollable When more items are present than screen space, the user can now scroll through them (previously these items were invisible) webgui: Dashboard and Docker: introduce lock button for sortable items By default sortable items are locked, which allows mobile devices to scroll the page. Upon request items can be made sortable webgui: Users: add icon to title bar webgui: Tools: new function -> PHP Settings View PHP info Configure error reporting Open LOG to see errors in real-time webgui: System info: fix reading inactive ports webgui: Plugin: Include the actual command, being executed webgui: System info: cache enhancement webgui: System info: memory enhancement webgui: DeviceInfo: disable buttons when erase operation is running webgui: Docker: filetree corrections webgui: Fixed: Dashboard: show heat alarm per pool webgui: Notifications: revised operation Autoclose new notifications after 3 seconds Fix notifications reappearing after closure webgui: DeviceList: add FS type in offline state webgui: Add notification agent for Bark webgui: Main: hide browse icon when disk is not mounted webgui: Diagnostics: add additional btrfs and zfs info webgui: Dashboard: add ZFS memory usage webgui: Revised New Permissions Select either disks or shares (not both) webgui: Add testparm to diagnostics webgui: Support new UD reserved mount point of /mnt/addons webgui: fix issue displaying Attributes when temperature display set to Fahrenheit webgui: Dashboard changes: lock the Dashboard completely: Editing/moving only becomes possible when unlocking the page An empty column is refilled when the respective tiles are made visible again, no need to reset everything added a visual "move indicator" on the Docker and VM page, to make clearer that rows can be moved now. change cursor shape when moving is enabled use tile title as index webgui: fix: Local Firefox account pop-up postmessages not working webgui: SMART test cannot be run on a UD disk because there is no spin down delay selection webgui: status footer stuck on "Starting services" when applying share config setting chagnes. webgui: Fix table layout for orphan images webgui: Plugin: Do not show update button if incompatible webgui: OpenTerminal: limit clients webgui: Context menu: automatic triangle placement webgui: Dashboard: fix pool warnings webgui: Allow SMART long test for UD webgui: Read processor type from /proc/cpuinfo webgui: CSS: solve scrollbar issue in firefox webgui: plugin: Make wget percentage detection more robust webgui: Add share: fix hidden share name check webgui: Display settings: add missing defaults webgui: Array Operation: prevent double clicking of Start button webgui: DeviceInfo: show shareFloor with units webgui: DeviceInfo: added automatic floor calculation webgui: Added autosize message webgui: Shares: added info icon webgui: Updated DeviceInfo and Shares page webgui: Fix network display aberration. webgui: Auto fill-in minimum free space for new shares webgui: feat(upc): update to v3 for connect webgui: Share/Pool size calculation: show and allow percentage values wireguard: add SSL support for WG tunnel IP addresses (myunraid.net wildcard certs only) wireguard: fix nginx issue when partial WireGuard config