Dreizarf

Ok, so after more than a week i can tell the problem was done. No more crash.

Some news. I make some adujstement in the bios and now my uptime its 1 day and 1 hour without crash. Let see if i can go to 1 week. For anyone who read this, in the bios, i remove the "Max power Saving" option and i set "APSM Control" to "Os"

Thank you for your quick response. By rolling back to version 6.12 this solved my problem. The server no longer crashed. Can C-state pose a problem on version 7.0?

The actual setup of syslog. Attached, you have the server syslog. To make it easier to find, I put a #CRASH tag. I also replaced the email addresses displayed in the file. Same i put a #ROLLBACK tag when im back to 6.12 I don't have the diagnostic zip because I am currently in 6.12 I saw the lines below which seemed strange to me regardless of the version. syslog-127.0.0.1.log

The syslog is already enabled and i show you in my previous comment that nothing appear.

Good morning, Since switching to version 7 of unRaid, the server no longer responds (GUI/Docker/ect) every 8 to 12 hours. I updated the bios and Intel ME firmware but it doesn't change anything. I performed a memtest86 on 5 passes but the RAM is ok. The solution was a rollback to 6.12. No more problems since. Here is my configuration : - CPU : Intel I5 13500 - RAM : One stick 32Gb DDR5 ECC - MB : Asus W680 Pro - PCIe : LSI9300-i8 - PSU : 550W BiQuiet Gold - HDD : 4*1To Sata + 2*1To Sata partition - SSD : 2*800Go SAS Cache Docker + 2*800Go SAS Cache VM Nothing appears in the logs. We see that nothing is published between the moment the server freezes and the moment I reboot it. Just an exemple below (RAM-Disk run every 30min) :