FlunkyBob

I have attached my Diagnostics zip, sorry if I seem such a noob. I'm very new to linux and Nas servers Thank you for trying to help me mainmediaserver-diagnostics-20240519-1858.zip

Took a day or two to get a new cable but its not that causing it, i think its a setting on the server but im not sure what or where

I am not sure how to set to auto, where would the setting be? Its connected to the router directly the same as a Mac in the other room, the mac seems to run at 1gbps just fine so i don't think its the router settings Its the router for the main internet of the house and i have just rebooted it to see if it sorted it but its still the same

Hiya, I have an issue with my server where it is limited to 100mb but the device should be 1gbs Is there any way to increase this output? Thank you

Thank you, i will have a look and give these a go, i will report back if it solves the issue or not

I have Attached the Diagnostics zip, thank you for willing to help me mainmediaserver-diagnostics-20240105-1439.zip

Hello guys I have been having an issue with a media server is built, it randomly becomes unresponsive and I have to restart it to get it to work again I have syslogs active and there are no errors as such only this as the last entries before it locks up: Jan 4 00:48:15 MainMediaServer kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth792272e: link becomes ready Jan 4 00:48:15 MainMediaServer kernel: docker0: port 4(veth792272e) entered blocking state Jan 4 00:48:15 MainMediaServer kernel: docker0: port 4(veth792272e) entered forwarding state Jan 4 00:48:22 MainMediaServer kernel: docker0: port 7(vethd6599df) entered disabled state Jan 4 00:48:22 MainMediaServer kernel: veth65da6ee: renamed from eth0 Jan 4 00:48:22 MainMediaServer kernel: docker0: port 7(vethd6599df) entered disabled state Jan 4 00:48:22 MainMediaServer kernel: device vethd6599df left promiscuous mode Jan 4 00:48:22 MainMediaServer kernel: docker0: port 7(vethd6599df) entered disabled state Jan 4 00:48:23 MainMediaServer kernel: docker0: port 7(veth5b63acc) entered blocking state Jan 4 00:48:23 MainMediaServer kernel: docker0: port 7(veth5b63acc) entered disabled state Jan 4 00:48:23 MainMediaServer kernel: device veth5b63acc entered promiscuous mode Jan 4 00:48:23 MainMediaServer kernel: docker0: port 7(veth5b63acc) entered blocking state Jan 4 00:48:23 MainMediaServer kernel: docker0: port 7(veth5b63acc) entered forwarding state Jan 4 00:48:23 MainMediaServer kernel: eth0: renamed from veth89cb382 Jan 4 00:48:23 MainMediaServer kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5b63acc: link becomes ready Is this the cause of the locking up of the system? I'm about to buy all new parts like a motherboard, PSU, RAM and CPU as I'm not sure what the cause could be These are the only things that are from an old computer I had, so it could be those causing it... The Server is alive as in power is running and you can see the fans spinning but is not making any HDD reads and writes Thank you in advance Chris