June 23, 20197 yr Any tips on how to troubleshoot this error? I can't access the log and/or machine at all, since the log is only in memory there's no way I can actually see the process causing the crash. Any tips for this? It's been happening with more and more frequency
June 24, 20197 yr Community Expert Give us a description of your current setup-- CPU, RAM, Plugins installed, VM's and Dockers. There have been several folks who have had similar problems. Sometimes the problem is that one of more of the dockers or plugins are storing files on the RAM disk that Unraid uses for the installation of its OS. All of these file paths should point to /mnt/user/ or /mnt/cache/ If any do not, it is probably using the RAM disk...
June 27, 20197 yr Author No VM's and Dockers. Running an ECS A88GM-A2 motherboard, AMD Sempron 145 @ 2.8 GHz 8 GB Memory (4 x 2GB) Plugins are: CA Auto Update Applications CA Backup / Restore Appdata Community Applications Dynamix Active Streams Dynamix Cache Directories Dynamix S3 Sleep Dynamix System Information Dynamix System Statistics Fix Common Problems Nerd Tools Network Statistics Preclear Disks User Scripts
June 27, 20197 yr Community Expert What nerd tools are you running? I seem to recall that there are a couple of the included tools are not compatible with later releases. You have a pretty 'Plain Jane' setup. One thing to do is to run a memtst (Boot menu option) for twenty-four hours. By the way, the latest release does have a new troubleshooting tool which will capture your syslog to your flash drive in real time. Ideal for these types of problems!
June 27, 20197 yr Author Looks like I'm running screen 4.6.2 (up to date) tmux 2.8 (need to update) utempter 1.1.6 (up to date) vnstat 2.1 (need to update) I'll update my nerd tools and also take a look at the new release as well.
July 8, 20196 yr Author @Frank1940 Thanks for the advice. Updating unRaid seemed to have fixed the issue.
Archived
This topic is now archived and is closed to further replies.