Hi guys.

I have an issue on unraid 7.1.0-beta3 that sshd is not running after boot, everything else works.
Starting it manually works.
I think the issue arrived after adding an I226-V NIC (instead of using the integratet I219-V).

Here is a similar thread with some suggestions: 

 

syslog.txt

I also have "carrier lost" in the syslog.

Bonding and bridging is disabled.
I have not installed the plugin "Tips and Tweaks", so icant uninstall it.

Please find attached the syslog.

thx

pOpY

 

I also have this during boot:

Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Antwort von 192.168.0.5: Bytes=32 Zeit=667ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.5: Bytes=32 Zeit<1ms TTL=64

 

So network is working short after boot ping is stable and than two drop outs and ping is back.
I think there the sshd is killed and not restarted.

Shouldn't it be restarted?

 

Figured out whats going on.
I had the following in my /boot/config/go file:

# enable IEEE 802.3az (Energy Efficient Ethernet): Could be incompatible to LACP bonds and break SSH daemon!
for i in /sys/class/net/eth?; do dev=$(basename $i); [[ $(echo $(ethtool --show-eee $dev 2> /dev/null) | grep -c "Supported EEE link modes: 1") -eq 1 ]] && ethtool --set-eee $dev eee on; done

 

This restarted the NIC and brougth it down/up during boot, which affected sshd.

After comment it out, it works now (tried 3 reboots and sshd was running).
Disabling EEE did not hurt idle power consumption which is basically the same with or without.
 

Edited April 12, 20251 yr by pOpYRaid