SimonF

Yes runtime is now being calculated with the patched driver.

The driver maybe compiled for a newer release. My machine is on 6.12 Sep 6 16:00:20 unraid rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release Sep 6 16:00:20 unraid rc.nut: /usr/libexec/nut/nutdrv_qx: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /usr/libexec/nut/nutdrv_qx)

I have removepkg for 2.8.4 and reinstalled 2.8.3 But can try the fix later.

Thanks for the quick fix. Data is now showing again. But the runtime is not now calculated I guess because the battery.runtime is not missing. on previous releases this was needed in the config. [ups] driver = nutdrv_qx port = auto # If not in manual mode, put any additional settings below this line default.battery.voltage.high = 40.40 default.battery.voltage.low = 31.20 default.battery.voltage.nominal = 36.0 runtimecal=300,100,600,50

Should have checked there. Stack trace: #0 /usr/local/emhttp/plugins/nut-dw/include/nut_status.php(111): round('') #1 {main} [06-Sep-2025 09:30:38 Europe/London] TypeError: round(): Argument #1 ($num) must be of type int|float, string given in /usr/local/emhttp/plugins/nut-dw/include/nut_footer.php:53 Stack trace: #0 /usr/local/emhttp/plugins/nut-dw/include/nut_footer.php(53): round('') #1 /usr/local/emhttp/plugins/nut-dw/include/nut_footer.php(106): nut_format_time('', 'seconds') #2 {main} [06-Sep-2025 09:30:38 Europe/London] TypeError: round(): Argument #1 ($num) must be of type int|float, string given in /usr/local/emhttp/plugins/nut-dw/include/nut_status.php:111 Stack trace: #0 /usr/local/emhttp/plugins/nut-dw/include/nut_status.php(111): round('') #1 {main} currently 6.12.5 on this machine.

@Rysz Hi, I have updated to the latest NUT plugin version all looks ok but its failing to retreive values. Sep 6 08:59:26 unraid rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release Sep 6 08:59:26 unraid rc.nut: Network UPS Tools 2.8.4 release - Generic Q* USB/Serial driver 0.45 Sep 6 08:59:26 unraid rc.nut: USB communication driver (libusb 1.0) 0.50 Sep 6 08:59:50 unraid rc.nut: Using protocol: Megatec 0.08 Sep 6 08:59:50 unraid rc.nut: Autodetected 1 as number of battery packs [36/40.20] Sep 6 08:59:50 unraid nutdrv_qx[46374]: Autodetected 1 as number of battery packs [36/40.20] Sep 6 08:59:50 unraid nutdrv_qx[46374]: No charge time specified, using built in default [43200 seconds] Sep 6 08:59:50 unraid rc.nut: No charge time specified, using built in default [43200 seconds] Sep 6 08:59:50 unraid rc.nut: No idle load specified, using built in default [10.0 %] Sep 6 08:59:50 unraid nutdrv_qx[46374]: No idle load specified, using built in default [10.0 %] Sep 6 08:59:51 unraid nutdrv_qx[46374]: Listening on socket /var/run/nut/nutdrv_qx-ups Sep 6 08:59:51 unraid rc.nut: Listening on socket /var/run/nut/nutdrv_qx-ups Sep 6 08:59:51 unraid nutdrv_qx[48431]: Startup successful Sep 6 08:59:52 unraid rc.nut: Network UPS Tools upsd 2.8.4 release Sep 6 08:59:52 unraid rc.nut: listening on 0.0.0.0 port 3493 Sep 6 08:59:52 unraid upsd[48497]: listening on 0.0.0.0 port 3493 Sep 6 08:59:52 unraid upsd[48497]: Connected to UPS [ups]: nutdrv_qx-ups Sep 6 08:59:52 unraid upsd[48497]: Found 1 UPS defined in ups.conf Sep 6 08:59:52 unraid rc.nut: Connected to UPS [ups]: nutdrv_qx-ups Sep 6 08:59:52 unraid rc.nut: Found 1 UPS defined in ups.conf Sep 6 08:59:52 unraid nutdrv_qx[48431]: sock_connect: enabling asynchronous mode (auto) Sep 6 08:59:52 unraid upsd[48498]: Startup successful Sep 6 08:59:52 unraid rc.nut: Network UPS Tools upsmon 2.8.4 release Sep 6 08:59:52 unraid rc.nut: UPS: [email protected] (primary) (power value 1) Sep 6 08:59:52 unraid rc.nut: Using power down flag file /etc/nut/no_killpower Sep 6 08:59:52 unraid upsmon[48501]: Startup successful Sep 6 08:59:52 unraid upsmon[48501]: Warning: running as one big root process by request (upsmon -p) Sep 6 08:59:52 unraid upsd[48498]: User [email protected] logged into UPS [ups] Diags attached. nut-ups (1).dev nut-debug-20250906091234.zip

Which GPU do you have as there is a new option in 7.2 for virgl3d which does allow vms and containers to use the GPU. But the VM cannot use the monitor. You would need to use remote access but will use the GPU for video acceleration. Currently only Intel and AMD are supported, or Nvidia if you use the Nouveau driver.

Click on the green +

If you bind to vfio GPU is not available to the host and containers.

Which OS version are you running and could you provide Diagnostics?

Could you provide a screen print

For each of the PIDs replacing pid with the number for top. cat /proc/pid/cgroup and then inspect the docker based on the value returned. intel-gpu-top: Intel Alderlake_s (Gen12) @ /dev/dri/card0 - 0/ 0 MHz; 100% RC6; 0 irqs/s ENGINES BUSY MI_SEMA MI_WAIT Render/3D 0.00% | | 0% 0% Blitter 0.00% | | 0% 0% Video 0.00% | | 0% 0% VideoEnhance 0.00% | | 0% 0% PID MEM RSS Render/3D Blitter Video VideoEnhance NAME 63278 608788K 495940K | || || || | Plex Transcoder root@computenode:~# cat /proc/63278/cgroup 0::/docker/563dfa688110d5112bbd1c4c44034e9ba27b179163e4b0c258611120f252100f root@computenode:~# docker container inspect 563dfa688110d5112bbd1c4c44034e9ba27b179163e4b0c258611120f252100f | grep Name "Name": "/Plex-Media-Server", "Name": "no", "Name": "btrfs" "DNSNames": null root@computenode:~# docker container inspect 563dfa688110d5112bbd1c4c44034e9ba27b179163e4b0c258611120f252100f | grep icon "net.unraid.docker.icon": "", root@computenode:~#

No the GPU top file I attached. If you put on you system and run GPU top it should show apps even for XE.

GPU Stats should show app in use as a icon, but that is all you can get currently. cat /sys/kernel/debug/dri/0000\:00\:02.0/clients will show the processes using the GPU which GPU Stats should use. Change PCI ID to match your device. JF should show HW transcoding I think.

Kernel 6.17 has not been released it is still in RC. If it becomes LTS and when ZFS supports it would likely been in the next Unraid release. But the sriov I believe is only going to be support on Battle mage pro cards. ARC cards are not supported. https://www.phoronix.com/news/Intel-SR-IOV-Only-For-Arc-Pro

Can you provide screen prints of disks page and the config page? DM if you prefer.

B570 uses XE driver and intel_gpu_top cannot be used. XE does not expose usage currently. Limited data is available. Things like fans added in later kernels.

The names don't match the application names in the plugin. I am refactoring the detction code based a PR from @Peuuuur Noel If you want to try the current test release. https://raw.githubusercontent.com/SimonFair/gpustat-unraid/refs/heads/Dynamic-App-Support/gpustat.plg You may need to do CTRL-F5 in dashboard. You can install in plugin install tab over top of existing. This is only supported on 6.12+

Select your GPU in Unit ID, if on 6.12+ you can select multiple. + Apply

@hoogstaddie Does the gputop provide any usage stats on your card. gputop

Maybe unlikely to change your issue as the default was changed in kernel 6.12 onwards. Default in the kernel is thunderbolt.host_reset=1 but we found this to break things if the device is connected at boot. In 7.2 it is patched to reset=0. Maybe worth trying as may help/

This may not fix you issue, but try the fix in this post. https://forums.unraid.net/bug-reports/prereleases/700-beta1-thunderbolt-drive-bay-not-detected-no-drives-visible-after-upgrade-r3056/#findComment-34784 It has been added into 7.2 as a default.

Bit I to build info as nothing like intel GPU top for xe. There is not a way to get work loads for any other stats. These may be able to be added when presented to sensors or sysfs. Unless you have a way to get this info

Can you post /tmp/inteljson

You may need to do CTRL F5 on dashboard as may be caching code.