Veah

My guess would be a docker container, or maybe a plugin. Try disabling docker and see if it happens again. A more broad effort is running in safe mode. Diagnostics may help. Consider enable syslog server just in case.

Maybe a manual controller https://a.co/d/1fJdVM4 Edit:. Adding this clever one https://a.co/d/fpA9gWs

Truer words never written.

Basically, SMR is slow. Cheaper high capacity drives use that 'shingled' tech. CMR is 'conventional' media. Faster but I'll ess density. CMR drives perform a lot faster.

Huh. I wonder what I was looking at.

Quick search on Toshiba MN10ADA10TS ... SMR drives. SMR speeds are known to be pretty poor.

If you can post your diagnostics, perhaps someone like jorgeb will show up and see something useful to help.

You need to identify the nic using each of those Mac address. Then assign them different IP addresses. The image has the word proxmox in it which strikes me as a little unusual for the scenario you described.

I notice some SMR drives. I'm guessing that is at least a part of why slower than you expect.

Agree with Squid on bonding part. After this part, connect the lan cable to the other network port. If no joy, it could be your firewall. Something there either blocking or not set to pass traffic from that IP or even a rule on the MAC address.

In system devices bind your wifi nic iommu group to vmio then restart. That will stop it from being assigned to eth0.

It looks like everything is working like it should. All that needs changed is static mappings from .10 to .2 (in pfsense). Follow that with clearing your DHCP leases. Then restart container so it acquires new lease.

Can compare the Mac address from ifconfig from the container console to the pfsense assignment Mac.

Would have thought in pfsense under status > DHCP leases you could configure the IP assignment there by finding the one in question, then clicking the + symbol on the right and filling it out. If it's already built, you can find it under services > DHCP server, select the correct lan and looking at assignments at bottom of page.

Beyond changing under settings > identification, I read somewhere needing to log out and back in to unraid connect based on this thread. You could go directly to the USB > config > ident.cfg file and mess around there. Highly recommend backing it up beforehand just in case.

Suggest start a thread under general. This looks like a back and forth needed not intended for this announcement section.

Settings > identification Rename it.

Rebooting modem and router may be in order.

I do not believe there's a way. Try disabling half then half again sort of method is best I can suggest.

Disable docker and see if those errors continue. If they stop, it points to one of your containers having a problem.

Yeah I thought of that after I wrote it. Hopefully it's not something wrong with the backplane.

Power or sata cables are typically the culprits. Posting your diagnostics will likely get the attention of the smart folk.

May also check the scaling on your mb fans. I've found some vrm and chipset fans to be pretty loud and throttling them down just a little can make a big difference.

Look into Tailscale. It is integrated into the more recent versions of Unraid.

The asm1166 chip on a pice or m2 slot play well with unraid too.