I apologize for not immediately answering a couple weeks ago when you asked about which ones were persistant syslogs. I had a super busy weekend that week and things have only gotten more hectic here with other non-technical home issues that needed to be taken care of before we hosted for the holidays this year. Again, I do appreciate your help.

I believe the logs for the previous session (2025-11-18_0157) might have been the one that should have covered the issue because the new logs that started 2025-11-08_2129 would have been created after the forced reboot, but unfortunately I'm not 100% sure since it's been so long and because as I mentioned in my post on November 7th, I'm pretty sure the syslog stops logging information when the server crashes with the crond error. I planned on waiting until the system crashed again with the same crond error before posting so we had multiple instances of data to help distinguish what was happening, but the next time it crashed was last night November 20th and when I rebooted I was met with an error at the top of my screen that said "your flash drive is corrupted or offline". Because of this Flash Drive Error and because I suspected this possible issue and made sure to purchase a legitimate San Disk USB and not use some I got off Amazon, I decided to replace the USB last night and forgot to look for any diags or logs. I have it back up and running on the new flash drive as of this morning, and if the system crashes again with the crond error, I'll copy any diags and syslogs I can and post again.

Nothing obvious logged there that I can see other than some PCIe errors that should not crash the server, but since it will spam the log, it should still be fixed, this may help:

https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009

Post the new ones to see if there's anything new.