sdchoni

To temporarily resolve this issue, you can use the previous release of Nginx Proxy Manager. Edit the app and change the repository to: jlesage/nginx-proxy-manager:v25.09.1 Once this is resolved, you should change it back to: jlesage/nginx-proxy-manage

To temporarily resolve this issue, you can use the previous release of Nginx Proxy Manager. Edit the app and change the repository to: jlesage/nginx-proxy-manager:v25.09.1 Once this is resolved, you should change it back to: jlesage/nginx-proxy-manage

Used a new USB for my unraid drive and that solved the issue. I think it got turned off in a thunderstorm or something, which probably caused some corruption, and a fresh install (using a backup) fixed it.

It's 8x, so I should be good there. I've limited the share to 1 drive. I'll try running it again and will report back (with log files) if it crashes again.

Could this be because I have the Volume Size Limit set to 8TB in SMB Security Settings? I wanted to have a 1-2 copies for each backup, but didn't want it taking up all my drive space. Currently the share is 7.89TB

It has the last 2 days when I have attempted doing a full (2tb total, 1tb for each drive on my windows computer) backup. Array. Pool is only 250gb so I previously set the share to be array only.

Hi All, Diagnostics and most recent log file attached. syslog-192.168.1.95.log sdchonitower-diagnostics-20250507-1144.zip When I go to back up my windows computer using Macrium Reflect Unraid will stop responding after ~2.5hrs. When I press the power button on my unraid server the display outputs the below (sorry for the picture. I need to buy a DVI to HDMI adapater and start running this through a capture card....) and does not shut down unless I do a forced shutdown. When it reboots, my bios doesn't see the flash drive unless I reboot the computer again. After rebooting, it successfully completes a parity check with 0 errors (this is the time this has happened). I originally thought this was related to docker failing and/or b/c of the FTPGrab Docker I was running, but I have not been running the FTPGrab Docker and the most recent logs (attached) do not mention the cache being full at the time of failure (it does mention it being full at other points though? I ran the mover a few hours ago to make sure this would not happen). Side note: I'm aware of the UPS failing error message. I'll get to that later....

I put all 4 sticks back in and I get errors again (more specifically: I ran a correcting parity check and got 1 error , ran a non-correcting parity check and the kernal crashed , and ran another correcting parity check and got 3 errors) When running a diagnostics on my windows machine firefox uses all my ram and then crashes (I do get a chuckle that there is a running theme with ram here lol). I guess it doesn't like 32gb of DDR3 ram for some reason? I will downgrade to 16gb for the time being (tbh, I only upgraded b/c we were running a palworld server at the time and it had a ram leak. 16gb has been fine without that) and I will look into a system upgrade in the future.

Alright, so I stuck in 2 sticks, ran a parity check, got 3 errors. Ran a correcting parity check got 0 errors! I then put in the other 2 sticks of ram, ran a parity check, and got 0 errors. Maybe it's my DIMM slots or maybe I just needed to re-seat my ram? I guess I'll put all 4 sticks back in, try running another parity check and see what happens? I tried downloading the diagnostics, but it crashes my browser after it uses up all of my ram.

Alright, so according to my archived notifications (which I believe is correct) I have run a correcting parity check, non-correcting, correcting, and non-correcting (each with a different amount of errors each time). According to History, I have run 3 non-correcting parity checks? I have attached my diagnostics. The Server has been on since I ran MemTest on Aug 27th sdchonitower-diagnostics-20240903-1341.zip

MemTest86-Report-20240827-141537.html Pass with 0 errors.

Okay, I ran it for 24 hours and 5 passes and it showed 0 errors. I pressed ESC to close instead of c, so it did not save the HTML output. My bad on that one.... EDIT: Apparently I was using an ancient version of memtest, version 4.37. I'm going to run it again using a newer version just to be safe.

Hi All, Every time I run a parity check I get a different number of errors each time (never 0). I dug through some earlier posts of people having similar issues and have ran a correcting parity check followed immediately by a non-correcting parity check and it gave me a different number of errors. Please see attached for Diagnostics, screenshot of my parity check history is also attached. sdchonitower-diagnostics-20240825-1714.zip

For some reason, files would not show up for me in the Appdata folder. I tried several hours of troubleshooting and the only way I was able to fix this was by un-installing and re-installing the app. FYI

This Community Application rocks!!! I was able to follow some of Blackout6vi6 steps above but instead installed Palworld and it works great (except for a memory leak issue, but that is a Palworld problem, not a Docker/AMP/Unraid problem). B/c of the memory leak, we have to restart the server every once in awhile so it doesn't crash my computer.