Outer_Zevin

Okay, I've been running memtest for over 48 hours now and it's found no errors. (A friend swears that reseating the RAM before running the test may have solved the problems I was having, I have no idea.) Anyone have advice for further troubleshooting from here if the problem persists?

Thank you for reaching out! My cache drive is a Samsung 970 EVO and when I reformatted the drive earlier in the thread I kept it as XFS just to see what how things went. It definitely lasted longer between problems. How did you go about diagnosing that problem? If memtest gets me no where I will definitely be interested in following up with that. My current RAM is 2x sticks of 16gb Crucial DDR4 unbuffered ECC RAM though. Same brand as your junked SSD. No idea if that means anything.

So while I'm waiting for the results I'm wondering something: I was running into problems every 12-36 hours, so would it be safe to assume Memtest should run for atleast that long before it may encounter errors? I know that most people in other threads here say it run for 24 to 48 hours, so I assume it making it through a few passes without problem isn't always an indicator that there aren't any problems.

This is my first time using memtest, I just need to fire it up and let it run right? No need to configure anything?

Server hanged again, required a hard reset. I attached the logs for today, if anyone sees anything in them that sticks out, let me know. I've done some more reading around the forums for people facing similar issues and currently have the server running memtest86 to see if RAM shows any errors. syslog-10.10.69.6.txt

Yeah, after reading around on the forums I determined that was the best bet. I regularly back up the stuff on the cache so I didn't lose anything important. I reformatted yesterday and have been up for 34 hours with no problems so far.

Okay, I had another problem this morning, the server didn't hang up, I was able to log into the gui and managed to shut down the server from there. All Docker containers showed as stopped with generic icons and no container names. I attached the logs from today below, it seems there was an error with my cache drive or possibly my memory? I'm no expert at reading these things yet, but I did find this thread while googling. If anyone has any input, it is greatly appreciated. If I have to reformat my NVME drive, I'm fine, the only things on there I'd be broken up about losing is backed up on the array and elsewhere. syslogs01022022.txt

Here they are. mother-ship-diagnostics-20220101-1459.zip

Hey, First time posting here, been having a problem with my server recently. Last night it crashed and I could not access the server from the GUI or SSH. I eventually gave up and hard reset the server (don't like to do this), and about 13 hours later, it crashed again presenting the same problems. I’ve got the syslog server set up to back the log contents up to a cache enabled share so if it happens again, I’ll have the logs. Beyond that, I also removed the only docker container I’ve added to my system since this started happening (I doubt it was the problem and I enjoyed it, but it's hardly a necessity, if it wasn't causing problems I'd happily reinstall it). In the mean time, while I wait for the logs to show something, I was wondering if people more experienced can offer me any advice on trouble shooting. Any common problems the should be checked for are appreciated. What tools are available to test for specific hardware, etc. I'll keep doing my own digging on the forums and documentation, but any help is appreciated. I'd like to diagnose the problem as soon as possible so the family won't have to ask me why Plex isn't working. EDIT: Attached Diagnostics mother-ship-diagnostics-20220101-1459.zip