calabriel

I just picked up a B570, do you mind messaging me the same files? I have a test server that I can use without the danger of corrupting my main Unraid machine. Thanks in advance!

Shut down the server to run Memtest, and we have major errors (561 of them and counting, in pass 2). I'm refunding this set of RAM since I got it less than a week ago and I'm getting a new set. Before shutdown, I had 48 hours of uptime and I think everything was stable without Tdarr. I think I'm clear once this RAM is replaced and I find an alternative to Tdarr. Thanks Jorge!

"zpool status -v" showed one error in a Tdarr file. Tdarr is currently off and I don't need that file, so I deleted it and re-ran the scrub. The pool currently shows as clean, my syslog shows normal activity from Unraid and all active containers, and we have the longest uptime in a week or so. I'm still going to Memtest, probably overnight tonight.

Good to know. I'll have to check in on this after work. I did run the ZFS scrub once, before running it showed no errors but after running it showed one checksum error. I'll update in about 12-13 hours when I get back home and can run Memtest and check on the cache error.

I ran Memtest for three passes on the original used RAM in the AMD build, and then for one pass on the brand new RAM I put into the Intel build. There were no errors found. I can run it again on the new RAM to really bake it in. I do have multiple sticks as well and pulling those is easy enough. Having the same/similar issue on two different sets of RAM bought years apart would be an interesting coincidence. Thanks, I'll be back with results!

Hello! I have been using Unraid for about a month and a half now, and have been dealing with random crashes essentially the entire time. I've lurked on this forum and the subreddit, looking to solve my own issues, but have had no luck. My original system was an old gaming PC that I had from around 2017, but now I am running a system with 100% new parts and it is still crashing. My server will crash randomly. Sometimes it stays on for 6 hours, sometimes 30 hours, sometimes 2 hours. I have set up syslog to a local share, mirrored it to my flash drive, but there is no rhyme or reason in the syslog. I found a thread where there was an issue with 1 Gen Ryzen CPUs, so I replaced that with an Intel chip along with most other parts just to do a full upgrade. Still encountering crashes. I have set it up today with just two of my Docker containers running and we are at 9 hours runtime; I am going to leave all my other containers off and see if I can make it more than three days without a crash. If so, I'm going to add a few more containers and see how things go from there. I've also attached my diags as well as my Syslog from the last three days, in case anyone can help me find a reason before my testing ends. Syslog is already being forwarded to the internal syslog server. In this testing, I'd like to also forward the logs from all of my Docker containers to the same share as my Unraid syslog, but I am not familiar enough with Docker yet to know how to do that. I'm doing my own research into that, but if anyone here knows of Unraid-specific commands I would be very grateful. Thanks! EDIT: I have enabled log forwarding from my Docker containers to the syslog server using the following command: --log-driver syslog --log-opt syslog-address=udp://x.x.x.x:514 --log-opt tag={{.Name}} I haven't had a crash since my original post, so I am going to let it ride for a couple of days before enabling other containers. kirane-diagnostics-20240615-2300.zip Syslog_Since_Rebuild.log

I did update host IPs. Everything is the same as it was, 192.168.1.212 for all containers and then default ports from the container configuration. I had proxies for Plex, Overseerr, Tautulli, Homarr, and a Rickroll container all using the same IP address but their own ports. Only Overseerr and Homarr aren't working after the move. Navigating to them via IP address is working, and my DNS records seem to be working because I am getting routed to NPM via DNS.

I have a weird issue - I had to move my entire UnRaid install to a new PC. Got all my containers installed, including NPM. I had proxy redirects set up and working properly, but now that I have set everything back up only three are successfully redirecting. Two of them are routing me to the default NPM page, saying this: In the Proxy Host list, they are set up properly and NPM says the server is online. I ran a cURL command from the NPM container aimed at my binhex-overseerr container, which is one of the failing redirects, and got this response: HTTP/1.1 307 Temporary Redirect X-Powered-By: Express Location: /login Date: Sun, 09 Jun 2024 18:29:19 GMT Connection: keep-alive Keep-Alive: timeout=5 Transfer-Encoding: chunked It was working previously and I didn't change any settings away from the original setup, so I don't know why I'm getting this 307 response. I asked in the binhex support page, but was redirected here because it seems like a NPM issue. Any help would be appreciated, and I can provide logs and things if needed and if I'm told where they are located. Thanks!

I have had some issues with my Unraid not related to Overseerr, but have gotten them straightened out. Now, when setting up Nginx Proxy Manager to point to Overseerr, I get the default page using the URL I have set up. Did a cURL from that container to the Overseerr one and I get a 307 temporary redirect response. Opening the Overseerr container using IP:Port works fine, and NPM shows the server as online. Here is the output from cURL: HTTP/1.1 307 Temporary Redirect X-Powered-By: Express Location: /login Date: Sun, 09 Jun 2024 17:00:35 GMT Connection: keep-alive Keep-Alive: timeout=5 Transfer-Encoding: chunked Both NPM and Overseerr were working correctly previously, for about a month, and now this is the only response I get between the two. I thought I had the same settings that I had before for both containers but I must have missed something to cause this redirect. I haven't found any quick solutions for this, but I don't think it's an issue with NPM as other proxies are working fine (Plexpass, Tautulli, and others) and I don't know if it's just the binhex-overseerr container with a problem because my Homarr container is doing the same thing. If anyone has any suggestions, I'd really appreciate them!