macieksoft

Running 2026.06.01.1911 version of Unraid Connect, still in the same loop after restarting the API. Are there any logs that would help?

I also have this issue, same loop. Something broke back in 7.2.3 I think and I didn't get any notifications for upgrading the server. Eventually after reinstalling the connect plugin yesterday my server notified me that 7.3.1 was available, but 7.2.3 wont let you update without signing in and I was still stuck in that loop. Manually updated to 7.3.1 and still have the sign in loop. I have tried different browsers, devices and incognito mode/normal mode, nothing works.

I'm having the same issue, 4K HW tone mapping on my i3 10300 worked before, but now its broke

I have not had an issue since adding default_ps_max_latency_us=0 , but unRAID still things the drive hits 84c randomly for exactly 30 min or 60 min. I originally thought it was the drive and talked to Samsung, they were willing to pay for a return lable and send a new drive under warranty, you might be able to do that, but you will not have the drive for a while. I would definitely go with another drive next time.

I definitely think this is an issue caused by 6.10 rc2, I haven't had any more issues after adding append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 but my Samsung 980 was fine for months before the update. It's been confirmed by others that the temperature sensor is bonked with 6.10 rc2 and the drive disconnecting from the pool could be a side affect of rc2 as well.

Thanks, I added that and rebooted the server, ill keep an eye on it. Its odd that it just started to happen though, I wonder what's causing it. I had mitigations off so I think this is still ok: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 mitigations=off

Hello, I started to get errors with my cache pool that the device is missing (Samsung 980 NVMe). The device is still there and can be read from but not written too. If you restart the system, the device disappears from the cache pool. If you shut down the system then turn it on it comes back and works normally (can read/write). This is the second time I have gotten this issue in the past 4 days, can someone take a look at the logs and see if something is up? Thanks. z490-diagnostics-20211206-1216.zip

I have the 1TB version.

Ya, the regular 980 (not the pro).

I also noticed it stays at 84c for exactly 1 hour. I have Pushbullet send me notifications and it's consistently going from 39c to 84c for 1 hour before dropping back to 39c.

I'm having the exact same issue with a z490 and Samsung 980. I have a massive heatsink with thermal bad and the temps go from 39C to 84C randomly. The actually drive is not very hot, so this seems to be an software issue reading the temps.

Was getting the constant parity check with 6.9.1, set the timeout to 100 seconds and its fixed. This is definitely a bug.

Great instructions, got HW transcoding for my i3 10300 working Thanks!

Hmm something else on my end then. On 2.0.3 im getting "error connection timed out" on all trackers. On 1.3.15 its fine though. Ill be on 1.3.15 for a while anyway but ill check in later to see if its working again.

None of my private trackers approve the client yet lol, ill be going back. I wasn't able to connect to any trackers though, including public on the new version....

Cant aces the web ui for lets encrypt and nextcloud but they both are functioning properly. Anyone know here I might have messed up? Im assuming it has to do with the 444,443, and 1443 changes.

Any file I try to download over 2gb just fails. I see some people talking about a proxy setting in lets encrypt (im also using this) but no actual answer on how they fixed it. Anyone know the solution to download limit? Edit: might(?) be the " proxy_max_temp_file_size 2048m;" in the lets encrypt conf file for next cloud. Edit2: Yup that fixed it ^ set it to 20480 for 20gb max size, could prob set it higher if need be.