Recently I have been getting this exit status 255 from user root php /usr/IocaI/enhttp/pIugins/community.applications/scripts/notices.php > /dev/null 2>&1 error a lot recently. There are a lot of references to dynamix plugins. As far as I'm aware I do not have any dynamix plugins installed. This copy of unraid has been updated from early 6 vers and I have installed and uninstalled many plugins in that time. I saw on some threads that use had modified a go file, I checked this file and it has never been modified. Hopefully this is just an easy fix. I'm fine with removing or changing whatever to get to "stock" unraid and stop these crashes from happening.

I have read multiple threads with this same error and they either had no solution or were told to "revert" manual code changes, something I have never done.

Thanks

kronos-diagnostics-20251115-1536.zip

Not exactly sure what's causing them, probably an old config file, but those should be harmless.

On 11/16/2025 at 3:33 AM, JorgeB said:

Not exactly sure what's causing them, probably an old config file, but those should be harmless.

Any recommendation on what config files I can update/reset?

The crash seems to happen more often after a parity check if that makes a difference.

If you mean getting rid of those errors, you can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit, though like mentioned that's probably not related to the crashing, for that, you can enable the syslog server and post that fater a crash, in case there's something there, but if it happens more during a parity check, it can be hardware related, and because of the increased load.

This crashing has only been "recent" (maybe only the last six months). I have had parity checks complete fine but now it just crashes after every parity check. Any advice for what hardware related issues could be occurring. It is getting very annoying having to hard reset the server every time it happens. For the time I guess I can just stop parity checks but of course that is not ideal.

If it crashes during a parity check, typically it is the board, CPU. RAM or PSU, in no particular order

I disabled parity checking but it still crashed at one point. I normally don't notice till someone tries watching plex and it says it's down. I never had issues with this system before and I have been using undraid on this PC for almost 4 years now. Normally if I have an issue there have been solutions online or steps to diagnose the issue. But for this error all I see a threads that have no conclusion or updating unraid fixed it (I'm on the latest stable build). Are there no other ideas for helping determine a solution to this problem?

You can enable the syslog server and post that after a crash to see if there's something there.

On 12/1/2025 at 2:19 AM, JorgeB said:

You can enable the syslog server and post that after a crash to see if there's something there.

Created after a crash and booted into safe mode. Hope these help.

kronos-safemode-diagnostics-20251202-1737.zip

I don't think I had syslog write to flash but I did have write to flash on shutdown. I enabled write to flash and will send another log when it crashes again.

Replaced my flash drive for the second time and all crashing has seemed to stop.