TwoFive5

Sent you a message how to do it

Once it crashes and reboots you won't see anything in the log from before, so nothing would be in there about what caused it. Normally you could turn on syslog server so it would capture those logs before the crash and store them on your server, but that is currently broken until the next release it looks like. https://forums.unraid.net/bug-reports/prereleases/690-beta25-through-690-beta35-syslog-server-broken-error-in-logs-r1003/ So in your case not having a remote computer to log to sucks. I guess the best option like u said would be to go back to a known working version until newer betas come out. Mine seems to crash randomly once a week so hopefully I'll be able to catch what is causing it on mine this time.

That is way more frequent then what I am experiencing. Are you able to get logs before the crash? It might help figure out exactly what is causing it. Not sure if that is an option for you but I was able to get syslog server running and sent the logs to another computer on my network and using Kiwi syslog server to capture them.

If you have the ability, you can run a syslog server on another machine and capture the logs. I am using Kiwi syslog server until this issue is fixed.

Yea I realized that as well. I was able to get syslog server up and running incase it happens again so I'll have logs when it crashes. So far no crashes since my earlier comment. Did you revert back to an earlier build, and did that solve the crashes?

I have also been experiencing issues with system crashes every couple days. I will get a kernel panic and need to reboot the server. Everything was running fine on the previous beta version. Nothing has changed hardware wise, this is on a Dell R730XD with 48GB of ECC Memory. Logs attached if it helps. Also, I am running the Nvidia Driver plugin for a Quadro p2000 if that helps, it seems like on the screen when the kernel panic happens it mentions something about Nvidia. Ill grab a screenshot when it happens again. unraid-media-syslog-20201128-0312.zip

I have been able to get everything set up and it is running great. I'm using the letsencrypt docker for reverse proxy and everything works. The only issue I have, is that I have no problem adding a link to another docker container from my server to the homepage of heimdall, provided it is set up as a subfolder, however I can not figure out how, or if its even possible, to add a link to something set up as a subdomain. For example if something was set up as myserveraddresss.com/plex I would just add /plex in heimdall to link it. But if I wanted to add plex.myserveraddress.com it doesn't really have the functionality to add something this way. I just want to be sure I'm not missing something obvious, and if not maybe it could be added in future releases to use subdomains as well as subfolders. Thanks.

That makes sense, I never knew that was the case with ECC ram.

Yes it is ECC 12x2GB DDR3

It has completed 1 pass with no errors so far

It was an error reported on the server's idrac. I moved some of the sticks around thinking the order I had them in was wrong. Sat Dec 21 2019 06:44:11 Persistent correctable memory error rate has increased for a memory device at location DIMM_A2. Thu Oct 24 2019 17:30:28 Persistent correctable memory error rate has increased for a memory device at location DIMM_A2. I am running a memtest now.

No, there doesn't seem to be any symptoms yet. But this just started a few days ago from what I can tell. Have not done a memtest. I am assuming you mean for the RAM? I have seen an error before on some of the ram sticks but it seemed to go away. I was planning on pulling the RAM and CPU's this weekend to upgrade them.

Ah ok, I thought I had included that. Here is the additional information. unraid-diagnostics-20200224-1617.zip

Hi all, So Fix common problems found a hardware error and suggested using mcelog to find out what the issue is. I have attached my log files below. I am not sure if this is the error it is detecting, but in the log this is the error I keep seeing over and over: Feb 24 09:37:00 Unraid kernel: usb 1-3.2: new low-speed USB device number 116 using ehci-pci Feb 24 09:37:00 Unraid kernel: usb 1-3.2: device descriptor read/64, error -32 Feb 24 09:37:00 Unraid kernel: usb 1-3.2: device descriptor read/64, error -32 I am guessing it might be my USB stick going bad, but that seems strange as it is only 6 months old. All of this is running on a Dell R710 if that matters. Hopefully someone can give me some advice on this. Thanks! unraid-syslog-20200224-1705.zip