• Unraid OS version 6.12.0-rc3 available


    limetech

    Please refer to the 6.12.0-rc1 topic for a general overview.

     


    Version 6.12.0-rc3 2023-04-14

    (This is consolidated change log vs. Unraid OS 6.11)

    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
    • Like 15
    • Thanks 1



    User Feedback

    Recommended Comments



    Happy to share any logs, diagnostics, or follow any troubleshooting tips that might help. Im spinning up a backup server so i can offload/backup all the data on this one. But in the mean time fingers crossed for RC4 or figuring out the root cause 😀

    Link to comment
    2 hours ago, Koenig said:

    I'm getting a lot of these:

    Apr 18 15:35:49 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:4468347
    Apr 18 15:36:20 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:4492680
    Apr 18 15:43:07 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:4647123
    Apr 18 15:48:56 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:4751101
    Apr 18 15:58:03 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:4894247
    Apr 18 15:58:34 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:4915435
    Apr 18 16:03:48 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:4989147
    Apr 18 16:04:50 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5040925
    Apr 18 16:05:22 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5059100
    Apr 18 16:09:37 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5093655
    Apr 18 16:10:09 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5115018
    Apr 18 16:10:40 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5139303
    Apr 18 16:11:11 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5166674
    Apr 18 16:15:55 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5216088
    Apr 18 16:16:58 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5256386
    Apr 18 16:22:48 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5362106
    Apr 18 16:23:51 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5404597
    Apr 18 16:24:23 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5429570
    Apr 18 16:29:43 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5500655
    Apr 18 16:31:17 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5564601
    Apr 18 16:35:34 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5608888
    Apr 18 16:36:37 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5651233
    Apr 18 16:37:08 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5675616
    Apr 18 16:37:39 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:5690590
    Apr 18 16:43:00 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close interrupted close
    Apr 18 16:43:00 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close cancelled mid failed rc:-9

     

    Since upgrading to RC3 and transferring files between my servers.

     

     

    unraid-diagnostics-20230418-1720.zip

    It looks to maybe be a networking issue:

    Apr 17 05:31:41 Unraid kernel: eth0: renamed from veth8c6b04b
    Apr 17 05:52:53 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8441542
    Apr 17 05:53:24 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8443211
    Apr 17 05:53:56 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8444803
    Apr 17 05:54:27 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8446309
    Apr 17 05:54:58 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8447662
    Apr 17 05:56:32 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8451591
    Apr 17 05:58:06 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8455817
    Apr 17 05:58:37 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8457093
    Apr 17 05:59:09 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8458260
    Apr 17 06:00:11 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8460857
    Apr 17 06:01:45 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8465455
    Apr 17 06:17:34 Unraid kernel: br-379290cfc013: port 1(veth87da490) entered disabled state
    Apr 17 06:17:34 Unraid kernel: veth48d86f5: renamed from eth0
    Apr 17 06:17:34 Unraid kernel: br-379290cfc013: port 1(veth87da490) entered disabled state
    Apr 17 06:17:34 Unraid kernel: device veth87da490 left promiscuous mode
    Apr 17 06:17:34 Unraid kernel: br-379290cfc013: port 1(veth87da490) entered disabled state
    Apr 17 06:17:35 Unraid kernel: br-379290cfc013: port 1(vethee73dfc) entered blocking state
    Apr 17 06:17:35 Unraid kernel: br-379290cfc013: port 1(vethee73dfc) entered disabled state
    Apr 17 06:17:35 Unraid kernel: device vethee73dfc entered promiscuous mode
    Apr 17 06:17:35 Unraid kernel: br-379290cfc013: port 1(vethee73dfc) entered blocking state
    Apr 17 06:17:35 Unraid kernel: br-379290cfc013: port 1(vethee73dfc) entered forwarding state
    Apr 17 06:17:35 Unraid kernel: eth0: renamed from veth4507586

     

    Link to comment
    9 minutes ago, dlandon said:

    It looks to maybe be a networking issue:

    Apr 17 05:31:41 Unraid kernel: eth0: renamed from veth8c6b04b
    Apr 17 05:52:53 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8441542
    Apr 17 05:53:24 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8443211
    Apr 17 05:53:56 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8444803
    Apr 17 05:54:27 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8446309
    Apr 17 05:54:58 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8447662
    Apr 17 05:56:32 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8451591
    Apr 17 05:58:06 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8455817
    Apr 17 05:58:37 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8457093
    Apr 17 05:59:09 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8458260
    Apr 17 06:00:11 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8460857
    Apr 17 06:01:45 Unraid kernel: CIFS: VFS: \\192.168.8.25\Backups Close unmatched open for MID:8465455
    Apr 17 06:17:34 Unraid kernel: br-379290cfc013: port 1(veth87da490) entered disabled state
    Apr 17 06:17:34 Unraid kernel: veth48d86f5: renamed from eth0
    Apr 17 06:17:34 Unraid kernel: br-379290cfc013: port 1(veth87da490) entered disabled state
    Apr 17 06:17:34 Unraid kernel: device veth87da490 left promiscuous mode
    Apr 17 06:17:34 Unraid kernel: br-379290cfc013: port 1(veth87da490) entered disabled state
    Apr 17 06:17:35 Unraid kernel: br-379290cfc013: port 1(vethee73dfc) entered blocking state
    Apr 17 06:17:35 Unraid kernel: br-379290cfc013: port 1(vethee73dfc) entered disabled state
    Apr 17 06:17:35 Unraid kernel: device vethee73dfc entered promiscuous mode
    Apr 17 06:17:35 Unraid kernel: br-379290cfc013: port 1(vethee73dfc) entered blocking state
    Apr 17 06:17:35 Unraid kernel: br-379290cfc013: port 1(vethee73dfc) entered forwarding state
    Apr 17 06:17:35 Unraid kernel: eth0: renamed from veth4507586

     

     

    Might very well be, but I've not seen them before, that I can remember...

    But now they are very frequent, as I run "Duplicati" as a docker and backup some shares and appdata (different shares on diffrent days) to another Unraid server and have been doing that for atleast a couple of years and can't remember something like this filling up the log.

    Edited by Koenig
    Link to comment
    13 minutes ago, Koenig said:

     

    Might very well be, but I've not seen them before, that I can remember...

    CIFS errors like this are generally network issues.  Have you made any changes in your network settings or hardware?

     

    Each release of Unraid will potentially have an updated version of samba.  Every samba update comes with challenges because Microsoft is continually making changes to SMB for security/updates and the samba team has to try to catch up.

     

    Do you have the opprtunity to downgrade to see if the issue remians?  If it does, post diagnostics again.

     

    Let's shift this discussion to the UD forum because this is probably not an Unraid issue.

    Link to comment
    38 minutes ago, Koenig said:

     

    Might very well be, but I've not seen them before, that I can remember...

    But now they are very frequent, as I run "Duplicati" as a docker and backup some shares and appdata (different shares on diffrent days) to another Unraid server and have been doing that for atleast a couple of years and can't remember something like this filling up the log.

    I just looked at your log again and see this.  This might be your problem depending on this device needing to be visible on the network:

    Apr 15 21:11:13 Unraid unassigned.devices: Successfully mounted '//192.168.8.25/Backups' on '/mnt/remotes/NAS_Backups'.
    Apr 15 21:11:13 Unraid unassigned.devices: Device '//192.168.8.25/Backups' is not set to be shared.

     

    Link to comment
    14 hours ago, dlandon said:

    I just looked at your log again and see this.  This might be your problem depending on this device needing to be visible on the network:

    Apr 15 21:11:13 Unraid unassigned.devices: Successfully mounted '//192.168.8.25/Backups' on '/mnt/remotes/NAS_Backups'.
    Apr 15 21:11:13 Unraid unassigned.devices: Device '//192.168.8.25/Backups' is not set to be shared.

     

    You meaning it is not set to share?

     

    I don't want to share it from the server where I use unassigned devices to mount it, it is just supposed to be mounted so I can be able to map it in the docker "duplicati"

    On the other server (backup server - NAS) it is set to share on the network and from there it is visible on the network.

     

    Perhaps there's a better way of doing this, but this way has worked for atleast 3 years now, but I'm open to suggestions if there's a better way to go about it.

     

    EDIT: Both servers are Unraid, but the "backup"-server is on the latest "stable" version. 

    I usually wait a good while before updating that one.

     

    EDIT2: Attached a fresh diagnostics

     

    EDIT3: Attached a diagnostics from "NAS" as well.

    unraid-diagnostics-20230419-1014.zip

    nas-diagnostics-20230419-1021.zip

    Edited by Koenig
    Link to comment

    (POSTED IN WRONG TOPIC ORIGINALLY APOLOGIES)

     

    Ive upgraded from 6.11.5 to 6.12.0-RC3 and one of my 3 appdata 240gb drives has failed.  This is ok, I also have another 240gb and a 512 m2 ssd in.  Ive replaced the failed 240gb with another 512gb same model drive as the other.  

    I mention this in case this is the reason for my issues....Any VMs or Docker containers that I have not got started when i click on them, they wont start.  However if I click start all button at the bottom of the pages then they all start and work as expected which is bizarre...?

     

    Update to first post, appdata cache rebuilt A ok, I rebooted server and issue persists.  So it acts as if the start button for each individual docker container from either the Dashboard or the main docker page cant actually be selected

    Link to comment
    1 hour ago, Koenig said:

    You meaning it is not set to share?

     

    I don't want to share it from the server where I use unassigned devices to mount it, it is just supposed to be mounted so I can be able to map it in the docker "duplicati"

    On the other server (backup server - NAS) it is set to share on the network and from there it is visible on the network.

     

    Perhaps there's a better way of doing this, but this way has worked for atleast 3 years now, but I'm open to suggestions if there's a better way to go about it.

     

    EDIT: Both servers are Unraid, but the "backup"-server is on the latest "stable" version. 

    I usually wait a good while before updating that one.

     

    EDIT2: Attached a fresh diagnostics

     

    EDIT3: Attached a diagnostics from "NAS" as well.

    unraid-diagnostics-20230419-1014.zip

    nas-diagnostics-20230419-1021.zip

    You should set up static IP addresses on your servers.  On your 'nas' server you are mounting a remote share on the Unraid server:

    Mar  6 10:58:13 NAS unassigned.devices: Mounting Remote Share '//UNRAID/ISOs'...
    Mar  6 10:58:13 NAS unassigned.devices: Mount SMB share '//UNRAID/ISOs' using SMB default protocol.
    Mar  6 10:58:13 NAS unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_ISOs' '//UNRAID/ISOs' '/mnt/remotes/UNRAID_ISOs'

    The problem is the IP address of Unraid can change and I'm not sure CIFS can handle that cleanly.

     

    On the 'nas' server, you have not done any network configuration:

    # Generated network settings
    USE_DHCP="yes"
    IPADDR=
    NETMASK=
    GATEWAY=
    BONDING="yes"
    BRIDGING="yes"

     

    Link to comment
    2 hours ago, dlandon said:

    You should set up static IP addresses on your servers.  On your 'nas' server you are mounting a remote share on the Unraid server:

    Mar  6 10:58:13 NAS unassigned.devices: Mounting Remote Share '//UNRAID/ISOs'...
    Mar  6 10:58:13 NAS unassigned.devices: Mount SMB share '//UNRAID/ISOs' using SMB default protocol.
    Mar  6 10:58:13 NAS unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_ISOs' '//UNRAID/ISOs' '/mnt/remotes/UNRAID_ISOs'

    The problem is the IP address of Unraid can change and I'm not sure CIFS can handle that cleanly.

     

    On the 'nas' server, you have not done any network configuration:

    # Generated network settings
    USE_DHCP="yes"
    IPADDR=
    NETMASK=
    GATEWAY=
    BONDING="yes"
    BRIDGING="yes"

     

     

    I have all clients on my network set to use DHCP, and then I manage all IP and network from my pfSense router.

    They have had the same IP since the day they first connected to my network.

    Again I do not know if this is the best way to go about it but I started doing it this way long before I got my first Unraid-server and it has been working well, but as I mentioned earlier if this is a bad way to do it I'm open to suggestions.

    Link to comment
    20 minutes ago, Koenig said:

     

    I have all clients on my network set to use DHCP, and then I manage all IP and network from my pfSense router.

    They have had the same IP since the day they first connected to my network.

    Again I do not know if this is the best way to go about it but I started doing it this way long before I got my first Unraid-server and it has been working well, but as I mentioned earlier if this is a bad way to do it I'm open to suggestions.

    One of the problems with SMB is that it can take a long time for the configuration to stabilize.  see this section of an MS document for details:

     

    https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc737661(v=ws.10)?redirectedfrom=MSDN#registration-and-propagation

     

    Make sure that you have one of your Unraid servers on 24-7 and force that server to be the Local Master.  See this code (to be added to SMB Extras section of SMB settings) to do that:

     

    [global]
    preferred master = yes
    os level = 255

     

    It does not always solve the problem when a new computer is started up but it seems to help...

     

    LEt me add one more thing.  With peer-to-peer networking, which Unraid uses in it basic configuration, any computer may be either a client, a server or a client and server simultaneously.  It all depends on how you setup each computer!

    Edited by Frank1940
    Link to comment

    Hello,

     

    Currently I have a btrfs pool (v6.11.5) with the following drives:

    8TB, 4TB, 3TB, 1TB, 1TB total 17TB in single mode (no worry I have backup for these)

     

    My question is: Can I do the same if I want to use zfs pool (in RC3)?

     

    Thank you.

     

    Untitled.jpg

     

    Link to comment
    37 minutes ago, Tun2022 said:

    My question is: Can I do the same if I want to use zfs pool (in RC3)?

    You can create a stripe with all devices, but usable space will be just 5TB.

    Link to comment
    2 hours ago, Frank1940 said:

    One of the problems with SMB is that it can take a long time for the configuration to stabilize.  see this section of an MS document for details:

     

    https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc737661(v=ws.10)?redirectedfrom=MSDN#registration-and-propagation

     

    Make sure that you have one of your Unraid servers on 24-7 and force that server to be the Local Master.  See this code (to be added to SMB Extras section of SMB settings) to do that:

     

    [global]
    preferred master = yes
    os level = 255

     

    It does not always solve the problem when a new computer is started up but it seems to help...

     

    LEt me add one more thing.  With peer-to-peer networking, which Unraid uses in it basic configuration, any computer may be either a client, a server or a client and server simultaneously.  It all depends on how you setup each computer!

    Both servers are on 24/7 the NAS has an uptime of 44 days as for now, had a power-outage back then otherwisw it would have an uptime since last OS-upgrade.

    I have the NAS set as master already but the line with "os level = 255" I have not, I will add it.

     

    They both act as client and server.

    On "NAS" I have a share "Backups" wich is then mounted on the other server, just namned Unraid.

    On "Unraid I have a share "ISOs" wich is then mounted on NAS, I thought it to be a good way of sharing the storage of ISO's for VM-deployment.

     

    This setup I have had for atleast 3 years now, should be 4 in just a matter of a month or so, but I have never before seen the log filling up with that message, I cannot be sure but I would bet good money on it not beeing so in RC2 even, due to it beeing some time between, and the fact that I do check to logs intemittently.

    Link to comment

    Does 6.12 rc3 still require at least single device in "main Unraid array"? Can I go "only zfs pool" route?

    Edited by Volkerball
    Link to comment
    34 minutes ago, Volkerball said:

    Does 6.12 rc3 still require at least single device in "main Unraid array"?

    It does, you can use a spare flash drive to avoid occupying a SATA port or device.

    • Upvote 1
    Link to comment

    I've tried upgrading to this version of unraid and when array started I got an error: "mount error: Unsupported or no file system" for all my array disks, I'm using btrfs. After reverting to stable, the issue resolved.

    I've tried restarting the array, but there wasn't any difference.

    tower-diagnostics-20230423-2243.zip

    Link to comment
    12 hours ago, Andraž said:

    I've tried upgrading to this version of unraid and when array started I got an error: "mount error: Unsupported or no file system" for all my array disks, I'm using btrfs. After reverting to stable, the issue resolved.

     

    Apr 23 22:35:52 Tower kernel: BTRFS: device fsid 406782ea-d62f-49f7-9a3d-0c0a71b9cf3c devid 2 transid 144758 /dev/sdb1 scanned by udevd (808)
    Apr 23 22:35:52 Tower kernel: BTRFS: device fsid 406782ea-d62f-49f7-9a3d-0c0a71b9cf3c devid 1 transid 144758 /dev/sdd1 scanned by udevd (808)

    Disk1 and disk2 are members of the same btrfs pool, that's not supported, likely the devices were previously used in a btrfs pool before being re-assigned to the array, you need to correct that, also note that when it's apparently working with previous releases you will be seeing the same stats/contents for disk1 and disk2 in the GUI, because they are the same.

     

     

     

     

    Link to comment
    On 4/18/2023 at 1:14 PM, JorgeB said:

    There have been some other reports but nothing conclusive that I know of, user that reported the initial issue with rc2 says it's solved with rc3, just a few posts above a user reported issues but now says it's working:

     

     

    Some users reported that going back to v6.11.5 and upgrading back helped, others that it only helped after doing a new config with v6.11.5 and then upgrade back.

     

    For now probably best to wait a little longer to see if more reports surface as more people update.

    Today I took the time to try both of these methods. Downloaded 6.11.5 zip, swapped bz files, made bootable. Didn't/couldn't format drives when setting the new config up on 6.11.5 because of single disc zfs in array and zfs pools (all array and pool devices) so perhaps the new config never really started since the array never really started? Updated back to rc3 and still no spin down. Tried downgrade again without new config and then upgraded back to rc3 still no spin down. Currently array started on rc3, no smb, nfs, or external access. Docker and vm service disabled. Still getting constant reads and writes on all discs that hold data, much more reads and writes on the drive containing more data(50% capacity segate exos18tb vs 3%same drive). Interestingly enough backup server running zfs on all array and pool devices spins down perfectly after a new build and fresh install of Unraid directly to rc3.

    infinity-diagnostics-20230427-1344.zip

    Link to comment
    20 minutes ago, reggienaz said:

    Didn't/couldn't format drives when setting the new config up on 6.11.5 because of single disc zfs in array and zfs pools (all array and pool devices)

    You do a new config, no need to format drives, just start the array after doing it, of course any zfs drives won't mount, but then just upgrade back to v6.12.

     

    Also make sure you try safe mode.

    Link to comment
    1 hour ago, JorgeB said:

    You do a new config, no need to format drives, just start the array after doing it, of course any zfs drives won't mount, but then just upgrade back to v6.12.

     

    Also make sure you try safe mode.

    I think I figured it out, I disabled dynamix cache directories and discs stopped constant reads and writes and have stayed spun down with docker and vms disabled. Hope this helps anyone trying to troubleshoot this. These were my settings when cache directories was enabled with 128gb of ram. 

    Screenshot 2023-04-27 151447.png

    Edited by reggienaz
    Link to comment

    By default all folders are part of the caching system, it is however recommended to do caching for specific folders which need it. This is done by either defining an explicit "include" list, or alternatively create an "exclude" list, which ever suits best. It is not necessary to set both include and exclude lists.

     

    Link to comment

    I;ve had to delete and rebuild my docker img many times using this build. the first time was because it filled up, so i increased the size to 30gb (using a container that  needs a heap of its own space), but even after that and deleting that particular container my img seems to be corrupting like once a week. I can't start, stop, or use certain containers (never the same one) and when I stop the docker service it refuses to restart with the error below and then I have to rebuild.

     

    image.png.bb1b43b191bdd081ac7fd4b7a52844ad.png

    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.