Hello everyone, I have a trouble that my server is freezing after 12 to 36 hours usually. The only way to recover the server is to hold the shutdown button and start it again.

 

Any suggestion is appreciated .

 

PS :

I have attached the syslog and diagnostic files

I have also read many of the post and tryed adjusting diffrent settings such as the docker network to ipvlan etc.

nasty-diagnostics-20240118-2106.zip syslog

That is the same syslog included in your diagnostics.

 

Setup syslog server.

that is with mirrored to flash

syslog-previous

That one was in the diagnostics too. It only includes a short time immediately after reboot.

 

After you have the problem again get the syslog and post it.

Ok so I will wait until the next freeze and than grab all syslog's from the USB before booting again.

 

Thanks

syslog from last crash

sys.log

Have you done memtest?

Yes after googling around the last error turned out to be connected most of the time with the memory. I have done one and it failed. I removed 2 sticks of the memory and now with the other 2 I have a pass. I have run for 30 minutes without an error and with a pass.

 

Do you have any recommendations for how long should I run it before I try to boot up the server again ?

 

Thank you

 

Couple of hours is usually enough for most serious issues, you then also should recreate the docker image.

So I did 4 hours running the memtest no errors multiple passes. The server froze in 20 hours after that.

This is the syslog at time of freezing syslog-previous(1)

Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

Is safe mode the same as just manually stopping docker, VMs etc ?

Safe Mode simply doesn't load any plugins.

 

Wish it also disabled Docker and VM Manager, but no.

Thanks.

 

So I have booted into safe mode and started the array. the server has frozen again after couple of hours.

 

On the hardware side I have swapped

• Motherboard
• CPU
• Memory (Multiple SWAPs until I got a set that I can have 4 hours of memtest without errors)

What would you suggest I swap next

The NVME drive for the cache or the PSU ? ( I will assume the hard drives for the array wont cause the server to completely freeze

Also another question. Could the USB stick cause the freezing ? How does UNRAID work once loaded into memory ?

 

Also should I try installing Ubuntu some other flavor of Linux and see if it crashes there ?

 

Edited January 28, 20242 yr by ninik

22 minutes ago, ninik said:

Memory (Multiple SWAPs until I got a set that I can have 4 hours of memtest without errors)

That much RAM trouble with multiple sets suggests some problem other than bad RAM, such as overclocking.

 

21 minutes ago, ninik said:

How does UNRAID work once loaded into memory ?

It runs in RAM. All of the Linux OS folders are in RAM. The flash drive just has settings from the webUI, which are applied at boot and kept in RAM, and changes to those settings are saved on flash so they can be reapplied.

I will try resetting the bios to defaults( Pretty sure I already did that but just in case and let it run afterwards)

So I have just reset the bios on the small hardware with Ryzen 1gen.

 

I have disabled the Cstate and enabled SVM. I have also set the current to Typical instead of Auto.

 

Everything else is set to default/auto. No overclocking no profiles enabled.

 

Any other suggestion to disable enable ?

 

Motherboard series Gigabyte Technology Co., Ltd. B450M DS3H-CF

CPU AMD Ryzen 3 1200

Edited January 30, 20242 yr by ninik