I set up unraid on a new-to-me r720xd. It runs way too hot and loud, but whatever, it's what I have. The trial went well, I bought the Pro license, but now I'm having more and more problems with unraid. The docker containers will stop and when I try to start them, they'll complain about Server Error something and not start. Sometimes on reboot, they won't come up at all. The WebUI will become totally unresponsive after enough docker nonsense and I'll have to kill the php/nginx processes to get it to go again. If that doesn't work and I try to reboot, it'll just hang there trying to shut down. I forgot about it the other night and it finally rebooted after about 6 hours. The logs are absolutely filled with "received packet with own address" errors that I can't seem to track down. Nothing about it seems to work quite right and I'm getting ready to just chuck the whole thing.

 

I've attached diagnostics. Thank you for your help!

munchlax-diagnostics-20230626-1127.zip

22 minutes ago, acerotercero said:

he logs are absolutely filled with "received packet with own address" errors that I can't seem to track down.

Try recreating the docker image, if this is a custom docker network it will be deleted.

I did that a few days ago. It didn't help, unfortunately. While Previous Apps helped a lot, manually clicking through 53 containers to change the network back was a pain.

I don't see any vlans on network settings but you can delete/rename /boot/config/network.cfg and reboot, lan settings will revert to default DHCP.

Ok, I've done that. I went to reboot and it said the system was going down for a reboot. 2 hours later and it's just hanging out. I refresh the webgui and it says that it's been online for 22 hours. I ask it to reboot again and this time it goes. We'll see if that fixes anything.

No dice, logs are still filled with the "received packet with own address" warning. That can't be causing the rest of my issues, though, can it?

11 hours ago, acerotercero said:

That can't be causing the rest of my issues, though, can it?

Possibly not, but still should be fixed, are you sure you've recreated the docker image? Can't see where else that vlan is coming from, though you could always start with a new install.

Yeah, I deleted the image, recreated it, and installed all the apps again with Previous Apps. I had to manually click through 53 containers to change their network because the custom docker network didn't survive the image deletion.

If you recreated the custom network then maybe that network is the problem, and it wasn't correctly configured.