I am a newbie, really appreciate any help. I've had this server running for a year or so, every 2-3 weeks my server will get into a state where the console display shows nothing/can't be typed on, and the web UI won't load, can't be pinged -- appears to be crashed. I managed to grab the attached log right before this occurred. 

 

I've noticed if I do a hard powercycle that it will auto-start the parity check, and usually crash again within a couple of hours, if I abort the parity check by a 2nd soft reboot then it'll stay alive for much longer.

 

I can't rule out it being a hardware or BiOS problem, since it's been happening since I initially setup the server.

unraid-diagnostics-20240207-1520.zip

There are several call traces logged, but difficult to say what causing them, you can try running memtest and/or 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.

Thanks Jorge, I attached my memtest.

 

The FixCommonProblems plugin did just yesterday link me to https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces so I did that fix. I had 1 docker (setup about a week ago) and 0 VMs running.

 

I have it booted into safe mode now, though I'm not able to access the share I had setup before. Is there a way to turn that on?

10 hours ago, gaarakenpachi said:

so I did that fix

That could have been the issue, make sure you reboot after the change and retest.

No luck, the issue reproduced again. Even when just using the system as a NAS, without plugins, dockers, VMs.

 

Are there any extra logging features I can enable to get better information?

Not really, and still crashing while running as a NAS makes me suspect hardware, try running with just one stick of RAM, if the same try the other one, memtest is only definitive if it finds errors.

I removed one RAM stick and it was successfully able to complete a parity check with all the services on -- which it has never been able to complete before -- so I think it's fixed (unless I post again in a few weeks). Thanks Jorge for your help!