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

Please refer to the 6.12.0-rc1 topic for a general overview. Version 6.12.0-rc4.1 2023-04-27 Fixes bug in bind-mount when share names contain spaces. 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

Please refer to the 6.12.0-rc1 topic for a general overview. Version 6.12.0-rc8 2023-06-10 Changes vs. 6.12.0-rc7 Bug fixes: Fix regression error in rc.S: must install third-party drivers before first invocation of udev. Fix smb bind when using wireguard/tailscale tunnel. Remove 'lo' from rc.rpc, it is already included. Fix regression error in disk utilization and disk temperature thresholds. Fix issue expanding single-device ZFS pool to multi-device mirror. Increase max number of devices per pool from 30 to 60 (experimental). DeviceInfo: fix incorrect floor size entries. Base Distro openzfs: version 2.1.12 Linux kernel version 6.1.33 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 Version 6.12.0-rc6 2023-05-17 Changes vs. 6.12.0-rc5 Use symlinks instead of bind-mounts. 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 colorr 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

Hi, after upgrading from 6.12.3 to 6.12.4 my Webui has been very slow. Special on docker tab and dashboard. Takes almost 12 sec before the page is visible. I can see my CPU are wokring MUCH more when i try to open DOCKER tab or the Dashboard. Never seen a behaver like this before. I tried to stop Array, but Dashboard is still slow 12 seconds to open it, normally it tooks 2 seconds. Tried to remove some plugins, but still the same EDIT 1: After removing more plugins and multiple reboots. The issue is till there. EDIT 2: I decide to revert back to 6.12.3. And guess what, it working normally again, fast like it always was So can someone please explain me why I had this kind of issue with 6.12.4 ? EDIT 3: Tested v.6.12.5 RC 1 and the latest version released yesterday, v.6.12.5. It's still the same. Adding the diagnostics from my backup server (Galactica)

There are several reports in the forums of this shfs error causing /mnt/user to go away: May 14 14:06:42 Tower shfs: shfs: ../lib/fuse.c:1451: unlink_node: Assertion `node->nlookup > 1' failed. Rebooting will fix it, until it happens again, I remember seeing at least 5 or 6 different users with the same issue in the last couple of months, it was reported here that it's possibly this issue: https://github.com/libfuse/libfuse/issues/128 Attached diags from latest occurrence. tower-diagnostics-20200514-1444.zip

I have binhex-qbittorrent setup, and I am routing some other containers (firefox + prowlarr) through that VPN container with "--network=container:binhex-qbittorrentvpn". On the Firefox and Prowlarr containers I have network type set to none. What has been happening recently, I think as far back as 6.12.3 is that it will randomly start showing port mappings from other unrelated containers (usually a container thats had a recent change, like recently installed, or recently upgraded). For example, right now its showing mapping information from my Overseerr container for no reason. The only way I can get the port mapping to disappear on this screen is to edit both Firefox and Prowlarr and toggle their network type to something else, and then toggle it back to "None" and it will show no port mapping for a while. But over time it reappears with a new random mapping from a different container I have installed at random. Now I don't think this is actually a concern. I don't believe its truly trying to do any mappings, as again the network type = none. I think this is more of an annoyance, but I wonder why this changed all of a sudden? Could this be fixed and have it be changed to just be blank with no mappings? Alternatively, have it show mappings for the master VPN container they are being routed through? Seems others are reporting the same bug: https://forums.unraid.net/bug-reports/stable-releases/docker-tab-ip-view-broken-on-network-bridged-containers-r2768/ https://forums.unraid.net/bug-reports/stable-releases/6124-dockerpage-shows-bogus-port-mappings-r2632/ https://forums.unraid.net/bug-reports/stable-releases/6123-wrong-info-in-docker-tab-when-some-containers-route-via-other-ones-r2615/

Hello, I got the following output in my syslog: https://pastebin.cloud-becker.de/5ede1251c0f8 (Diagnostic attached) I know, the general fix for this is using "ipvlan" instead of "mcvlan". But in my (and other people) case, this isn't an option. The AVM Fritzbox (7595 in my case) isn't compatible with ipvlan. I came from the latest 6.11.x stable without any problems, the same for 6.10.x . @alturismo got the same problem with 6.12.x, also when he was problemless on 6.11.x . Maybe he can post some more details from his setup. So I hope it is fixable, especially when version before run without this problem. unraid-1-diagnostics-20230429-1014.zip

In previous versions of UNRAID the /usr and part of the /lib folder were a part of the root filesystem / and in the process were never unmounted because the root filesystem / persisted in RAM throughout the shutdown sequence in /etc/rc.d/rc.6. This also meant that all the binaries in /usr/sbin and /usr/local/sbin were available to the services until the system halted entirely, ensuring - for example - plugins could also run their respective shutdown sequences gracefully by utilizing their binaries in /usr/sbin (e.g. shutdown devices, stop their associated services etc.) In newer versions of UNRAID (e.g. the latest 6.12.3) the /usr and entire /lib folder are no longer part of the root filesystem / and are unmounted being separate mount-points due to the mass-unmount-all command present early on in /etc/rc.d/rc.6: # Unmount local file systems: echo "Unmounting local file systems:" /bin/umount -v -a From that point on anything in the /usr and /lib folders becomes unavailable including anything in /usr/sbin or /usr/local/sbin, which is curious because the shutdown script actually proceeds to reference such an unavailable binary directly below that mass-unmount-all command: # Unmount local file systems: echo "Unmounting local file systems:" /bin/umount -v -a # limetech - shut down the unraid driver if started if /bin/grep -qs 'mdState=STARTED' /proc/mdstat ; then echo "Stopping md/unraid driver:" /usr/local/sbin/mdcmd stop if ! /bin/grep -qs 'mdState=STOPPED' /proc/mdstat ; then echo "Unclean shutdown - Cannot stop md/unraid driver" else # we have to mount /boot again if ! /sbin/mount -v /boot ; then echo "Unclean shutdown - Cannot remount /boot" else /bin/rm -f /boot/config/forcesync /sbin/umount /boot echo "Clean shutdown" fi fi fi This if-clause will never be able to stop the md/unraid driver (if it is started), because the binary mdcmd at that point is already unmounted and unavailable due to the command above that if-close unmounting the entire /usr tree. Another problem we're facing with this behaviour is - as an example - our NUT plugin (for UPS) being unable to shutdown the UPS inverter because the binary call to /usr/sbin/upsdrvctl is made impossible by the premature unmounting of /usr - see further details here: I therefore propose the developers consider persisting the /usr and /lib mount-points until the system halts, as they should only be in RAM anyhow and their unmounting seems to be no requirement for a graceful shutdown but rather complicates such a graceful shutdown for both the plugins and the core system itself. Perhaps reverting to either specifying which types of filesystems to unmount or which types of filesystems not to unmount utilizing umount -v -a -t instead of just umount -v -a could be considered, as it was done in earlier versions of UNRAID. Overall, is unmounting the local filesystems on shutdown even necessary at all when they exist just in RAM?

Hi, I have built an new UNRAID ITX-System and want to use the onboard Realtek RTl8125BG network adapter because of the support of 2,5GBit/s network speed. The network adapter is recognised correctly and is using the kernel integrated r8169 driver. I have expirienced the already known problem like in the thread below: With iperf3 I am also reaching nearly the whole performance of the max. 2,5GBit/s in both directions. But If I use an SMB share and try to load an big file on it, I only reach approx. 30MByte/s upload speed. Download instead ist working fine. The file was loaded to an Samsung 970 Evo Plus M.2 SSD so this should not be the bootleneck here. It seems that the r8169 driver is not working well with the RTL8125BG network card in my case. The only "and not good" solution was to load an different bzmodules and bzimage file from these chinese unraid forum thread: After blacklisting the r8169 kernel driver the new r8125 driver was loaded and the adapter was working well afterwards with up- and downlink speeds of nearly 300MByte/s when using SMB shares. Is there any solution how to get this fixed without exchanging the whole bzmodules/bzimage file and load only the extra driver for my network card? best regards René unraid-diagnostics-20230506-1403.zip

Hi, I would like to report a Bug with the Official 6.12.0 / 6.12.1 version. SInce the 6.12.x beta + rc, it seems that there is some kind of memory leak or similar, that make Docker not working properly until a full Reboot occurs. The issue can be reproduce easily : 1. Boot Unraid 6.12 2. Start all your dockers 3. Wait (randomly 3-4-5 days, never same amount of time) 4. Update a docker, and it will not be able to start, throwing a "Execution Error" / "Server Error". Once you start getting this error, you won't be able to restart ANY dockers you have running (it will throw the same error). You can't even disable Docker, then Re-enable Docker, it just fail. A full server reboot will fix it for 3-4-5 more days, then it will come back. Another observation, I'm running "homepage" docker, and it sees the "health" of "PlexMediaServer" docker. When the bug isn't triggered yet (during the first days after a reboot), it reports the health of PlexMediaServer to be "healthy", but once the bug is happening, even without restarting a docker, the homepage docker report "Unhealthy" for Plex. At that point, I know I need to reboot. I confirmed by trying restarting any docker, and got the "Execution Error" every single time that the Plex is shown as "unhealthy". Hopefully, this bug report will get some traction. If you haven't seen it yet, I suppose it's a question of days before it happens. I see that i'm not alone with this bug (see : https://forums.unraid.net/topic/140301-unraid-612-rc7-docker-stops-after-update/#comment-1274038 )

Posting this on behalf of multiple Tailscale plugin users. Related Discussions https://forums.unraid.net/topic/136889-plugin-tailscale/page/7/#comment-1272479 (contains diagnostics) https://github.com/dkaser/unraid-tailscale/issues/57 (further discussion, includes the relevant configuration file) Symptoms SSH will fail to start when: Normal/Wireguard interfaces only have IPv4 addresses, and Extra (e.g., tailscale) interfaces have IPv4 + IPv6 addresses. In this configuration, the sshd_config file is created with the following information: Port 22 AddressFamily inet ListenAddress 192.168.1.66 ListenAddress 100.69.69.16 ListenAddress fd7a:115c:a1e0:ab12:4843:cd96:6245:4510 This is an invalid configuration, since "AddressFamily inet" forces sshd to only accept IPv4 addresses. As a result, the service fails to start. Fix The check() function in /etc/rc.d/rc.library.source does not consider "extra" interfaces when setting the values of $ipv4 and $ipv6. It then uses these variables to determine if AddressFamily should be set to inet, inet6, or any. /etc/rc.d/rc.library.source should either consider extra interfaces when setting the sshd family, or AddressFamily should always be set to any.

Hi, As we previously discussed in this topic, I noticed that if the mover is running, transferring a file from the cache drive to the array, and the system receives a shutdown command, unRaid will not be able to move the file that was being transferred anymore. In fact, after rebooting, part of the file is in the array, meaning the mover will not retry to transfer the actual file that is in the cache drive. A manual fix is to manually delete the partial file on the array.

Don't know if this has been reported before, but the diagnostics package saved contains VPN passwords if the server is currently running a docker container using a VPN. That would create an issue for anyone that has posted their diagnostics to the forum (note that I've masked the user and pass here) \_ /usr/bin/openvpn --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV pia --setenv VPN_CLIENT openvpn --setenv DEBUG false --setenv VPN_DEVICE_TYPE tun0 --setenv VPN_ENABLED yes --setenv VPN_REMOTE_SERVER denmark.privacy.network --setenv APPLICATION deluge --script-security 2 --writepid /root/openvpn.pid --remap-usr1 SIGHUP --log-append /dev/stdout --pull-filter ignore up --pull-filter ignore down --pull-filter ignore route-ipv6 --pull-filter ignore ifconfig-ipv6 --pull-filter ignore tun-ipv6 --pull-filter ignore dhcp-option DNS6 --pull-filter ignore persist-tun --pull-filter ignore reneg-sec --up /root/openvpnup.sh --up-delay --up-restart --keepalive 10 60 --setenv STRICT_PORT_FORWARD yes --setenv VPN_USER xxxxxxxx --setenv VPN_PASS xxxxxxxxxx --down /root/openvpndown.sh --disable-occ --auth-user-pass credentials.conf --cd /config/openvpn --config /config/openvpn/denmark.ovpn

Ive had trouble with my connection(s) for a while now and i finally found the root cause for it. Having the macvtap enabled causes consistent incoming package loss, which is really not noticeable unless you have to rely on every package. Which in this case it did and caused a lot of issues. Activating the macvlan bridge or even ipvlan bridge removes the issue completely. Observed this on 2 different systems. Macvtap.mp4 magnon-box-diagnostics-20240203-0926.zip Update: Its 3 different PCs now, also persists into .8. I do lack the diagnostics for the following 3 cases but at least it provides visual evidence for the repeatability of the issue regardless of hardware used. Desktop 2024.02.17 - 09.34.50.08.mp4 Vid 20240217 103910.mp4 This is a comparison with an earlier version Vid 20240217 112145.mp4

I formatted 2 disks in my Array to ZFS & those two disks will not stay spun down. (Also spins up the parity disks) These disks are completely empty. Docker & VM disabled There is disk activity about once a minute. See Screenshot, only the 2 ZFS formatted disks stay spun up. I also have a ZFS Pool that won't stay spun down, A single disk ZFS Pool that is empty and will not spin down And to make it weird, an empty 6 Disk ZFS pool that does spin down.

After upgrading from 6.9.2 to 6.10.0-rc5 all ACLs in /mnt/user stopped working. Hower ACLs on the disks (/mnt/disk[1-6], /mnt/cache) itself are working fine. Disks and Cache are formatted with btrfs (encrypted). Example: g0dscookie@nas:/$ ls /mnt/user/isos ls: cannot open directory '/mnt/user/isos': Permission denied g0dscookie@nas:/$ ls /mnt/disk5/isos Windows proxmox-ve_7.1-2.iso g0dscookie@nas:/$ getfacl /mnt/user/isos getfacl: Removing leading '/' from absolute path names # file: mnt/user/isos # owner: administrator # group: domain\040admins user::rwx user:administrator:rwx group::rwx group:domain\040admins:rwx group:isos\040ro:r-x group:isos\040rw:rwx mask::rwx other::--- default:user::rwx default:user:administrator:rwx default:group::--- default:group:domain\040admins:rwx default:group:isos\040ro:r-x default:group:isos\040rw:rwx default:mask::rwx default:other::--- g0dscookie@nas:/$ getfacl /mnt/disk5/isos getfacl: Removing leading '/' from absolute path names # file: mnt/disk5/isos # owner: administrator # group: domain\040admins user::rwx user:administrator:rwx group::rwx group:domain\040admins:rwx group:isos\040ro:r-x group:isos\040rw:rwx mask::rwx other::--- default:user::rwx default:user:administrator:rwx default:group::--- default:group:domain\040admins:rwx default:group:isos\040ro:r-x default:group:isos\040rw:rwx default:mask::rwx default:other::--- g0dscookie@nas:/$ id uid=1461716048(g0dscookie) gid=1461715457(domain users) groups=1461715457(domain users),1461716076(isos rw),[...] I've already rejoined samba to my Active Directory and reapplied ACLs. /mnt/user seems to be able to read/write ACLs, however it doesn't seem to actually apply them. If I chown the directory to g0dscookie I can access it through /mnt/user/isos. Same with chgrp to "domain users".

After updating to 6.11.1 i issued an update all through the UI button to update all dockers in my installation. After the process completed all the updates it was supposed to do, it started updating all my dockers one by one. This is not supposed to happen, the process was stopping the dockers, tried to pull an updated image which was up to date and then started the docker again. When the list of dockers ended it started again from the top. To stop it i had to go to the cli and kill the update process manually. root 27866 1 0 08:18 ? 00:00:01 /usr/bin/php -q /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/update_container swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma*swag*adguardhome*Agent-DVR*redis*unifi-controller*Metabase*code-server*nextcloud*binhex-delugevpn*sonarr*nzbhydra2*jackett*overseerr*netdata*uptime-kuma

EDIT: issue was traced to libtorrent 2.x, it's not an Unraid problem, more info in this post: https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-for-qbittorrent-and-deluge-users-r2153/?do=findComment&comment=21671 Original Post: I'm creating this to better track an issue that some users have been reporting where Unraid started crashing after updating to v6.11.x (it happens with both 6.11.0 and 6.11.1), there's a very similar call traced logged for all cases, e.g: Oct 12 04:18:27 zaBOX kernel: BUG: kernel NULL pointer dereference, address: 00000000000000b6 Oct 12 04:18:27 zaBOX kernel: #PF: supervisor read access in kernel mode Oct 12 04:18:27 zaBOX kernel: #PF: error_code(0x0000) - not-present page Oct 12 04:18:27 zaBOX kernel: PGD 0 P4D 0 Oct 12 04:18:27 zaBOX kernel: Oops: 0000 [#1] PREEMPT SMP PTI Oct 12 04:18:27 zaBOX kernel: CPU: 4 PID: 28596 Comm: Disk Tainted: P U W O 5.19.14-Unraid #1 Oct 12 04:18:27 zaBOX kernel: Hardware name: Gigabyte Technology Co., Ltd. Z390 AORUS PRO WIFI/Z390 AORUS PRO WIFI-CF, BIOS F12 11/05/2021 Oct 12 04:18:27 zaBOX kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21 Oct 12 04:18:27 zaBOX kernel: Code: e8 8e 61 63 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 9e 9b 64 00 48 81 c4 88 00 00 00 5b c3 cc cc cc cc <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb Oct 12 04:18:27 zaBOX kernel: RSP: 0000:ffffc900070dbcc0 EFLAGS: 00010246 Oct 12 04:18:27 zaBOX kernel: RAX: 0000000000000082 RBX: 0000000000000082 RCX: 0000000000000082 Oct 12 04:18:27 zaBOX kernel: RDX: 0000000000000001 RSI: ffff888757426fe8 RDI: 0000000000000082 Oct 12 04:18:27 zaBOX kernel: RBP: 0000000000000000 R08: 0000000000000028 R09: ffffc900070dbcd0 Oct 12 04:18:27 zaBOX kernel: R10: ffffc900070dbcd0 R11: ffffc900070dbd48 R12: 0000000000000000 Oct 12 04:18:27 zaBOX kernel: R13: ffff88824f95d138 R14: 000000000007292c R15: ffff88824f95d140 Oct 12 04:18:27 zaBOX kernel: FS: 000014ed38204b38(0000) GS:ffff8888a0500000(0000) knlGS:0000000000000000 Oct 12 04:18:27 zaBOX kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 12 04:18:27 zaBOX kernel: CR2: 00000000000000b6 CR3: 0000000209854005 CR4: 00000000003706e0 Oct 12 04:18:27 zaBOX kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Oct 12 04:18:27 zaBOX kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Oct 12 04:18:27 zaBOX kernel: Call Trace: Oct 12 04:18:27 zaBOX kernel: <TASK> Oct 12 04:18:27 zaBOX kernel: __filemap_get_folio+0x98/0x1ff Oct 12 04:18:27 zaBOX kernel: ? _raw_spin_unlock_irqrestore+0x24/0x3a Oct 12 04:18:27 zaBOX kernel: filemap_fault+0x6e/0x524 Oct 12 04:18:27 zaBOX kernel: __do_fault+0x2d/0x6e Oct 12 04:18:27 zaBOX kernel: __handle_mm_fault+0x9a5/0xc7d Oct 12 04:18:27 zaBOX kernel: handle_mm_fault+0x113/0x1d7 Oct 12 04:18:27 zaBOX kernel: do_user_addr_fault+0x36a/0x514 Oct 12 04:18:27 zaBOX kernel: exc_page_fault+0xfc/0x11e Oct 12 04:18:27 zaBOX kernel: asm_exc_page_fault+0x22/0x30 Oct 12 04:18:27 zaBOX kernel: RIP: 0033:0x14ed3a0ae7b5 Oct 12 04:18:27 zaBOX kernel: Code: 8b 48 08 48 8b 32 48 8b 00 48 39 f0 73 09 48 8d 14 08 48 39 d6 eb 0c 48 39 c6 73 0b 48 8d 14 0e 48 39 d0 73 02 0f 0b 48 89 c7 <f3> a4 66 48 8d 3d 59 b7 22 00 66 66 48 e8 d9 d8 f6 ff 48 89 28 48 Oct 12 04:18:27 zaBOX kernel: RSP: 002b:000014ed38203960 EFLAGS: 00010206 Oct 12 04:18:27 zaBOX kernel: RAX: 000014ed371aa160 RBX: 000014ed38203ad0 RCX: 0000000000004000 Oct 12 04:18:27 zaBOX kernel: RDX: 000014c036530000 RSI: 000014c03652c000 RDI: 000014ed371aa160 Oct 12 04:18:27 zaBOX kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 000014ed38203778 Oct 12 04:18:27 zaBOX kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000 Oct 12 04:18:27 zaBOX kernel: R13: 000014ed38203b40 R14: 000014ed384fe940 R15: 000014ed38203ac0 Oct 12 04:18:27 zaBOX kernel: </TASK> Oct 12 04:18:27 zaBOX kernel: Modules linked in: macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net vhost vhost_iotlb tap tun veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs md_mod kvmgt mdev i915 iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper intel_gtt agpgart hwmon_vid iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls ipv6 nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) x86_pkg_temp_thermal intel_powerclamp drm_kms_helper btusb btrtl i2c_i801 btbcm coretemp gigabyte_wmi wmi_bmof intel_wmi_thunderbolt mxm_wmi kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd Oct 12 04:18:27 zaBOX kernel: btintel rapl intel_cstate intel_uncore e1000e i2c_smbus bluetooth drm nvme nvme_core ahci i2c_core libahci ecdh_generic ecc syscopyarea sysfillrect input_leds sysimgblt led_class joydev nzxt_kraken2 intel_pch_thermal fb_sys_fops thermal fan video tpm_crb wmi tpm_tis backlight tpm_tis_core tpm acpi_pad button unix Oct 12 04:18:27 zaBOX kernel: CR2: 00000000000000b6 Oct 12 04:18:27 zaBOX kernel: ---[ end trace 0000000000000000 ]--- Another example with very different hardware: Oct 11 21:32:08 Impulse kernel: BUG: kernel NULL pointer dereference, address: 0000000000000056 Oct 11 21:32:08 Impulse kernel: #PF: supervisor read access in kernel mode Oct 11 21:32:08 Impulse kernel: #PF: error_code(0x0000) - not-present page Oct 11 21:32:08 Impulse kernel: PGD 0 P4D 0 Oct 11 21:32:08 Impulse kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI Oct 11 21:32:08 Impulse kernel: CPU: 1 PID: 5236 Comm: Disk Not tainted 5.19.14-Unraid #1 Oct 11 21:32:08 Impulse kernel: Hardware name: System manufacturer System Product Name/ROG STRIX B450-F GAMING II, BIOS 4301 03/04/2021 Oct 11 21:32:08 Impulse kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21 Oct 11 21:32:08 Impulse kernel: Code: e8 8e 61 63 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 9e 9b 64 00 48 81 c4 88 00 00 00 5b e9 cc 5f 86 00 <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb Oct 11 21:32:08 Impulse kernel: RSP: 0000:ffffc900026ffcc0 EFLAGS: 00010246 Oct 11 21:32:08 Impulse kernel: RAX: 0000000000000022 RBX: 0000000000000022 RCX: 0000000000000022 Oct 11 21:32:08 Impulse kernel: RDX: 0000000000000001 RSI: ffff88801e450b68 RDI: 0000000000000022 Oct 11 21:32:08 Impulse kernel: RBP: 0000000000000000 R08: 000000000000000c R09: ffffc900026ffcd0 Oct 11 21:32:08 Impulse kernel: R10: ffffc900026ffcd0 R11: ffffc900026ffd48 R12: 0000000000000000 Oct 11 21:32:08 Impulse kernel: R13: ffff888428441cb8 R14: 00000000000028cd R15: ffff888428441cc0 Oct 11 21:32:08 Impulse kernel: FS: 00001548d34fa6c0(0000) GS:ffff88842e840000(0000) knlGS:0000000000000000 Oct 11 21:32:08 Impulse kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 11 21:32:08 Impulse kernel: CR2: 0000000000000056 CR3: 00000001a3fe6000 CR4: 00000000003506e0 Oct 11 21:32:08 Impulse kernel: Call Trace: Oct 11 21:32:08 Impulse kernel: <TASK> Oct 11 21:32:08 Impulse kernel: __filemap_get_folio+0x98/0x1ff Oct 11 21:32:08 Impulse kernel: filemap_fault+0x6e/0x524 Oct 11 21:32:08 Impulse kernel: __do_fault+0x30/0x6e Oct 11 21:32:08 Impulse kernel: __handle_mm_fault+0x9a5/0xc7d Oct 11 21:32:08 Impulse kernel: handle_mm_fault+0x113/0x1d7 Oct 11 21:32:08 Impulse kernel: do_user_addr_fault+0x36a/0x514 Oct 11 21:32:08 Impulse kernel: exc_page_fault+0xfc/0x11e Oct 11 21:32:08 Impulse kernel: asm_exc_page_fault+0x22/0x30 Oct 11 21:32:08 Impulse kernel: RIP: 0033:0x1548dbc04741 Oct 11 21:32:08 Impulse kernel: Code: 48 01 d0 eb 1b 0f 1f 40 00 f3 0f 1e fa 48 39 d1 0f 82 73 28 fc ff 0f 1f 00 f3 0f 1e fa 48 89 f8 48 83 fa 20 0f 82 af 00 00 00 <c5> fe 6f 06 48 83 fa 40 0f 87 3e 01 00 00 c5 fe 6f 4c 16 e0 c5 fe Oct 11 21:32:08 Impulse kernel: RSP: 002b:00001548d34f9808 EFLAGS: 00010202 Oct 11 21:32:08 Impulse kernel: RAX: 000015480c010d30 RBX: 000015480c018418 RCX: 00001548d34f9a40 Oct 11 21:32:08 Impulse kernel: RDX: 0000000000004000 RSI: 000015471f8cd50f RDI: 000015480c010d30 Oct 11 21:32:08 Impulse kernel: RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000 Oct 11 21:32:08 Impulse kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000 Oct 11 21:32:08 Impulse kernel: R13: 00001548d34f9ac0 R14: 0000000000000003 R15: 0000154814013d10 Oct 11 21:32:08 Impulse kernel: </TASK> Oct 11 21:32:08 Impulse kernel: Modules linked in: xt_connmark xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha xt_mark xt_nat xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc ipv6 mlx4_en mlx4_core igb i2c_algo_bit edac_mce_amd edac_core kvm_amd kvm wmi_bmof mxm_wmi asus_wmi_sensors crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel mpt3sas aesni_intel crypto_simd nvme cryptd ahci i2c_piix4 raid_class rapl k10temp i2c_core nvme_core ccp scsi_transport_sas libahci wmi button acpi_cpufreq unix [last unloaded: mlx4_core] Oct 11 21:32:08 Impulse kernel: CR2: 0000000000000056 Oct 11 21:32:08 Impulse kernel: ---[ end trace 0000000000000000 ]--- So they always start with this (end address will change): Oct 11 05:02:02 Cogsworth kernel: BUG: kernel NULL pointer dereference, address: 0000000000000076 and always have this: Oct 11 05:02:02 Cogsworth kernel: Call Trace: Oct 11 05:02:02 Cogsworth kernel: <TASK> Oct 11 05:02:02 Cogsworth kernel: __filemap_get_folio+0x98/0x1ff The fact that it's happening to various users with very different hardware, both Intel and AMD, makes me think it's not a hardware/firmware issue, so we can try to find if they are running anything in common, these are the plugins I've found in common between the 4 or 5 cases found so far, these are some of the most used plugins so not surprising they are installed in all but it's also easy to rule them out: ca.backup2.plg - 2022.07.23 (Up to date) community.applications.plg - 2022.09.30 (Up to date) dynamix.active.streams.plg - 2020.06.17 (Up to date) file.activity.plg - 2022.08.19 (Up to date) fix.common.problems.plg - 2022.10.09 (Up to date) unassigned.devices.plg - 2022.10.03 (Up to date) unassigned.devices-plus.plg - 2022.08.19 (Up to date) So anyone having this issue try temporarily uninstalling/disabling these plugin to see if there's any difference.

just to keep this issue alive as there are more open questions regarding this and its still open in 6.10 rc2 description is simple as the topic, whenever there was a unsafe shutdown, starting unraid with docker setting will result in a non working state, stopping/starting docker service or rebooting clean resolving the issue. easy to reproduce and annoying when you externally working on the mashine and hard reboot externally while using as sample ssh guac to access it again, but doesnt work as described above, so only VPN backdoor to restart it. may a workaroud possible if its a bigger issue ? like you can trigger parity after a unclean shutdown, trigger a docker service restart too ? tested here from 6.92 until today 6.10 rc2 on 4 different mashines with the same result, open issues as reminder ...

Hi Unraid community, I'm facing a problem with the writes to my USB flash drive in Unraid. Every time I access the dashboard, the USB writes increase by 14 times. It seems like the docker config file is being updated with each access. Here's my setup: Main server running Unraid 6.12.4 Intel i5-12600 Ram 32GB Test server running Unraid 6.11.5 Intel i7-4770K Ram 16GB Interestingly, the issue doesn't occur on the test server with version 6.11.5, but it starts happening when I update to 6.12.4. If I roll back to 6.11.5, the problem disappears. Here are the steps I've taken to troubleshoot: Disabled Docker and the VM. Performed a fresh install with no additional software or configurations, but the issue persists. Checked with a friend who has a similar setup and is also experiencing the same problem. I've attached a diagnostic report to provide more information. Any assistance or insights would be greatly appreciated. Thanks in advance Recording 2023-11-07 161254.mp4 diagnostics-20231107-1605.zip

Since the 5.x kernel based releases many users have been reporting system hangs every few days once the i915 module is loaded. With reports from a few users detailed in the thread below we have worked out that the issue is caused by the i915 module and is a persistent issue with both the 6.9.x release and 6.10 release candidates. The system does not need to be actively transcoding for the hang to occur. 6.8.3 does not have this issue and is not hardware related. Unloading the i915 module stops the hangs. Hangs are still present in 6.10.0RC2. I can provide a list of similar reports if required.

Is the 'Docker' page supposed to correctly display containers\stacks created by a Docker Compose file? I've encountered several issues in this case. They appear as shown in the screenshot below: The required custom Docker networks were created using the code: docker network create revers-proxy docker network create homeassistant Below are some basic network settings that might be helpful: Settings -> Network Settings -> Enable bridging: No Settings -> Docker -> Preserve user defined networks: Yes Settings -> Docker -> Host access to custom networks: Enabled For my test, I created a simple 'docker-compose.yml' file: I'd like to address the following issues visible in the screenshot above: 1) Long network IDs are displayed instead of names. 2) In case of the nginx-proxy-manager container, only a single network is displayed, even though the container is attached to two different networks in the Compose file. 3) The nginx-proxy-manager container has several port mappings ('80:80', '443:443', '81:81') in the Compose file, but these mappings are not displayed in the corresponding column on the user interface. 4) Incorrect port mappings are displayed for the zigbee2mqtt container. Although it has no mappings in the Compose file, the UI shows port mapping 8123, which is actually a port of the Home Assistant container attached to the HOST network. 5) A minor user interface improvement can be made for long container names. For example, it would be better if the zigbee2mqtt container's name is positioned on the right next to the icon and not shifted down. Again, these issues are related to running containers using a Docker Compose file. When I tested this configuration by creating apps from the CA store, everything appeared to be correct:

Hello, I've been trying for a while to mount a NFS drive on another server using NFS v4.2. And every time, it fallback to v4.0. This is really strange since the NFS server configured by Unraid has no issue talking in the v4.2 protocol. Example of mount command: root@Tower:~# mount -vvvv dolma:/Backs-Movies /tmp/test/ mount.nfs: timeout set for Tue Sep 12 21:01:32 2023 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.42.12,clientaddr=192.168.42.57' mount.nfs: mount(2): Invalid argument mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.42.12,clientaddr=192.168.42.57' mount.nfs: mount(2): Invalid argument mount.nfs: trying text-based options 'vers=4,addr=192.168.42.12,clientaddr=192.168.42.57' dolma:/Backs-Movies on /tmp/test type nfs (rw) I also tried with another server that I just configured NFS on, completely clean with Raspbian Bookworms. root@Tower:~# mount -vvvv vpn-mgt:/srv/test /tmp/test/ mount.nfs: timeout set for Tue Sep 12 21:14:18 2023 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.42.8,clientaddr=192.168.42.57' mount.nfs: mount(2): Invalid argument mount.nfs: trying text-based options 'vers=4,minorversion=1,addr=192.168.42.8,clientaddr=192.168.42.57' mount.nfs: mount(2): Invalid argument mount.nfs: trying text-based options 'vers=4,addr=192.168.42.8,clientaddr=192.168.42.57' vpn-mgt:/srv/test on /tmp/test type nfs (rw,noatime) It looks like an oversight in either Unraid configuration of NFS Mount or missing kernel config or some issue in slackware ? It's hard to say what's the cause, since Unraid support v4.1 and v4.2 as a Server which lead me to think its configuration issue somewhere. I've asked for support to confirm the issue before opening this ticket.

I've been running into a bug with updating dockers on 6.12.3 recently where I'll have a few containers that have updates and when I go to "Update all" and it launches the popup it will go through and update everything but then continue to loop through the containers over and over again attempting to update. So the first pass, things update, then the second pass it doesn't find any new updates to pull for the container: "Status: Image is up to date for {containerName} TOTAL DATA PULLED: 0 b" and it just does this over and over and over again. There is no close button because Unraid thinks it is still updating so the only way to dismiss the modal is to refresh the page. I'm not sure if it is till then running on a loop under the covers until I restart? I took a quick look through the 6.12.4 patch notes and don't see anything about this mentioned so figured I would report.

Originally reported as 6.12.3, still occurs on 6.12.4. As the title indicates, mousing over the RAM percentages (such that is shows the absolute size) can spike your CPU quite high. On hover of the RAM percentage, it fires of a POST request to /webGui/include/DashboardApps.php Just doing this once probably won't be noticeable. However if you constantly mouse over these, it'll spike your CPU quite high, for me it almost pegs to 100%. Reproduction: Goto dashboard Have both CPU graph and RAM chart open and visible Mouse over the RAM percentages rapidly Observe CPU usage increase dramatically (depending on CPU, potentially 100% usage) Attached is a video of it occurring, and my diagnostics. Screen Recording 2023-08-02 at 11.32.59 PM.mov unraid-diagnostics-20230803-1310.zip

I am running an OpenVPN Docker container (ich777/openvpn-client) with network=host and want my unRAID webUI to be accessible via this VPN. I can add the corresponding interface (tun0) to Network Settings -> Interface Extras -> Include listening interfaces but the webUI doesn't bind to the tunnel IP after a restart. I need to delete and readd the entry to get it to work. I guess this happens because the VPN container is still starting when the webUI process binds to the ports.

Greetings. This issue was previously reported: And subsequently fixed in 6.11.1: However it's back now in 6.12.4. Looking closely at /etc/rc.d/rc.docker, there are two issues: Issue #1 - line 296: if [[ -n $MY_NETWORK && $MY_NETWORK != $MY_NETWORK ]]; then - The point of the if-statement is to skip processing MY_NETWORK from the inner loop if it is the same as MY_NETWORK from the outer loop. This situation would represent the case where we are looking at the default network that is defined in the XML, that will be processed like normal in the outer loop, hence the attempt to skip it in the inner loop. However, someone has done some 'clean up' and re-named the variables in this inner loop the same as the ones in the outer loop, specifically MY_NETWORK, which overwrites our only handle to the one in the outer loop. As-is, it just skips everything because MY_NETWORK is always equal to MY_NETWORK. In order to fix this, we'll need a new variable to hold the value of MY_NETWORK before this inner loop starts and we'll need to reference that in the if-statement, like so: OUTER_LOOP_NETWORK=$MY_NETWORK #save-off the value to use in the if-statement below for ROW in $USER_NETWORKS; do ROW=(${ROW/;/ }) MY_NETWORK=${ROW[0]} MY_IP=${ROW[1]/,/;} if [[ -n $MY_NETWORK && $MY_NETWORK != $OUTER_LOOP_NETWORK ]]; then LABEL=${MY_NETWORK//[0-9.]/} if [[ "br bond eth" =~ $LABEL && $LABEL != ${PORT:0:-1} ]]; then MY_NETWORK=${MY_NETWORK/$LABEL/${PORT:0:-1}} fi logger -t $(basename $0) "container $CONTAINER has an additional network that will be restored: $MY_NETWORK" NETRESTORE[$MY_NETWORK]="$CONTAINER,$MY_IP ${NETRESTORE[$MY_NETWORK]}" fi done Issue #2 - lines 297 - 300: LABEL=${MY_NETWORK//[0-9.]/} if [[ "br bond eth" =~ $LABEL && $LABEL != ${PORT:0:-1} ]]; then MY_NETWORK=${MY_NETWORK/$LABEL/${PORT:0:-1}} fi - I am guessing this has something to do with re-working network names when a user has applied the macvlan fix introduced in 6.12.4, maybe this tries to do an automatic 'translation' of sorts? It doesn't seem to 'translate' things very well, for me anyway it always just wants to change 'bond' to 'eth' so I get a bunch of 'eth2.10', 'eth2.20', etc. instead of what they should be - 'bond2.10' or 'bond2.20', etc. I have to completely comment this in order for the script to correctly restore my networks. It was obviously put here for a particular situation, but it seems to break other situations. My initial thought would be to just get rid of it entirely and let users know they will need to update their Post Arguments to correctly reference the proper network name(s), but I admit I am not aware of the exact, original reason this was put here so I may be missing something. Any thoughts? Thanks!!

Had a share named temp. Main storage was zfs pool, named "cache". Secondary storage, was the main unraid array. Set the secondary storage to "none", and clicked saved. Instead, of expected confirmation, received popup message saying share was deleted. Found broken symlink under /mnt/user for temp, pointing to non-existent directory /mnt/cache/temp. What I believe happened here- There were no files on the "cache" pool. The ZFS dataset didn't even exist yet, as I had not written anything to it. There were, however files on the unraid array. So, when I remove the secondary storage, there was "nothing", hence the confusing message. However, the files still do exist on /mnt/disk1/temp, as I would expect. TLDR / To Reproduce- Create a share on the array. Add a few files. Update the share, to have primary storage pointing at a zfs pool, and secondary storage, on the array, with mover action set move files to array. Save. Do note, zfs list will not yet show the dataset, until something has been written to it. But, dont' write anything to it. Instead, update the share again. Remove the secondary storage (array). Save. You will be presented with a broken symlink, and a "Deleted" dialog.

Description: The diagnostics zip files created using the "Anonymize Diagnostics" option in the UI still contain the public facing IPv6 address, which can be used to roughly geolocate users or gather lists of unraid hosts on the internet, scan them to find exposed services and so on. In the dhcplog.txt is a line like "eth0: adding address 2a02:9...." and " Registering new address record for ..." in the syslog.txt. Since with ipv6 there is no nat and instead all addresses are directly addressing individual devices, this can be used to geolocate you to about a 10km radius and try accessing services running on the unraid box, if it is exposed to the internet (e.g. by enabling connect?). For IPv4 this is not much of an issue, since pretty much everyone will be using NAT, so the ip in the logs will be in the private ranges in this case. See the Screenshots for the full list of occurences. I also checked a few diagnostics files from the forum, to verify it's not just in mine and found that the IPv6 address is also in the log of other people who have it enabled. Reproduction: Make fresh 6.12.3 USB Stick Enable IPv6 in IP settings Create diagnostic with anonymization turned on Look in the following files: Suggested Solution: Replace each unique IP address with a placeholder like IP1 IP2 etc, so you can still keep them apart for debugging, but the ip doesn't need to be included in the logs. tower-diagnostics-dhcp.zip

Hi, been rock solid 6.11 and since 6.12 its stuck once a week, or since latest 6.12.1 stuck once a day... (i thought it would get better...) Jun 24 09:06:46 Unraid-Server kernel: ------------[ cut here ]------------ Jun 24 09:06:46 Unraid-Server kernel: WARNING: CPU: 6 PID: 0 at net/netfilter/nf_nat_core.c:594 nf_nat_setup_info+0x8c/0x7d1 [nf_nat] Jun 24 09:06:46 Unraid-Server kernel: Modules linked in: tcp_diag udp_diag inet_diag xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap af_packet macvlan veth xt_nat xt_tcpudp xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs dm_crypt nvidia_uvm(PO) md_mod dm_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) nvidia_modeset(PO) nvidia(PO) nct6775 nct6775_core hwmon_vid iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc e1000e i915 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iosf_mbi kvm drm_buddy i2c_algo_bit ttm drm_display_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 Jun 24 09:06:46 Unraid-Server kernel: drm_kms_helper aesni_intel mei_hdcp mei_pxp wmi_bmof mxm_wmi crypto_simd cryptd drm rapl intel_cstate i2c_i801 intel_gtt intel_uncore mpt3sas agpgart video i2c_smbus syscopyarea nvme sysfillrect mei_me sysimgblt input_leds ahci raid_class i2c_core nvme_core joydev led_class mei libahci scsi_transport_sas fb_sys_fops thermal fan wmi backlight intel_pmc_core acpi_pad button unix [last unloaded: md_mod] Jun 24 09:06:46 Unraid-Server kernel: CPU: 6 PID: 0 Comm: swapper/6 Tainted: P W O 6.1.34-Unraid #1 Jun 24 09:06:46 Unraid-Server kernel: Hardware name: System manufacturer System Product Name/Z170 PRO GAMING, BIOS 3805 05/16/2018 Jun 24 09:06:46 Unraid-Server kernel: RIP: 0010:nf_nat_setup_info+0x8c/0x7d1 [nf_nat] Jun 24 09:06:46 Unraid-Server kernel: Code: a8 80 75 26 48 8d 73 58 48 8d 7c 24 20 e8 18 4b d3 ff 48 8d 43 0c 4c 8b bb 88 00 00 00 48 89 44 24 18 eb 54 0f ba e0 08 73 07 <0f> 0b e9 75 06 00 00 48 8d 73 58 48 8d 7c 24 20 e8 eb 4a d3 ff 48 Jun 24 09:06:46 Unraid-Server kernel: RSP: 0018:ffffc900002207b8 EFLAGS: 00010282 Jun 24 09:06:46 Unraid-Server kernel: RAX: 0000000000000180 RBX: ffff88821aca7600 RCX: ffff888107078640 Jun 24 09:06:46 Unraid-Server kernel: RDX: 0000000000000000 RSI: ffffc9000022089c RDI: ffff88821aca7600 Jun 24 09:06:46 Unraid-Server kernel: RBP: ffffc90000220880 R08: 000000000e00a8c0 R09: 0000000000000000 Jun 24 09:06:46 Unraid-Server kernel: R10: 0000000000000158 R11: 0000000000000000 R12: ffffc9000022089c Jun 24 09:06:46 Unraid-Server kernel: R13: 0000000000000000 R14: ffffc90000220980 R15: 0000000000000001 Jun 24 09:06:46 Unraid-Server kernel: FS: 0000000000000000(0000) GS:ffff889006d80000(0000) knlGS:0000000000000000 Jun 24 09:06:46 Unraid-Server kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jun 24 09:06:46 Unraid-Server kernel: CR2: 000015be94c5ecc8 CR3: 00000007f0688005 CR4: 00000000003706e0 Jun 24 09:06:46 Unraid-Server kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jun 24 09:06:46 Unraid-Server kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jun 24 09:06:46 Unraid-Server kernel: Call Trace: Jun 24 09:06:46 Unraid-Server kernel: <IRQ> Jun 24 09:06:46 Unraid-Server kernel: ? __warn+0xab/0x122 Jun 24 09:06:46 Unraid-Server kernel: ? report_bug+0x109/0x17e Jun 24 09:06:46 Unraid-Server kernel: ? nf_nat_setup_info+0x8c/0x7d1 [nf_nat] Jun 24 09:06:46 Unraid-Server kernel: ? handle_bug+0x41/0x6f Jun 24 09:06:46 Unraid-Server kernel: ? exc_invalid_op+0x13/0x60 Jun 24 09:06:46 Unraid-Server kernel: ? asm_exc_invalid_op+0x16/0x20 Jun 24 09:06:46 Unraid-Server kernel: ? nf_nat_setup_info+0x8c/0x7d1 [nf_nat] Jun 24 09:06:46 Unraid-Server kernel: ? nf_nat_setup_info+0x44/0x7d1 [nf_nat] Jun 24 09:06:46 Unraid-Server kernel: ? percpu_counter_add_batch+0x85/0xa2 Jun 24 09:06:46 Unraid-Server kernel: ? xt_write_recseq_end+0xf/0x1c [ip_tables] Jun 24 09:06:46 Unraid-Server kernel: ? __local_bh_enable_ip+0x56/0x6b Jun 24 09:06:46 Unraid-Server kernel: ? ipt_do_table+0x57a/0x5bf [ip_tables] Jun 24 09:06:46 Unraid-Server kernel: ? rt_dst_alloc+0x2f/0xa0 Jun 24 09:06:46 Unraid-Server kernel: ? xt_write_recseq_end+0xf/0x1c [ip_tables] Jun 24 09:06:46 Unraid-Server kernel: __nf_nat_alloc_null_binding+0x66/0x81 [nf_nat] Jun 24 09:06:46 Unraid-Server kernel: nf_nat_inet_fn+0xc0/0x1a8 [nf_nat] Jun 24 09:06:46 Unraid-Server kernel: nf_nat_ipv4_local_in+0x2a/0xaa [nf_nat] Jun 24 09:06:46 Unraid-Server kernel: nf_hook_slow+0x3a/0x96 Jun 24 09:06:46 Unraid-Server kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jun 24 09:06:46 Unraid-Server kernel: NF_HOOK.constprop.0+0x79/0xd9 Jun 24 09:06:46 Unraid-Server kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jun 24 09:06:46 Unraid-Server kernel: ip_sabotage_in+0x4f/0x60 [br_netfilter] Jun 24 09:06:46 Unraid-Server kernel: nf_hook_slow+0x3a/0x96 Jun 24 09:06:46 Unraid-Server kernel: ? ip_rcv_finish_core.constprop.0+0x3e8/0x3e8 Jun 24 09:06:46 Unraid-Server kernel: NF_HOOK.constprop.0+0x79/0xd9 Jun 24 09:06:46 Unraid-Server kernel: ? ip_rcv_finish_core.constprop.0+0x3e8/0x3e8 Jun 24 09:06:46 Unraid-Server kernel: __netif_receive_skb_one_core+0x77/0x9c Jun 24 09:06:46 Unraid-Server kernel: netif_receive_skb+0xbf/0x127 Jun 24 09:06:46 Unraid-Server kernel: br_handle_frame_finish+0x438/0x472 [bridge] Jun 24 09:06:46 Unraid-Server kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] Jun 24 09:06:46 Unraid-Server kernel: br_nf_hook_thresh+0xe2/0x109 [br_netfilter] Jun 24 09:06:46 Unraid-Server kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] Jun 24 09:06:46 Unraid-Server kernel: br_nf_pre_routing_finish+0x2c1/0x2ec [br_netfilter] Jun 24 09:06:46 Unraid-Server kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] Jun 24 09:06:46 Unraid-Server kernel: ? NF_HOOK.isra.0+0xe4/0x140 [br_netfilter] Jun 24 09:06:46 Unraid-Server kernel: ? br_nf_hook_thresh+0x109/0x109 [br_netfilter] Jun 24 09:06:46 Unraid-Server kernel: br_nf_pre_routing+0x236/0x24a [br_netfilter] Jun 24 09:06:46 Unraid-Server kernel: ? br_nf_hook_thresh+0x109/0x109 [br_netfilter] Jun 24 09:06:46 Unraid-Server kernel: br_handle_frame+0x277/0x2e0 [bridge] Jun 24 09:06:46 Unraid-Server kernel: ? do_kernel_restart+0x7/0x1b Jun 24 09:06:46 Unraid-Server kernel: ? br_pass_frame_up+0xdd/0xdd [bridge] Jun 24 09:06:46 Unraid-Server kernel: __netif_receive_skb_core.constprop.0+0x4fa/0x6e9 Jun 24 09:06:46 Unraid-Server kernel: ? __build_skb+0x20/0x4e Jun 24 09:06:46 Unraid-Server kernel: ? kmem_cache_alloc+0x122/0x14d Jun 24 09:06:46 Unraid-Server kernel: __netif_receive_skb_list_core+0x8a/0x11e Jun 24 09:06:46 Unraid-Server kernel: netif_receive_skb_list_internal+0x1d2/0x20b Jun 24 09:06:46 Unraid-Server kernel: gro_normal_list+0x1d/0x3f Jun 24 09:06:46 Unraid-Server kernel: napi_complete_done+0x7b/0x11a Jun 24 09:06:46 Unraid-Server kernel: e1000e_poll+0x9e/0x23e [e1000e] Jun 24 09:06:46 Unraid-Server kernel: __napi_poll.constprop.0+0x28/0x124 Jun 24 09:06:46 Unraid-Server kernel: net_rx_action+0x159/0x24f Jun 24 09:06:46 Unraid-Server kernel: __do_softirq+0x126/0x288 Jun 24 09:06:46 Unraid-Server kernel: __irq_exit_rcu+0x5e/0xb8 Jun 24 09:06:46 Unraid-Server kernel: common_interrupt+0x9b/0xc1 Jun 24 09:06:46 Unraid-Server kernel: </IRQ> Jun 24 09:06:46 Unraid-Server kernel: <TASK> Jun 24 09:06:46 Unraid-Server kernel: asm_common_interrupt+0x22/0x40 Jun 24 09:06:46 Unraid-Server kernel: RIP: 0010:cpuidle_enter_state+0x11d/0x202 Jun 24 09:06:46 Unraid-Server kernel: Code: 17 39 a0 ff 45 84 ff 74 1b 9c 58 0f 1f 40 00 0f ba e0 09 73 08 0f 0b fa 0f 1f 44 00 00 31 ff e8 39 f8 a4 ff fb 0f 1f 44 00 00 <45> 85 e4 0f 88 ba 00 00 00 48 8b 04 24 49 63 cc 48 6b d1 68 49 29 Jun 24 09:06:46 Unraid-Server kernel: RSP: 0018:ffffc90000107e98 EFLAGS: 00000246 Jun 24 09:06:46 Unraid-Server kernel: RAX: ffff889006d80000 RBX: ffff889006db6250 RCX: 0000000000000000 Jun 24 09:06:46 Unraid-Server kernel: RDX: 00002c3eeb167c21 RSI: ffffffff8209093c RDI: ffffffff82090e45 Jun 24 09:06:46 Unraid-Server kernel: RBP: 0000000000000002 R08: 0000000000000002 R09: 0000000000000002 Jun 24 09:06:46 Unraid-Server kernel: R10: 0000000000000020 R11: 0000000000000026 R12: 0000000000000002 Jun 24 09:06:46 Unraid-Server kernel: R13: ffffffff82320440 R14: 00002c3eeb167c21 R15: 0000000000000000 Jun 24 09:06:46 Unraid-Server kernel: ? cpuidle_enter_state+0xf7/0x202 Jun 24 09:06:46 Unraid-Server kernel: cpuidle_enter+0x2a/0x38 Jun 24 09:06:46 Unraid-Server kernel: do_idle+0x18d/0x1fb Jun 24 09:06:46 Unraid-Server kernel: cpu_startup_entry+0x1d/0x1f Jun 24 09:06:46 Unraid-Server kernel: start_secondary+0xeb/0xeb Jun 24 09:06:46 Unraid-Server kernel: secondary_startup_64_no_verify+0xce/0xdb Jun 24 09:06:46 Unraid-Server kernel: </TASK> Jun 24 09:06:46 Unraid-Server kernel: ---[ end trace 0000000000000000 ]--- If more is needed, tell me. PS: picture might be on another day, even if set to record syslogs, unraid doesnt always do. above is the only tracelog i could find...

Hi, Today I added a Docker Container that is on a custom Container Registry and not on DockerHub. The Registry is a Gitlab Registry hosted by my University. I've added the login credentials via the CLI and it worked without problems. I could add the Docker Container in the GUI and Unraid pulled and started it normaly. I immediately noticed that on the Docker Page that for the container it showed "not available" for the version. So I made an update to the docker image (I'm pushing the updates so I now that there is one available), and tried to force the update via the advance view. But there it just showed my "TOTAL DATA PULLED: 0 B" and restarted the container. Of course the container was not updated. I then tried doing a docker pull in the CLI with the same URL as shown in the GUI and there it worked without a problem. As soon as I did the pull, I went back and retried the forced update, there of course, as excepted, it also pulled 0B and restarted the container with the new image since it now was present locally. So I think the Problem may be that the URL has a port after the domain and so the Unraid updater thinks the port and beyond is already the tag and not part of the URL anymore. If that is really the problem it should be easily fixed by looking for ":" on the far right instead of the first. The Diagnostic file was generated right after trying to update the container in the GUI so maybe there is something there that can help. storinator-diagnostics-20230716-2139.zip

Process "lsof" is pegging out the CPU at 100% on the server. When viewing Tower/Main page the CPU on the host is seeing high utilization as well. I do have log spammed with this about an hour ago, but not spamming right now.

Screenshot attached. Same issue in all themes. Downgrading to 6.11.5 restores. Upgraded, downgraded and upgraded again to check while trying to get the Tailscale interface setup. Changing the order in 11.5 and then upgrading again held.

The 6.12 release includes initial ZFS support in addition to the usual set of bug fixes, kernel, and package updates. Please create new topics here in this board to report Bugs or other Issues. As always, prior to updating, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Note regarding plugins: This release includes upgrading PHP from v7.4 to v8.2.3, necessary for continued PHP security updates. We recommend you upgrade all your plugins before updating the OS, and be aware that any plugin which hasn't been updated recently (with a comment about PHP 8 in the change logs) may not work correctly. You may want to uninstall that plugin until the author has had time to update it. Plugin authors are aware of necessary changes and many plugins have already been updated. If you encounter an issue with a plugin, please create a nice post in the plugins support topic. Special thanks to all our beta testers and especially: @bonienl for his continued refinement and updating of the Dynamix webGUI. @Squid for continued refinement of Community Apps and associated feed. @dlandon for continued refinement of Unassigned Devices plugin. @ich777 for continued support of third-party drivers, recommendations for base OS enhancements and beta testing. @JorgeB for rigorous testing of the storage subsystem and helping us understand ZFS nuances, of which there are many. @SimonF for curating our VM Manager and adding some very nice enhancements. Thanks to everyone above and our Plugin Authors for identifying and putting up with all the changes which came about from upgrading PHP from v7 to v8. Finally a big Thank You! to @steini84 who brought ZFS to Unraid via plugin several years ago. Version 6.12.0-rc1 2023-03-14 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 ealier, 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. 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 devices 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 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. 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, 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. 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 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 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. Linux kernel version 6.1.19 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_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 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 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 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.3 php-libvirt: version 0.5.7 php-markdown: version 2.0.0 samba: version 4.17.4 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 5.13.0 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 Misc cgroup2 now the default do not mount loopback images using directio Patch upgradepkg to prevent replacing existing package with older version. NFS: enable UPD transport emhttp: fix cache pool (null) syslog strings emhttp: fix cache pool display wrong device size for selected replacement device mover: fixed bug: improper handling of symlinks shfs: igonore top-level hidden directoris (names beginning with '.') 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

unraid-api process is pegging 1-3 CPU cores at 100% all the time, is this expected? 7955 root 20 0 14.4g 3.7g 50432 R 310.2 1.5 3485:00 unraid-api - 3 cores here?! Also, "My Servers" is throwing errors: JSON.parse: unexpected character at line 1 column 1 of the JSON data Edit: This was resolved potentially with a reboot, that said, I hadn't done anything on it, its been sitting running since RC2 so Im not sure what caused the "My Servers" to freak out... Post reboot: 8498 root 20 0 10.9g 155760 50196 S 1.0 0.1 0:06.53 unraid-api - Normal usage unraid-diagnostics-20230331-0853.zip

At the moment the two default VM network adapters have the following names: This is really confusing as "virtio" and "virtio-net" are using the same virtual network adapter "virtio-net-pci" (which cost me hours to find out). The only difference is that "virtio-net" disables "vhost-net" access. My suggestion is to use the real name, but with different notes (and its time for more adapters of course):

I just upgraded to 6.10.3 from 6.9.3 last night and am getting a temp warning for the pulling interval on my Samsung 980 Cache drive saying its at 84C it will go from 44C to 84C in 10 seconds and back again. I changed to pulling interval to 10 seconds to watch the behavior. I believe this is a bug I have also found many post on this forum and reddit about this as well. Any guidance would be appreciated. Thank you. diagnostics-20220622-0902.zip

Dec 6 14:14:50 NightOwl kernel: ------------[ cut here ]------------ Dec 6 14:14:50 NightOwl kernel: kernel BUG at mm/huge_memory.c:2154! Dec 6 14:14:50 NightOwl kernel: invalid opcode: 0000 [#1] PREEMPT SMP PTI Dec 6 14:14:50 NightOwl kernel: CPU: 1 PID: 30090 Comm: rocket-worker-t Tainted: G W 5.19.17-Unraid #2 Dec 6 14:14:50 NightOwl kernel: Hardware name: Supermicro Super Server/X11SSM-F, BIOS 2.3 11/26/2019 Dec 6 14:14:50 NightOwl kernel: RIP: 0010:__split_huge_pmd+0x565/0x6ab Dec 6 14:14:50 NightOwl kernel: Code: 00 48 8b 54 24 40 48 8b 74 24 48 48 0f 45 cf bf 11 ff ff 01 48 c1 e7 27 48 01 d7 48 21 c8 48 01 c7 48 f7 07 9f ff ff ff 74 02 <0f> 0b e8 db cf ff ff 83 7c 24 10 00 75 06 f0 41 ff 44 24 30 49 81 Dec 6 14:14:50 NightOwl kernel: RSP: 0018:ffffc90003defbf8 EFLAGS: 00010282 Dec 6 14:14:50 NightOwl kernel: RAX: 000000043596c000 RBX: ffff888186d4f9c0 RCX: 000ffffffffff000 Dec 6 14:14:50 NightOwl kernel: RDX: 0000000000000a98 RSI: 800000044d753027 RDI: ffff88843596ca98 Dec 6 14:14:50 NightOwl kernel: RBP: ffffea0011358000 R08: 0000000000000000 R09: 0000000000000000 Dec 6 14:14:50 NightOwl kernel: R10: 0000000000000003 R11: 0000000000000000 R12: ffffea001135d4c0 Dec 6 14:14:50 NightOwl kernel: R13: ffff888104b0a510 R14: 00000000ff800001 R15: 000014e354553000 Dec 6 14:14:50 NightOwl kernel: FS: 000014e3875fa700(0000) GS:ffff888857a80000(0000) knlGS:0000000000000000 Dec 6 14:14:50 NightOwl kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 6 14:14:50 NightOwl kernel: CR2: 0000149b96961000 CR3: 00000001d682e001 CR4: 00000000003706e0 Dec 6 14:14:50 NightOwl kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Dec 6 14:14:50 NightOwl kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Dec 6 14:14:50 NightOwl kernel: Call Trace: Dec 6 14:14:50 NightOwl kernel: <TASK> Dec 6 14:14:50 NightOwl kernel: ? _raw_spin_unlock+0x14/0x29 Dec 6 14:14:50 NightOwl kernel: unmap_page_range+0x23d/0x66e Dec 6 14:14:50 NightOwl kernel: zap_page_range+0x96/0xd6 Dec 6 14:14:50 NightOwl kernel: do_madvise+0x685/0xa04 Dec 6 14:14:50 NightOwl kernel: ? percpu_counter_add_batch+0x85/0xa2 Dec 6 14:14:50 NightOwl kernel: ? __seccomp_filter+0x89/0x313 Dec 6 14:14:50 NightOwl kernel: ? __do_munmap+0x2ca/0x2e2 Dec 6 14:14:50 NightOwl kernel: __x64_sys_madvise+0x28/0x2f Dec 6 14:14:50 NightOwl kernel: do_syscall_64+0x68/0x81 Dec 6 14:14:50 NightOwl kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd Dec 6 14:14:50 NightOwl kernel: RIP: 0033:0x14e38eddd6e7 Dec 6 14:14:50 NightOwl kernel: Code: ff ff ff ff c3 66 0f 1f 44 00 00 48 8b 15 a1 87 0d 00 f7 d8 64 89 02 b8 ff ff ff ff eb bc 0f 1f 44 00 00 b8 1c 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 79 87 0d 00 f7 d8 64 89 01 48 Dec 6 14:14:50 NightOwl kernel: RSP: 002b:000014e3875f9998 EFLAGS: 00000246 ORIG_RAX: 000000000000001c Dec 6 14:14:50 NightOwl kernel: RAX: ffffffffffffffda RBX: 00000000003a7180 RCX: 000014e38eddd6e7 Dec 6 14:14:50 NightOwl kernel: RDX: 0000000000000004 RSI: 0000000000387000 RDI: 000014e354170000 Dec 6 14:14:50 NightOwl kernel: RBP: 000014e354000020 R08: 0000000000000007 R09: 0000000000000000 Dec 6 14:14:50 NightOwl kernel: R10: 000014e35406c4e0 R11: 0000000000000246 R12: 0000000000387000 Dec 6 14:14:50 NightOwl kernel: R13: 0000000000170000 R14: 000014e354000000 R15: 000014e35414fe80 Dec 6 14:14:50 NightOwl kernel: </TASK> Dec 6 14:14:50 NightOwl kernel: Modules linked in: xt_mark xt_nat veth xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod efivarfs wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls igb x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ast aesni_intel drm_vram_helper crypto_simd drm_ttm_helper ttm cryptd rapl intel_cstate intel_uncore ipmi_ssif drm_kms_helper i2c_i801 drm i2c_smbus nvme agpgart i2c_algo_bit syscopyarea sysfillrect sysimgblt fb_sys_fops mpt3sas i2c_core nvme_core ahci libahci raid_class Dec 6 14:14:50 NightOwl kernel: intel_pch_thermal joydev input_leds led_class scsi_transport_sas thermal fan acpi_ipmi ipmi_si video button backlight acpi_power_meter acpi_pad unix [last unloaded: igb] Dec 6 14:14:50 NightOwl kernel: ---[ end trace 0000000000000000 ]--- Dec 6 14:14:52 NightOwl kernel: RIP: 0010:__split_huge_pmd+0x565/0x6ab Dec 6 14:14:52 NightOwl kernel: Code: 00 48 8b 54 24 40 48 8b 74 24 48 48 0f 45 cf bf 11 ff ff 01 48 c1 e7 27 48 01 d7 48 21 c8 48 01 c7 48 f7 07 9f ff ff ff 74 02 <0f> 0b e8 db cf ff ff 83 7c 24 10 00 75 06 f0 41 ff 44 24 30 49 81 Dec 6 14:14:52 NightOwl kernel: RSP: 0018:ffffc90003defbf8 EFLAGS: 00010282 Dec 6 14:14:52 NightOwl kernel: RAX: 000000043596c000 RBX: ffff888186d4f9c0 RCX: 000ffffffffff000 Dec 6 14:14:52 NightOwl kernel: RDX: 0000000000000a98 RSI: 800000044d753027 RDI: ffff88843596ca98 Dec 6 14:14:52 NightOwl kernel: RBP: ffffea0011358000 R08: 0000000000000000 R09: 0000000000000000 Dec 6 14:14:52 NightOwl kernel: R10: 0000000000000003 R11: 0000000000000000 R12: ffffea001135d4c0 Dec 6 14:14:52 NightOwl kernel: R13: ffff888104b0a510 R14: 00000000ff800001 R15: 000014e354553000 Dec 6 14:14:52 NightOwl kernel: FS: 000014e3875fa700(0000) GS:ffff888857a80000(0000) knlGS:0000000000000000 Dec 6 14:14:52 NightOwl kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 6 14:14:52 NightOwl kernel: CR2: 0000149b96961000 CR3: 00000001d682e001 CR4: 00000000003706e0 Dec 6 14:14:52 NightOwl kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Dec 6 14:14:52 NightOwl kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Dec 6 14:14:52 NightOwl kernel: note: rocket-worker-t[30090] exited with preempt_count 1 Dec 6 14:14:52 NightOwl kernel: ------------[ cut here ]------------ Dec 6 14:14:52 NightOwl kernel: WARNING: CPU: 1 PID: 30090 at kernel/exit.c:741 do_exit+0x39/0x8e5 Dec 6 14:14:52 NightOwl kernel: Modules linked in: xt_mark xt_nat veth xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod efivarfs wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls igb x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ast aesni_intel drm_vram_helper crypto_simd drm_ttm_helper ttm cryptd rapl intel_cstate intel_uncore ipmi_ssif drm_kms_helper i2c_i801 drm i2c_smbus nvme agpgart i2c_algo_bit syscopyarea sysfillrect sysimgblt fb_sys_fops mpt3sas i2c_core nvme_core ahci libahci raid_class Dec 6 14:14:52 NightOwl kernel: intel_pch_thermal joydev input_leds led_class scsi_transport_sas thermal fan acpi_ipmi ipmi_si video button backlight acpi_power_meter acpi_pad unix [last unloaded: igb] Dec 6 14:14:52 NightOwl kernel: CPU: 1 PID: 30090 Comm: rocket-worker-t Tainted: G D W 5.19.17-Unraid #2 Dec 6 14:14:52 NightOwl kernel: Hardware name: Supermicro Super Server/X11SSM-F, BIOS 2.3 11/26/2019 Dec 6 14:14:52 NightOwl kernel: RIP: 0010:do_exit+0x39/0x8e5 Dec 6 14:14:52 NightOwl kernel: Code: 89 fd 53 48 83 ec 28 65 48 8b 04 25 28 00 00 00 48 89 44 24 20 31 c0 65 48 8b 1c 25 c0 bb 01 00 48 83 bb a0 07 00 00 00 74 02 <0f> 0b 48 8b bb c8 06 00 00 e8 b7 c0 7c 00 48 8b 83 c0 06 00 00 83 Dec 6 14:14:52 NightOwl kernel: RSP: 0018:ffffc90003defee0 EFLAGS: 00010282 Dec 6 14:14:52 NightOwl kernel: RAX: 0000000000000000 RBX: ffff8881065f0000 RCX: 0000000000000000 Dec 6 14:14:52 NightOwl kernel: RDX: 0000000000000001 RSI: 0000000000000003 RDI: 000000000000000b Dec 6 14:14:52 NightOwl kernel: RBP: 000000000000000b R08: 0000000000000000 R09: ffffc9000117a020 Dec 6 14:14:52 NightOwl kernel: R10: 0000000000aaaaaa R11: 0000000000000001 R12: ffffc90003defb48 Dec 6 14:14:52 NightOwl kernel: R13: ffff8881065f0000 R14: 0000000000000002 R15: ffffffff820b236d Dec 6 14:14:52 NightOwl kernel: FS: 000014e3875fa700(0000) GS:ffff888857a80000(0000) knlGS:0000000000000000 Dec 6 14:14:52 NightOwl kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Dec 6 14:14:52 NightOwl kernel: CR2: 0000149b96961000 CR3: 00000001d682e001 CR4: 00000000003706e0 Dec 6 14:14:52 NightOwl kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Dec 6 14:14:52 NightOwl kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Dec 6 14:14:52 NightOwl kernel: Call Trace: Dec 6 14:14:52 NightOwl kernel: <TASK> Dec 6 14:14:52 NightOwl kernel: make_task_dead+0xba/0xba Dec 6 14:14:52 NightOwl kernel: rewind_stack_and_make_dead+0x17/0x17 Dec 6 14:14:52 NightOwl kernel: RIP: 0033:0x14e38eddd6e7 Dec 6 14:14:52 NightOwl kernel: Code: ff ff ff ff c3 66 0f 1f 44 00 00 48 8b 15 a1 87 0d 00 f7 d8 64 89 02 b8 ff ff ff ff eb bc 0f 1f 44 00 00 b8 1c 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 79 87 0d 00 f7 d8 64 89 01 48 Dec 6 14:14:52 NightOwl kernel: RSP: 002b:000014e3875f9998 EFLAGS: 00000246 ORIG_RAX: 000000000000001c Dec 6 14:14:52 NightOwl kernel: RAX: ffffffffffffffda RBX: 00000000003a7180 RCX: 000014e38eddd6e7 Dec 6 14:14:52 NightOwl kernel: RDX: 0000000000000004 RSI: 0000000000387000 RDI: 000014e354170000 Dec 6 14:14:52 NightOwl kernel: RBP: 000014e354000020 R08: 0000000000000007 R09: 0000000000000000 Dec 6 14:14:52 NightOwl kernel: R10: 000014e35406c4e0 R11: 0000000000000246 R12: 0000000000387000 Dec 6 14:14:52 NightOwl kernel: R13: 0000000000170000 R14: 000014e354000000 R15: 000014e35414fe80 Dec 6 14:14:52 NightOwl kernel: </TASK> Dec 6 14:14:52 NightOwl kernel: ---[ end trace 0000000000000000 ]--- Dec 6 16:17:35 NightOwl kernel: BUG: Bad rss-counter state mm:00000000f7646224 type:MM_SHMEMPAGES val:1 ==== Unraid server becomes unresponsive. You have to force reboot the machine. It crash at least a week. See attached logs. nightowl-diagnostics-20221206-1659.zip unraid.crash.log

In 6.10.1+ the dockerman icon caching mechanism does not work correctly for icons specified by the net.unraid.docker.icon container label on containers without a dockerman template. For containers created with this label outside of dockerman the caching mechanism initially downloads and displays the correct icon. If the icon url is changed however the new icon is never downloaded because the old icon remains cached and there is no mechanism in place for invalidating the icon in the absence of a dockerman template. This issue was discovered by others including those using the compose plugin. Since I have not seen this raised in the Bug Reports section yet I am posting this as a bug report in addition to my proposed fix here https://github.com/limetech/webgui/pull/1146.

Hi, I found the my 10G network card cannot negotiate to 5G link mode after system boot. However, the link speed could recover to 5000bastT/Full after executing command "ethtool -s eth0 autoneg on". My network card is "Intel Corporation Ethernet 10G 2P X550-t Adapter". The switch is NETGEAR MS510TXPP. Here is the process to reproduce the problem: ethtool -i eth0 driver: ixgbe version: 5.15.40-Unraid firmware-version: 0x80000f32, 19.5.12 expansion-rom-version: bus-info: 0000:04:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 100baseT/Full 1000baseT/Full 10000baseT/Full 2500baseT/Full 5000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 100baseT/Full 1000baseT/Full 10000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Auto-negotiation: on Port: Twisted Pair PHYAD: 0 Transceiver: internal MDI-X: Unknown Supports Wake-on: d Wake-on: d Current message level: 0x00000007 (7) drv probe link Link detected: yes ethtool -s eth0 autoneg on ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 100baseT/Full 1000baseT/Full 10000baseT/Full 2500baseT/Full 5000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 100baseT/Full 1000baseT/Full 10000baseT/Full 2500baseT/Full 5000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 5000Mb/s Duplex: Full Auto-negotiation: on Port: Twisted Pair PHYAD: 0 Transceiver: internal MDI-X: Unknown Supports Wake-on: d Wake-on: d Current message level: 0x00000007 (7) drv probe link Link detected: yes dmesg | grep -i ixgbe [ 39.766547] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver [ 39.766645] ixgbe: Copyright (c) 1999-2016 Intel Corporation. [ 40.601995] ixgbe 0000:04:00.0: Multiqueue Enabled: Rx Queue count = 36, Tx Queue count = 36 XDP Queue count = 0 [ 40.700054] ixgbe 0000:04:00.0: 31.504 Gb/s available PCIe bandwidth (8.0 GT/s PCIe x4 link) [ 40.812033] ixgbe 0000:04:00.0: MAC: 4, PHY: 0, PBA No: J69754-003 [ 40.812149] ixgbe 0000:04:00.0: b4:96:**:**:**:** [ 40.971001] ixgbe 0000:04:00.0: Intel(R) 10 Gigabit Network Connection [ 41.651898] ixgbe 0000:04:00.1: Multiqueue Enabled: Rx Queue count = 36, Tx Queue count = 36 XDP Queue count = 0 [ 41.752195] ixgbe 0000:04:00.1: 31.504 Gb/s available PCIe bandwidth (8.0 GT/s PCIe x4 link) [ 41.866258] ixgbe 0000:04:00.1: MAC: 4, PHY: 0, PBA No: J69754-003 [ 41.866375] ixgbe 0000:04:00.1: b4:96:**:**:**:** [ 42.029314] ixgbe 0000:04:00.1: Intel(R) 10 Gigabit Network Connection [ 43.646539] ixgbe 0000:04:00.1: complete [ 43.661631] ixgbe 0000:04:00.0: complete [ 43.976969] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver [ 43.976972] ixgbe: Copyright (c) 1999-2016 Intel Corporation. [ 44.669028] ixgbe 0000:04:00.0: Multiqueue Enabled: Rx Queue count = 36, Tx Queue count = 36 XDP Queue count = 0 [ 44.769080] ixgbe 0000:04:00.0: 31.504 Gb/s available PCIe bandwidth (8.0 GT/s PCIe x4 link) [ 44.883503] ixgbe 0000:04:00.0: MAC: 4, PHY: 0, PBA No: J69754-003 [ 44.883512] ixgbe 0000:04:00.0: b4:96:**:**:**:** [ 45.048905] ixgbe 0000:04:00.0: Intel(R) 10 Gigabit Network Connection [ 45.740533] ixgbe 0000:04:00.1: Multiqueue Enabled: Rx Queue count = 36, Tx Queue count = 36 XDP Queue count = 0 [ 45.840620] ixgbe 0000:04:00.1: 31.504 Gb/s available PCIe bandwidth (8.0 GT/s PCIe x4 link) [ 45.954050] ixgbe 0000:04:00.1: MAC: 4, PHY: 0, PBA No: J69754-003 [ 45.954059] ixgbe 0000:04:00.1: b4:96:**:**:**:** [ 46.119016] ixgbe 0000:04:00.1: Intel(R) 10 Gigabit Network Connection [ 46.563594] ixgbe 0000:04:00.0: registered PHC device on eth0 [ 46.880177] ixgbe 0000:04:00.1: registered PHC device on eth1 [ 51.336232] ixgbe 0000:04:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: None [ 323.198656] ixgbe 0000:04:00.0 eth0: NIC Link is Down [ 327.927630] ixgbe 0000:04:00.0 eth0: NIC Link is Up 5 Gbps, Flow Control: None [ 329.425081] ixgbe 0000:04:00.0 eth0: NIC Link is Down [ 329.553606] ixgbe 0000:04:00.0 eth0: NIC Link is Up 5 Gbps, Flow Control: None [ 329.633081] ixgbe 0000:04:00.0 eth0: NIC Link is Down [ 330.177570] ixgbe 0000:04:00.0 eth0: NIC Link is Up 5 Gbps, Flow Control: None [ 330.257093] ixgbe 0000:04:00.0 eth0: NIC Link is Down [ 330.801629] ixgbe 0000:04:00.0 eth0: NIC Link is Up 5 Gbps, Flow Control: None [ 330.881077] ixgbe 0000:04:00.0 eth0: NIC Link is Down [ 331.945575] ixgbe 0000:04:00.0 eth0: NIC Link is Up 5 Gbps, Flow Control: None Thanks! Best regards, Beikesea

Hello all, I was attempting to have my unraid server log to itself so that the logs persisted. I did the following: enabled the local syslog server set it log to a new share that I previously created enabled rotation set it to 50mb 4 files Set my remote server to my private unraid ip left the ports alone (UDP 514) Mirror to flash set to No When I click apply, I get an error in my System Logs that says the configuration failed to parse. Nothing gets put in the share I created. The error: Text of the error: Jul 19 08:03:18 XXX ool www[24597]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Jul 19 08:03:20 XXX rsyslogd: Could not find template 1 'remote' - action disabled [v8.2002.0 try https://www.rsyslog.com/e/3003 ] Jul 19 08:03:20 XXX rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 121: errors occured in file '/etc/rsyslog.conf' around line 121 [v8.2002.0 try https://www.rsyslog.com/e/2207 ] Jul 19 08:03:20 XXX rsyslogd: [origin software="rsyslogd" swVersion="8.2002.0" x-pid="26836" x-info="https://www.rsyslog.com"] start fenrir-diagnostics-20200719-0823.zip

With the latest release candidate, I have a few plug-ins that do not work as expected. This seems to have to do with an openssl change, although I did not see any updates to openssl in the changelog. Affected applications: ProFTPd (Client auth disabled/not available) Python2.x (including pip): ImportError: cannot import name md5 Python3.x (including pip3): Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.",)': /simple/six/ Fix: Download and apply openssl: https://slackware.pkgs.org/14.2/slackware-patches-x86_64/openssl-1.0.2q-x86_64-1_slack14.2.txz.html Reboot.

Can I please ask everyone when you mark an issue as "urgent" to obey these conditions: 1) The problem is reproduceable 2) Diagnostics and other relevant information are attached in the post We (the receiving side) get alarm bells ringing and act asap, but need info as much as possible to find and resolve the issue. Thank you.