Hi guys,
yesterday i updated my fine working omv (2.0) (thx for the work!) with a complete reinstall to omv 3.0. (the most users said: better reinstall than update).
Installation goes fine, configuration made with some made screenshots from 2.0, ok.... it works again, now on 3.0
Than i checked the 'autoshutdown'-function: and i have the same problem like here:
e1000e Detected Hardware Unit Hang
The NIC hangs during hibernate-command and omv is unreachable per LAN.
Only a reboot brings it back in the network.
I installed the last driver from intel-website (3.3.5.3), compiled the kernel,.. lookes good:
root@openmediavault:~# ethtool -i eth1
driver: e1000e
version: 3.3.5.3-NAPI
firmware-version: 0.13-4
bus-info: 0000:00:19.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
root@openmediavault:~# ethtool -i eth2
driver: e1000e
version: 3.3.5.3-NAPI
firmware-version: 1.8-0
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
but when i send omv to sleep with the Android OMV-App by doods, the same errors.
What can be done?
I remember, that on omv2.0 i had the same problem and the solution was to recompile the kernel with the intel-drivers (https://downloadcenter.intel.c…nder-Linux-?product=47620)
Any ideas?
thx,
dask2