Leaderboard

As some have figured out, there are new license key types coming soon™ for Unraid OS. We are still working on minor details but here is what we have planned. We are going to introduce two new keys: Starter - supports up to 4 6 devices. This will be offered at a lower price than today's Basic key. Unleashed - supports unlimited number of devices. This will be offered at about the same price as today's Plus key. These two new keys provide for free Unraid OS updates for one year following activation. After a year you have the option of extending the key for another year of updates for a fraction of the cost of the original key. If you choose not to extend, you can still run any version of Unraid OS released prior to your renewal date, back to version 6.12.8. Simultaneous with introducing these two key types, we will no longer offer Basic, Plus, and Pro keys; We will offer a new Lifetime license that will be more than a current Pro. Nothing changes for existing Basic/Plus/Pro keys: you still get Unraid OS updates for life and you will still have the option to upgrade Basic to Plus/Pro or Plus to Pro. For more on these changes, please see our blog post and for a wide-ranging discussion about the origin of Unraid, present state of the company and future plans, please see our Uncast Show episode: Please use this topic for any comments or questions.

The 6.12 release includes ZFS support (phase 1), several minor feature improvements, bug fixes, base package updates, and update to the latest 6.1.x longterm maintenance Linux kernel. Check out the detailed Release Notes on our new docs site, and while there, take a look around. As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". To upgrade: First create a backup of your USB flash boot device: Main/Flash/Flash Backup If you are running any 6.4 or later release, click 'Check for Updates' on the Tools/Update OS page. If you are running a pre-6.4 release, click 'Check for Updates' on the Plugins page. If the above doesn't work, navigate to Plugins/Install Plugin, select/copy/paste this plugin URL and click Install: https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer.plg Bugs: If you discover a bug or other issue in this release, please open a Stable Releases Bug Report and please attach your diagnostics. ALL USERS are encouraged to upgrade. Special thanks to all our contributors and beta testers and especially: @bonienl for his continued refinement and updating of the Dynamix webGUI especially in the area of networking. @Squid for continued refinement of Community Apps and customer support. @dlandon for continued refinement of the Unassigned Devices, associated plugins, and customer support. @ich777 for assistance and package contributions in all things Linux-related. @SimonF for greatly improving our VM manager. @JorgeB for rigorous testing of storage subsystem and user support. Finally a big Thank You! to @steini84 who brought ZFS to Unraid via plugin several years ago.

Hi Unraiders, I just wanted to take a minute to recognize and honor @JorgeB for surpassing 50,000 posts here! Wow 👏 Thank you for all of your help to the Unraid community over these past 15+ plus years! We are sending Jorge a gift as a token of our gratitude and if you would like to as well, please do so here. Thank you Jorge!

Can't really believe how I've made so many posts, and due to the increasing number of daily user posts over the years, at this pace it will take me considerably fewer years to reach 100K, if we are not all replaced by ChatGPT by then It really means a lot to me being a valued member of this great community, thanks all!

The 6.12.4 release includes a fix for macvlan call traces(!) along with other features, bug fixes, and security patches. All users are encouraged to upgrade. Please refer also to the 6.12.0 Announcement post. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.3, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (This issue was thought to be resolved with 6.12.3, but some systems are still having issues) Go to Tools -> Update OS. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot Special thanks to all our contributors and beta testers and especially: @bonienl for finding a solution to the macvlan problem! @SimonF for bringing us the new System Drivers page This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip.

We've mothballed our old, outdated wiki and are pleased to bring you a whole new home for Unraid Documentation. Using a new static-site provider with fast client-side navigation and an interactive interface powered by React, we're stoked to bring you a cleaner, more modern Unraid Docs experience that is fully searchable, versioned to OS releases, lightning-fast, mobile-friendly, and accessible to all. Even better, Unraid users can now submit page edit Pull Requests, helping us ensure that the docs keep up as the Unraid OS ecosystem grows and changes. More New Features New Site and Page Nav bars on every page of the Docs Easy URL linking to specific page sections Light and Dark themes Coming Soon Ability for users to create new community Docs pages Submit and share Unraid Guides 🌍 Internationalization: Ability to help translate the Unraid docs into multiple languages such as Spanish, French, German and Chinese. https://docs.unraid.net/ We hope you enjoy our new Docs experience.

The current 28-device limitation applies to the unRAID array. You can have any number of btrfs/zfs pools with other devices. An upcoming version will let you have multiple unRAID arrays though we don't plan on increasing the width of a single unRAID array. With your Pro key you'll get this update for free 🙂

We need more of these.

Hybrid or "tiered" storage (NVME + SSD + HDD). Where "hot" data is in NVME, then transitions down the stack. Least used data is on hdd. In other words; a QNAP qtier alternative.

FolderView lets you create folders for grouping Dockers and VMs together to help with organization. Especially useful if you're using docker-compose. Getting Started: A new button named "Add Folder" will appear at the bottom of the docker and VM tab(s) next to "Add Container". GitHub AUTOSTART With this plugin installed, you have to keep in mind that the order of the containers/vm might not be the actual order of the container, this is an issue with containers that are set to autostart. The plugin checks what you see and the unraid order and shows if the order is the same with this icon . If this icon is green like here means that the order you see is the same of unraid, if the icon is red this means that the unraid order is different. To fix that you can simply reorder a folder or a container and then refresh the page, you will see that the icon is turned green. DEBUG MODE To enable the debug mode you have to type 'debug' and you should see a download starting. If you have a problem you will likely be asked to submit that file, the file is specific to the tab that you are on. If nothing happens, open the browser console and send a screenshot of that. CUSTOM CSS/SCRIPT Using custom CSS/scripts is easy, just download the files and import it with the button in the settings. Here is a list of repository with custom CSS: hernandito Mattaton For the ones brave enough to make custom CSS or scripts, on GitHub you will find a README with all the instruction, if you have question you can DM me or ask it here. TRANSLATIONS If you want to translate this plugin, you can find the files here, but before read below. The "locale" field and the name of the file should be an ISO 639-1 language code. If you translate, don't edit any HTML tags you see, only edit text. In the translation file, you might encounter the symbol $ followed by a number, you can't remove them, but you can move them around as much as you want. DOCKER LABELS You can add docker containers to folders by adding the label "folder.view", the value of the label is the name of the folder. FAQ BEFORE asking, please search if any other user asked the same thing, you might find your solution. Q: How can I sort the content of a folder? A: In the edit page, you can drag and drop the containers/VM just like the normal docker page. Q: How can I sort the folder themselves? A: In the docker page since 6.12 there is a padlock green icon in the toolbar, click that, and you can just drag and drop the folder like normal containers/VM.

This plugin does a quick patch to the docker system on 6.12.8 only to prevent any empty host paths or container paths which may be present in an already installed template (or on a new installation) from triggering an error (and creating an orphan image) when updating the application. This is NOT fixing any bug in Unraid at all. Previously, the docker run command (eg: on 6.12.6) would not return an error if there was no container path specified. The docker system in 6.12.8+ does return an error (which is the proper operation). This quick patch simply has the docker system not add in to the docker run command any paths which has either the container or host side of it blank. If you did update an application and then had it orphan due to an empty path, then simply installing this plugin and then going to Apps, Previous Apps and reinstalling will get you back and running without changing the template to how it should be set up

You clearly didn't make the effort of even reading the post you're replying to.

The 6.12.3 release includes a set of bug fixes for networking and Docker. All users are encouraged to upgrade. Please refer also to the 6.12.0 Announcement post. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.2, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (This issue is resolved with this release) Go to Tools -> Update OS. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip.

UPDATE! please see my comment further down in this thread https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/#comment-1283203 ------------------------------- Original message: ------------------------------- I hit this today when stopping my array. Here is what worked for me, would appreciate if someone hitting this would confirm it works for them too. To get into this state, stop the array. If you are having this issue you will see "retry unmounting shares" in the lower left corner. Note: There are other reasons this message could happen (like if you left an SSH terminal open while cd'd into the array). This discussion assumes none of the usual suspects apply. In a web terminal or SSH type 'losetup'. In my case it showed: root@Tower:/etc/rc.d# losetup NAME SIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC /dev/loop1 0 0 1 1 /boot/bzfirmware 0 512 /dev/loop2 0 0 1 0 /mnt/cache/system/docker/docker.img 0 512 /dev/loop0 0 0 1 1 /boot/bzmodules 0 512 The problem is that docker.img is still mounted. Note that in my case is it on /dev/loop2 Then run `/etc/rc.d/rc.docker status` to confirm that docker has stopped: # /etc/rc.d/rc.docker status status of dockerd: stopped (It should be stopped, since you were in the process of stopping the array. But if Docker is still running, you can type `/etc/rc.d/rc.docker stop` and wait a bit, then run status again until it has stopped.) Then to fix the problem, type: umount /dev/loop2 (use whatever /dev/loopX docker.img is on, as noted above) Once that is unmounted, the array will automatically finish stopping. We are looking into a fix for this, but it would help if we could reliably reproduce the problem (it has only happened to me once). If anyone is able to identify what it takes to make this happen I'd appreciate it.

No native Docker-Compose option 🥲

Alright, everyone. Here is the UUD 1.7 preview. It looks pretty different from 1.6, and since I made this version, I haven't really changed it much. It is the most fined tuned and refined version that I have developed, and there isn't much more that I need for me personally. I'm pretty pleased with the way it turned out. Let me know your thoughts and/or if you have any questions! @SpencerJ ULTIMATE UNRAID DASHBOARD Version 1.7 (Click Each Image for 4K High Resolution)

Oh come on ! Just 50 mins after I updated to 6.12.5 ! *mumbles* I'll look into it later *mumbles*

Summary: Support Thread for Nodiaque Gameserver Dockers Application: SteamCMD DockerHub: https://hub.docker.com/r/nodiaque/steamcmd All dockers are easy to set up and are highly customizable, all dockers are tested with the standard configuration (port forwarding,...) if the are reachable and show up in the server list form the "outside". The default password for the gameservers if enabled is: Docker It there is a admin password the default password is: adminDocker Please read the discription of each docker and the variables that you install (some dockers need special variables to run). The Steam Username and Password is only needed in templates where the two fields are marked as required with the red * Special thanks to @ich777 that created the original docker and supported them for many years.

I had to chime in, this hit a nerve. I agree with 1812, they want everything for free. Even downloading movies. They will spend the money for hardware but software they want for free or next to nothing. Take a look at the users that rant the most. They are fairly new members. I doubt they have experienced a hard disk failure. This is where Unraid shines. If they complain about pricing, I doubt they use parity drive(s). I say let them leave and go to an alternative. I chose Unraid 14 years ago. Back then the biggest concern was LT’s risk management since Tom was a one man show. I wanted a system to be expandable, I wanted to use my various sized hard disks. I wanted the disk to spin down and I liked the idea that you could still access a disk by itself. It had to be an unconventional server, Unraid fit the bill. I went with the pro license at that time since it was the only one that covered my hard disk count. I just checked my email invoice from “Tom” and it was on sale for $109 ($10 discount) at that time. I spent more for a UPS. Soon I was maxed out and bought two 1TB drives, then larger drives and survived through the 2TB limit! I have experienced the introduction of Joe L.’s creations; cache_dirs, unMENU and preclear. We endured a number of LT re-locations. Unraid has come along way. Thanks Tom! Sorry, I haven’t been active on this forum lately, I been busy doing other things and frankly, Unraid just works. I have recovered through a number of hard disk failures, parity swaps, array up sizing and array down sizing. All painlessly. BTW, I still have the original flash drive. I didn’t cheap out on that. I’ve recommended and help setup Unraid using the Pro license to lots of people and not one complained about the cost. When my kids finally move out, we will happily pay for the “Lifetime” license no matter what the cost.

I've switched from Proxmox to unraid not that long ago and I've run into several problems/inconveniences that I managed to overcome and would like to share with everyone as it doesn't seem to be a common knowledge. The issues: 1. Windows VM (Win10 1703 +) high CPU usage when idle. Pretty self explanatory. Default settings the VMs are created with cause CPU to be busy with interrupts contstantly. 2. No KSM enabled by default = much less ram is free/available to other services when running 2+ windows VMs at the same time. This has caused OOM (out of memory) to kick in and kill one of the VMs over time when docker containers start using more RAM. This will probably be useful to people with limited RAM on their servers. I only have 32GB myself and this made a huge difference for me. 3. CPU pinning is the default in unRaid. This is great to isolate certain cores to only be used with a certain VM in some situation, when for example, unraid is also your main PC and you want some cores dedicated to the VM that you use day to day to play games or whatever else you do, but terrible for server workloads, especially if your server doesn't have that many cores and a lot of containers/services/VMs and there is no way to know which core will be loaded at any given time, while others are idling. Solutions: 1. I stumbled upon a thread on the forums that recommended enabling HPET timer which seemed to resolve the issue somewhat. The issue is that HPET is an unreliable clock source and often goes out of sync. The real solution is to enable Hyper-V Enlightenments which was introduced in qemu 3.0. It is already partially enabled in unRaid by default. This is what Proxmox uses by default for Windows VMs Go to settings for your Windows VM, and enable XML view in the upper right corner. We will need to edit 2 blocks: add the following to <hyperv mode='custom'> block <vpindex state='on'/> <synic state='on'/> <stimer state='on'/> Change migratable='on' to migratable='off' in the following line <cpu mode='host-passthrough' check='none' migratable='off'> add the following to <clock offset='localtime'> block <timer name='hypervclock' present='yes'/> In the end, it should look like this The bonus is that this reduces idle CPU usage even further compared to HPET, without all of the HPET drawbacks. Please note this ONLY applies to Windows VMs. Linux and *BSD already use a different paravirtualized clock source. 2, (do NOT do this if you are gaming on the VM or otherwise need a more predictable performance not affected by all the other containers/VMs running on the same machine - you are better off adding more ram to the host) unRaid does come with a kernel that has KSM (kernel samepage merging) enabled (thank you, unraid dev team). What it does is it looks for identical pages in memory for multiple VMs and replaces them with write-protected single page, thus saving (a lot) of RAM. The more similar VMs you have, the more ram you will save with almost no performance penalty. To enable KSM at runtime append the following line to /boot/config/go echo 1 > /sys/kernel/mm/ksm/run And remove the following block from all of the VMs configs that are subject to KSM: <memoryBacking> <nosharepages/> </memoryBacking> Let it run for an hour or 2, and then you can check if it's actually working (besides seeing more free ram) by cat /sys/kernel/mm/ksm/pages_shared The number should be greater than 0 if it's working. If it isn't working then either your VMs aren't similar enough, or your server hasn't reached the threshold of % used memory. The result (This is with Windows 11 and Windows Server 2022 VMs, 8GB ram each) 3. (do NOT do this if you are gaming on the VM or otherwise need a more predictable performance not affected by all the other containers/VMs running on the same machine) We want to disable CPU pinning completely and let the kernel deal with scheduling and distributing load between all the cores on the CPU. Why is CPU pinning not always good? Let's assume you did your best to distribute and pin cores to different VM. For simplicity let's assume we have a 2 core CPU and 4 VMs. We pin core #1 to VM1 and VM3, and core #2 to VM2 and VM4. Now it so happened that VM1 and VM3 started doing something CPU intensive at the same time and they have to share that core #1 between the two of them all while core #2 is doing completely nothing. By letting kernel schedule the load without pinning it will distribute the load between both cores. Let's go back into the VM settings and Delete the following block <cputune> . . . </cputune> Make sure that the line <vcpu placement='static'>MAX_CPU_NUMBER</vcpu> and <topology sockets='1' dies='1' cores='MAX_CPU_NUMBER' threads='1'/> still has the maximum number of cores your VM is allowed to use (obviously MAX_CPU_NUMBER is a number of cores you want to limit this particular VM to, so replace it with a number) NOTE: if you switch back from XML view to the basic view and change some setting (could be completely unreleated) and save, unraid may overwrite some of these settings. Particularly I noticed that it likes to overwrite max cores assigned to VM to just a single core. You will just need to change back to XML view and change "vcpu placement" and "topology" again Bonus: - Make sure you are only using VirtIO devices for storage and network - Make sure CPU is in passthrough mode - Disable drive encryption (BitLocker) which is enabled by default with latest Win10 an 11 ISOs. - For "network model" pick "virtio" for better throughput ("virtio-net" is the default) - If you have Realtek 8125[A || B] network adapter and having issues with throughput, have a look at @hkall comment below. OR There is now a native r8125 driver available in under Apps within unraid.

There is not currently, as this is my personal preview build, and I still need to sanitize the code. If enough people are interested, and when I have time, I'll put together the release notes and post it as an official release.

New Macinabox almost complete. Should be out soon. Hoping for the end of next week or shortly there after Will have a few new features such as Ventura and Sonoma support Also the companion User Scripts will no longer be necessary, the container will do everything itself. Also I plan to add checks so the container can see that your cpu has the correct features to be able to run macOS ie checking for AVX2 etc And a few other new things

Found the solution on reddit. Due to the recent change in the authentication process, using your email and password for the manual connection method will no longer work. You will need to use the service credentials instead. You can find your service credentials by following these steps: Please log in to your Nord Account by following this link: https://my.nordaccount.com/dashboard/nordvpn/ Click on the NordVPN tab on the left panel which is under the Services tab. Scroll down and locate the Manual Setup tab, then click on Set up NordVPN manually: Verify your email by entering the one-time code you will receive in your registered email inbox. If you are unable to find the email, please make sure to also check your spam/junk folder. Copy your service credentials by using the buttons on the right.

This thread is meant to replace the now outdated old one about recommended controllers, these are some controllers known to be generally reliable with Unraid: Note: RAID controllers are not recommended for Unraid, this includes all LSI MegaRAID models, doesn't mean they cannot be used but there could be various issues because of that, like no SMART info and/or temps being displayed, disks not being recognized by Unraid if the controller is replaced with a different model, and in some cases the partitions can become invalid, requiring rebuilding all the disks. 2 ports: Asmedia ASM1061/62 (PCIe 2.0 x1) or JMicron JMB582 (PCIe 3.0 x1) 4 ports: Asmedia ASM1064 (PCIe 3.0 x1) or ASM1164 (PCIe 3.0 x4 physical, x2 electrical, though I've also seen some models using just x1) 5 ports: JMicron JMB585 (PCIe 3.0 x4 - x2 electrically) These JMB controllers are available in various different SATA/M.2 configurations, just some examples: 6 ports: Asmedia ASM1166 (PCIe 3.0 x4 physical, x2 electrical) * * There have been some reports that some of these need a firmware update for stability and/or PCIe ASPM support, see here for instructions. These exist with both x4 (x2 electrical) and x1 PCIe interface, for some use cases the PCIe x1 may be a good option, i.e., if you don't have larger slots available, though bandwidth will be limited: 8 ports: any LSI with a SAS2008/2308/3008/3408/3808 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, 9400-8i, 9500-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed (most of these require a x8 or x16 slot, older models like the 9201-8i and 9211-8i are PCIe 2.0, newer models like the 9207-8i, 9300-8i and newer are PCIe 3.0) For these and when not using a backplane you need SAS to SATA breakout cables, SFF-8087 to SATA for SAS2 models: SFF-8643 to SATA for SAS3 models: Keep in mind that they need to be forward breakout cables (reverse breakout look the same but won't work, as the name implies they work for the reverse, SATA goes on the board/HBA and the miniSAS on a backplane), sometimes they are also called Mini SAS (SFF-8xxx Host) to 4X SATA (Target), this is the same as forward breakout. If more ports are needed you can use multiple controllers, controllers with more ports (there are 16 and 24 port LSI HBAs, like the 9201-16i, 9305-16i, 9305-24i, etc) or use one LSI HBA connected to a SAS expander, like the Intel RES2SV240 or HP SAS expander. P.S. Avoid SATA port multipliers with Unraid, also avoid any Marvell controller. For some performance numbers on most of these see below:

This release has two very important fixes around security and data integrity, along with other improvements and bug fixes. All users are encouraged to read the release notes and upgrade. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.6, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (this release takes another stab at preventing issues related to Docker not stopping properly) If you have the latest Connect plugin installed, or Unraid 6.12.7-rc2: Open the dropdown in the top-right of the Unraid webgui and click Check for Update. More details in this blog post If you don't have the Connect plugin installed Go to Tools -> Update OS and switch to the "Stable" branch if needed. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip.

A small point: it's not a subscription fee in this sense: with a subscription if you don't renew then the service ends. By contrast if you do not extend your Starter or Unleashed key your server still runs as before and you still have complete access to your data, etc.

Da in der letzten Zeit vermehrt Fragen zu dem Thema aufkamen, will ich mich mal an einer (deutschsprachigen) Anleitung zu diesem Thema versuchen. Grundsätzliches Wer Docker einsetzt wird früher oder später schon über IPVLAN und MACVLAN gestolpert sein. Das sind zwei Arten um aus dem einen physischen Netzwerkanschluss den euer UNRAID Server in aller Regel besitzt, mehrere virtuelle Schnittstellen (ggfs. für jeden Container eine eigene) zu erzeugen. Für eine der beiden Varianten müsst ihr euch entscheiden. Bei MACVLAN wird die MAC-Adresse für jede Schnittstelle neu generiert, zu jedem Docker gibt es also auch eine MAC-Adresse. Bei IPVLAN ist das nicht der Fall Auch nochmal nachzulesen in den Release Notes zu 6.12.4: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces Potenzielle Probleme Bei MACVLAN ist ein Fehler vorhanden der zu sog. Call Traces führt und im schlimmsten Fall den Server zum Absturz bringt (dieser Fehler liegt bei Docker und hat per se nichts mit UNRAID zu tun!) Bei IPVLAN wiederum werden insbesondere Fritzboxen und wohl zum Teil auch Unify Geräte etwas zickig - da sich verschiedenste Docker dieselbe MAC-Adresse teilen und das mögen Fritzboxen/Unify Geräte nicht. Sie "verwechseln" dann die Docker => man landet womöglich beim falschen Docker oder eine Verbindung ist nicht mehr möglich Variante 1: Keine Fritzbox/Unify im Haus bzw. der Router/Switch hat kein Problem mit IPVLAN Go for IPVLAN Variante 2: Fritzbox/Unify im Haus Damit MACVLAN richtig funktioniert, müssen ein paar Einstellungen vorgenommen werden: Vorher VM Manager + Docker auf disabled! Settings->Network Settings Enable bridging: no Enable bonding: no (nicht zwingend erforderlich, aber wenn man sowieso nur einen Netzwerk Port im Rechner hat, ist das einfach unnütz) Settings->Docker Docker custom network type: macvlan Docker custom network type: Enabled Host access to custom networks: Enabled Jetzt VM Manager und Docker wieder auf enabled Falls bereits Docker angelegt waren, müssen diese eventuell noch einmal bearbeitet werden, damit sie im custom netowrk eth0 landen, dürfte ggfs vorher bond0 gewesen sein

I have now adapted the plugin so that users are able to install it on Unraid 6.12.4 without any workarounds and to make sure that packages for upcoming Unraid versions are available. The new plugin also is a bit more verbose, made a few changes under the hood which makes installation a bit more easy and reliable -> this means you don't need to have a Userscript anymore that runs on startup. The plugin is now also part of the Plugin-Update-Helper, this will basically ensure when you update Unraid to a newer version that it will download the new plugin package version even before you reboot to the new Unraid version (keep an eye on your Unraid Notifications since the Plugin-Update-Helper will inform you there when the download is finished or failed). You can install the new plugin with this link (currently it's not on the CA App): https://raw.githubusercontent.com/ich777/unraid-i915-sriov/master/i915-sriov.plg Thanks to @domrockt for helping me test the plugin if everything is working properly since I have no compatible hardware on hand! (This plugin requires Unraid 6.12.4+)

The 6.12.1 release includes a set of bug fixes and security updates. All users are encouraged to upgrade. Please refer also to the 6.12.0 Announcement post. As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Bugs: If you discover a bug or other issue in this release, please open a Stable Releases Bug Report and please attach your diagnostics.

Settings, display settings - color codes in hex

Here is the support thread for the Realtek R8125, R8168\R8111 and R8152\6 drivers plugins. If you have any questions, please ask in this thread. Thanks to @ich777, we can bring this plugin to the community. It is fully open source and free. The repo is: https://github.com/jinlife/unraid-r8125-r8152-driver Precaution: Please be carefull about these drivers. You may lose the network if the driver is wrong. If you have no idea what type of chip your network card is, please do NOT install this plugin. There are supported chips listed in the description of the plugin. If you have no issues with Unraid built-in drivers, please ignore the nofitication from Fix Common Problems and keep using built-in drivers. Instructions: Navigate to Tools -> System in the Unraid. If you see: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller Then you will probably benefit from the "RTL8125" plugin Same step goes to R8156 and R8168\R8111 plugins. Scenario: It is the driver for PCI 2.5G Realtek RTL8125 chip, PCI 1G Realtek RTL8168\8111 and for USB 2.5G Realtek RTL8152\6 chip network card. If you have one of those network card and it is not working properly and is not full speed, you can try this plugin. If you think the driver isn't good with your hardware, uninstallation can clean it completely. Note: Please only install the plugin for RTL8125, R8168\R8111 and RTL8152\6 chips. Especially, if you have both RTL8168\8111 and RTL8125 network card, please install RTL8168\8111 and RTL8125 plugin together. Please feel free to share your comments here. Please search key word realtek in CA App and you can find them. Thanks to @Squid Note: 1. The R8125 or R8168 plugin will blacklist R8169 automatically, and uninstall them all will remove the blacklist. 2. The R8152\6 plugin will blacklist cdc_ncm automatically, and uninstall it will remove the blacklist. Original source code: R8125 v9.012.04 and R8168 v8.052.01 https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software R8152(6) v2.17.1 https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-usb-3-0-software

Powertop [Support auf Deutsch] Powertop is an Intel tool (yes, works for AMD, too) to check power consumption states of sata, pcie, usb, etc devices. You can download powertop as follows, then restart your server and it will be automatically installed: mkdir /boot/extra cd /boot/extra wget https://github.com/mgutt/unraid-packages/raw/main/6.11.0/powertop-2.15-x86_64-1.txz Then open your terminal and execute: powertop Now press "TAB" until you reach "Idle Stats" and check your CPU Pkg (HW). Depending of the brand and model of your CPU you can reach different C-States. If your system isn't optimized, you will see this: If you press "TAB" you will see additional information about standby states of different hardware components of your system. In the tab "Tunables" you will see multiple devices which have the state "Bad", which means powertop found devices which do not allow standby/sleep states: Now you can execute the following command to optimize this: WARNING Many SATA controllers (JMB xxx or ASM xxxx) do not support link power management and your disks loose connection after reaching spindown! Read further before executing --auto-tune! powertop --auto-tune &>/dev/null By that all compents will return "Good": Now, your server should reach better C-States. Package C-States This table shows the dependency between CPU Core and CPU Package C-States: Several things are important to reach Package (Pkg) C-States C3, C7, C9 or even C10: Accurate power measurement - do some research how accurate your power meter is (UPS integrated power meters are usually bad) - close your Unraid WebGUI and wait 1 minute! (this closes many background jobs, which cost your energy, use your PC's terminal and "ssh root@tower" to monitor your C-States with powertop) - don't use Unraid in GUI mode (you should avoid this mode, if you want low power consumption) Powertop shows only C1, C2 and C3 Pgk-States This happens if powertop does not recognize your CPU (happens for most AMD CPUs and recent Intel CPUs). Your CPU could still reach C9 or even C10, but powertop is not able to obtain this and shows only C3. BIOS - only Gigabyte 8th or 9th Intel: enable CEC2019 - enable ASPM (Active-State Power Management) in the PCI settings - enable all C-States like C7/C9/C10 in the CPU settings ("auto" usually means "disabled", so select "enable") - disable Audio - disable RGB LED controller - disable Turbo in the CPU settings PCIe cards Some PCIe cards prevent states other than C0 or C3 (Intel). As an example my Qnap Aquantia 10G card allowed only C3 while all my Intel 10G cards allowed C7. Without any installed card I'm able to reach C10. iGPU Install the iGPU driver plugin through unRAID Apps if your CPU has an iGPU hpet Set hpet=disable as a Kernel setting if you have an 8th, 9th or 10th Intel CPU as there is a bug which can cause crashes (shouldn't be necessary anymore since unRAID 6.10) CPU governor Use the tips & tweaks Plugin to set the CPU governor to "powersave" or use the below commands in the Go file. 10G networking SFP+ DAC consumes less power than SFP+ SR/LR and both less than 10G RJ45. Depending on your internet connection the most efficient scenario is not to use a 10G switch. Instead directly connect your client with your server and use a second 1G cable to connect with your internet router. By that your 10G controller/card goes to sleep while your client is powered off. In comparison an active connection to a 10G switch never allows sleep states. MTU Surprisingly a user was not able to reach any C-State other than C1E after setting the MTU to 9000. SATA Controller Some mainboards or pcie cards provide SATA ports through an additional SATA controller. Sadly some of the most popular and usually well supported JMB xxx and ASM xxxx controllers have an incompatibility to "powertop --auto-tune" because it sets all SATA ports to "med_power_with_dipm". To bypass this problem, you should not use "powertop --auto-tune". Instead read the "Commands" paragraph to set the commands manually. Then you can remove the line with the "med_power_with_dipm" setting or you can set each hostX individually. Example: # Enable SATA link power management (this skips SATA host3 and host4) echo med_power_with_dipm | tee /sys/class/scsi_host/host1/link_power_management_policy echo med_power_with_dipm | tee /sys/class/scsi_host/host2/link_power_management_policy echo med_power_with_dipm | tee /sys/class/scsi_host/host5/link_power_management_policy echo med_power_with_dipm | tee /sys/class/scsi_host/host6/link_power_management_policy If you are using the ASM1166 you could even try to update the firmware. NVMe A user found out that a specific NVMe SSD allowed only C2, while with a Samsung Evo Plus the system reached C10. Power supply An unnecessary high-power and/or inefficient power supply can raise the power consumption by 5 to 15W. Choose wisely: - as low power (watt) as possible - as efficient as possible (like Titanium grade) - avoid dual power supply setups (server grade hardware is not build for efficiency) If you plan to build a setup with extremely low power consumption, consider these power supplies: - PicoPSU (up to 200 watts, but is limited to ~4 SSDs as it has low 5V output) - Corsair RM550x (2021) (this looses only 1 watt more than a PicoPSU at 10W to 20W load!) - BeQuiet Pure Power 11 FM 550W (similar to the Corsair, but 2 watts more than a PicoPSU, but cheaper than the Corsair) Notes: - As of writing this post all other power supplies are much more inefficient. So don't think for example a Corsair SF450 is more efficient than the Corsair RM550x (2021) although the former is Platinum grade . It's not. I have both and the Platinum looses 4W more at 10W load. The reason is that some of the most recent power supplies include a new technology to reach the future ATX12VO standard, which has the requirement of being extremely efficient at low loads. For example Seasonic told me in 06/2022 that power supplies for ATX12VO are still in development. - An HDD can consume up to 30W if you switch on your server, but in this state the other server components do not reach their maximum load. So summarize wisely to obtain the correct power supply size. - Do not buy the Corsair / BeQuiet if you don't reach a power consumption under 30W: Above this, usual Platinum / Titanium power supplies are more efficient. Commands Instead of using "powertop --auto-tune" you could add the following power-saving commands to your /boot/config/go file (stop your array and execute them through your terminal to test them first) with the Config File Editor Plugin: # ------------------------------------------------- # Set power-efficient CPU governor # ------------------------------------------------- /etc/rc.d/rc.cpufreq powersave # ------------------------------------------------- # Disable CPU Turbo # ------------------------------------------------- [[ -f /sys/devices/system/cpu/intel_pstate/no_turbo ]] && echo "1" > /sys/devices/system/cpu/intel_pstate/no_turbo [[ -f /sys/devices/system/cpu/cpufreq/boost ]] && echo "0" > /sys/devices/system/cpu/cpufreq/boost # ------------------------------------------------- # Enable power-efficient ethernet # ------------------------------------------------- # enable IEEE 802.3az (Energy Efficient Ethernet): Could be incompatible to LACP bonds! for i in /sys/class/net/eth?; do dev=$(basename $i); [[ $(echo $(ethtool --show-eee $dev 2> /dev/null) | grep -c "Supported EEE link modes: 1") -eq 1 ]] && ethtool --set-eee $dev eee on; done # Disable wake on lan for i in /sys/class/net/eth?; do ethtool -s $(basename $i) wol d; done # ------------------------------------------------- # powertop tweaks # ------------------------------------------------- # Enable SATA link power management echo med_power_with_dipm | tee /sys/class/scsi_host/host*/link_power_management_policy # Runtime PM for I2C Adapter (i915 gmbus dpb) echo auto | tee /sys/bus/i2c/devices/i2c-*/device/power/control # Autosuspend for USB device echo auto | tee /sys/bus/usb/devices/*/power/control # Runtime PM for disk echo auto | tee /sys/block/sd*/device/power/control # Runtime PM for PCI devices echo auto | tee /sys/bus/pci/devices/????:??:??.?/power/control # Runtime PM for ATA devices echo auto | tee /sys/bus/pci/devices/????:??:??.?/ata*/power/control Note: EEE can cause problems with 2.5G Intel Ethernet. Config File Editor: Debugging Here are some helpful terminal commands. Spin down all disks (Unraid only) for dev in /dev/sd?; do /usr/local/sbin/emcmd cmdSpindown="$(grep -zoP "(?<=name=\")[a-z0-9]+(?=\"\ndevice=\"${dev: -3})" /var/local/emhttp/disks.ini | tr -d '\0')"; done Obtain ASPM status of all devices: lspci -vv | awk '/ASPM/{print $0}' RS= | grep --color -P '(^[a-z0-9:.]+|ASPM )' Watch CPU frequency: watch -n3 "cpufreq-info | grep 'current CPU'"

Overview: Support for Docker image unraid-api-re in the bokker/unraid-api-re repo (fork of the original). Docker Hub: https://hub.docker.com/repository/docker/bokker/unraidapi-re Github/ Docs: https://github.com/BoKKeR/UnraidAPI-RE If you feel like supporting my work: just say thanks! This is a fork of https://github.com/ElectricBrainUK/UnraidAPI I managed to fork and make the original project work on github ci. I will try to keep this project alive with newer unraid releases, its an exact dropin for the original https://github.com/ElectricBrainUK/UnraidAPI just replace the image electricbrainuk/unraidapi with bokker/unraidapi-re I will create a tag for each minor release as in: bokker/unraidapi-re:6.12 which will cover 6.12.0 <-> 6.12.2 I mostly test the functions related to reporting status, if you have special needs as removing/editing containers, vms, switch gpus please tell if the container malfunctions for you. I cant stress enough that this is not a proper solution, this container scrapes the unraid UI. Every minor update will possibly break functionality. I would love to setup automated tests, but to be able to do that I need a way to spin up the unraid os (or frontend) in a test environment. Happy to hear what ideas people can come up with. Until then please call up your local Unraid congressman and tell them how much you care about a publicly available API.

This is a bug fix release, resolving a nice collection of problems reported by the community, details below. All users are encouraged to read the release notes and upgrade. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.6, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully If you have Unraid 6.12.8 or Unraid Connect installed: Open the dropdown in the top-right of the Unraid webgui and click Check for Update. More details in this blog post If you are on an earlier version: Go to Tools -> Update OS and switch to the "Stable" branch if needed. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip.

It's any publicly published version of Unraid OS, including "major" version updates, eg, from v6 to v7. We're also not going to play any games like coming up with "NewUnraid OS" where all of a sudden your key won't work or we start charging an extra fee to keep using.

Yes.

✭ unBALANCE is now unbalanced !! ✭ NOTE: To install it, look for "unbalanced" in Community Apps (the old unbalance plugin will be deprecated by Squid) i had the opportunity to completely rewrite the user interface for the plugin, it's now a lot more polished, a lot more usable and a lot more beautiful the main features are: - a new, more modern and more polished user interface - support for multiple cache pools (multi-device pools too) - dark mode support (dark is preferred, light theme may need some future tweaking) - more information about the planning process is now displayed - transfer speed is now calculated as an average of the last 60 samples (depending on the refresh rate you set) - logs are written to /var/log to reduce stress on the flash drive - other minor improvements, take a look for yourself ! the core is still the same: the code that runs the rsync commands changed just to accommodate connectivity with the new ui for some additional context, i wrote a post about unbalanced on my blog, you can read it here. i still enjoy Unraid the same way i did when i started using it (and use it daily), it brings me pleasure to be able to modernize this plugin hope you enjoy the new version as much as i do ! P.S.: since this is basically a 1.0 release (in terms of the user interface), there might some bugs here and there, if you find any, please report them here or on github P.S 2: i changed the name to unbalanced mostly to avoid issue with version naming (my old scheme was vYYYY.MM.DD, instead of the standard YYYY.MM.DD, and there wasn't a way to change it for the old plugin) P.S. 3: i haven't added support for unassigned devices at the moment, mostly because i don't have any and i need better context on how the unassigned devices and partitions work

The Unraid 6.12.5 release includes a mitigation for a ZFS data corruption issue, along with other bug fixes and security updates. All users are encouraged to read the release notes and upgrade. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.4, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (issues related to Docker not stopping should be resolved in this release) Go to Tools -> Update OS. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip. Release Notes

Can I use a cache, log, special, spare and/or dedup vdev with my zfs pool? At this time (Unraid v6.12) they cannot be added to a pool using the GUI, but you can add them manually and have Unraid import the pool, a few notes: currently zfs must be on partition #1, for better future compatibility (though not guaranteed) recommend partitioning the devices first with UD. main pool should be created with Unraid, then add the extra vdev(s) using the CLI and re-import the pool available vdev types and what they do are beyond the scope of this entry, you can for example see here for more information. please note that since the GUI doesn't not support this it might give unpredictable results if you then try to replace one of pool devices, so if you plan to use this recommend for now doing any needed device replacement with the CLI. How to: first create the main pool using Unraid in this example I've created a 4 device raidz pool start array, format the pool if it's a new one, and with the array running partition then add the extra vdev(s) using the command line to partition the devices with UD you need to format them, but there's no need to use zfs, I usually format with xfs since it's faster, just format the device and leave it unmounted: to add a vdev to the pool use the CLI (need to use -f to overwrite the existing filesystem, always double check that you are specifying the correct devices, also note the 1 in the end for the partition), a few examples: - add a 2-way mirror special vdev zpool add tank -f special mirror /dev/sdr1 /dev/sds1 - add a 2-way mirror log zpool add tank -f log mirror /dev/sdt1 /dev/sdu1 - add a striped cache vdev zpool add tank -f cache /dev/sdv1 /dev/sdw1 - add a 2-way mirror dedup vdev zpool add tank -f dedup mirror /dev/sdx1 /dev/sdy1 - add a couple of spares zpool add tank -f spare /dev/sdb1 /dev/sde1 when all the vdev(s) are added to the pool stop the array, now you need to re-import the pool unassign all pool devices start array (check the "Yes I want to do this" box) stop array re-assign all pool devices, including the new vdev(s), assign all devices sequentially in the same order as zpool status shows, and don't leave empty slots in the middle of the assigned devices. start array existing pool will be imported with the new vdev(s):

Ok, finally solved it. In case anyone runs into this, `umount -l /dev/loop2` worked

I appreciate the response regarding the licensing situation. The other concern that I would like some explanation for is the privacy issue related to the new update mechanism. I was finally able to coax some debug logs out of my browser, and I discovered that there's a lot of information being sent with every click of the "Update OS" button: apiVersion caseModel connectPluginVersion description expireTime flashProduct flashVendor guid inIframe keyfile lanIp name osVersion osVersionBranch registered regGuid regExp regTy regUpdatesExpired site state wanFQDN Some of these make sense as part of a license check (guid, keyfile, flash information). Some, though, seem to be quite extraneous: caseModel (does Limetech really need what kind of case my server is in?), LAN IP, hostname, description... none of these are needed to validate a license. The privacy policy (https://unraid.net/policies) says nothing about collecting this kind of information: What is the primary purpose for collecting all of this information? Is the information used for other purposes? If so, what? Is this information stored? If so: Is it stored in identifiable form? How long is it retained?

I'd recommend to install the Docker Patch 6.12.8 from Apps due to docker now treating as an error a common mistake that users may have made (leaving unused paths empty on the template) when installing from Apps. It's not a bug in the OS, but now docker enforcing their specification on the run command

Hello Guys and Gals, there was an exciting announcement from the OpenZFS team: They have announced that this pull request: https://github.com/openzfs/zfs/pull/12225 Will finally be implemented. The pull request has been around for over two years. iXsystems is sponsoring the implementation/further development. Why this is exciting: This feature will allow single storage discs to be added to an existing zfs pool. With the current state of zfs, you'd have to add an additional pool which typically means that you'd have to double the number of discs. The expansion feature will come in handy for smaller pools and especially for many of us who like unraid for it's flexibility but still want the most reliable filesystem. What do you guys think? Anyone else as excited as me? You can follow the status here: https://github.com/openzfs/zfs/pull/15022

I just came across an issue after restarting my server where mergefs wasn't installing. After some investigation it seems the latest build from mergerfs does not work properly and I solved the problem by adding the previous (and currently listed as latest) version to the tag (line 184). I'm not sure why the latest build is looking for 2.37 but 2.36 is listed by trapexit as latest on his github. I hope this helps someone escape some frustration and that the problem resolves itself soon..

I’m getting a little frustrated with the company and community conversation regarding the macvlan issues. I see so many posts where users are taken through the same set of questions as others, post your logs, switch to ipvlan (when things don’t work for the user as they did with macvlan), why do you need this, try that etc etc. This seems like a waste of time and or a diversionary tactic as either the outcome ends up being the same or the answers from those providing advice imply they know the issue. Therefore why keep repeating. I run docker containers, all through a dedicated interface seperate to the main unraid interface, many with their own ip address on various vlans on my network. I have all unifi networking equipment except pfsense as my edge device. Host access to guest networks enabled. I get hit by kernel panics very regularly. Switching to ipvlan does not deliver the same outcome as macvlan in my case so is therefore not the answer. I’d really like a comprehensive explanation as to what can be expected to be achieved and what can not with either macvlan and or ipvlan. An honest warts and all answer would be nice as I can see my use case (which is my own) is not unique. My ask: Create a honest comprehensive post containing the issue and current explanation, what can be expected to be achieved from each option and don’t leave anything you know (ie even that which relates to why you might consider the “edge” use cases) out, even add what you “think” might be happening or the answer and then make the post a sticky. When a support request gets asked that fits the issue, link to it. Let people discuss it in that thread. Provide updates on progress of a fix or accept limitations of the product. Please.

Hey Everyone! We're very excited to announce **Unraid Connect**, the successor to My Servers! If you want to skip reading, update your plugin, then view the dashboard at https://connect.myunraid.net To update your plugin, head over to the Plugins tab and check for updates - Unraid Connect (previously My Servers) version 2023.04.25.0813 is now available! Unraid Connect - My Servers is now Unraid Connect - enjoy a dedicated website with an entirely new design, far more server insights, and tons of new features. Visit https://connect.myunraid.net to get started. - Dynamic Remote access let's you enable and disable WAN access to your server whenever you need to use it from a remote location. - UPNP support for your server dashboard - Manage your server from within Connect - when equipped with a myunraid.net domain, you can view your server inside of Unraid Connect. The dashboard links directly to relevant pages on your server to make navigation easier. This version resolves: - Issue where API would repeatedly disconnect - Issue where API would get stuck in an endless disconnection cycle and never maintain connection - Issue where API would not reconnect until unraid-api restart was run - Upgrade all dependencies to the latest.

Running `unraid-api restart` fixed it for me.

Appdata.Backup Support Thread This is the support thread for appdata.backup (formerly known as ca.backup2). This plugin primary takes care of your appdata backup! It allows you to configure backup settings for each of your docker containers. Flash and VM meta backup is integrated as well! If you encounter any issues, post it here with the debug log file attached! For your beta feedback, please post here instead! Why do I need to reinstall the plugin (again)? After my adoption of the ca.backup2 plugin (which needed a manual reinstall from every user the 1st time), I decided to make a complete overhaul of the whole plugin. The main reason was the PHP8 incompatibility. This new plugin is the result. Because it is actually a seperate new plugin, you have to switch to it manually again. This will be the last time Hints The plugin send me here to check for some Plex exclusions. Yes, thats right. You dont need to save Plex cache (and some other) directories. But its up to you to exclude them or not. Currently you are advised to set the following exclusions for plex: Each following paths need to be prefixed with your correct appdata path! Library/Application Support/Plex Media Server/Cache Library/Application Support/Plex Media Server/Media Library/Application Support/Plex Media Server/Metadata The plugin sent me here for help with the grouping function The grouping function allows you to group cotainers. The backup process stops all those containers, backup them and starts them back up before going to the next single container. This works for the mode "Stop, backup, start for each container" only. If the plugin reaches a group, it stops all containers in it, backup them and start them back up. The backup method "Stop all, backup, start all" has no effect here because every single container will be stopped nefore starting backup. The plugin sent me here to get help for the "Mapping used in multiple containers!" message The plugin can detect if you use the same mapping within more containers. That is completely okay but you should know that this can lead to "verification failed: contents differ" messages if you use stop/backup/start method and another container modifies the data during backup of the container that uses that share. The best way to get rid of that message is to add that share to the exclusion in all but the main container. One could also change the backup type but it does not prevent backing that share up multiple times!

1. The "core" of Unraid (the main array) isn't open source, and there aren't any "equals" to it in the OSS world (there are things that are similar, but nothing that has the whole feature set to my knowledge). 2. Even if "similar" is good enough, configuring an OSS-based system is still more complicated to deploy/configure/monitor/maintain. 3. Donations "just because people like the product as it is" sounds nice, but in practice very few people actually do that. (Simple example, because I know the numbers: I created and maintain the Tailscale plugin for Unraid. There are around 6,000 active installs right now. Of those 6,000 installs, I've had 3 people send anything via the donation button - 0.05%. I'm not complaining, just pointing out how things work in reality.)

I've been playing with the code behind this plugin and have made a couple of tweaks. I'd be interested on peoples thoughts and suggestions. The first allows you to specify any .env file. This allows use of a central env for all your compose files. https://github.com/dcflachs/compose_plugin/pull/24 Update the built in unRaid image versions so the GUI correctly shows updates for containers. I'm still testing this before doing a PR. https://github.com/dcflachs/compose_plugin/commit/4297b46fdfeaa077f405a328ee074606363d5f9b I've tweaked how the network info is shown in the GUI. It now shows all network names with the associated IP. This is in the dynamix.docker.manager plugin which is a core part of unRaid's GUI - so not technically part of this plugin. You need to set the label net.unraid.docker.managed: 'composeman' for this to work (this is usually done with the overide yaml). https://github.com/unraid/webgui/issues/1569 Here's a screenshot of it: I've contemplated making the network name bold but I don't think it's needed. At present, these all need to be implemented by overwriting the files in /usr/local/emhttp/plugins/. Look at the commits to see what files need to be edited.