Hi,

 

I am facing freezes regularly on Unraid lately, I need to hard reboot the NAS because nothing else work, even SSH. I have activated syslog on USB drive in case of freeze, which I attached.

 

Is that a hardware or software problem?

 

I also have a 3.0 USB drive, which I will trade for a 2.0 one in the next fews days, when I reboot the serveur, I often have to change the USB port of the USB drive for the system to find it, otherwise it only boot the BIOS, could it be related?

syslog.log

A new crash happened, this time with a USB 2.0 flash drive, I join the new syslog.

syslog.log

Edited September 7, 20241 yr by seifer

There are constant OOM events, they appear to be caused by Frigate.

Yes, it's FFMPEG that causes the OOM events, but unfortunately I cannot limit it's RAM consumption, I did it on Frigate but it doesn't affect FFMPEG...

 

The OOM are a pain in the neck, but it's not Frigate that causes the crashes (at least not totally), because I stopped the container a few days and the crashes still occured.

Then suggest stopping that container temporarily to stop spamming the log and post a new syslog after a crash

Ok, I'll try that. Thank you.

So the server once again freezes, here's the logs.

syslog.log

There are a couple of NIC related crashes logged, try using a different NIC if possible.

I just have purchased a Ugreen USB device to get my NAS to 2,5gbps, installed the plugon realtek to get the drivers. But, as I read on some topics, I have the bonding option enabled, could this affect the network stability? I read that bonding could cause network instability with some network peripherals.

Have tinkered with bonding a few times and found it more trouble than it is worth.  Disable it and see how it goes.

From things I've read, it only shines if you are hosting many simultaneous users.

Ok, right, I am actually setting this off, I will see if the crashes will come back or not.

 

Thanks for help!

Hi,

 

I had a new freeze today, at 10:40, I had to restard the system because even SSH was unreacheable. But I cannot notice why in the syslog.

 

These are the lines just before restarting the system, I do not see anything weird though :

 

Sep 11 10:42:44 SeiferNAS kernel: mdcmd (36): set md_write_method 1
Sep 11 10:42:44 SeiferNAS kernel: 
Sep 11 10:42:44 SeiferNAS root: Delaying execution of fix common problems scan for 10 minutes
Sep 11 10:42:45 SeiferNAS emhttpd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh "/tmp/user.scripts/tmpScripts/GPU Idle/script" >/dev/null 2>&1
Sep 11 10:42:45 SeiferNAS emhttpd: Starting services...
Sep 11 10:42:45 SeiferNAS emhttpd: shcmd (55): /etc/rc.d/rc.samba restart
Sep 11 10:42:45 SeiferNAS wsdd2[5693]: 'Terminated' signal received.
Sep 11 10:42:45 SeiferNAS winbindd[5696]: [2024/09/11 10:42:45.023962,  0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler)
Sep 11 10:42:45 SeiferNAS winbindd[5698]: [2024/09/11 10:42:45.023960,  0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler)
Sep 11 10:42:45 SeiferNAS winbindd[5696]:   Got sig[15] terminate (is_parent=1)
Sep 11 10:42:45 SeiferNAS winbindd[5698]:   Got sig[15] terminate (is_parent=0)
Sep 11 10:42:45 SeiferNAS winbindd[5943]: [2024/09/11 10:42:45.024016,  0] ../../source3/winbindd/winbindd_dual.c:1950(winbindd_sig_term_handler)
Sep 11 10:42:45 SeiferNAS winbindd[5943]:   Got sig[15] terminate (is_parent=0)
Sep 11 10:42:45 SeiferNAS wsdd2[5693]: terminating.

 

I joined the syslog as usual.

 

EDIT :

 

I have checked the port on my docker, and 2 of them had the same port, so I fixed it, it has runned smoothly for some hours and it crashed again, but I have been able to access the GUI so I performed a clean reboot but before that I downloaded the diagnostics file.

 

I have been able to access the log while the crash was on going, and I kept an eye over the syslog, and I notice when the following lines appeared, this have caused the crash, so I think it is network related. Is it?

 

 

 

I noticed also that in my Unifi Network Controller Docker, these lines appeared too :

 

syslog.log

seifernas-diagnostics-20240911-2220.zip updated syslog.log

Edited September 11, 20241 yr by seifer
New crash

It seems that I figured out what was the problem. It's been two whole days without any freeze at all, I have a USB dongle to reach 2.5gbps because my mobo only hits 1gbps. Once the realtek plugin was removed, no more crashes for now. I hope this will continue this way.