Every time I open Docker Settings or Network Settings, then my server becomes completely unresponsive. I cannot go to any page or SSH to the server either. I am forced to shutdown the server by holding power button. I have enabled syslog after last hard shutdown.

 

Even pulling diagnostics makes the server unresponsive. So I had to attach monitor and input to get the diagnostics. The server is frozen, so I could only take a screenshot with my phone... I will try to get the logs out to a file..

 

I tried removing subnets, and changing multiple docker and network settings.

 

Furthermore, I keep noticing 'eth1' as a culprit.

 

What else can I do?

 

Diagnostics:

 

mkdir -p /boot/logs
mkdir -p '/tower-diagnostics-20240415-1911/system' '/tower-diagnostics-20240415-1911/config' '/tower-diagnostics-20240415-1911/logs' '/tower-diagnostics-20240415-1911/shares' '/tower-diagnostics-20240415-1911/smart' '/tower-diagnostics-20240415-1911/qemu' '/tower-diagnostics-20240415-1911/xml'
top -bn1 -o%CPU 2>/dev/null|todos >'/tower-diagnostics-20240415-1911/system/top.txt'
tail /boot/bz*.sha256 >> '/tower-diagnostics-20240415-1911/unraid-6.12.10.txt'
uptime
nproc
lscpu 2>/dev/null|todos >'/tower-diagnostics-20240415-1911/system/lscpu.txt'
lsscsi -vgl 2>/dev/null|todos >'/tower-diagnostics-20240415-1911/system/lsscsi.txt'
lspci -knn 2>/dev/null|todos >'/tower-diagnostics-20240415-1911/system/lspci.txt'
lsusb 2>/dev/null|todos >'/tower-diagnostics-20240415-1911/system/lsusb.txt'
free -mth 2>/dev/null|todos >'/tower-diagnostics-20240415-1911/system/memory.txt'
ps -auxf --sort=-pcpu 2>/dev/null|todos >'/tower-diagnostics-20240415-1911/system/ps.txt'
lsof -Pni 2>/dev/null|todos >'/tower-diagnostics-20240415-1911/system/lsof.txt'
lsmod|sort 2>/dev/null|todos >'/tower-diagnostics-20240415-1911/system/lsmod.txt'
df -h 2>/dev/null|todos >'/tower-diagnostics-20240415-1911/system/df.txt'
ip -br a|awk '/^(eth|bond)[0-9]+ /{print $1}'|sort
dmidecode -qt2|awk -F: '/^ Manufacturer:/{m=$2};/^ Product Name:/{p=$2} END{print m" -"p}' 2>/dev/null|todos >'/tower-diagnostics-20240415-1911/system/motherboard.txt'
dmidecode -qt0 2>/dev/null|todos >>'/tower-diagnostics-20240415-1911/system/motherboard.txt'
cat /proc/meminfo 2>/dev/null|todos >'/tower-diagnostics-20240415-1911/system/meminfo.txt'
dmidecode --type 17 2>/dev/null|todos >>'/tower-diagnostics-20240415-1911/system/meminfo.txt'
ethtool 'bond0' 2>/dev/null|todos >>'/tower-diagnostics-20240415-1911/system/ethtool.txt'
ethtool -i 'bond0' 2>/dev/null|todos >>'/tower-diagnostics-20240415-1911/system/ethtool.txt'
ethtool 'eth0' 2>/dev/null|todos >>'/tower-diagnostics-20240415-1911/system/ethtool.txt'
ethtool -i 'eth0' 2>/dev/null|todos >>'/tower-diagnostics-20240415-1911/system/ethtool.txt'
ethtool 'eth1' 2>/dev/null|todos >>'/tower-diagnostics-20240415-1911/system/ethtool.txt'

 

 

logs.zip

Edited April 15, 20242 yr by mrbusiness

Try renaming /boot/config/network.cfg to .bak and reboot, LAN settings will go back to default DHCP, in case it's something in the config.

27 minutes ago, JorgeB said:

Try renaming /boot/config/network.cfg to .bak and reboot, LAN settings will go back to default DHCP, in case it's something in the config.

 

Did not work. Same issues. Diagnostics gets stuck at 

ethtool 'eth1' 2>/dev/null|todos >>'/tower-diagnostics-20240415-1911/system/ethtool.txt'

 

From what I see in the logs there are 4 identical NICs? If these are onboard disable all in the BIOS except for eth0, there may an issue with that one, since they all use the same driver, I would think that if it was a compatibility issue it should crash on the first NIC

2 hours ago, JorgeB said:

From what I see in the logs there are 4 identical NICs? If these are onboard disable all in the BIOS except for eth0, there may an issue with that one, since they all use the same driver, I would think that if it was a compatibility issue it should crash on the first NIC

Yes, 4 similar NICs from this board: Alder Lake N100 NAS Motherboard ITX  Home Processor DDR5 4* I226 2.5G LAN M.2 Slot 6xSATA DP HD Low Power
https://a.aliexpress.com/_Ex41iIT

 

It’s Intel I226. It has been working for a months now without this issue. Suddenly just happened. Instead of disabling in BIOS is there a way to get correct driver?

The driver is the same for all NICs, if one works that others should also work, unless it's caused by specific setting differences.