Celtic8058

After a lot of troubleshooting, I noticed that one of my disks had one bad sector. I did not think much of it but my Supermicro had a lot of trouble booting or even getting into unRAID. After some Googling: Or does it mean that my USB stick died?

Maybe I should have clarified better in my original post but I did setup a syslog server. I have a Pi as 'remote server' (the files shown in the screenshot is of the Pi) but when the unRAID server reboots, it wipes the files on the Pi. Which I did not expect. So I did setup a syslog server that sends the logs to a remote machine, but I do not understand why the remote machine files get wiped upon reboot/restart of the unRAID machine.

What do you mean? The logs only get wiped when you use syslog server? As I said in my post, I am logging to a remote syslog server. I would not have expected those logs to be wiped on crash/reboot of unRAID

Hey there, After having months of headache working with a Ryzen 1700 in my unRAID system where it would crash almost weekly (even after doing all the recommended fixes, like disabling C-states). I reverted back to my Supermicro X9srL-f with an Xeon E5-2650 v2. When I had the Xeon setup before, I had years upon years of stability. But now I have similar stability to my old Ryzen 1700 system. After making the swithc back to my Supermicro/Xeon setup. It worked wonderfully for 4~ months. Suddenly the system started to hang one day and now it is only stable for a couple of hours. I try to figure out what error caused the hang but I seem to also have some trouble with the remote logging. I have setup the unraid remote logging to another Linux system (to /var/log) but when the system hangs, all the log files get emptied. I am aware the logs get wiped on unRAID reboot but I would have thought it would create subfolders on the remote syslog and just keep what has been logged. P.S. Already did a memtest and that seems to be fine. Thanks in advance!