fabienm

Hi, sorry for the delay in my answer. The IP address of my PC is 192.168.1.165. It seems the issue was due to the fact that this was connected to Tailscale. I deconnected it from TS, and I was then able to access the WebGUI. But this is odd: when connected to TS, I'm still able to access other container WebGUI, through their local IP address, but not sabnzbd.

Hi, I'm experiencing an issue since upgrading to Unraid 7 RC2 a few hours ago: when trying to reach SABnzbd WebGUI, I encounter a connection time out. I've tried restarting the container, deleting and recreating it, but it did not solve the issue. I've taken a look at the container log, but did not see anything worrying (but I don't have technical skills, so I might be missing something). I've attached the log to this post. Any support would be much appreciated. container_log.txt

So I upgraded to Unraid v7 beta, everything went smoothly, but the issue remains the same: first parity-sync speed plummets after a few % completion. Is there a way to perform a hardware diagnostic in order to identify the culprit?

Will I be able to downgrade from beta to regular version if needed?

So I've changed the RAM and performed a memtest: everything is fine with this new RAM. When trying to setup parity, I encounter the same issue I before: after a couple of hours of parity-sync, speed is declining to a few MB/sec. I attached the new diagnostic files to this post. What could be the reason of this issue? newnas-diagnostics-20240909-1104.zip

By "the results are not good", I didn't mean it was a false positive, but that the outcome of the tests were not good for my NAS I'll cancel the parity sync and turn off the NAS until I can check the BIOS settings or replace the RAM. Thanks for your help!

Thanks for your answer. I will not have physical access to the server before end of August, so I used the "live memory tester" plugin to perform some tests, and I guess the results are not good, right?

I've just setup my first Unraid server, and things were going reasonably well until I tried to initiate a first parity sync. After ~18 hours, the process is stuck at 42%, and the 'estimated finish' is +685 days 😮. It seems I can't pause or cancel the sync. I've rebooted the server, but the same issue appears again. I've attached the diagnostic file to this post, any help would be greatly welcomed. tower-diagnostics-20240817-2348.zip