As I can't diagnose the problem and it's too strange to me, I'll try to describe the situation.
Yesterday my emby installation starrted to act strange. The emby app on my Tv seemed to log into the server but it wasn't loading all the contents. Only one or two here and there (I'm talking of video lists)
So I went to my computer and tried to log into omv web gui, without success. Also I tried to log into ipmi web management but couldn't get into it.
I realized that if I leave those pages loading, after some long time they load partially. In case of omv, it loads the background and title (no login) and ipmp loads an imcomplete login.
network drives seemed accesible, but as I tried to open them windows stuck loading the content
I also tried ssh and It connected, but as long I executed some command, as top, it became unresponsive and the ssh connection resets with a timeout.
I tought then that the network port could be damaged and plugged the second one and configured for another IP. This worked. I could enter the OMV web gui and seemed fast and completely loaded. No IPMI though.
So I executed omv-firstaid and configured the 1st interface with some other ip (ok) and then tried to configure the 2nd with the original ip. It failed when saving, but I could access the web gui on that ip.
I saw anywhere that something failed with LO interface configuration (i'll try to reproduce again)
The icons con the web gui where weird and the services where not working. Docker throws error opening it's page.... network interfaces page is empty...
I thought of disk corruption on the SSD and got the smart values but all are ok. I executed shutdown -rF now so I could check the filesystem on boot, but showed several messages about being unable to unmount ZFS filesystems, failing stopping vbox and then stuck on "Deconfiguring network interfaces..."
I pulled the cord and restarted it. While booting it showed the root fs check without problems.
PAR0: recovering journal (PAR0 is my parity drive for snapraid)
PAR0: clean, xx/xxxxxx files, xxx/xxx blocks
[Firmware warn]: error section length is too small 95%
Configuring network interfaces...RTNETLINK answers: File exists
Failed to bring up lo.
[63.157733] [Firmware Warn]: error section length is too small
Well, it seems not to be stuck since I can insert an usb stick and it shows detection messages.