bonienl

As long as the bad disk is not replaced, it will be emulated. You can keep on using it, but no further redundancy is available.

Shutdown Swap the bad disk for a new disk Start the system Assign the new disk as replacement Start array and let system do the rebuild

In Docker settings you can specify which interfaces can be used together with docker. In the container configuration you can select the specific interface you want to use. Make sure these interfaces do not have an IP address assigned for Unraid, this ensures Unraid will not use them.

References are never automatically updated when the user changes the pool name. It was a design decision, but can lead to confusion. Perhaps need to add a warning to manually update settings when this happens.

This is added in Unraid version 6.10

Be aware that the actual reference may be different, and the GUI in this case shows the first possible choice. You can make a change in the settings (and revert) to force a update and ensure the correct reference is used.

Your Unraid server is correctly configured, it looks something external, perhaps a switch causing a loop. You could try disconnecting (unused) cables to localize the source of the problem.

Try a direct connection between server and Macbook, thus eliminating the switch and see if that makes a difference. To make this work you would need to configure fixed IP addresses on both ends.

It could be a race condition, the bond interface is not ready yet while the bridge interface is. Since you have a single interface eth0 assigned, you can disable bonding in the network configuration, it has no added value.

There is nothing wrong with the webGUI. When using bridge mode you need to create a port mapping for each port that is needed, including the port to access the webUI.

First make sure your 10G interface is set as eth0, see Interface rules. You need to reboot when interface assignments are changed, after that you can disable bonding and start using eth0 as a single interface.

Don’t use Pi-hole as DNS for Unraid, it gives conflicts and interferes with the operation of Unraid. Use a public DNS server or your router (if it can act as DNS forwarder) instead.

eth0 is used to access the GUI. If you don’t need the onboard NIC and have disabled it, you need tonupdate the network interface rules to make one of the other interfaces eth0. Actually you need to define the new eth0 and eth1 interfaces. Delete the file network.cfg to start with a default config and make changes afterwards.

To make this work, you need to configure bonding for eth0 as well, and have eth0 as the only member.

The br0 interface is fully transparent. Check if there is a firewall function in Debian which may block certain traffic.

What kind of VM? All my VMs have an IPv6 address.

Just a general note about this PR on github. It requires some adaption when it comes to storing settings. I guess it can be looked into after the release of 6.10.

The GUI indeed is unaware of whether a disk is precleared or not. The standard procedure is to clear a new disk added to the array. The lower level function doing the clearing would recognize the signature set by preclear and sees clearing is already done and skip it. If you want to avoid confusion, then simply let Unraid do all the work, it knows exactly what is required.

Diagnostics creates a temporary file in memory before zipping it to the flash device. You are running out of memory space, and diagnostics is not able to properly create the temporary file. You need to check if you have any (docker) application writing to a destination which isn't on disk but in memory instead (e.g. a wrongly defined path mapping).

rc3c is an internal test release, not meant for general purpose. Have a little patience, rc3 is around the corner…

Only user 'root' can be used to access the server. All other users are for share access.

Mover will never overwrite existing files. You need to determine which files to keep and which files to delete, and move as needed.

I updated all the "foreign" translation repos to the latest English (en_US) source files.

Yes, it is was dependent on network and management configuration. My test server worked fine, but my main server exhibited the issue. Your latest CA update solves the issue.

Syslog supports subfolders, but you need to edit the configuration file to make it work.