• Unraid OS version 6.10.0-rc1 available


    limetech

    6.10.0 Summary of New Features

     

    As always, prior to updating, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".

     

    UPC and My Servers Plugin

    The most visible new feature is located in the upper right of the webGUI header.  We call this the User Profile Component, or UPC.  The UPC allows a user to associate their server(s) and license key(s) with their Unraid Community forum account.

     

    Starting with this release, it will be necessary for a new user to either sign-in with existing forum credentials or sign-up, creating a new account via the UPC in order to download a Trial key.  All key purchases and upgrades are also handled exclusively via the UPC.

     

    Signing-in provides these benefits:

    1. No more reliance on email and having to copy/paste key file URLs in order to install a license key - keys are delivered and installed automatically to your server.
    2. Notification of critical security-related updates.  In the event a serious security vulnerability has been discovered and patched, we will send out a notification to all email addresses associated with registered servers.
    3. Ability to install the My Servers plugin (see below).
    4. Posting privilege in a new set of My Servers forum boards.

     

    Once a license key has been provisioned, it is not necessary to remain signed-in, though there is no particular reason to sign-out.  Exception: if you have installed the My Servers plugin, signed-in servers will maintain a websocket connection to a Lime Technology cloud server for the purpose of transmitting real-time status.

     

    My Servers Plugin

    My Servers is what we call our set of cloud-based or cloud-enabled services and features that integrate with your Unraid server(s).  Once installed here are some of the features of My Servers:

    • My Servers Dashboard - when logged into the forum a new My Servers menu item appears. Clicking this brings up a Dashboard which displays a set of tiles representing each signed-in server.  Here you can see real-time status such as whether the server is online or offline, storage utilization and other information.  In addition, links are created to bring up a server webGUI, either locally on the LAN or remotely over the Internet (if Remote Access has been enabled).
    • flash backup - every registered server is provided with a private git repo initially populated with the contents of your USB flash boot device (except for certain files which contain private information such as passwords).  Thereafter, configuration changes are automatically committed.  Through the My Servers webApp it's possible to download a custom zip file that can be fed as input to the USB Flash Creator tool to move your configuration to a new USB flash device.
    • License key download - Again, through the My Servers webApp you can download your license key directly.

     

    My Servers is an optional add-on, installed through Community Apps or via direct plugin URL.  Detailed instructions can be found here.

     

    Security Changes

    • It is now mandatory to define a root password.  We also created a division in the Users page to distinguish root from other user names.  The root UserEdit page includes a text box for pasting SSH authorized keys.
    • For new configurations, the flash share default export setting is No.
    • For all new user shares, the default export setting is No.
    • For new configurations, SMBv1 is disabled by default.
    • For new configurations, telnet, ssh, and ftp are disabled by default.
    • We removed certain strings from Diagnostics such as passwords found in the 'go' file.

     

    Virtualization

    Both libvirt and qemu have been updated.  In addition qemu has been compiled with OpenGL support.

     

    The built-in FireFox browser available in GUI-mode boot is built as an AppImage and located in the bzfirmware compressed file system image.  This saves approximately 60MB of RAM.

     

    The Wireguard plugin has been integrated into webGUI, that is, no need for the plugin.  If you had the plugin installed previously, it will be uninstalled and moved to the "Plugins/Plugin File Install Errors" page. No action is needed unless you want to press the Delete button to remove it from that page. Your WireGuard tunnels and settings will be preserved.

     

    Simplified installation of the Community Apps plugin.  The webGUI automatically includes the Apps menu item, and if CA is not already installed, the page offers an Install button.  No need to hunt for the plugin link.

     

    Let's Encrypt SSL provisioning change.  In previous releases code that provisions (allocates and downloads) a LE SSL certificate would first test if DNS Rebinding Protection was enforced on the user's LAN; and, if so, would not provision the certificate.  Since there are other uses for a LE certificate we changed the code so that provision would always proceed.  Next, we changed the logic behind the Auto selection of "Use SSL/TLS" setting on the Management Access page.  Now it is only possible to select Auto if both a LE certificate has been provisioned and DNS Rebinding Protection is not enforced.  This is a subtle change but permits certain My Servers features such as Remote Access.

     

    Linux Kernel

    Upgrade to Linux 5.13.8 kernel which includes so-called Sequoia vulnerability mitigation.

     

    In-tree GPU drivers are now loaded by default if corresponding hardware is detected:

    • amdgpu
    • ast
    • i915
    • radeon

     

    These drivers are required mostly for motherboard on-board graphics used in GUI boot mode.  Loading of a driver can be prohibited by creating the appropriate file named after the driver:

    echo "blacklist i915" > /boot/config/modprobe.d/i915.conf

    Alternately, the device can be isolated from Linux entirely via the System Devices page.  Note that in Unraid OS 6.9 releases the in-tree GPU drivers are blacklisted by default and to enabling loading a driver you need to create an empty "conf" file.  After upgrading to Unraid OS 6.10 you may delete those files, or leave them as-is.  This change was made to greatly improve the Desktop GUI experience for new users.

     

    Added support for Intel GVT-g, which lets you split your Intel i915 iGPU into multiple virtual GPUs and pass them through to multiple VMs, using @ich777's Intel-GVT-g plugin.

     

    Added support for gnif/vendor-reset.  This simplifies @ich777's AMD Vendor Reset plugin which permits users to get their AMD video cards to reset properly.

     

    Base Packages

    Virtually the entire base package set has been updated.

     

    Other improvements available in 6.10, which are maybe not so obvious to spot from the release notes and some of these improvements are internal and not really visible:

     

     

    Event driven model to obtain server information and update the webGUI in real-time

    • The advantage of this model is its scalability. Multiple browsers can be opened simultaneously to the webGUI without much impact
    • In addition stale browser sessions won't create any CSRF errors anymore
    • People who keep their browser open 24/7 will find the webGUI stays responsive at all times

     

    Docker labels

    • Docker labels are added to allow people using Docker compose to make use of icons and GUI access
    • Look at a Docker 'run' command output to see exactly what labels are used

     

    Docker custom networks

    • A new setting for custom networks is available. Originally custom networks are created using the macvlan mode, and this mode is kept when upgrading to version 6.10
    • The new ipvlan mode is introduced to battle the crashes some people experience when using macvlan mode. If that is your case, change to ipvlan mode and test. Changing of mode does not require to reconfigure anything on Docker level, internally everything is being taken care off.

     

    Docker bridge network (docker0)

    • docker0 now supports IPv6. This is implemented by assigning docker0 a private IPv6 subnet (fd17::/64), similar to what is done for IPv4 and use network translation to communicate with the outside world
    • Containers connected to the bridge network now have both IPv4 and IPv6 connectivity (of course the system must have IPv6 configured in the network configuration)
    • In addition several enhancements are made in the IPv6 implementation to better deal with the use (or no-use) of IPv6

     

    Plugins page

    • The plugins page now loads information in two steps. First the list of plugins is created and next the more time consuming plugin status field is retrieved in the background. The result is a faster loading plugins page, especially when you have a lot of plugins installed

     

    Dashboard graphs

    • The dashboard has now two graphs available. The CPU graph is displayed by default, while the NETWORK graph is a new option under Interface (see the 'General Info' selection)
    • The CPU graph may be hidden as well in case it is not desired
    • Both graphs have a configurable time-line, which is by default 30 seconds and can be changed independently for each graph to see a longer or shorter history.
    • Graphs are updated in real-time and are useful to observe the behavior of the server under different circumstances

     

    Other Changes

    • We switched to a better-maintained version of the WSD server component called wsdd2 in an effort to eliminate instances where the wsd daemon would start consuming 100% of a CPU core.
    • Fixed issue where you couldn't create a docker image on a share name that contains a space.
    • Fixed issue where 'mover' would not move to a pool name that contains a space.
    • Fixed issue in User Share file system where permissions were not being honored.
    • We increased the font size in Terminal.
    • Many other small bug fixes and improvements.

     

    Credits

    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 and patience as we change things under the hood.

    @ich777 for assistance and passing on knowledge of Linux kernel config changes to support third party drivers and other kernel-related functionality via plugins.

    @SimonF for refinements to System Devices page and other webGUI improvements.  We intend to merge your mover progress changes during this RC series.

     


     

    Version 6.10.0-rc1 2021-08-07

     

    Base distro:

    • aaa_base: version 15.0
    • aaa_glibc-solibs: version 2.33
    • aaa_libraries: version 15.0
    • acl: version 2.3.1
    • acpid: version 2.0.32
    • adwaita-icon-theme: version 40.1.1
    • apcupsd: version 3.14.14
    • appres: version 1.0.5
    • at: version 3.2.2
    • at-spi2-atk: version 2.38.0
    • at-spi2-core: version 2.40.3
    • atk: version 2.36.0
    • attr: version 2.5.1
    • avahi: version 0.8
    • bash: version 5.1.008
    • beep: version 1.3
    • bin: version 11.1
    • bind: version 9.16.19
    • bluez-firmware: version 1.2
    • bridge-utils: version 1.7.1
    • brotli: version 1.0.9
    • btrfs-progs: version 5.13.1
    • bzip2: version 1.0.8
    • ca-certificates: version 20210526
    • cairo: version 1.16.0
    • celt051: version 0.5.1.3
    • cifs-utils: version 6.13
    • coreutils: version 8.32
    • cpio: version 2.13
    • cpufrequtils: version 008
    • cracklib: version 2.9.7
    • cryptsetup: version 2.3.6
    • curl: version 7.78.0
    • cyrus-sasl: version 2.1.27
    • db48: version 4.8.30
    • dbus: version 1.12.20
    • dbus-glib: version 0.112
    • dcron: version 4.5
    • dejavu-fonts-ttf: version 2.37
    • devs: version 2.3.1
    • dhcpcd: version 8.1.9
    • diffutils: version 3.8
    • dmidecode: version 3.3
    • dnsmasq: version 2.85
    • docker: version 20.10.6
    • dosfstools: version 4.2
    • e2fsprogs: version 1.46.3
    • ebtables: version 2.0.11
    • editres: version 1.0.7
    • eject: version 2.1.5
    • elogind: version 246.10
    • elvis: version 2.2_0
    • encodings: version 1.0.5
    • etc: version 15.0
    • ethtool: version 5.13
    • eudev: version 3.2.10
    • file: version 5.40
    • findutils: version 4.8.0
    • flex: version 2.6.4
    • floppy: version 5.5
    • fluxbox: version 1.3.7
    • fontconfig: version 2.13.92
    • freeglut: version 3.2.1
    • freetype: version 2.11.0
    • fribidi: version 1.0.10
    • fuse3: version 3.10.4
    • gawk: version 5.1.0
    • gd: version 2.3.2
    • gdbm: version 1.20
    • gdk-pixbuf2: version 2.42.6
    • genpower: version 1.0.5
    • getty-ps: version 2.1.0b
    • git: version 2.32.0
    • glew: version 2.2.0
    • glib2: version 2.68.3
    • glibc: version 2.33
    • glibc-zoneinfo: version 2021a
    • glu: version 9.0.2
    • gmp: version 6.2.1
    • gnutls: version 3.6.16
    • gptfdisk: version 1.0.8
    • graphite2: version 1.3.14
    • grep: version 3.6
    • gtk+3: version 3.24.30
    • gzip: version 1.10
    • harfbuzz: version 2.8.2
    • haveged: version 1.9.14
    • hdparm: version 9.62
    • hicolor-icon-theme: version 0.17
    • hostname: version 3.23
    • htop: version 3.0.5
    • hwloc: version 2.2.0
    • icu4c: version 69.1
    • imlib2: version 1.7.1
    • inetd: version 1.79s
    • infozip: version 6.0
    • inih: version 53
    • inotify-tools: version 3.20.11.0
    • iproute2: version 5.13.0
    • iptables: version 1.8.7
    • iputils: version 20210722
    • irqbalance: version 1.7.0
    • jansson: version 2.13.1
    • jemalloc: version 5.2.1
    • jq: version 1.6
    • json-c: version 0.15_20200726
    • keyutils: version 1.6.3
    • kmod: version 29
    • krb5: version 1.19.2
    • lbzip2: version 2.5
    • less: version 590
    • libICE: version 1.0.10
    • libSM: version 1.2.3
    • libX11: version 1.7.2
    • libXau: version 1.0.9
    • libXaw: version 1.0.14
    • libXcomposite: version 0.4.5
    • libXcursor: version 1.2.0
    • libXdamage: version 1.1.5
    • libXdmcp: version 1.1.3
    • libXevie: version 1.0.3
    • libXext: version 1.3.4
    • libXfixes: version 6.0.0
    • libXfont: version 1.5.2
    • libXfont2: version 2.0.5
    • libXfontcache: version 1.0.5
    • libXft: version 2.3.4
    • libXi: version 1.7.10
    • libXinerama: version 1.1.4
    • libXmu: version 1.1.3
    • libXpm: version 3.5.13
    • libXrandr: version 1.5.2
    • libXrender: version 0.9.10
    • libXres: version 1.2.1
    • libXt: version 1.2.1
    • libXtst: version 1.2.3
    • libXxf86dga: version 1.1.5
    • libXxf86misc: version 1.0.4
    • libXxf86vm: version 1.1.4
    • libaio: version 0.3.112
    • libarchive: version 3.5.1
    • libcap-ng: version 0.8.2
    • libcgroup: version 0.41
    • libdaemon: version 0.14
    • libdmx: version 1.1.4
    • libdrm: version 2.4.107
    • libedit: version 20210714_3.1
    • libepoxy: version 1.5.8
    • libestr: version 0.1.9
    • libevdev: version 1.11.0
    • libevent: version 2.1.12
    • libfastjson: version 0.99.9
    • libffi: version 3.3
    • libfontenc: version 1.1.4
    • libgcrypt: version 1.9.3
    • libglvnd: version 1.3.3
    • libgpg-error: version 1.42
    • libgudev: version 236
    • libidn: version 1.38
    • libjpeg-turbo: version 2.1.0
    • liblogging: version 1.0.6
    • libmnl: version 1.0.4
    • libnetfilter_conntrack: version 1.0.8
    • libnfnetlink: version 1.0.1
    • libnftnl: version 1.2.0
    • libnl3: version 3.5.0
    • libpcap: version 1.10.1
    • libpciaccess: version 0.16
    • libpng: version 1.6.37
    • libpsl: version 0.21.1
    • libpthread-stubs: version 0.4
    • libseccomp: version 2.5.1
    • libssh: version 0.9.5
    • libssh2: version 1.9.0
    • libtasn1: version 4.17.0
    • libtiff: version 4.3.0
    • libtiff: version 4.3.0
    • libtirpc: version 1.3.2
    • libunistring: version 0.9.10
    • libunwind: version 1.5.0
    • libusb: version 1.0.24
    • libusb-compat: version 0.1.7
    • libuv: version 1.41.0
    • libvirt: version 7.3.0
    • libvirt-php: version 0.5.5
    • libwebp: version 1.2.0
    • libwebsockets: version 4.2.0
    • libx86: version 1.1
    • libxcb: version 1.14
    • libxkbcommon: version 1.3.0
    • libxkbfile: version 1.1.0
    • libxml2: version 2.9.12
    • libxshmfence: version 1.3
    • libxslt: version 1.1.34
    • libzip: version 1.8.0
    • listres: version 1.0.4
    • lm_sensors: version 3.6.0
    • lmdb: version 0.9.29
    • logrotate: version 3.18.1
    • lshw: version B.02.19.2
    • lsof: version 4.94.0
    • lsscsi: version 0.32
    • lvm2: version 2.03.12
    • lz4: version 1.9.3
    • lzip: version 1.22
    • lzo: version 2.10
    • mc: version 4.8.26
    • miniupnpc: version 2.1
    • mkfontscale: version 1.2.1
    • mpfr: version 4.1.0
    • mtdev: version 1.1.6
    • nano: version 5.8
    • ncompress: version 5.0
    • ncurses: version 6.2_20201219
    • net-tools: version 20181103_0eebece
    • nettle: version 3.7.3
    • network-scripts: version 15.0
    • nfs-utils: version 2.5.4
    • nghttp2: version 1.44.0
    • nginx: version 1.19.9
    • nss-mdns: version 0.14.1
    • ntfs-3g: version 2017.3.23
    • ntp: version 4.2.8p15
    • numactl: version 2.0.13
    • oniguruma: version 6.9.7
    • openssh: version 8.6p1
    • openssl: version 1.1.1k
    • openssl-solibs: version 1.1.1k
    • p11-kit: version 0.24.0
    • pam: version 1.5.1
    • pango: version 1.48.7
    • patch: version 2.7.6
    • pciutils: version 3.7.0
    • pcre: version 8.45
    • pcre2: version 10.37
    • php: version 7.4.18
    • pixman: version 0.40.0
    • pkgtools: version 15.0
    • procps-ng: version 3.3.17
    • pv: version 1.6.6
    • qemu: version 6.0.0
    • qrencode: version 4.1.1
    • reiserfsprogs: version 3.6.27
    • rpcbind: version 1.2.5
    • rsync: version 3.2.3
    • rsyslog: version 8.2102.0
    • sakura: version 3.5.0
    • samba: version 4.12.15
    • sdparm: version 1.12
    • sed: version 4.8
    • sessreg: version 1.1.2
    • setxkbmap: version 1.3.2
    • sg3_utils: version 1.46
    • shadow: version 4.8.1
    • shared-mime-info: version 2.1
    • slim: version 1.3.6
    • smartmontools: version 7.2
    • spice: version 0.15.0
    • sqlite: version 3.36.0
    • ssmtp: version 2.64
    • startup-notification: version 0.12
    • sudo: version 1.9.7p2
    • sysfsutils: version 2.1.0
    • sysvinit: version 2.99
    • sysvinit-scripts: version 15.0
    • talloc: version 2.3.2
    • tar: version 1.34
    • tcp_wrappers: version 7.6
    • tdb: version 1.4.5
    • telnet: version 0.17
    • tevent: version 0.11.0
    • traceroute: version 2.1.0
    • transset: version 1.0.2
    • tree: version 1.8.0
    • ttyd: version 20210507
    • usbredir: version 0.8.0
    • usbutils: version 013
    • utempter: version 1.2.0
    • util-linux: version 2.37.1
    • vbetool: version 1.2.2
    • vsftpd: version 3.0.5
    • vte3: version 0.50.2
    • wayland: version 1.19.0
    • wget: version 1.21.1
    • which: version 2.21
    • wireguard-tools: version 1.0.20210424
    • wsdd2: version 1.8.3.2
    • xauth: version 1.1
    • xcb-util: version 0.4.0
    • xclock: version 1.0.9
    • xdpyinfo: version 1.3.2
    • xdriinfo: version 1.0.6
    • xev: version 1.2.4
    • xf86-input-evdev: version 2.10.6
    • xf86-input-keyboard: version 1.9.0
    • xf86-input-mouse: version 1.9.3
    • xf86-input-synaptics: version 1.9.1
    • xf86-video-ast: version 1.1.5
    • xf86-video-mga: version 2.0.0
    • xf86-video-vesa: version 2.5.0
    • xfsprogs: version 5.12.0
    • xhost: version 1.0.8
    • xinit: version 1.4.1
    • xkbcomp: version 1.4.5
    • xkbevd: version 1.1.4
    • xkbutils: version 1.0.4
    • xkeyboard-config: version 2.33
    • xkill: version 1.0.5
    • xload: version 1.1.3
    • xlsatoms: version 1.1.3
    • xlsclients: version 1.1.4
    • xmessage: version 1.0.5
    • xmodmap: version 1.0.10
    • xorg-server: version 1.20.13
    • xprop: version 1.2.5
    • xrandr: version 1.5.1
    • xrdb: version 1.2.0
    • xrefresh: version 1.0.6
    • xset: version 1.2.4
    • xsetroot: version 1.1.2
    • xsm: version 1.0.4
    • xterm: version 368
    • xtrans: version 1.4.0
    • xwd: version 1.0.8
    • xwininfo: version 1.1.5
    • xwud: version 1.0.5
    • xxHash: version 0.8.0
    • xz: version 5.2.5
    • yajl: version 2.1.0
    • zlib: version 1.2.11
    • zstd: version 1.5.0

    Linux kernel:

    • version 5.13.8 (CVE-2021-33909 CVE-2021-33910)
    • CONFIG_USB4: Unified support for USB4 and Thunderbolt
    • CONFIG_USB4_NET: Networking over USB4 and Thunderbolt cables
    • CONFIG_DRM_I915_GVT: Enable Intel GVT-g graphics virtualization host support
    • CONFIG_DRM_I915_GVT_KVMGT: Enable KVM/VFIO support for Intel GVT-g
    • CONFIG_VFIO_MDEV: Mediated device driver framework
    • CONFIG_VFIO_MDEV_DEVICE: VFIO driver for Mediated devices
    • CONFIG_FTRACE: Tracers
    • CONFIG_FUNCTION_TRACER: Kernel Function Tracer
    • CONFIG_KPROBES: Kprobes
    • CONFIG_DEBUG_KERNEL: Kernel debugging
    • CONFIG_KALLSYMS_ALL: Include all symbols in kallsyms
    • CONFIG_X86_X32: removed
    • md_unraid: version 2.9.18

    Management:

    • emhttp new defaults:
      - root password required
      - newly created shares not exported by default
      - predefined 'flash' share not exported by default
      - ftp, ssh, telnet: disabled by default
      - NetBIOS disabled by default
      - WSD enabled (and using newer 'wsdd2' package)
      - Enhanced macOS interoperability enabled
    • mover: fix bug not moving shares with embedded spaces
    • shfs: fix bug where permissions being ingored ('default_permissions' was missing in mount command)
    • webgui: support simultanious LAN SSL with self-signed cert and DNS-based SSL with Lets Encrypt cert
    • webgui: Suppress non-relevant IPv6 routes in routing table
    • webgui: Fixed smart temperature settings sometimes not possible
    • webgui: Add internal container reference
    • webgui: Diagnostics: Remove lines from go containing passwords etc
    • webgui: Better translation of docker container variables
    • webgui: Fix monitor false positives
    • webgui: Allow ruleset for local rules in rsyslog.conf
    • webgui: Include links in email and Discord agent notifications
    • webgui: Allow all notification agents to send links
    • webgui: Validate WebGUI ports before applying
    • webgui: Add vmxnet3 and e1000 into available NICs for VMs
    • webgui: Error checking etc on ports for syslog server
    • webgui: Check for flash offline / quick check on if it is corrupted
    • webgui: Only allow png files to be uploaded as user image
    • webgui: Diagnostics: Revamp anonymization
    • webgui: Add WireGuard GUI
    • webgui: Update DashStats.page
    • webgui: Bug fix in DashStats
    • webgui: Fix corruption check after a New Config is issued
    • webgui: Update alert text
    • webgui: Translation support (Unraid.net)
    • webgui: WireGuard: preset peer DNS server with "Remote tunneled access"
    • webgui: Plugins page loading improvements
    • webgui: Docker page loading improvements
    • webgui: Make WireGuard trademark visible on "full" page
    • webgui: Replace polling scripts with event driven Nchan interface
    • webgui: Improved format of stale and error plugin pages
    • webgui: Docker: Add crypto as a category
    • webgui: Dashboard: add CPU and NETWORK chart
    • webgui: Docker: compress too long author names
    • webgui: Convert notify polling to Nchan
    • webgui: Docker: process bash ANSI colors in web log display
    • webgui: dockerMan: remove HTML from descriptions
    • webgui: SSH authorized keys UI
    • webgui: Device_list replace .png icon with font icon
    • webgui: Compress too long share names in dropdown menus
    • webgui: Show management access and shares access groups for users
    • webgui: Added "User 'root'" reference on Management Access page
    • webgui: Show warning when javascript is disabled
    • webgui: Force creation of root password
    • webgui: Edit/Add Container: Fix browser console error
    • webgui: WireGuard: warn when directly connected with public IP
    • webgui: Fix network bonding display
    • webgui: Add tracking after system shutdown
    • webgui: Added notify when plugin fails to install
    • webgui: Add Apps link to install CA
    • webgui: Diagnostics: Add share summary
    • webgui: Suppress IPv6 anycast addresses in routing table
    • webgui: Diagnostics: Add share summary
    • webgui: Diagnostics: Include current plugin versions
    • webgui: Diagnostics: add DHCP log
    • webgui: Diagnostics fix plugin deprecated max version error
    • webgui: Docker: Support CA tag
    • webgui: Delete DockerRepositories.page
    • webgui: dockerMan Security: Remove HTML tags from Config elements
    • webgui: When viewing source, identify which .page file is responsible
    • webgui: System devices additions
    • webgui: Create syslog entry when user logs out
    • webgui: privatize host in diagnostics
    • webgui: Create favicon.ico
    • webgui: Update Credits.page
    • Like 22



    User Feedback

    Recommended Comments



    Sorry my fault. I should of added that I'm waiting to see if 6.10 will fix all the issues that I'm having with 6.9

    Link to comment

    I am posting this here just for some direction on whether this is a known bug or not (i.e. if we know a rouge or non updated plugin could be causing this). If the former then I will raise a bug report and post diagnostics.

     

    In summary, in this release I am noticing that my array seems to be spun up more than usual. Anecdotal I know.

     

    Querying the log, it appears that disks are spinning up and spinning down all day long even when there is little to no usage.

     

    What I am seeing is the disks will spin down and then at regular intervals Ill get "unraid emhttpd: read SMART" on each disk which causes them to spin up. Then, as per my settings, the disks will spin down after a period of time "unraid emhttpd: spinning down". 

     

    Rinse and repeat every two hours. Has anyone else noticed this?

    • Like 1
    Link to comment
    55 minutes ago, danioj said:

    Rinse and repeat every two hours. Has anyone else noticed this?

    How are your disks connected: SATA ports on the motherboard or a disk controller (which type)?

     

    Link to comment
    1 hour ago, bonienl said:

    How are your disks connected: SATA ports on the motherboard or a disk controller (which type)?

     

     

    Predominantly ports on my motherboard. However I do have one expansion card. My motherboard is an Supermicro X10SL7-F and my expansion card is a Marvell based card.

     

    Here is how they are connected:

     

    [8086:8c02] 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)

    [2:0:0:0] disk ATA CT1000MX500SSD1 023 /dev/sdb 1.00TB

    [3:0:0:0] disk ATA ST8000DM004-2CX1 0001 /dev/sdc 8.00TB

    [4:0:0:0] disk ATA WDC WD30EFRX-68A 0A80 /dev/sdd 3.00TB

    [5:0:0:0] disk ATA WDC WD30EFRX-68A 0A80 /dev/sde 3.00TB

    [6:0:0:0] disk ATA WDC WD30EURS-63R 0A80 /dev/sdf 3.00TB

    [7:0:0:0] disk ATA WDC WD30EFRX-68A 0A80 /dev/sdg 3.00TB

     

    [1000:0086] 02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05)

    [1:0:0:0] disk ATA WDC WD30EFRX-68A 0A80 /dev/sdl 3.00TB

    [1:0:1:0] disk ATA ST8000AS0002-1NA AR13 /dev/sdm 8.00TB

    [1:0:2:0] disk ATA ST8000VN0022-2EL SC61 /dev/sdn 8.00TB

    [1:0:3:0] disk ATA ST8000AS0002-1NA AR13 /dev/sdo 8.00TB

    [1:0:4:0] disk ATA ST8000AS0002-1NA AR13 /dev/sdp 8.00TB

    [1:0:5:0] disk ATA ST8000AS0002-1NA AR13 /dev/sdq 8.00TB

    [1:0:6:0] disk ATA ST8000AS0002-1NA AR13 /dev/sdr 8.00TB

    [1:0:7:0] disk ATA ST8000AS0002-1NA AR13 /dev/sds 8.00TB

     

    [1b4b:9230] 07:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller (rev 11)

    [8:0:0:0] disk ATA ST8000VN004-2M21 SC60 /dev/sdh 8.00TB

    [9:0:0:0] disk ATA ST8000VN004-2M21 SC60 /dev/sdi 8.00TB

    [10:0:0:0] disk ATA ST8000DM004-2CX1 0001 /dev/sdj 8.00TB

    [11:0:0:0] disk ATA CT250BX100SSD1 MU01 /dev/sdk 250GB

     

    From the diagnostics, I cannot see a pattern as to which drives get their SMART read but the timing is conspiquously regular. 

    unraid-diagnostics-20210902-1852.zip

    Link to comment
    3 hours ago, bonienl said:

    How are your disks connected: SATA ports on the motherboard or a disk controller (which type)?

     


    Last few hours of my logs:

     

    Sep  2 16:26:51 unraid webGUI: Successful login user root from 10.9.69.31
    Sep  2 16:27:59 unraid crond[1959]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
    Sep  2 17:29:37 unraid emhttpd: spinning down /dev/sdg
    Sep  2 17:29:37 unraid emhttpd: spinning down /dev/sdd
    Sep  2 17:29:37 unraid emhttpd: spinning down /dev/sde
    Sep  2 17:29:37 unraid emhttpd: spinning down /dev/sdl
    Sep  2 17:29:53 unraid emhttpd: spinning down /dev/sdf
    Sep  2 17:29:55 unraid emhttpd: spinning down /dev/sdm
    Sep  2 17:29:55 unraid emhttpd: spinning down /dev/sdr
    Sep  2 17:29:55 unraid emhttpd: spinning down /dev/sds
    Sep  2 17:29:55 unraid emhttpd: spinning down /dev/sdn
    Sep  2 17:29:55 unraid emhttpd: spinning down /dev/sdq
    Sep  2 17:29:55 unraid emhttpd: spinning down /dev/sdo
    Sep  2 17:29:55 unraid emhttpd: spinning down /dev/sdp
    Sep  2 17:30:20 unraid emhttpd: read SMART /dev/sdg
    Sep  2 17:30:26 unraid emhttpd: spinning down /dev/sdh
    Sep  2 17:30:39 unraid emhttpd: spinning down /dev/sdj
    Sep  2 17:30:39 unraid emhttpd: spinning down /dev/sdc
    Sep  2 17:30:39 unraid emhttpd: spinning down /dev/sdi
    Sep  2 17:31:35 unraid kernel: mdcmd (54): set md_write_method 0
    Sep  2 17:31:35 unraid kernel: 
    Sep  2 18:30:22 unraid emhttpd: spinning down /dev/sdg
    Sep  2 18:44:34 unraid webGUI: Successful login user root from 10.9.69.31
    Sep  2 18:51:29 unraid emhttpd: read SMART /dev/sds
    Sep  2 18:51:39 unraid emhttpd: read SMART /dev/sdr
    Sep  2 18:51:50 unraid emhttpd: read SMART /dev/sdp
    Sep  2 18:52:01 unraid emhttpd: read SMART /dev/sdo
    Sep  2 18:52:12 unraid emhttpd: read SMART /dev/sdm
    Sep  2 18:52:23 unraid emhttpd: read SMART /dev/sdq
    Sep  2 18:52:42 unraid emhttpd: read SMART /dev/sdj
    Sep  2 18:52:59 unraid emhttpd: read SMART /dev/sdc
    Sep  2 18:52:59 unraid emhttpd: read SMART /dev/sdn
    Sep  2 18:53:18 unraid emhttpd: read SMART /dev/sdh
    Sep  2 18:53:38 unraid emhttpd: read SMART /dev/sdi
    Sep  2 18:56:40 unraid kernel: mdcmd (55): set md_write_method 1
    Sep  2 18:56:40 unraid kernel: 
    Sep  2 19:09:03 unraid emhttpd: read SMART /dev/sdd
    Sep  2 19:09:41 unraid emhttpd: read SMART /dev/sde
    Sep  2 19:09:57 unraid emhttpd: read SMART /dev/sdf
    Sep  2 19:52:35 unraid emhttpd: spinning down /dev/sdj
    Sep  2 19:52:44 unraid emhttpd: spinning down /dev/sdc
    Sep  2 19:53:01 unraid emhttpd: spinning down /dev/sdh
    Sep  2 20:09:12 unraid emhttpd: spinning down /dev/sdd
    Sep  2 20:09:17 unraid emhttpd: spinning down /dev/sdq
    Sep  2 20:09:27 unraid emhttpd: spinning down /dev/sdm
    Sep  2 20:09:49 unraid emhttpd: spinning down /dev/sde
    Sep  2 20:09:50 unraid emhttpd: spinning down /dev/sdr
    Sep  2 20:09:52 unraid emhttpd: spinning down /dev/sds
    Sep  2 20:09:52 unraid emhttpd: spinning down /dev/sdo
    Sep  2 20:09:56 unraid emhttpd: spinning down /dev/sdp
    Sep  2 20:10:08 unraid emhttpd: spinning down /dev/sdf
    Sep  2 20:10:08 unraid emhttpd: spinning down /dev/sdn
    Sep  2 20:11:40 unraid kernel: mdcmd (56): set md_write_method 0
    Sep  2 20:11:40 unraid kernel: 
    Sep  2 20:27:20 unraid emhttpd: read SMART /dev/sdr
    Sep  2 20:27:31 unraid emhttpd: read SMART /dev/sds
    Sep  2 20:27:44 unraid emhttpd: read SMART /dev/sdm
    Sep  2 20:27:54 unraid emhttpd: read SMART /dev/sdg
    Sep  2 20:28:02 unraid emhttpd: read SMART /dev/sdl
    Sep  2 20:28:09 unraid emhttpd: read SMART /dev/sdo
    Sep  2 20:28:19 unraid emhttpd: read SMART /dev/sdq
    Sep  2 20:28:30 unraid emhttpd: read SMART /dev/sdn
    Sep  2 20:28:45 unraid emhttpd: read SMART /dev/sdp
    Sep  2 20:28:58 unraid emhttpd: read SMART /dev/sde
    Sep  2 20:29:04 unraid emhttpd: read SMART /dev/sdd
    Sep  2 20:29:16 unraid emhttpd: read SMART /dev/sdf
    Sep  2 20:29:40 unraid emhttpd: read SMART /dev/sdj
    Sep  2 20:29:40 unraid emhttpd: read SMART /dev/sdc
    Sep  2 20:31:41 unraid kernel: mdcmd (57): set md_write_method 1
    Sep  2 20:31:41 unraid kernel: 
    Sep  2 20:31:47 unraid emhttpd: read SMART /dev/sdh

     

    Link to comment
    6 hours ago, danioj said:

    I am posting this here just for some direction on whether this is a known bug or not (i.e. if we know a rouge or non updated plugin could be causing this). If the former then I will raise a bug report and post diagnostics.

     

    In summary, in this release I am noticing that my array seems to be spun up more than usual. Anecdotal I know.

     

    Querying the log, it appears that disks are spinning up and spinning down all day long even when there is little to no usage.

     

    What I am seeing is the disks will spin down and then at regular intervals Ill get "unraid emhttpd: read SMART" on each disk which causes them to spin up. Then, as per my settings, the disks will spin down after a period of time "unraid emhttpd: spinning down". 

     

    Rinse and repeat every two hours. Has anyone else noticed this?

    This is exactly what I posted about a few days ago. Same thing happening for me!

    • Like 1
    Link to comment
    6 hours ago, danioj said:

     

    Predominantly ports on my motherboard. However I do have one expansion card. My motherboard is an Supermicro X10SL7-F and my expansion card is a Marvell based card.

     

    unraid-diagnostics-20210902-1852.zip

     

    Its been highly recommended to move away from Marvel Expansion Cards because they have been extremely troublesome. I was having all kinds of disconnection issues and bad drive reports when I ran mine. When I switched to my LSI all problems went away. 

    • Like 1
    Link to comment
    8 hours ago, danioj said:

    Last few hours of my logs:

     

    Sep 2 18:56:40 unraid kernel: mdcmd (55): set md_write_method 1

     

     

    It looks like you have the Turbo-write plugin installed. I believe it's responding to the spin-ups and spin-downs, rather than causing them, but it might be worth disabling it temporarily just in case.

     

    Link to comment

     

    10 hours ago, Mathervius said:

    This is exactly what I posted about a few days ago. Same thing happening for me!


    Will you list what Plugin's you are using and also if you are using a Marvel controller in your setup please?

     

    7 hours ago, kizer said:

     

    Its been highly recommended to move away from Marvel Expansion Cards because they have been extremely troublesome. I was having all kinds of disconnection issues and bad drive reports when I ran mine. When I switched to my LSI all problems went away. 

     

    I have read that and it is good advice. I will probably retire it when I upgrade the Motherboard, CPU and RAM. Almost impossible to get a M/B with the same number of ports as the one I have so a good controller card will be a must.

     

    For this issue, I find it hard to believe that it is the card which is causing this issue. I base this on nothing other than observing that the spin up is happening across all drives and not just the 3 that are on the controller.

     

    3 hours ago, John_M said:

     

    It looks like you have the Turbo-write plugin installed. I believe it's responding to the spin-ups and spin-downs, rather than causing them, but it might be worth disabling it temporarily just in case.

     

     

    That is a good nod. I will do that. Thanks.

     

    So - what do we collectively think? Worth posting as a bug?

     

    EDIT: I have just disabled the Turbo Write Plug-in and spun the array down. I am heading to work now. It will be interesting to see if the SMART read commands are issued during the day.

    Edited by danioj
    Additional action documented
    Link to comment
    1 hour ago, danioj said:

     


    Will you list what Plugin's you are using and also if you are using a Marvel controller in your setup please?

     

     

    I have read that and it is good advice. I will probably retire it when I upgrade the Motherboard, CPU and RAM. Almost impossible to get a M/B with the same number of ports as the one I have so a good controller card will be a must.

     

    For this issue, I find it hard to believe that it is the card which is causing this issue. I base this on nothing other than observing that the spin up is happening across all drives and not just the 3 that are on the controller.

     

     

    That is a good nod. I will do that. Thanks.

     

    So - what do we collectively think? Worth posting as a bug?

     

    EDIT: I have just disabled the Turbo Write Plug-in and spun the array down. I am heading to work now. It will be interesting to see if the SMART read commands are issued during the day.

    I am not using a Marvel controller.

     

    My plugins:

    CA Auto Turbo Write Mode

    CA Auto Update Applications

    CA Backup / Restore Appdata

    CA Config Editor

    CA Mover Tuning

    Community Applications

    Custom Tab

    Dynamix Active Streams

    Dynamix Local Master

    Dynamix SSD TRIM

    Dynamix System Statistics

    Dynamix System Temperature

    Fix Common Problems

    GUI Links

    GUI Search

    Nerd Tools

    Network UPS Tools (NUT)

    Parity Check Tuning

    Recycle Bin

    Speedtest Command Line Tool

    Theme Engine

    Tips and Tweaks

    Unassigned Devices

    Unassigned Devices Plus

    User Scripts

     

    I uninstalled my CA Auto Turbo Write Mode plugin and it didn't seem to help. 

     

    What's really strange is that today my drives have started spinning down again. The only change I made was to uninstall the CA Auto Turbo Write Mode plugin and then reinstalled it later.

    Link to comment
    1 hour ago, Mathervius said:

    I am not using a Marvel controller.

     

    My plugins:

    CA Auto Turbo Write Mode

    CA Auto Update Applications

    CA Backup / Restore Appdata

    CA Config Editor

    CA Mover Tuning

    Community Applications

    Custom Tab

    Dynamix Active Streams

    Dynamix Local Master

    Dynamix SSD TRIM

    Dynamix System Statistics

    Dynamix System Temperature

    Fix Common Problems

    GUI Links

    GUI Search

    Nerd Tools

    Network UPS Tools (NUT)

    Parity Check Tuning

    Recycle Bin

    Speedtest Command Line Tool

    Theme Engine

    Tips and Tweaks

    Unassigned Devices

    Unassigned Devices Plus

    User Scripts

     

    I uninstalled my CA Auto Turbo Write Mode plugin and it didn't seem to help. 

     

    What's really strange is that today my drives have started spinning down again. The only change I made was to uninstall the CA Auto Turbo Write Mode plugin and then reinstalled it later.

     

    Thanks. Since I posted earlier this morning (well for me it is in Australia) that I spun my array down this has been my log:

     

    Sep  3 09:09:48 unraid emhttpd: spinning down /dev/sdc
    Sep  3 09:09:49 unraid emhttpd: spinning down /dev/sdf
    Sep  3 09:09:49 unraid emhttpd: spinning down /dev/sdd
    Sep  3 09:09:50 unraid emhttpd: spinning down /dev/sdg
    Sep  3 09:09:50 unraid emhttpd: spinning down /dev/sdl
    Sep  3 09:09:51 unraid emhttpd: spinning down /dev/sde
    Sep  3 09:09:51 unraid emhttpd: spinning down /dev/sdq
    Sep  3 09:09:52 unraid emhttpd: spinning down /dev/sdr
    Sep  3 09:09:52 unraid emhttpd: spinning down /dev/sdm
    Sep  3 09:09:53 unraid emhttpd: spinning down /dev/sds
    Sep  3 09:09:53 unraid emhttpd: spinning down /dev/sdo
    Sep  3 09:09:54 unraid emhttpd: spinning down /dev/sdn
    Sep  3 09:09:55 unraid emhttpd: spinning down /dev/sdp
    Sep  3 09:09:55 unraid emhttpd: spinning down /dev/sdi
    Sep  3 09:09:56 unraid emhttpd: spinning down /dev/sdh
    Sep  3 09:09:57 unraid emhttpd: spinning down /dev/sdj
    Sep  3 09:23:24 unraid webGUI: Successful login user root from 10.9.69.31
    Sep  3 09:29:01 unraid kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000dc000-0x000dffff window]
    Sep  3 09:29:01 unraid kernel: caller _nv000722rm+0x1ad/0x200 [nvidia] mapping multiple BARs
    Sep  3 09:59:41 unraid webGUI: Successful login user root from 10.9.69.31
    Sep  3 10:06:42 unraid emhttpd: read SMART /dev/sdm
    Sep  3 10:06:52 unraid emhttpd: read SMART /dev/sdi
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sdh
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sdr
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sds
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sdn
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sdq
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sdo
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sdp
    Sep  3 10:07:41 unraid emhttpd: read SMART /dev/sdj
    Sep  3 10:07:41 unraid emhttpd: read SMART /dev/sdc
    Sep  3 10:28:30 unraid emhttpd: read SMART /dev/sdg
    Sep  3 10:28:42 unraid emhttpd: read SMART /dev/sdl
    Sep  3 10:28:49 unraid emhttpd: read SMART /dev/sde
    Sep  3 10:28:56 unraid emhttpd: read SMART /dev/sdd
    Sep  3 10:34:43 unraid emhttpd: read SMART /dev/sdf
    Sep  3 11:17:57 unraid emhttpd: spinning down /dev/sdh
    Sep  3 11:18:58 unraid emhttpd: spinning down /dev/sdj
    Sep  3 11:18:58 unraid emhttpd: spinning down /dev/sdc
    Sep  3 11:34:04 unraid emhttpd: spinning down /dev/sdd
    Sep  3 11:34:35 unraid emhttpd: spinning down /dev/sde
    Sep  3 11:59:54 unraid emhttpd: spinning down /dev/sdf
    Sep  3 11:59:54 unraid emhttpd: spinning down /dev/sdn
    Sep  3 11:59:56 unraid emhttpd: spinning down /dev/sdm
    Sep  3 11:59:56 unraid emhttpd: spinning down /dev/sdg
    Sep  3 11:59:56 unraid emhttpd: spinning down /dev/sdq
    Sep  3 11:59:56 unraid emhttpd: spinning down /dev/sdo
    Sep  3 11:59:56 unraid emhttpd: spinning down /dev/sdl
    Sep  3 11:59:56 unraid emhttpd: spinning down /dev/sdi
    Sep  3 11:59:58 unraid emhttpd: spinning down /dev/sdr
    Sep  3 11:59:58 unraid emhttpd: spinning down /dev/sds
    Sep  3 11:59:58 unraid emhttpd: spinning down /dev/sdp
    Sep  3 12:00:36 unraid emhttpd: read SMART /dev/sdf
    Sep  3 12:03:02 unraid kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000dc000-0x000dffff window]
    Sep  3 12:03:02 unraid kernel: caller _nv000722rm+0x1ad/0x200 [nvidia] mapping multiple BARs
    Sep  3 12:03:04 unraid emhttpd: read SMART /dev/sdm
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdh
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdr
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sds
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdn
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdq
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdo
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdi
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdp
    Sep  3 12:03:49 unraid emhttpd: read SMART /dev/sdj
    Sep  3 12:03:49 unraid emhttpd: read SMART /dev/sdc
    Sep  3 12:03:59 unraid emhttpd: read SMART /dev/sdg
    Sep  3 12:03:59 unraid emhttpd: read SMART /dev/sdd
    Sep  3 12:03:59 unraid emhttpd: read SMART /dev/sde
    Sep  3 12:03:59 unraid emhttpd: read SMART /dev/sdl

     

    Something appears (to me) to be causing unRAID to keep reading SMART of inactive devices and spinning them up. Not sure what it is.

     

    I think I will just raise this as a bug and we can track it separately from this announcement thread. Ill summarise these posts into one opening post. Happy to work with you closely on this @Mathervius

     

    P.S. My array is spinning down quicker too but that is to be expected I think this is an effect of the Turbo Write Plugin.

    Edited by danioj
    Link to comment
    7 hours ago, danioj said:

     

    Thanks. Since I posted earlier this morning (well for me it is in Australia) that I spun my array down this has been my log:

     

    Sep  3 09:09:48 unraid emhttpd: spinning down /dev/sdc
    Sep  3 09:09:49 unraid emhttpd: spinning down /dev/sdf
    Sep  3 09:09:49 unraid emhttpd: spinning down /dev/sdd
    Sep  3 09:09:50 unraid emhttpd: spinning down /dev/sdg
    Sep  3 09:09:50 unraid emhttpd: spinning down /dev/sdl
    Sep  3 09:09:51 unraid emhttpd: spinning down /dev/sde
    Sep  3 09:09:51 unraid emhttpd: spinning down /dev/sdq
    Sep  3 09:09:52 unraid emhttpd: spinning down /dev/sdr
    Sep  3 09:09:52 unraid emhttpd: spinning down /dev/sdm
    Sep  3 09:09:53 unraid emhttpd: spinning down /dev/sds
    Sep  3 09:09:53 unraid emhttpd: spinning down /dev/sdo
    Sep  3 09:09:54 unraid emhttpd: spinning down /dev/sdn
    Sep  3 09:09:55 unraid emhttpd: spinning down /dev/sdp
    Sep  3 09:09:55 unraid emhttpd: spinning down /dev/sdi
    Sep  3 09:09:56 unraid emhttpd: spinning down /dev/sdh
    Sep  3 09:09:57 unraid emhttpd: spinning down /dev/sdj
    Sep  3 09:23:24 unraid webGUI: Successful login user root from 10.9.69.31
    Sep  3 09:29:01 unraid kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000dc000-0x000dffff window]
    Sep  3 09:29:01 unraid kernel: caller _nv000722rm+0x1ad/0x200 [nvidia] mapping multiple BARs
    Sep  3 09:59:41 unraid webGUI: Successful login user root from 10.9.69.31
    Sep  3 10:06:42 unraid emhttpd: read SMART /dev/sdm
    Sep  3 10:06:52 unraid emhttpd: read SMART /dev/sdi
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sdh
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sdr
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sds
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sdn
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sdq
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sdo
    Sep  3 10:07:21 unraid emhttpd: read SMART /dev/sdp
    Sep  3 10:07:41 unraid emhttpd: read SMART /dev/sdj
    Sep  3 10:07:41 unraid emhttpd: read SMART /dev/sdc
    Sep  3 10:28:30 unraid emhttpd: read SMART /dev/sdg
    Sep  3 10:28:42 unraid emhttpd: read SMART /dev/sdl
    Sep  3 10:28:49 unraid emhttpd: read SMART /dev/sde
    Sep  3 10:28:56 unraid emhttpd: read SMART /dev/sdd
    Sep  3 10:34:43 unraid emhttpd: read SMART /dev/sdf
    Sep  3 11:17:57 unraid emhttpd: spinning down /dev/sdh
    Sep  3 11:18:58 unraid emhttpd: spinning down /dev/sdj
    Sep  3 11:18:58 unraid emhttpd: spinning down /dev/sdc
    Sep  3 11:34:04 unraid emhttpd: spinning down /dev/sdd
    Sep  3 11:34:35 unraid emhttpd: spinning down /dev/sde
    Sep  3 11:59:54 unraid emhttpd: spinning down /dev/sdf
    Sep  3 11:59:54 unraid emhttpd: spinning down /dev/sdn
    Sep  3 11:59:56 unraid emhttpd: spinning down /dev/sdm
    Sep  3 11:59:56 unraid emhttpd: spinning down /dev/sdg
    Sep  3 11:59:56 unraid emhttpd: spinning down /dev/sdq
    Sep  3 11:59:56 unraid emhttpd: spinning down /dev/sdo
    Sep  3 11:59:56 unraid emhttpd: spinning down /dev/sdl
    Sep  3 11:59:56 unraid emhttpd: spinning down /dev/sdi
    Sep  3 11:59:58 unraid emhttpd: spinning down /dev/sdr
    Sep  3 11:59:58 unraid emhttpd: spinning down /dev/sds
    Sep  3 11:59:58 unraid emhttpd: spinning down /dev/sdp
    Sep  3 12:00:36 unraid emhttpd: read SMART /dev/sdf
    Sep  3 12:03:02 unraid kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000dc000-0x000dffff window]
    Sep  3 12:03:02 unraid kernel: caller _nv000722rm+0x1ad/0x200 [nvidia] mapping multiple BARs
    Sep  3 12:03:04 unraid emhttpd: read SMART /dev/sdm
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdh
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdr
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sds
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdn
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdq
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdo
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdi
    Sep  3 12:03:29 unraid emhttpd: read SMART /dev/sdp
    Sep  3 12:03:49 unraid emhttpd: read SMART /dev/sdj
    Sep  3 12:03:49 unraid emhttpd: read SMART /dev/sdc
    Sep  3 12:03:59 unraid emhttpd: read SMART /dev/sdg
    Sep  3 12:03:59 unraid emhttpd: read SMART /dev/sdd
    Sep  3 12:03:59 unraid emhttpd: read SMART /dev/sde
    Sep  3 12:03:59 unraid emhttpd: read SMART /dev/sdl

     

    Something appears (to me) to be causing unRAID to keep reading SMART of inactive devices and spinning them up. Not sure what it is.

     

    I think I will just raise this as a bug and we can track it separately from this announcement thread. Ill summarise these posts into one opening post. Happy to work with you closely on this @Mathervius

     

    P.S. My array is spinning down quicker too but that is to be expected I think this is an effect of the Turbo Write Plugin.

     

    Bug report raised as discussed.

     

     

    Link to comment
    On 8/18/2021 at 10:19 PM, Leoyzen said:

    @bonienl @uldiseOk I got it.

    I haven't noticed that before, but it is quite strange after upgrading 6.10...Maybe some behaviors have been changed as the status of io-waits which makes me feel "different" between 6.9.2 and 6.10.

     

    I will stay tuned.

    Someone help me?😭

    Link to comment
    On 8/19/2021 at 9:37 AM, Beermedlar said:

    Failed to start vm(GPU passthrough) after upgrade. After rolling back to 6.9.2, it works normally.

    bar-diagnostics-20210819-1533.zip

    You should probably create a specific thread as it is very difficult to follow several discussions in a single thread.

    Link to comment

    maybe in the future with the logged in upc etc on the server we can assign a license to the server. And get rid for the USB key. 

    And if i want to move the license to a new server.. i have unbound the license and add it on another server...

     

    Edited by orlando500
    Link to comment

    The flash backup and restore function is nice, but I can't get the USB creator to work on my windows desktop. It won't recognize any USB stick I plug in to my machine.

     

    I'll add, that it doesn't seem to be compliant with apple very much these days either.

     

    @limetech moving to an img or iso file and telling people to use rufus would probably be less work to maintain.

    Edited by eagle470
    additional information
    Link to comment

    I'm curious with this option. 

     

    Added support for Intel GVT-g, which lets you split your Intel i915 iGPU into multiple virtual GPUs and pass them through to multiple VMs, using @ich777's Intel-GVT-g plugin.

     

    how do i set it up?

    • Like 1
    Link to comment

    I just updated to 6.10.0-rc1 and on my Dell r610 where virtualization had been working, I am now getting a message that

    Quote

    Your hardware does not have Intel VT-x or AMD-V capability. This is required to create VMs in KVM. Please disable the VM function.

     

    It currently has 160GB RAM and 2x Xeon X5675s, and all virtualization is enabled in the BIOS.  It has the latest available BIOS and firmware for everything as well.  Searching this thread and the forums in general I couldn't find anything that applied to it working previously, but then stopping after an update.

    Link to comment

    Apologies to the moderator. I have now posted my bug report as a new item in bug-reports/pre-releases list. Just getting used to being involved, again sorry for posting it incorrectly earlier.

    Link to comment
    15 minutes ago, Fuggin said:

    What happened to the template repositories in the docker tab?

    2nd reply in the thread:

     

     

    Link to comment

    Encountered "Invalid Username or Password" when login in with root to the web GUI after the upgrade on one of my servers. SSH still works when login in as root. I had no issues with the other server.

     

    I have to add that I had to do a scan and repair the USB drive prior to upgrading to 6.10.0-rc1 since it was not writable.

    Edited by SCSI
    Link to comment
    On 9/17/2021 at 6:25 AM, SCSI said:

    Encountered "Invalid Username or Password" when login in with root to the web GUI after the upgrade on one of my servers. SSH still works when login in as root. I had no issues with the other server.

     

    I have to add that I had to do a scan and repair the USB drive prior to upgrading to 6.10.0-rc1 since it was not writable.

     

    I've had this issue as well when upgrading.

    I was unable to resolve it and have not retried upgrading to 6.10.0-rc1 since.

    In my case my USB drive appeared to be in good condition though.

     

    Did you ever change the root password on that server at some point prior to upgrading?

    Edited by Spiritreader
    Link to comment



    Guest
    This is now closed for further comments

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