Good morning everyone,
for some time now, the error message in the subject has been appearing on my Unraid server.

I have already tried replacing the USB stick and positioning it on a different USB port on the server, but it did not yield positive results.

I don't know what the specific issue is, so I am attaching the relevant logs from my server to this thread.

Thank you all for your support.

tower-diagnostics-20260224-1458.zip

Your logs are filling up with a lot of this

Feb 24 04:41:34 Tower kernel: br-2d799c063852: port 3(veth0f962ca) entered disabled state
Feb 24 04:41:34 Tower kernel: veth0f962ca (unregistering): left allmulticast mode
Feb 24 04:41:34 Tower kernel: veth0f962ca (unregistering): left promiscuous mode
Feb 24 04:41:34 Tower kernel: br-2d799c063852: port 3(veth0f962ca) entered disabled state
Feb 24 04:41:34 Tower kernel: br-2d799c063852: port 3(veth2063f81) entered blocking state
Feb 24 04:41:34 Tower kernel: br-2d799c063852: port 3(veth2063f81) entered disabled state
Feb 24 04:41:34 Tower kernel: veth2063f81: entered allmulticast mode
Feb 24 04:41:34 Tower kernel: veth2063f81: entered promiscuous mode
Feb 24 04:41:34 Tower kernel: eth0: renamed from vetha55abe8

Can't see anything else because of that. Can you make those stop?

Reboot to clear the logs, then get diagnostics again when you get that error message.

Hi trutl,

I restarted the server as you instructed and I’m attaching the related logs.

tower-diagnostics-20260224-1724.zip

1 hour ago, trurl said:

when you get that error message.

Did you already get that error message again since rebooting?

Feb 24 17:24:58 Tower kernel: br-2d799c063852: port 7(veth229ee34) entered disabled state

Feb 24 17:24:58 Tower kernel: br-2d799c063852: port 7(veth8a92399) entered blocking state

Feb 24 17:24:58 Tower kernel: br-2d799c063852: port 7(veth8a92399) entered disabled state

Feb 24 17:24:58 Tower kernel: veth8a92399: entered allmulticast mode

Feb 24 17:24:58 Tower kernel: veth8a92399: entered promiscuous mode

Feb 24 17:24:58 Tower kernel: eth0: renamed from vethe3de5c4

If these keep going on, you likely have a container constantly restarting. Check their uptimes and look for one that has only been running for a few seconds.

1 hour ago, trurl said:

Did you already get that error message again since rebooting?

yes→

1 hour ago, JorgeB said:

Feb 24 17:24:58 Tower kernel: br-2d799c063852: port 7(veth229ee34) entered disabled state

Feb 24 17:24:58 Tower kernel: br-2d799c063852: port 7(veth8a92399) entered blocking state

Feb 24 17:24:58 Tower kernel: br-2d799c063852: port 7(veth8a92399) entered disabled state

Feb 24 17:24:58 Tower kernel: veth8a92399: entered allmulticast mode

Feb 24 17:24:58 Tower kernel: veth8a92399: entered promiscuous mode

Feb 24 17:24:58 Tower kernel: eth0: renamed from vethe3de5c4

If these keep going on, you likely have a container constantly restarting. Check their uptimes and look for one that has only been running for a few seconds.

I will keep an eye on the situation.

Hi JorgeB,

I monitored the containers in question and found one with a short uptime of about 20 seconds ("pterodactyl-daemon"). Since I don't use it, I proceeded to shut it down, disable auto-start, and restart the server, but the error persists:

Please find the server logs attached again.
Thank you for your support.

tower-diagnostics-20260224-2010.zip

The problem is with share.cfg, delete that file, then make a dummy change to recreate it. You can, for example, toggle the SMB or NFS services, clicking Apply each time.

Hi Jorge,

I followed your advice to remove and stop the pterodactyl-daemon. At first, the error still appeared (probably because it was cached), but now it’s gone, so I think that was indeed the issue.

I also waited 24 hours to be sure, and the error hasn’t shown up again, so it definitely seems that was the problem.

Thanks a lot for your support!