bonienl

Sorry for the late reply, but I have some personal issues to deal with first. I can't test at the moment, but there are two ways to deal with your configuration. 1. Define eth0 as bonding interface as well (next to bond2). Then upgrade and see if all assignment are correctly processed. 2. If the above doesn't work, then (temporary) configure eth2 as regular interface (remove bonding)

The "docker network ls" command is useful to see what docker has created as networks. These coming days I'll try to replicate your set up and see in more detail what is happening. Some explanation: 6.12 uses a different implementation when bridging is disabled and macvlan is enabled, when upgrading from 6.11 - it should - convert automatically to the new settings without user intervention, it is not clear what exactly happens in your situation. The usual fix is to manually edit the container(s) and set the proper settings.

Unraid 6.12.8 has an earlier kernel (point) version, because later kernels have a modification which breaks bonding. For future Unraid versions we made a modification to support bonding on latest kernel versions.

This looks okay. Can you update to 6.12.8 and provide the same information. Thx

Can you also post a screenshot of the docker settings page with Docker stopped.

Something went wrong in the creation of the docker networks. Feb 16 10:53:04 unraid-outer root: Error response from daemon: network dm-ac543d521cd9 is already using parent interface vhost2.60 Feb 16 10:53:08 unraid-outer root: Error response from daemon: network dm-c962d0d87feb is already using parent interface vhost4.70 Can you post a screenshot of your docker settings page (advanced mode) And post the result of this command docker network ls

This looks like a problem with your USB stick not being read properly. Please take the USB stick out (shutdown server first) and run a file system check on a windows machine.

This is indeed a bug, since routes should be added to either br0 or eth0 (depending on what is in use). I made a fix for this for upcoming 6.13 version (might get backported to 6.12). Thanks

How do remotely access the server? Are you using vpn or other method? The picture shows there is no nchan communication (this is the background communication to update the gui). Some how your remote access blocks this.

Every release comes with the latest 6.1.x kernel version available at the time. I don't remember the exact 6.1.x kernel versions for Unraid 6.12.3 and 6.12.4.

In Unraid 6.12.4 we introduced a fix for macvlan. To make this work seemlessly for users the system automatically updates configuration files and other relevant settings when bridging gets enabled or disabled. This introduces the config files updates on the flash device.

We will incorporate these changes for upcoming Unraid version 6.12.7 (and 6.13 of course). I have done a similar fix for VMs, which may experience the same thing. It would be nice if more users can confirm this fix works for them. Thanks everyone for participating and bringing in some useful information and help to uncover this situation. Though it is still a mystery to me why some people have slow write access to their flash device, something to keep an eye on.

Kubernetes is aimed at datacenter environments, the Unraid solution is mostly used in home environments. Probably this is not a widely requested feature for home use.

@CiscoCoreX I made some typos, sorry for that. Here are the updated files dashboard-test.zip

@CiscoCoreX Can you go to Tools -> PHP Settings Error reporting level = All Categories Then open the View Log Revisit the pages which end up blank and observe the PHP log for any errors. Please post these errors. Thx Fixed my typos, please use the updated files. @KluthR The fix is not really the answer to the root cause, which I don't know but it prevents unnecessary writing to the flash device.