• Unraid OS version 6.10.0-rc2 available


    limetech

    6.10.0 Summary of Changes and New Features

     

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

     

    Note: In order to permit ongoing development, some changes/features are marked experimental.  This means underlying support is included in the release, but high level functionality or UI has not been included yet.

     

    UPC and My Servers Plugin - [rc2] reworded

    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, also known as an Unraid.net 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. 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 servers associated with this account.  Each tile includes a link to bring up the servers webGUI on your LAN.  Install the My Servers plugin to provide real-time status and other advanced features (see below).
    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. Posting privilege in a new set of My Servers forum boards.
    4. 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.

     

    Once a license key has been provisioned, it is not necessary to remain signed-in, though there is no particular reason to sign-out.

    [rc2]  Exception:  A server must be signed-in to Provision and Renew a Let's Encrypt SSL certificate.

     

    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:

    • Real-time Status - with the plugin installed each server tile on the My Servers Dashboard will display real-time status such as whether the server is online or offline, storage utilization and other information. 
    • Remote Access link - if enabled, a link is displayed on the My Servers Dashboard to bring up a server webGUI remotely over the Internet.
    • Automatic 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.  A link is provided 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.

     

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

     

    If you have installed the My Servers plugin, signed-in servers will maintain a websocket connection to a cloud-based Lime Technology proxy server for the purpose of relaying real-time status.

     

    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, and [rc2] ARM emulation (experimental).

     

    [rc2] To support Windows 11 which requires TPM and Secure boot, we have added TPM emulation; and, added a "Windows 11" VM template which automatically selects TPM-aware OVMF bios.  Also, here are instructions for upgrading a Windows 10 VM to Windows 11.  Special thanks to @ich777 who researched and determined what changes and components were necessary to provide this functionality.

     

    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 [rc2] Linux 5.14.15 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.

     

    [rc2] Added so-called "add-relaxable-rmrr-5_8_and_up.patch" modified for our kernel
      https://github.com/kiler129/relax-intel-rmrr/blob/master/patches/add-relaxable-rmrr-5_8_and_up.patch

    Thanks to @ich777 for pointing this out,

     

    [rc2] Enabled additional ACPI kernel options
    [rc2] Updated out-of-tree drivers

    [rc2] Enabled TPM kernel modules (not utilized yet) - note this is for Unraid host utilizing physical TPM, not emulated TPM support for virtual machnes.

     

    Base Packages

    Virtually the entire base package set has been updated.

     

    [rc2] For SMB: Samba version 4.15 SMB3 multi-channel is no longer marked "experimental" and is enabled by default.

     

    [rc2] Per request we added the mcelog package.  With inclusion of this package, if you have an AMD processor you may see this error message in the system log:

    mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead.

    We're not sure what to make of this.  It appears mcelog is begin deprecated in favor of rasdaemon.  This is something we need to research further.

     

    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.  [rc2] Automatically restrict wsdd to listen only at the primary network interface (br0, bond0, or eth0, depending on config).
    • 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 and [rc2] fixed issue with macOS Monterey.
    • [rc2] Fixed jumbo frames not working.
    • [rc2] sysctl: handle net.netfilter.nf_conntrack_count max exceeded (increase setting to 131072) - hattip to Community Member @DieFalse

    • [rc2] Mover will create '.partial' file and then rename upon completion.

    • [rc2] Check bz file sha256sums at boot time.

     

    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-rc2 2021-11-01 (vs. 6.10.0-rc1)

     

    Base distro:

    • acpid: version 2.0.33
    • at-spi2-core: version 2.42.0
    • bind: version 9.16.22
    • btrfs-progs: version 5.14.2
    • ca-certificates: version 20211005
    • cifs-utils: version 6.14
    • coreutils: version 9.0
    • cryptsetup: version 2.4.1
    • curl: version 7.79.1
    • dhcpcd: version 9.4.1
    • dnsmasq: version 2.86
    • docker: version 20.10.9
    • e2fsprogs: version 1.46.4
    • ethtool: version 5.14
    • file: version 5.41
    • fribidi: version 1.0.11
    • fuse3: version 3.10.5
    • gd: version 2.3.3
    • gdbm: version 1.22
    • git: version 2.33.1
    • glib2: version 2.70.0
    • glibc-zoneinfo: version 2021e
    • gnutls: version 3.7.2
    • grep: version 3.7
    • gzip: version 1.11
    • harfbuzz: version 3.0.0
    • haveged: version 1.9.15
    • htop: version 3.1.1
    • iproute2: version 5.14.0
    • jansson: version 2.14
    • json-glib: version 1.6.6
    • libXi: version 1.8
    • libarchive: version 3.5.2
    • libedit: version 20210910_3.1
    • libepoxy: version 1.5.9
    • libgcrypt: version 1.9.4
    • libgudev: version 237
    • libjpeg-turbo: version 2.1.1
    • libssh: version 0.9.6
    • libssh2: version 1.10.0
    • libtpms: version 0.9.0
    • libvirt: version 7.8.0
    • libvirt-php: version 0.5.6a
    • libwebp: version 1.2.1
    • libxkbcommon: version 1.3.1
    • lvm2: version 2.03.13
    • mc: version 4.8.27
    • mcelog: version 179
    • nano: version 5.9
    • ncurses: version 6.3
    • nghttp2: version 1.46.0
    • nginx: version 1.19.10
    • ntfs-3g: version 2021.8.22
    • openssh: version 8.8p1
    • openssl: version 1.1.1l
    • openssl-solibs: version 1.1.1l
    • pam: version 1.5.2
    • pango: version 1.48.10
    • pcre2: version 10.38
    • php: version 7.4.24
    • qemu: version 6.1.0
    • samba: version 4.15.0
    • sudo: version 1.9.8p2
    • swtpm: version 0.6.1
    • ttyd: version 20211023
    • usbutils: version 014
    • util-linux: version 2.37.2
    • wget: version 1.21.2
    • wireguard-tools: version 1.0.20210914
    • wsdd2: version 1.8.6
    • xfsprogs: version 5.13.0
    • xkeyboard-config: version 2.34
    • xrdb: version 1.2.1
    • xterm: version 369

     

    Linux kernel:

    • version 5.14.15
    • restore CONFIG_X86_X32: x32 ABI for 64-bit mode
    • added so-called "add-relaxable-rmrr-5_8_and_up.patch" modified for this kernel
    • added several ACPI-related CONFIG settings
    • added CONFIG_TCG_TPM and associated TPM chip drivers
    • added CONFIG_NFSD_V4: NFS server support for NFS version 4
    • added CONFIG_USB_NET_AQC111: Aquantia AQtion USB to 5/2.5GbE Controllers support
    • added NFS_V4: NFS client support for NFS version 4
    • oot: md/unriad: version 2.9.19
    • oot: nvidia: version 470.63.01 [via plugin]
    • oot: r8125:version 9.006.04
    • oot: r8152: version 2.15.0

     

    Management:

    • emhttpd: fix regression: user shares should be enabled by default
    • emhttpd: minimize information transmitted by 'stock' UpdateDNS function
    • firefox: version 91.0.r20210823123856 (AppImage)
    • mover: append '.partial' suffix to filename when move in-progess
    • rc.mcelog: mcelog added to base distro
    • rc.nginx: support custom wildcard self-signed certs
    • rc.S: check bz file sha256 during initial boot
    • sysctl: handle net.netfilter.nf_conntrack_count max exceeded (increase setting to 131072)
    • wsdd2: listen only on active interface by default (br0, bond0, or eth0)
    • webgui: remove 'My Servers' skeleton page
    • webgui: present CA-signed certificate subject as a link
    • webgui: Relax update frequency a bit
    • webgui: Docker: Only save templates as v2
    • webgui: Fix pools display on Main page when empty pool exists
    • webgui: Escape double quotes in text input submit
    • webgui: Add 'root' folder protection to filetree
    • webgui: Support multi-language in filetree display
    • webgui: Use background checking for flash corruption
    • webgui: Proactive script security hardening
    • webgui: Diagnostics: add check for DNS Rebinding Protection
    • webgui: Diagnostics: privatize routable IPs
    • webgui: Diagnostics: add url details
    • webgui: Docker: Fix incorrect caching when deleting / recreating image
    • webgui: Silence PHP error on syslinux page if flash drive is missing
    • webgui: various Multi-language corrections
    • webgui: VM Manager: added Windows 11 template and OVMF TPM
    • webgui: VM Manager: add virtio-win-0.1.208.iso download link
    • webgui: Sign-in required to provision/renew Unraid LE SSL certificate
    • Like 10
    • Thanks 4



    User Feedback

    Recommended Comments



    25 minutes ago, Squid said:

    It was a clean shutdown (assuming that is the diagnostics immediately after it booting back up), so the system didn't crash or anything....

    Agreed but triggered by the VM and not the host hence the post here given that I am running the RC.

     

    If its not a glitch / bug thats fine but thought I would post just in case.

     

    BTW I think you can reproduce by changing the UUID.

     

    Thanks as ever Squid.

     

    T

    Edited by ccsnet
    Link to comment

    the vm template screen in unraid is a little buggy. I spent a few days trying to get a manjaro vm up and running, and it was very hard.

     

    Initially you set the vm to have vnc graphics, and after the vm is working, you can switch to the nvidia card.

    • The VM template gets damaged somehow, and cannot return to vnc mode. The graphics system stalls and only solution was to delete the template and recreate, attaching to the existing vdisk.
    • The VM template offers an input field to point to the rom bios. This field used to be able to point to the /mnt/user dir structure. But no more... its just a blank text field.

    I tried saving off the xml and copy/paste it... so can preserve the vm template... but did not work.

    • Like 1
    Link to comment

    I'm a bit late to the party but is there a hardware passthrough issue in this rc version? I have been messing around and pushing the limits of the VM configs to see what works and what doesn't. Oddly enough my usb controller that is passed through is now glitchy (Vantec 3.1 gen 2 2-port Usb c + Usb A) and does not show any devices. I am having to run individual passthrough for each device vs the entire controller. 

    Edit: It may also just be the ASMedia chipset is not good at passing through because it was working before perfectly fine on 6.9.2.

    Edited by TPNuts
    Link to comment

    Issue:

     

    Share settings / Excluded disks setting is not working without array restart.

     

    Example:  If I have a backup share and have nothing checked in either included disks (all) or Excluded disks (none) it works as intended.  Files are written to disk 12 as it has most free space. 

     

    However, if I change Excluded disks to Disk 12 and write to the share, given that disk 12 still has the most free space and allocation is set to Most-free it will still write new files to Disk 12.  

     

    An array restart solves this problem. 

     

    Link to comment
    44 minutes ago, dredge999 said:

    Share settings / Excluded disks setting is not working without array restart

    Known issue.  Should be fixed next release

    Link to comment

    Overall my experience with RC2 was good.  The random crashes when Docker using custom br0 seems to have been addressed with ipvlan.  However I did revert back to 6.9.2 because of SMB issues with large file copies (volumes drop off, copy is interrupted and file copies are corrupted.).  In particular this happened when I tried to copy a multi GB file containing photos from an unassigned drive to the server using an rsync  backup script.  I don't seem to have these issues with 6.9.2.   I recognize that this SMB issue  has been reported by others, but I wanted to add another voice as  its a fairly big deal and will limit my ability to move 6.10.  

    Link to comment

    I'm very new with unRAID and just installed unRAID 6.9.2. After testing period I decide to buy the licence and install unRraid on my productive infrastructure (instead of HyperV). I would like to avoid future upgrade to 6.10. 

    Works the 6.10 R2 version well and stable? May I install it wihout any problems or better stay on 6.9.2?

     

    Thank You.

    Link to comment
    23 minutes ago, norbo80 said:

    I'm very new with unRAID and just installed unRAID 6.9.2. After testing period I decide to buy the licence and install unRraid on my productive infrastructure (instead of HyperV). I would like to avoid future upgrade to 6.10. 

    Works the 6.10 R2 version well and stable? May I install it wihout any problems or better stay on 6.9.2?

     

    Thank You.

     Have you read all the posts in this thread?  There are several issues still being worked on, that's why it's a RC.  Unless you want to test and provide feedback, you may want to stay on the current stable release until 10 stable is released.  On the other hand, several people don't have any issues at all. It may depend on hardware and how you are using Unraid.  Could be risky for a Production server because the team is still sorting out some bugs / known issues.  Of course this is just my opinion

    • Thanks 1
    Link to comment

    Please give us an option to remove background from UPC when using a banner. Current default is white linear-gradient and it does not look right. Had to set banner to hide to make it better.

    First is how it looks now. I had to edit unraid.min.js to make it like it should(in pic 2)

    How it looks now.png

    How it should be.png

    Edited by csrihari
    Language
    Link to comment
    2 hours ago, csrihari said:

    Please give us an option to remove background from UPC when using a banner. Current default is white linear-gradient and it looks disgusting. Had to set banner to hide to remove this eye-sore.

    First is how it looks now. I had to edit unraid.min.js to make it like it should(in pic 2)

    How it looks now.png

    How it should be.png

     

    Please be courteous to the devs - that was unnecessarily rude. While your fix does look nice, how you suggest needs a little love.

    Link to comment
    4 minutes ago, Unraid_Student said:

     

    Please be courteous to the devs - that was unnecessarily rude. While your fix does look nice, how you suggest needs a little love.

    Agreed. My apologies to devs. I was in a bad mood. (Edited my original post)

    Edited by csrihari
    Link to comment

    Been loving the switch to UnRAID and 6.10RC2

     

    One issue i have been seeing is that the GPU usage on my 5600G will get "stuck at 100% as reported by radeontop. Doesnt seem to affect plex transcoding or anything else, but it requires a full reboot to get the usage looking correct again.

     

    Any word on what Kernel version is going to be in stable? Looks like 5.15 adds support for quite a few CPUs/GPUs, and some compatibility improvements for Ryzen 5000 series.

    Link to comment
    11 hours ago, eatoff said:

    Any word on what Kernel version is going to be in stable? Looks like 5.15 adds support for quite a few CPUs/GPUs, and some compatibility improvements for Ryzen 5000 series.

    No idea on final version, but there has already been comments that rc3 will have the 5.15 kernel (or later I guess).

    • Like 1
    Link to comment

    can anyone please confirm if the drive spin down issue is resolved in RC2?  That's the only reason I haven't tried it yet and why I'm stuck on 6.9.1.  When I went to 6.9.2, all my drives would remain spun up 😭

    Link to comment
    3 hours ago, optiman said:

    can anyone please confirm if the drive spin down issue is resolved in RC2?  That's the only reason I haven't tried it yet and why I'm stuck on 6.9.1.  When I went to 6.9.2, all my drives would remain spun up 😭

    I'll readily admit that I haven't read this entire thread. But I've been on 6.9.2 since it was released and I haven't experienced this issue at all. My disks spin down just fine. Hardware specs are in my signature.

     

    ---------------------------------------------------------

     

    One question I do have though, for QEMU / KVM: I heard from a birdie about 5-6 months ago - an oVirt dev, really - that QEMU/KVM had an update that allowed console access to a Windows VM that had a GPU passed through to it. In the past, if you passed a GPU through to a VM you were left with a blank screen on the console. So this enhancement added a feature that Citrix / VMWare have had for quite a while.

     

    Is that a thing here? Or am I possibly making something up in my own head? I've checked Phoronix and other upstream sites but haven't found anything to link here to back up my question with documentation (I know, I'm the worst...). But I figured I'd ask the question anyway.

     

    But I swear I read this somewhere. I'm going to keep searching. I can't find it now. Maybe I had too many IPAs when I heard it. /shrug

    Edited by Jason Harris
    Link to comment
    1 hour ago, sheiy said:

    when will release?

    Limetech never offers release dates.

    It's out when they judge there are no more blocking points.

    Link to comment

    I just built my first Unraid box and decided to start on 6.10 RC2.  
    Everything was working great for the first couple of weeks, I've been watching Space Invader videos, reading the forum and reddit and "optimizing" things.  I figured it's best to poke around now and learn how to and not to do things early on.

    I did an "optimization" yesterday switching Docker from using a BTRFS disk to a directory as it seems like that is the way to go???*  I also switched from macvlan to ipvlan.  Of course, when I started Docker back up, all of the containers were gone, took me a minute to figure out the right way was to reinstall them with Community Apps, which makes it super easy.  All of this was OK, however, I shut Unraid down (clean shutdown) to add a new drive last night and brought it back up, half the docker containers would not start.  Each was giving a different error about some file or other being missing.

    Most of the containers I could get back up and running by deleting them and readding, but MakeMKV refuses to play nice.  I've tried everything I can think of, including removing its data in appdata (didn't need it), cleaning images, doing a `docker system prune`, etc., it keeps throwing the following error.
     

    [cont-init.d] executing container initialization scripts...
    [cont-init.d] 00-app-niceness.sh: executing...
    exec: fatal: unable to exec sh: No such file or directory
    [cont-init.d] 00-app-niceness.sh: exited 111.
    [services.d] stopping services

     

    I've tried running the exact same image locally in Windows Subsystem for Linux and it runs fine.
    Only thing I can think of is that something in the docker directory has gotten corrupted.  
    I'm out of ideas on how to fix this without stopping the docker service and blowing away the docker directory.  

    Any thoughts from anyone?

     

    A few notes about my config.

    • Dell R720xd lff
    • CPU's 2 X Intel Xeon E5-2697 v2 
    • 128 gigs new RAM that has passed Memtest, though I haven't ran it with the new CPUs I just put in, might want to do that.
    • Cache volume are two new Samsung 970 EVO Plus 2TB nvme drives.  I've been getting over temp readings from these, but they are going just over the warning temp, I have heatsinks for them coming on Sunday

     

    * I have questions about why a BTRFS volume was ever used for Docker, why not just use a directory.  Was there some design win?  Some reason to use a disk image I don't get?

     

    Any help anyone can give would be appreciated, let me know if you think this should be a seperate post.

     

    Update 1: I got impatient and went ahead and tried to blow away the docker directory, it wouldn't let me, even with the Docker service stopped, so I just pointed the Docker servers at /mnt/user/system/docker2/, restarted the service and now everything installs and runs correctly.  Very strange.  Any help anyone can give on why this happened would be appreciated.  No SMART warnings on the cache drives other than temp which according to the spec sheet for those drives is not a problem.  They are at 47 and 48c and drive specs say up to 85c is fine but others have said the drives start the thermal throttle at 62c.  Note that Unraid was sending warnings at 47c, even though the default warning temp is much higher.    

    Edited by Sarge
    Link to comment
    16 minutes ago, Sarge said:

    I just built my first Unraid box and decided to start on 6.10 RC2.  
    Everything was working great for the first couple of weeks, I've been watching Space Invader videos, reading the forum and reddit and "optimizing" things.  I figured it's best to poke around now and learn how to and not to do things early on.

    I did an "optimization" yesterday switching Docker from using a BTRFS disk to a directory as it seems like that is the way to go???*  I also switched from macvlan to ipvlan.  Of course, when I started Docker back up, all of the containers were gone, took me a minute to figure out the right way was to reinstall them with Community Apps, which makes it super easy.  All of this was OK, however, I shut Unraid down (clean shutdown) to add a new drive last night and brought it back up, half the docker containers would not start.  Each was giving a different error about some file or other being missing.

    Most of the containers I could get back up and running by deleting them and readding, but MakeMKV refuses to play nice.  I've tried everything I can think of, including removing its data in appdata (didn't need it), cleaning images, doing a `docker system prune`, etc., it keeps throwing the following error.
     

    [cont-init.d] executing container initialization scripts...
    [cont-init.d] 00-app-niceness.sh: executing...
    exec: fatal: unable to exec sh: No such file or directory
    [cont-init.d] 00-app-niceness.sh: exited 111.
    [services.d] stopping services

     

    I've tried running the exact same image locally in Windows Subsystem for Linux and it runs fine.
    Only thing I can think of is that something in the docker directory has gotten corrupted.  
    I'm out of ideas on how to fix this without stopping the docker service and blowing away the docker directory.  

    Any thoughts from anyone?

     

    A few notes about my config.

    • Dell R720xd lff
    • CPU's 2 X Intel Xeon E5-2697 v2 
    • 128 gigs new RAM that has passed Memtest, though I haven't ran it with the new CPUs I just put in, might want to do that.
    • Cache volume are two new Samsung 970 EVO Plus 2TB nvme drives.  I've been getting over temp readings from these, but they are going just over the warning temp, I have heatsinks for them coming on Sunday

     

    * I have questions about why a BTRFS volume was ever used for Docker, why not just use a directory.  Was there some design win?  Some reason to use a disk image I don't get?

     

    Any help anyone can give would be appreciated, let me know if you think this should be a seperate post.

    Not sure about the docker issue but NVME drives run significantly hotter than normal SSD.  I have researched the nominal/overtemp for these (I have Samsung also) and it is safe to just raise the warning temp for each NVME.

     

    Edited by dredge999
    Link to comment
    4 minutes ago, dredge999 said:

    Not sure about the docker issue but NVME drives run significantly hotter than normal SSD.  I have researched the nominal/overtemp for these (I have Samsung also) and it is safe to just raise the warning temp for each NVME.

     

    Good call, I've looked into it some and know there is a point where the Samsung drives will throttle due to temp so wanted some extra cooling anyway.

    Link to comment
    17 hours ago, Sarge said:

    Good call, I've looked into it some and know there is a point where the Samsung drives will throttle due to temp so wanted some extra cooling anyway.

    I heard that the NAND chips run better hot, so you shouldn't add heatsinks (which is why they don't come with them in the first place).

    Link to comment
    22 hours ago, Sarge said:

    Any help anyone can give on why this happened would be appreciated. 

    Unfortunately not without diagnostics showing what happened...

     

    22 hours ago, Sarge said:

    I have questions about why a BTRFS volume was ever used for Docker, why not just use a directory.  Was there some design win?  Some reason to use a disk image I don't get?

    History lesson:

     

    At the beginning of docker introduction into the OS (6.0-beta something), it was originally a directory (and directory only).  This however (at the time) imposed a rather strict limitation that the cache drive had to be formatted as BTRFS (at the time there wasn't an XFS (or reiserFS) driver for docker).  Since this was rather annoying, the idea of using a BTRFS image came into being as it could be placed onto any particular filesystem without worry.

     

    Eventually with 6.9.x the folder idea was one solution to a extraneous writes to SSD problem and it was re-introduced, and it also helps with an eventual integration of ZFS into the system and the folder could also be hosted directly on a ZFS array which will massively increase performance.

     

    I'm personally a fan of the folder method as it tends to solve certain problems but it also comes with it's own big caveat.  NEVER NEVER NEVER run the New Permission Tool against that folder.  You will automatically have to recreate the folder because nothing will work after trashing the permissions.

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