[Help] F424-MAX random crashes after days / weeks

[TMzethar]

Yes, this indicates that your data read and write operations are frequent, fully utilizing the SSD Hyper. The cause of this error is currently unclear, but it cannot be ruled out that it may be related to insufficient remaining RAM capacity. You might consider disabling some services or other applications to free up some RAM.

[haudegen1993]

ram is currently only 14gb of the 32gb in use.
ive shutdown vm2 - but still i get the errors...

im a little bit afraid that when i shutdown vm1 too and reboot the whole nas, that i wont be able to power on the vm1 - which is a necessary system, because there is running our accounting server (lexware)


Edit: did a backup from the vm and restarted the nas - now the errors are gone...

[Herewerare2024]

I had what sounds like a similar problem. My F6-424 Max would "stop responding" for no apparent reason and needed a manual reboot. I implemented a daily network adapter reset script and it fixed the problem. My application is just plex and backups so not related to out of memory. Maybe this approach with assist in your case.

[TMzethar]

We have been working on diagnosing this extremely hard-to-reproduce issue. Perhaps your insights can help us improve the system.
Could you please note the Kernel Panic information when the problem occurs?
Also, could you tell us how you configured things to avoid this issue?

[Herewerare2024]

I have not experienced the issue in about 2 months. I created a scheduled task to execute at night with a custom command script:
ip link set eth0 down
wait 10
ip link set eth0 up

I had previously tried a weekly reboot script, which fundamentally does reset the network, but found every so often the system would be unresponsive (network frozen). If you connect a keyboard and monitor to the NAS directly you do see the CLI and I believe can interact so the system is not actually unresponsive. Other than a suspect GRO implementation message, I do not have any related panic msgs in the log.

[sergio]

Hi， maybe you can update to the latest tos version, and check if still crashs?