Laov

Apparently it went away after update to 7.3... Weird...

ZFS is still barely integrated with Unraid... Like the only thing you can natively do with the GUI is delete an empty, non snapshotted top level data set. That is about it... No UI for manual snapshots any snapshot will brick UIs ability to delete the folder or at least any nested dataset with a snapshot will (I only tested those)... Honestly if it wasn't for this plugin I wouldn't be using ZFS at all.

Frick... With the release of 7.3 this is even more of an issue... ZFS master sits itself in between pool devices and boot pools. Since you can now use the internal boot pool as a data partition having something sit in between is VERRY annoying... Is there any way to force ZFS master down bellow the Boot pool?

For a while I've noticed that ZFS master information is kinda fcked up on the Main tab. Is it on my side somehow? Updates don't seem to resolve it...

Why is this plugin no longer in community apps? If I remember correctly there was 2 different IT87 plugins? Was one of them removed? The current one I have installed seems to not be linked with the one in community apps...

It would be really nice if Unraid had a UI for users to manage (start, shutdown, restart, snapshot) VMs. To be precise user logs in with their unraid share credentials and if assigned can control specific VMs. (maybe dockers as well). Maybe this is a bit off topic as mostly virtualized hardware is discussed here but hey I'm literally looking for a "VM manager" for non root user!

You have posted a verry vague description... Generally speaking it should work if you know what you are doing networking wise and know how to solve routing issues... If you'd post a more complete description of your setup along with routing involved maybe someone would be able to give you more input...

Can you post your settings for: network settings -> routing table tailscale Managment access? Along with trace route for when you are unable to access the server.

I know the limitations of fan RPM and I know it is not the case as the same fans were plugged on different headers yielding different results. Issue was due to it8792 chip and its implementation on unraid. I just switched to a header that is on it8688 and solved all of the issues. So most likely case is that the driver has an issue with this chip. Regarding fan speed not displaying - apparently playing around with PWM causes issues with the driver which in turn can brick systemp temps plugin from loading the proper driver to display RPM. System restart usually fixes that... Anyway summary for PWM on unraid - pray that it works and don't touch it if it does. If it does not - 1st try server restart.

You should be able to just do this using tailscale IP or DNS (Might need use tailscale DNS option) and SMB share. Mount the share and you should be able to point to it from docker...

I recreated the VM. Posting the diagnostics in case you can see something as to why it happened. Server was not restarted since. Happened around 2025-12-13 13:23:28 I also noticed that one of my docker containers was not starting due to errors in /etc/localtime. The reason was that unraid timezone information was lost during the update 7.1.4->7.2.2. Once I set the correct timezone it started up. Not sure if it is related to VM issue. dataserver-diagnostics-20251214-1527.zip

Hello, After update to 7.2.2 I was trying to change some VM settings. I disabled auto start and tried to update RAM capacity of my VM. The update process hung and then my VM disappeared from VM manager UI. Any way to restore its settings? Or should I just recreate it and point it to the correct disk? This is the libvirt log: 2025-12-13 13:23:28.807+0000: 33765: info : libvirt version: 11.7.0 2025-12-13 13:23:28.807+0000: 33765: info : hostname: DataServer 2025-12-13 13:23:28.807+0000: 33765: error : qemuProcessQMPLaunch:10104 : internal error: Failed to start QEMU binary /usr/local/sbin/qemu for probing: Start/autostart is disabled in VM settings. 2025-12-13 13:23:28.807+0000: 33765: warning : virQEMUCapsLogProbeFailure:5842 : Failed to probe capabilities for /usr/local/sbin/qemu: internal error: Failed to start QEMU binary /usr/local/sbin/qemu for probing: Start/autostart is disabled in VM settings. 2025-12-13 13:23:28.811+0000: 33765: error : qemuProcessQMPLaunch:10104 : internal error: Failed to start QEMU binary /usr/local/sbin/qemu for probing: Start/autostart is disabled in VM settings. 2025-12-13 13:23:28.811+0000: 33765: warning : virQEMUCapsLogProbeFailure:5842 : Failed to probe capabilities for /usr/local/sbin/qemu: internal error: Failed to start QEMU binary /usr/local/sbin/qemu for probing: Start/autostart is disabled in VM settings. 2025-12-13 13:23:28.811+0000: 33765: error : qemuAutostartDomain:187 : internal error: Failed to autostart VM 'Windows 11': internal error: Failed to start QEMU binary /usr/local/sbin/qemu for probing: Start/autostart is disabled in VM settings. 2025-12-13 13:33:50.212+0000: 33753: error : qemuProcessQMPLaunch:10104 : internal error: Failed to start QEMU binary /usr/local/sbin/qemu for probing: Start/autostart is disabled in VM settings. 2025-12-13 13:33:50.212+0000: 33753: warning : virQEMUCapsLogProbeFailure:5842 : Failed to probe capabilities for /usr/local/sbin/qemu: internal error: Failed to start QEMU binary /usr/local/sbin/qemu for probing: Start/autostart is disabled in VM settings. 2025-12-13 13:33:50.217+0000: 33754: error : qemuProcessQMPLaunch:10104 : internal error: Failed to start QEMU binary /usr/local/sbin/qemu for probing: Start/autostart is disabled in VM settings. 2025-12-13 13:33:50.217+0000: 33754: warning : virQEMUCapsLogProbeFailure:5842 : Failed to probe capabilities for /usr/local/sbin/qemu: internal error: Failed to start QEMU binary /usr/local/sbin/qemu for probing: Start/autostart is disabled in VM settings.

Hello, I am having weird issues with PWM, and fan speed sensors. I expect it is related to the drivers. How to find out which driver I need to use? System temp plugin detects it87 k10temp. However I am having weird issues. I have 3 fans connected on different mobo headers. Sys fan 1,3, CPU. Issues: Unraid only detects fan speed for sys fan 3. PWM control only works at 1000 - 1700 rpm. Fan does not slow down bellow 1000 rpm. Mobo: Gigabyte aorus b550 v2 I expect that my issues are due to wrong drivers? I'd like to be able to see all 3 of my fans and have my case fans spin up only when my disks are active... FanCtrl plus seems perfect for this task yet my fans do not spin down bellow 1000 rpm... pwmconfig command returns the folowing: Found the following devices: hwmon0 is acpitz hwmon1 is k10temp hwmon2 is nvme hwmon3 is nvme hwmon4 is nvme hwmon5 is it8792 Found the following fan sensors: hwmon5/fan1_input current speed: 0 ... skipping! hwmon5/fan2_input current speed: 0 ... skipping! hwmon5/fan3_input current speed: 1695 RPM Testing pwm control hwmon5/pwm3 ... hwmon5/fan3_input ... speed was 1695 now 1136 It appears that fan hwmon5/fan3_input is controlled by pwm hwmon5/pwm3 Would you like to generate a detailed correlation (y)? y PWM 255 FAN 1358 PWM 240 FAN 1149 PWM 225 FAN 1083 PWM 210 FAN 1053 PWM 195 FAN 1040 PWM 180 FAN 1036 PWM 165 FAN 1027 PWM 150 FAN 1022 PWM 135 FAN 1022 PWM 120 FAN 1019 PWM 105 FAN 1018 PWM 90 FAN 1018 PWM 75 FAN 1019 PWM 60 FAN 1021 PWM 45 FAN 1016 PWM 30 FAN 1010 PWM 28 FAN 1008 PWM 26 FAN 1018 PWM 24 FAN 1019 PWM 22 FAN 1016 PWM 20 FAN 1011 PWM 18 FAN 1010 PWM 16 FAN 1002 PWM 14 FAN 1016 PWM 12 FAN 1016 PWM 10 FAN 1013 PWM 8 FAN 1010 PWM 6 FAN 1007 PWM 4 FAN 1004 PWM 2 FAN 1005 PWM 0 FAN 1011 And sensors output: root@DataServer:~# sensors nvme-pci-0100 Adapter: PCI adapter Composite: +31.9°C (low = -273.1°C, high = +84.8°C) (crit = +84.8°C) Sensor 1: +31.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +26.9°C (low = -273.1°C, high = +65261.8°C) nvme-pci-0400 Adapter: PCI adapter Composite: +32.9°C (low = -0.1°C, high = +74.8°C) (crit = +79.8°C) acpitz-acpi-0 Adapter: ACPI interface temp1: +16.8°C it8792-isa-0a60 Adapter: ISA adapter in0: 1.79 V (min = +0.00 V, max = +2.78 V) in1: 589.00 mV (min = +0.00 V, max = +2.78 V) in2: 1.04 V (min = +0.00 V, max = +2.78 V) +3.3V: 3.38 V (min = +0.00 V, max = +5.56 V) in4: 1.79 V (min = +0.00 V, max = +2.78 V) in5: 1.50 V (min = +0.00 V, max = +2.78 V) in6: 2.78 V (min = +0.00 V, max = +2.78 V) ALARM 3VSB: 3.36 V (min = +0.00 V, max = +5.56 V) Vbat: 3.23 V Array Fan: 1018 RPM (min = 0 RPM) temp1: +34.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp2: -55.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp3: +34.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor intrusion0: ALARM nvme-pci-0500 Adapter: PCI adapter Composite: +35.9°C (low = -0.1°C, high = +74.8°C) (crit = +79.8°C) ERROR: Can't get value of subfeature temp2_min: I/O error ERROR: Can't get value of subfeature temp2_max: I/O error Sensor 1: -226.2°C (low = +0.0°C, high = +0.0°C) ERROR: Can't get value of subfeature temp3_min: I/O error ERROR: Can't get value of subfeature temp3_max: I/O error Sensor 2: -239.2°C (low = +0.0°C, high = +0.0°C) ERROR: Can't get value of subfeature temp4_min: I/O error ERROR: Can't get value of subfeature temp4_max: I/O error Sensor 3: -237.2°C (low = +0.0°C, high = +0.0°C) k10temp-pci-00c3 Adapter: PCI adapter CPU Temp: +34.2°C MB Temp: +32.0°C Any tips as to what I should look into?

This plugins latest version only supports Unraid 7 thus you cant find it on the previous versions.

Hello, I tried to hook up Shinobi docker container with tailscale and received the following exception: Executing Unraid Docker Hook for Tailscale Detecting Package Manager... Detected Advanced Package Tool! Installing packages... Please wait... ERROR: Installing packages! Err:1 http://deb.debian.org/debian buster InRelease Temporary failure resolving 'deb.debian.org' Err:2 http://security.debian.org/debian-security buster/updates InRelease Temporary failure resolving 'security.debian.org' Err:3 http://deb.debian.org/debian buster-updates InRelease Temporary failure resolving 'deb.debian.org' Reading package lists... W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease Temporary failure resolving 'deb.debian.org' W: Failed to fetch http://security.debian.org/debian-security/dists/buster/updates/InRelease Temporary failure resolving 'security.debian.org' W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease Temporary failure resolving 'deb.debian.org' W: Some index files failed to download. They have been ignored, or old ones used instead. Reading package lists... Building dependency tree... Reading state information... ca-certificates is already the newest version (20200601~deb10u2). ca-certificates set to manually installed. wget is already the newest version (1.20.1-1.1). The following NEW packages will be installed: jq libjq1 libonig5 0 upgraded, 3 newly installed, 0 to remove and 6 not upgraded. Need to get 355 kB of archives. After this operation, 1072 kB of additional disk space will be used. Err:1 http://deb.debian.org/debian buster/main amd64 libonig5 amd64 6.9.1-1 Temporary failure resolving 'deb.debian.org' Err:2 http://deb.debian.org/debian buster/main amd64 libjq1 amd64 1.5+dfsg-2+b1 Temporary failure resolving 'deb.debian.org' Err:3 http://deb.debian.org/debian buster/main amd64 jq amd64 1.5+dfsg-2+b1 Temporary failure resolving 'deb.debian.org' E: Failed to fetch http://deb.debian.org/debian/pool/main/libo/libonig/libonig5_6.9.1-1_amd64.deb Temporary failure resolving 'deb.debian.org' E: Failed to fetch http://deb.debian.org/debian/pool/main/j/jq/libjq1_1.5+dfsg-2+b1_amd64.deb Temporary failure resolving 'deb.debian.org' E: Failed to fetch http://deb.debian.org/debian/pool/main/j/jq/jq_1.5+dfsg-2+b1_amd64.deb Temporary failure resolving 'deb.debian.org' E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? ERROR: Unraid Docker Hook script throw an error! Starting container without Tailscale! Starting container... Does tailscale attempt to resolve these URLs through the network specified in the docker container instead of the servers network?

I also started having weird ZFS spin up issues (unraid ver 6.12.15). To me it looks like it is related to docker as when I enter the main page the docker list is not populated and only gets populated after ZFS drive spinup. This consistently happens 1ce a day on 1st visit to unraid main page. Consequent visits do not spin up the drive. Weird issues but I am planning to upgrade to 7.x.x so I was not keen to look at it for now. But since a wild post appeared that pinged me on this 2 year old thread might as well ask for what I can check...

Did you ever get this to work? I am also looking to upgrade to the latest shinobi version...

Hello, I have started receiving these email alerts from unraid: cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null Console and webGui login account 10 Feb 2025, 04:40 (20 hours ago) warning: Potentially dangerous mode on unraid-api: 0666 error: Ignoring unraid-api because it is writable by group or others. warning: Potentially dangerous mode on unraid-api.patch: 0666 error: Ignoring unraid-api.patch because it is writable by group or others. Can you help me identify the cause? This started after updating to 6.12.15 and installing the patch plugin. This seems to be a one time event after server restart. dataserver-diagnostics-20250211-0124.zip

I made the change and the notification still popped up whe I entered the page. root@DataServer:~# cat /proc/cmdline~ cat: /proc/cmdline~: No such file or directory root@DataServer:~# cat /proc/cmdline BOOT_IMAGE=/bzimage initrd=/bzroot isolcpus=11-15,27-31 root@DataServer:~# cat /boot/syslinux/syslinux.cfg default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot isolcpus=11-15,27-31 label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui isolcpus=11-15,27-31 label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest root@DataServer:~# cat /tmp/reboot_notification cat: /tmp/reboot_notification: No such file or directory root@DataServer:~# cat /tmp/reboot_notifications CPU Isolation: A reboot is required to apply changesroot@DataServer:~#

From my personal experience you can switch out stream settings. Had the same problem on HLS and it stopped when I switched to Poseidon. Also you are better of defining audio coded instead of copy. Shinobi is a bug riddled mess but the UI is still better then ZoneMinder... Wish this could get updated to the latest version of shinobi...

Before entering /Dashboard/Settings/CPUset root@DataServer:~# cat /boot/syslinux/syslinux.cfg default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot isolcpus=11-15,27-31 label Unraid OS GUI Mode kernel /bzimage append isolcpus=11-15,27-31 initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest root@DataServer:~# cat /proc/cmdline BOOT_IMAGE=/bzimage initrd=/bzroot isolcpus=11-15,27-31 root@DataServer:~# cat /tmp/reboot_notifications cat: /tmp/reboot_notifications: No such file or directory After Entering root@DataServer:~# cat /boot/syslinux/syslinux.cfg default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot isolcpus=11-15,27-31 label Unraid OS GUI Mode kernel /bzimage append isolcpus=11-15,27-31 initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest root@DataServer:~# cat /proc/cmdline BOOT_IMAGE=/bzimage initrd=/bzroot isolcpus=11-15,27-31 root@DataServer:~# cat /tmp/reboot_notifications CPU Isolation: A reboot is required to apply changes Attached diagnostics after clean boot before entering the page (no notification) and after (with notification). Before: dataserver-diagnostics-20250120-2223-Before.zip After: dataserver-diagnostics-20250120-2228-After.zip

Any info bassed on what I provided above?

root@DataServer:~# cat /boot/syslinux/syslinux.cfg default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot isolcpus=8-15,24-31 label Unraid OS GUI Mode kernel /bzimage append isolcpus=8-15,24-31 initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest root@DataServer:~# cat /proc/cmdline BOOT_IMAGE=/bzimage initrd=/bzroot isolcpus=8-15,24-31 Diags in previous post.

I have a verry similar issue in 6.12.14. When I visit cpu pining page (Dashboard/Settings/CPUset) and change docker pinning it prompts me to restart even though I do not touch Isolation... Is this normal behavior? I had the verry same kind of problem with VM manager where enterring the page would also cause the message to instantly pop up. The cause was either 'PCIe ACS override' or 'VFIO allow unsafe interrupts' setting once I removed them it solved the issue. Problem is I need CPU isolation x docker pinning so it would be annoying having this message show up every I change docker pinning... dataserver-diagnostics-20250116-0341.zip

All my changes were done with GUI. Apparently the cause was PCIe ACS override or VFIO allow unsafe interrupts. Once I dissabled these the message no longer appears. These were left over from pfsense VM with mobo ports passed through to it. I forgot to remove them once I got a physical machine for pfsense. No idea why the message kept appearing though...