dumbestsmarthouse

Not sure if this is driver related, but I've been having some strange issues with my 5060 Ti. I was on 7.1.4 and it was working fine, but the issue popped up about a week or two ago. I just updated to 7.2.0 and with it the Nvidia driver (was on v575.57.08, now on v580.95.05) to see if that would fix it, but no dice. Before the issue popped up, the GPU would idle at 5-6W at P8 with power throttling on. Suddenly, it is now "idling" at 10-22W, with the fan spun up to 42%, the load between 0-2%, and P0 power state. I check nvidia-smi and nvtop and they show nothing is using the GPU. SMI shows 10W, but the GPU statistics widget on the dashboard shows 22W. nvidia-smi Sun Nov 16 22:20:27 2025 +-----------------------------------------------------------------------------------------+ | NVIDIA-SMI 580.95.05 Driver Version: 580.95.05 CUDA Version: 13.0 | +-----------------------------------------+------------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+========================+======================| | 0 NVIDIA GeForce RTX 5060 Ti Off | 00000000:01:00.0 Off | N/A | | 45% 26C P0 10W / 180W | 0MiB / 16311MiB | 0% Default | | | | N/A | +-----------------------------------------+------------------------+----------------------+ +-----------------------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=========================================================================================| | No running processes found | +-----------------------------------------------------------------------------------------+The strange thing with nvtop, though, is that when I run it and leave it running, the GPU utilization goes back to the regular 5W idling. Once I exit nvtop or the terminal, it pops back to 22W. I've tested this through multiple reboots, disabling/re-enabling docker, shutting off my Home Assistant VM, and nothing moves the dial. Even with the array stopped its still sitting at that state. Diagnostics below, I did a quick scan for any issues and couldn't really find anything: https://drive.proton.me/urls/WRRR0D83H4#ofF0g6IG4OBx

Just wanted to pop back in and say I found the culprit - the Home Assistant Unraid integration was using the API to poll stats on hard drive status/temp/etc, and that’s what was causing them to always stay spun up. Disabling it immediately solved the issue!

+1 to this, I went through the process of disabling everything to check if a container or VM was writing to the disk but no luck. Any time I try to spin down disks they start back up witching 5 seconds. I’ve used the File Activity plugin (which shows nothing is using the disks) and the cache directories plugin (which by default waits for an idle time with the disks, which isn’t happening because something’s being written every ~5s, I can hear the thunk of the disk on an even cadence).