bonienl

NIC's are chosen by their sequence definition in the bonded interface, which is normally eth0, eth1, eth2, etc ... Yes, the general advice is use active-backup mode when interfaces differ in speed (focus is on availability), and use a balanced mode when all interfaces are equal (focus is on performance) On the Dashboard you can see which interfaces are up or down

I understand you don't see why, but you are not the developer and aware of the internals The array and pools can not be easily separated. First and foremost the licensing scheme is based on the number of attached devices when you start the array, this includes both array and pool devices. Unless the licensing scheme is changed, it is not possible to start pools only. Secondly, all internal handling of devices need a complete rework when array and pools can start independently. This is a major change and should not be taken lightly.

When you use Unraid as a syslog server, it will keep a separate log file for each different device (= IP address) it detects. Under Tools > Syslog server the individual logs can be viewed.

There are regular file reads from the USB drive, but linux caches file content in RAM, which means the actual file on the USB drive is hardly accessed. The USB drive must be present at all times though.

Start with clearing the cache of your browser and restarting your browser fresh.

The GUI reads the system uptime from the system itself. It is more likely something happened to your system when seeing such a short uptime.

@SpencerJ woke up this morning and mumbled ... bg==

Please remove the IPv6 DHCP pool, this is conflicting and not needed. Docker IPv6 gets the IP assignment using SLAAC.

yes icons are locally cached.

Maximum size is the largest memory size your motherboard can support. Usable size is what is actually available to the system.

The way to make this work properly is to define different custom networks. A custom network is by design a isolated environment and only members in this custom network can talk to each other. Also by design docker containers in a custom network can not communicate with the host (Unraid server), though there is a setting to bypass this restriction (not recommended) Custom networks are either assigned to different physical ethernet ports or different VLANs (virtual networks). This ensures traffic between custom networks is never shared, but completely segregated.

The message with the -m option is only available in email notifications. The message can be indeed the content of a log file.

The GUI relies on unique codes for icons, which isn’t the case in font awesome 5, hence we still use version 4.7, an additional requirement to take into account. Btw, there is a special icon created for CA and used in the GUI

Font awesome is widely used in the GUI (and plugins) and replacing it, is not really an option. The GUI does use a specific Unraid font with additional icons, which was created and used by permission from user @Mex Perhaps special requests can be made, but ultimately @limetech decides what can and can not be included.

The conf file should reside on your usb drive. Have tried to do a file system repair of the usb drive? Take the drive out (after shutting down) and run a repair on a windows machine.

The dynamix file integrity plugin does not touch any file itself, it purely operates on extended attributes. The file modification time is never altered by the plugin.

I can only speak for myself, I use the Dynamix File Integrity plugin to monitor bitrot. Never had any occurrence in the last 6 years, besides some false positives due to file processing. Though I keep monitoring, bitrot isn't a real issue for me.

The console access in GUI mode is limited to US keyboard. For VMs you can select a different keyboard in the VM settings, did you try this?

It looks like the container can not be found on dockerhub, which explains the unavalibility status. Have you tried to completely uninstall and then re-install the container?

Switch to advanced view and use “force update” to update a container. Post the output in case it isn’t working.

Can you open a terminal window and show the output of (assuming you want to activate tunnel 0) wg-quick up wg0

The pool bug has indeed internal attention, doesn’t hurt to bump occasionally…

I guess once in a while you have to give your request a bump, to help us remind

I made a change to view cpu details and graph separately. It allow to view the graph only, or cpu details only or both.