System has been around since Aug 2022 and about 1.5 years ago would become unresponsive in the sense that I could not access it via WebGUI and all my docker apps would go down and generally speaking I would have to perform a hard shutdown since the system is headless. Not really sure how to check what is wrong with it as it sometimes stays up for 6+ months without issue and more recently seems to be going down more often than previously. Attached diagnostics since I saw someone else do so in their post but if anything else is needed that can help please let me know. The next time it goes down(locks up) I will also move the system and place it where I can attach a monitor to see if it's still running when it "locks up" in the future, or if it's completely crashed.

chonk-diagnostics-20260122-1440.zip

Edited January 22Jan 22 by Acefej

Enable the syslog server and post that after the next crash.

14 minutes ago, JorgeB said:

Enable the syslog server and post that after the next crash.

I did enable the syslog server a bit ago(can't remember when) but not sure what to look for. Let me know if this looks like what you're referring to or if I didn't set it up correctly.

syslog-127.0.0.1.log

Does it cover a crash, and if so, what was the timecode?

Just now, JorgeB said:

Does it cover a crash, and if so, what was the timecode?

Latest crash was around 15 hours ago at 1-1:30 log time.

Jan 11 12:54:21 Chonk kernel: WARNING: CPU: 6 PID: 24258 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]

Macvlan call trace, this will crash Unraid; it's been a while since I've seen this, it's been fixed since 6.12.11, but you are on 6.12.10, so the first thing is to update Unraid.

Also check filesystem for this device:

Jan 18 04:40:04 Chonk kernel: XFS (sdb1): Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0x4004947b dinode

Jan 18 04:40:04 Chonk kernel: XFS (sdb1): Unmount and run xfs_repair

9 minutes ago, JorgeB said:

Jan 11 12:54:21 Chonk kernel: WARNING: CPU: 6 PID: 24258 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]

Macvlan call trace, this will crash Unraid; it's been a while since I've seen this, it's been fixed since 6.12.11, but you are on 6.12.10, so the first thing is to update Unraid.

Also check filesystem for this device:

Jan 18 04:40:04 Chonk kernel: XFS (sdb1): Metadata corruption detected at xfs_dinode_verify+0xa0/0x732 [xfs], inode 0x4004947b dinode

Jan 18 04:40:04 Chonk kernel: XFS (sdb1): Unmount and run xfs_repair

Strange thing is unraid has been telling me I'm up to date but guess it's bugged out. I'll update now if I can figure out how to force it to let me since it is giving me some false already updated prompt from the WebGUI. I'll check on all those you linked and see what's up and get back to you once I perform some house cleaning.

Ok I have updated my server to 7.2.3 and repaired the cache drive(sdb1) successfully. Unfortunately it messed up the nvidia driver along the way somehow but now that I've got it all fixed I seem to be back up and running same as before the update. I will just leave the logs running and hopefully this fixes the crash issues related to pre 6.12.11 as you mentioned. Appreciate all the help @JorgeB now it's just a waiting game with fingers crossed.

Edited January 23Jan 23 by Acefej