Hey!

 

I'm reaching out because recently I've started experiencing system freezes that I can't attribute to a specific cause.

 

In general, I first notice that DNS is no longer working on the network (I'm using an AdGuard container on the unRAID host), which prompts me to investigate. Then I'll find the machine unresponsive (connection refused or timeout on the web interface and SSH, no disk activity lights, and plugging in an HDMI cable to a display also doesn't give an output) but with the power indicator still on. The only way I've found to recover from it is a hardware reset, after which the machine runs fine again (but requires a parity check). This happens once or twice a week now.

 

Today, the same symptoms (I don't know if the cause is the same) occurred by manually triggering a short "Fix Common Problems" scan. This is the first time I've seen this cause the symptoms, which is why I wanted to post this question in General Support initially.

 

In the attachment you'll find a recently generated diagnostics file. Now I've read that this may not be entirely useful since for example system logs are not preserved over reboots. Because of this I've set-up persistent logging using the syslog server and I also have a copy of the system log since November 1 which should include log files pre-freeze. Since this is not anonymised I'd prefer sending it directly to somebody who is willing to help me out, instead of posting it here publicly.

 

I've did a bit of digging and did found some threads that ended up with something along the lines of "the hardware is old and starting to be unreliable". I would not be surprised if that's it (oldest components incl. CPU, RAM and MoBo are 8 years old, HDD's are new), but before I look into replacement hardware, I just would like to confirm there's not something else going on.

 

If there's more information I can provide please do let me know. Thank you in advance for any help, it's much appreciated!

rannoch-diagnostics-20231114-1154.zip

Nov 14 11:49:42 Rannoch kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Nov 14 11:49:42 Rannoch kernel: ? _raw_spin_unlock+0x14/0x29
Nov 14 11:49:42 Rannoch kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

 

Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.

I've changed that setting (as well as disabling "Host access to custom networks" as the help menu's explicitly mentions macvlan and not enabling unless you're sure - and I don't recall having a good reason to enabling it).

 

The setting has been on for months (if not a year or wo) and I'm not sure why it's causing issues only now. Having said that, I have seen some strange things in the past months - just not so frequent.

 

The server is rebooted and everything is running. I'll report back when this doesn't solve the problem.  

 

Thanks very much for the quick repsonse!