andrebrait

Would it be possible to support different temperature ranges for different sets of drives? EDIT: for the same fan e.g. I have HDDs and SSDs being cooled by the same fan and I'd like the fan to react to temperature changes in both, but the range of temperature for my HDDs is 30~45ºC (25% fan speed to 100% fan speed) and for the SSDs that range would be from 40~65ºC. I assume, other than adding the ability to add an arbitrary set of Drive Selector + Temperature Range elements on the GUI, this would require the percentage formular to change to something along the lines of (pseudo-algorithm): let x = select_speed(hdd_temp, 30, 45, idle_hdd_speed) let y = select_speed(ssd_temp, 40, 65, idle_ssd_speed) let final_speed = max(x, y)

I have moved my license to my server's fTPM during the BETA and I never looked back... Until now, because I suspect I have a bad CPU and I need to replace it, which means the fTPM will be inaccessible/have to be reset. I bought a discrete TPM module in anticipation to the fact I'll very likely have to move the license to it. So, what do I do?

@JorgeB it turns out it was a failing power supply. The Corsair SF750 Platinum I was using was probably having a hard time dealing with the bursty loads caused by Docker's recurring maintenance tasks/checks so it ended up happening disproportionally there, but the machine was also turning itself off. It's been running like a champ since I disabled all power saving features possible to confirm the PSU had issues with low power modes.

I think I found the issue. It seems my power supply was failing and the crashes were triggered by it being unable to handle the CPU bursting and then going into a low power state. It's been working flawlessly for a while now with all C-states/SpeedStep disabled.

I wasn't expecting another update to Docker at this point, but 29.4.2 has some additional hardening against CVE-2026-31431 (a.k.a. CopyFail)

My tailscale on unRAID has been crashing or something and it requires a reauth to come back up. It then works for a bit and goes down again.

@JorgeB this is resolved. Upstream bug in Docker and interaction with healthchecks.

After multiple days of uptime now, I have confirmed the crash was due to some healthcheck in a container. I disabled healthchecks for all containers both via --no-healthcheck in the additional arguments, for unRAID templates; as well as healthcheck.disable: true in the compose yaml, and all crashes are gone. I'll begin enabling healthchecks one by one again, but it's scary this can ever happen. Going to report the issue to Docker (moby) as it shouldn't be possible for a bad healthcheck toncause the daemon to crash, after all.

The license will still be specific to your current USB drive. The USB drive must be connected for the license checking, but it won't be read/written besides that. If you want to remove the USB drive, you need to port the license to a TPM (either a hardware TPM or a firmware TPM, both will work; but a firmware TPM is linked to the system CPU) As for settings and whatnot, the wizard that does the process for you copies everything for you. You'll have 100% the same system, just booting from a different device.

@JorgeB any idea whether containerd storage backend for Docker will be in 7.3.0 for e.g. beta 3 or later? The zMr for it was merged so I thought it would come to 7.3.0.

Well, yes, it was a healthcheck. Somehow Docker is not handling it well. Only after I removed all health checks it stopped breaking. docker (1).log (2).txt

The latest logs I got seem to indicate a nil pointer is being dereferenced when trying to run the health check for my crowdsec container. I have reviewed all my healthcheck commands to ensure they exit properly and timeout properly.

It's also been stable for me. Just waiting for the containerd image store support and I'll likely move all my NAS'es to 7.3.0.

Nope. It crashed again. I'm lost. Gonna try enabling debug logs for dockerd.

It seems to be somehow connected to Tailscale. I'm taking the time to debug it, but every time my rsync job over Tailscale failed, Docker also crashed. I disabled Tailscale on unRAID, relying on my Firewall to do the routing for me, so let's see.