As soon as the first new release (6.12) was out I updated to the latest version from 6.11.5 . But just after 2 hours of runtime the server crashed without any reasons so I had to reboot with the reset button on the server itself and tried again. After 5 hours another crash. So I reverted back to 6.11.5. Again with 6.11.5 I had no problems at all for several days.

 

Then 6.12.1 was released and I thought they might have solved an issue that I had with my setup. So I just did the update and after 2 hours again a crash.... So 6.12.1 is again not stable on my machine but I have no Idea why. The 6.11.5 version was stable for several months without any issue.

Here is the diagnostic files I took before reverting back to 6.11.5.

 

Any Ideas?

 

Thx Andy

nas-diagnostics-20230625-1934.zip

Enable the syslog server and post that after a crash.

so here we go. After around 10h again a crash with 6.12.2.

Now with syslog server activated

 

 

nas-diagnostics-20230627-0518.zip

You're not alone... my server has crashed two times in the last 72 hours.

Just stops working... a reboot via IPMI is the only solution it seems because even ssh isn't working. 

 

Supermicro X9DRL-3F/iF , Version 1.01
American Megatrends Inc., Version 3.3
BIOS dated: Thu 12 Jul 2018 12:00:00 AM CEST

2x Intel® Xeon® CPU E5-2620 v2 @ 2.10GHz

128 GiB DDR3 Multi-bit ECC
 

same here, can't reboot it via SSH and that's really bad, hope someone can look at the logs and figure out what the problems might be...

4 hours ago, gekoch said:

Now with syslog server activated

That doesn't come with the diags, you need to also post that log.

i thought it should be in the log folder? i set it up like this

 

It will be in the flash drive, /logs folder

so this is not the file in the diagnostic file?

 

here is the file the crash should be around 01:30 in the morning of the 27.06.2023

syslog

Jun 27 05:18:41 NAS kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Jun 27 05:18:41 NAS kernel: ? _raw_spin_unlock+0x14/0x29
Jun 27 05:18:41 NAS kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
 

ok thx did switch it to ipvlan, now udpate again to 6.12.2 and test it if the server is stable?

Yep

4 hours ago, gekoch said:

so this is not the file in the diagnostic file?

 

No.  That is the current syslog taken from RAM at the time you create the diagnostics and only has entries from after the reboot.  It is not the one from the syslog server which is in the logs folder on the flash drive (assuming you are using the mirror to flash option).

27 minutes ago, itimpi said:

No.  That is the current syslog taken from RAM at the time you create the diagnostics and only has entries from after the reboot.  It is not the one from the syslog server which is in the logs folder on the flash drive (assuming you are using the mirror to flash option).

 

ok thx for the explanation. In an earlier post I did add the syslog file directly from the log file folder.

So the system is currently running on 6.12.2 for the past 2 hours, fingers crossed

 

 

after 48h of uptime no crash! Thx a lot for the help, seems resolved with the ipvlan setting.