July 19, 20196 yr I created a post a while back about the same thing but didn't attach any syslogs or anything. My server keeps crashing every now and then. It seems like the more I'm actually using it the faster it crashes, but sometimes it crashes with just Plex and a few Deluge docker instances running. I've attached my towerdiagnostics.zip file with everything in it. I also ran the Fix Common Problems plugin in troubleshooting mode because once it crashes I can't access anything: no GUI, no shares, no VMs and I can't even access the Console Command Prompt, but the hardware seems to be running. tower-diagnostics-20190718-2205.zip
July 19, 20196 yr Community Expert I almost hate to answer these threads anymore because the solution is so difficult to find. Basically, it is almost always either hardware or a misconfiguration of a plugin or Docker. You probably want to eliminate one basic hardware issue first. Open up the case. Clean all the dust and dirt out of it. Pay attention to the intake ports (and filters, if any), exhaust ports, and cooling fins. Make sure that all the fans actually work. Configuration issues. Check your settings on all plugins and Dockers to make sure that they are writing any data or 'skratch' files to a physical device. i.e., /mnt/diskX/ /mnt/cache/ /mnt/user/ or /mnt/user0/ Any other location will be to the RAM disk that Unraid uses to store itself in! Filling up that RAM disk will virtually guarantee a crash! You are also using an old version of Unraid. The latest version is 6.7.2 The reason I am mentioning this at this point is that there is a powerful new troubleshooting tool built into this version-- a Syslog Server! This server can easily be setup to mirror the syslog to the flash drive in real time.
July 19, 20196 yr Author I understand what you mean, I'm usually very good at troubleshooting shit like this and rarely ask for help. I've changed sata cables, power supply and ram, they only thing that I haven't swapped are the drives and mobo/cpu for obvious reason. I'm sure my dockers aren't writing anything to a physical device directly, except to an unassigned drive I have connected, this shouldn't be causing the issues right? I will update the system so I can use that new troubleshooting tool. Thanks for the reply.
July 19, 20196 yr Test the ram, same just happened to me last week. I was seeing kernel panics. It was making me crazy. Two sticks just went bad one day. I pulled the ram and all is well.
July 19, 20196 yr Community Expert There is also the memory. If it is not ECC memory, You can run memtst from the boot menu for twenty-four hours. Also, overclocking is not recommended for Unraid.
July 19, 20196 yr Community Expert 7 hours ago, Frank1940 said: Check your settings on all plugins and Dockers to make sure that they ARE writing any data or 'skratch' files to a physical device. i.e., /mnt/diskX/ /mnt/cache/ /mnt/user/ or /mnt/user0/ Any other location will be to the RAM disk that Unraid uses to store itself in! Filling up that RAM disk will virtually guarantee a crash! You seem to have taken his meaning exactly the opposite of what he said 1 hour ago, Tuf Inside said: I'm sure my dockers AREN'T writing anything to a physical device directly, except to an unassigned drive I have connected, this shouldn't be causing the issues right? Also, a path that is intended for an Unassigned Device will actually be in RAM if that device isn't mounted.
July 19, 20196 yr Author 4 hours ago, daniel.boone said: Test the ram, same just happened to me last week. I was seeing kernel panics. It was making me crazy. Two sticks just went bad one day. I pulled the ram and all is well. I swapped the RAM a while ago, crashes were happening before and after the swap. 4 hours ago, Frank1940 said: There is also the memory. If it is not ECC memory, You can run memtst from the boot menu for twenty-four hours. Also, overclocking is not recommended for Unraid. It is ECC memory. I've never overclocked this server. 3 hours ago, trurl said: You seem to have taken his meaning exactly the opposite of what he said Also, a path that is intended for an Unassigned Device will actually be in RAM if that device isn't mounted. Yup, thanks for the clarification. The device is in fact mounted, I can see it through the network and I run my Plex docker container from it. Not sure what else I should test Edited July 19, 20196 yr by Tuf Inside Spelling.
Archived
This topic is now archived and is closed to further replies.