IamSpartacus

Which board? I have tested on X10 and currently have an X11. The plugin is based on specific ipmi commands for different models. If your bmc firmware isnt updated or consistant with other models this may affect it also. Recently I was made aware also at least one bmc firmware puts spaces in the fan names. The plugin expects FANA, FAN1.... I haven't implemented an update yet to trim out the spaces yet. The full speed setting is intended so the bmc doesn't try controlling the fans while fan control is running. This board with the latest BMC firmware. No spaces in the fan names. Oh so it should be set to full speed in IPMI and then Unraid should lower the fan speeds based on the settings in Fan Control? EDIT: I got this working. Now that I know full speed is intended, I just had to fix an issue on my side that was forcing one of my fans to keep ramping up and down. Even though I manually set thresholds really low (200) my fan control setting was actually causing the fan to go below that causing it to ramp up to full speed. Once I set a high minimum fan speed % it fixed my issue.

I can't say that I have sorry.

Install IPMItool via nerdpack and do it via CLI. https://www.ixsystems.com/community/threads/how-to-change-sensor-thresholds-with-ipmi-using-ipmitool.23571/

I don't have the ramping issue, that is usually resolved by fixing your thresholds which is pretty easy to do. My issue is it seems I can't use the Fan Control in Unraid because any time it attempts to interact with the fans it forces Supermicro to change it's fan mode to full speed.

So I bought a new Supermicro motherboard and this plugin doesn't appear to interact with the BMC correctly. As soon as I enable Fan control, it automatically changed the Fan Mode in SuperMicro's IPMI settings to Full Speed. If I then change that to Standard or Optimal, the fan's return to normal operation as per SuperMicro's settings but do not adjust as per the fan control settings in Unraid. Has this happened to any one else in the past and know of a work around?

Is it possible to run two backups on a schedule? Ideally I'd like to run one weekly backup encompassing all appdata and then a daily that only encompasses the "vital" appdata.

Did you have the same issue in 6.8rc1-3? When I upgraded to rc1 it seemed to fix my issue and I'm now running rc3 with no issues.

It appears the CPU Scaling Governor "Power Save" setting no longer is functioning in 6.8. It keeps the CPU scaled down and does not ramp it up on load. I have to set to "On Demand" for it to scale up.

Is there a permanent fix for this? Seems this has to be done every time on certain VMs (ie. MacOS VM).

Oh hmmm, it finished a lot quicker than I thought. I was looking at the time going up and that was the time of the movie not the time left. When it finished, I didn't see and ending stats like you showed though.

GTX 1660. Tremendous value GPU for HW acceleration. Can do 20 1080p > 720p transcodes or 5 4K > 720p transcodes at once. Lower power usage. All for $220.

Hmmm I wonder why my FPS is so low then. It's been holding steady at 169 FPS the entire time. I have heard the new Turing GPU's are a little slower and high quality but this seems really slow.

And what kind of GPU are you using?

The one line worked. What kind of FPS do you get with that command and what GPU are you using? Trying to compare to my GTX 1660.

With or without the quotes like you have in your initial command? EDIT: Nvmd, it worked without the quotes. I guess I needed to remove them in my above command?

Yup. NVENC works fine in your handbrake container and in both Plex and Emby. Hmmmm.

Running this command on my system gives me the following error. Any ideas? docker run --rm --runtime=nvidia -v "/mnt/user/Downloads/handbrake/watch:/input:rw" -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-90490eba-cd03-39f1-d641-3360df982f5a' djaydev/ffmpeg-ccextractor \ > ffmpeg -hwaccel nvdec -i "/input/test.mkv" -c:v hevc_nvenc -c:a copy "/input/test1.mvk" docker: invalid reference format. See 'docker run --help'.

Sorry, quoted the wrong post.

The mover is absolutely going to affect cache since it's going to be doing reads off of cache. So if you have trying to play a 4K remux off cache at the same time the mover is reading from cache I'm not surprised you are having issues.

Thanks for the quick response!

@fryfrog I see you've been testing v3.10.5 since about 13 days ago? Stable? If so, wanna move it to the latest tag?

Has anyone successfully gotten the inputs.nvidia_smi plugin working in telegraf? Even with the --runtime=nvidia extra paramater and the NVIDIA_DRIVER_CAPABILITIES/NVIDIA_VISIBLE_DEVICES variables I can not get it to work. I just get: Yet inside the container I can see nvidia-smi in /usr/bin. EDIT: Turned out to be the alpine repo. Changed to latest and now it works.

I've created a bug report so Limetech can hopefully address this issue.

Ok so even trying to do multiple scatter jobs doesn't seem to work. The behavior you describe above is not happening. No matter what, the data is getting moved to disk8 even though it does not have the most free space. So I'm not sure if I'm doing something wrong or if Unbalance will just always start with the first chosen disk regardless of free space available.