Output

All 4 cards are dell cards, only serial numbers differ: In the bios, I cant find a way to control the fan curve, but as I said, 2 cards work fine. Running the commands, to set fan speed control to automatic actually seems to do something: Attribute 'GPUFanControlState' ([gpu:0]) assigned value 0. Attribute 'GPUFanControlState' ([gpu:1]) assigned value 0. Attribute 'GPUFanControlState' ([gpu:2]) assigned value 0. Attribute 'GPUFanControlState' ([gpu:3]) assigned value 0. But it does not change the actual fan values, GPU1 & 2 are fan 41% and GPU2-3 are fan 0% Running commands: nvidia-settings -c :0 -a [gpu:0]/GPUFanControlState=1 -a [fan:0]/GPUTargetFanSpeed=50 nvidia-settings -c :0 -a [gpu:1]/GPUFanControlState=1 -a [fan:1]/GPUTargetFanSpeed=50 nvidia-settings -c :0 -a [gpu:2]/GPUFanControlState=1 -a [fan:2]/GPUTargetFanSpeed=50 nvidia-settings -c :0 -a [gpu:3]/GPUFanControlState=1 -a [fan:3]/GPUTargetFanSpeed=50 output in terminal: Attribute 'GPUFanControlState' ([gpu:0]) assigned value 1. Attribute 'GPUTargetFanSpeed' ([fan:0]) assigned value 50. Attribute 'GPUFanControlState' ([gpu:1]) assigned value 1. Attribute 'GPUTargetFanSpeed' ([fan:1]) assigned value 50. Attribute 'GPUFanControlState' ([gpu:2]) assigned value 1. Attribute 'GPUTargetFanSpeed' ([fan:2]) assigned value 50. Attribute 'GPUFanControlState' ([gpu:3]) assigned value 1. Attribute 'GPUTargetFanSpeed' ([fan:3]) assigned value 50. This results in GPU0 & 1 the fans are running at 50% and GPU2 & 3 fans still at 0% So, the commands do work, but still only for the first 2 GPU's, not for 3 and 4. I'm only running the commands to test why I have this issue, not that I wish to control the fans of the GPUs

I only noticed this because of throttling when running the models, I have not tried to control the fans before finding out that the fans do not run. The cards are all the same with the same firmware on all 4. I tried to control fanspeed to see if I could fix the issue I know it works with 2 cards, since when testing ollama with 2 cards i did monitor fan speed and temps

I'm having some issues with fan control, starting with unraid 7.0.x I've added 2 Dell A4000 GPU's to my Dell R740xd server. Running 2 cards, the fan control state = 0 seems to work, fans spin up with the GPU core temperature. I've now added 2 more Dell A4000 GPU's to my server, with a total of 4 cards. This seems to break fan control, both automatic and manual. Same issue with unraid 7.1 released yesterday. I've tried multiple drivers, latest: v575.51.02, Open Source Driver: v570.144 and Production Branch: v570.144. It does not make a difference. GPU0 and GPU1 seems to have basic fan control, but they are always spinning at around 30%, no matter of temperature. GPU2 and GPU3, the fans never spin at all. This leads to the cards quickly hitting 103c and throttling down to more or less 0 power. I've tried to manually control the fans using: nvidia-settings -c :0 -a [gpu:0]/GPUFanControlState=1 -a [fan:0]/GPUTargetFanSpeed=80 nvidia-settings -c :0 -a [gpu:1]/GPUFanControlState=1 -a [fan:1]/GPUTargetFanSpeed=80 nvidia-settings -c :0 -a [gpu:2]/GPUFanControlState=1 -a [fan:2]/GPUTargetFanSpeed=80 nvidia-settings -c :0 -a [gpu:3]/GPUFanControlState=1 -a [fan:3]/GPUTargetFanSpeed=80 nvidia accepts the settings, but only gpu0 and GPU1 are set to fan speed 80, gpu 2-3 are still set at 0%. Changing to: nvidia-settings -c :0 -a "[gpu:0]/GPUFanControlState=0" nvidia-settings -c :0 -a "[gpu:1]/GPUFanControlState=0" nvidia-settings -c :0 -a "[gpu:2]/GPUFanControlState=0" nvidia-settings -c :0 -a "[gpu:3]/GPUFanControlState=0" only affects GPU0 and GPU1, but they do not go to 0% when cool, they stay at around 30% It seems like vBIOS is not in control of the fan curve but the driver/system is always in control of the fan curve. I only use the GPUS for ollama, ollama is working correctly spreading the models across the 4 GPU's

update 2 servers, the first had no issues at all, the second, that also takes snapshot backups from the first had issues, none related to 7.0 though First issue, the USB drive died when rebooting the server for the update. sector errors so its a HW issue. Then, it took 20 minutes to mount the drives, seemed to be that there where 35000 snapshots for the volumes that where backup from the first server. Now I have a script to remove the snapshots from the backups. Great work with the release!

I've updated to new hardware thats quite beefy, dual xeon platinum, total of 108 cores, 512gig ram. After that I could not start the container, running out of threads or shm memory. Setting shm memory to 2G did not help at all. Solution was to limit the number of puma threads. guess this can be done in the container settings with pinning. Just a heads up when you provide lots of hw to the container

After updating Dynamix Auto Fan Control to 2023.02.05a it seems like the Minnimum PWM value is actually now the max PWM value. I had this set to 45 prior and after the update my server will not spin the fans faster than 45% and then my server shutdown due to drives too hot, setting it to 100% seems to work, current fans speed is now 1666 rpm (66%) , thats a lot less than 100%.

Ive been getting this issue, radom drives that says incorrect key when starting the array. I can start in safe mode without any issues. Been removing plugins and it seems like I can start the array when I remove My servers version 2023.01.23.1223 . Im on Unraid 6.11.5. There is no error in the log either, so my guess is that this is a timeout issue of some sort.

running the following 1 unraid filserver 1 unraid database server ( all databases) and logging 4 proxmox servers with k3s cluster

Been using this for a long time and really like it! I have a server with backplane and I though it would be great if we could bind the port to a slot instead of a drive to a slot? When removing or moving a drive the drive in the slot would change automatically then

Well, Im in the process of removing 4 3gb drives that now have reached EOL with over 7 years of operation. I'm replacing them with 2 10gb drives instead and really would like this built in even if it would take a long time. Doing it manually is just such a pain

+1 , would be great to be able to have Unraid handle the removal of a drive, that is shrink the array. unBalance is a great tool but it does not handle the fact that unRaid can still write to the disk during the process. If Unraid handled the process it could be a one click solution where the system: -Ensures writes are not done to the disk -Moves all data to other disks -New config -notification when drive is removed from the array

upgraded from 6.8-rc7 without any issue. Great work guys!

Nope, I keep all my drives spinning all the time

cool!

Sounds bad with the ipmi issue. When you run igpu and no ipmi do you have issues with fan control?