milouz

Hi everyone, I’m releasing the first public version of Unraid VSOCK Sensors, a plugin that exports disk and HBA temperatures from an Unraid VM to its Proxmox host using AF_VSOCK. GitHub: GitHubGitHub - milouz1985/unraid-vsock-sensorsContribute to milouz1985/unraid-vsock-sensors development by creating an account on GitHub.What does it do? The plugin runs a small server inside the Unraid VM. A companion service installed on the Proxmox host retrieves the sensor data through VSOCK and exposes it as standard Linux hwmon devices. The temperatures can then be used by tools such as: lm-sensors CoolerControl fancontrol fan2go custom monitoring scripts On the Proxmox host, the sensors appear as: unraid_storage: individual disk temperatures and maximum temperatures by category unraid_hba: HBA controller temperatures, when HBA monitoring is enabled The storage device includes one channel per internal disk. It can also expose maximum temperature channels for HDDs, SATA SSDs and NVMe SSDs. Why VSOCK? My previous solution used the Unraid web API. It worked, but I wanted something more direct and better suited to communication between a VM and its host. AF_VSOCK provides a dedicated communication channel between the Unraid guest and the Proxmox host: no IP address or virtual network configuration is required; it does not depend on the Unraid web interface or its authentication API; the sensor service is not exposed on the LAN; communication still works independently of the VM’s network configuration; the protocol is small and dedicated to this specific use case. VSOCK also makes the architecture clearer: Unraid remains responsible for collecting its hardware information, while Proxmox only consumes the resulting sensor data. Disk spin-down support The plugin reads disk temperatures directly from Unraid’s existing /var/local/emhttp/disks.ini temperature cache. It does not run smartctl to collect disk temperatures. Therefore, querying the plugin does not wake up sleeping disks. A spun-down disk remains in the inventory, but its temperature is reported according to Unraid’s cached state. The Proxmox hwmon integration also includes failsafe handling when readings are unavailable or communication is interrupted. HBA monitoring Two HBA backends are currently available: native /dev/mpt3ctl access for controllers using the mpt3sas driver; StorCLI, when installed separately. The native mpt3ctl backend communicates directly with the Linux mpt3sas driver. Its implementation is based on the upstream Linux kernel ABI, structures and reference code, including the mpt3sas control interface and its hwmon support. The long-term goal is for HBA monitoring to rely exclusively on interfaces and code provided by the Linux kernel, without requiring any proprietary user-space utility. Requirements Unraid running as a QEMU/KVM VM on Proxmox; a vhost-vsock-pci device added to the VM; the Unraid plugin installed inside the VM; the companion Debian package installed on the Proxmox host; Proxmox kernel headers for the virt-temp DKMS module. Basic installation Add a VSOCK device to the Unraid VM configuration: args: -device vhost-vsock-pci,guest-cid=3 If the VM already has an args line, append the device to the existing line. The VM must be fully stopped and started after this change. add plg url in unraid: https://raw.githubusercontent.com/milouz1985/unraid-vsock-sensors/refs/heads/main/unraid-plugin/unraid-vsock-sensors.plg Install the companion .deb package on the Proxmox host. The complete installation and configuration instructions are available in the GitHub README. Current status The project is functional on my own setup, but this is its first public release. I hope this will be useful to others running Unraid as a VM and wanting to control host-side cooling using the actual storage temperatures.

Thanks for your insights. The goal is to prevent oom with swapiness really low, i'll try just to see!

hi @primeval_god, my cache pool is in zfs, so i start looking for an alternative solution and ended up reading this blog post : https://blog.nerdcruft.net/2017/02/06/linux-swap-over-loopback-devices/ so, I have written a small bash script to implement this using user script plugin: #!/bin/bash # Chemin du fichier de swap SWAP_FILE="/mnt/cache_nvme/system/swapfile" # Taille du swap en Mo SWAP_SIZE=4096 # 4 Go # Vérifier si le fichier de swap existe, sinon le créer if [ ! -f "$SWAP_FILE" ]; then echo "Création du fichier de swap..." dd if=/dev/zero of="$SWAP_FILE" bs=1M count=$SWAP_SIZE chmod 600 "$SWAP_FILE" fi # Trouver un loopback disponible LOOP_DEVICE=$(losetup -f) # Associer le fichier de swap au loopback losetup "$LOOP_DEVICE" "$SWAP_FILE" # Formater en swap mkswap "$LOOP_DEVICE" # Activer le swap swapon "$LOOP_DEVICE" # Régler le swappiness SWAPINESS=42 echo $SWAPINESS > /proc/sys/vm/swappiness echo "Swap activé sur $LOOP_DEVICE avec une taille de $SWAP_SIZE Mo et un swappiness de $SWAPINESS." if it can help you to implement a workaround for your plugin with zfs...

Ok, I think I understood what happend. I had a traefik instance on my swarm, when I first join the swarm with unraid it wasn't running. I started it later on, but didn't notice the webui wasn't accesible at this time. Traefik messed up Ports 80 and 443 port on unraid host. rookie mistake... thanks for your help @JorgeB.

ok, so stock install works, then adding docker config doesn't. I had join my swarm with unraid, which seemed working fine for several days until now. Removing it from my swarm seems to solve my problem. Not sure what is the link between joining a swarm and not having access webui though. we'll see if the problem come back...

so, i copied back files from flash backup using this: https://docs.unraid.net/unraid-os/getting-started/manual-install-method/ no luck, still no webui. in safe mode, i got ERR_CONNECTION_REFUSED in chrome and i suspect the array is not starting

I tried to use unraid usb creator to recreate my flash drive but i got "MISSING GUID" on the key i'm already using... does it mean it is dying?

Thanks for the link. I was unaware of the diagnostics command to use with cli! nas-diagnostics-20240911-1021.zip

Hi, when navigating to http://localip i get redirected to https://localip and get a "404 page not found" error message. by searching in forum i ended up deleting certs in /boot/config/ssl/certs, but a new one appear after reboot. I can't access the webui which is quite annoying. everything else seems to work fine. any idea?

May I ask you what is the prupose of using mergerfs on unraid?

is there any news on that? What can I do to make the plugin automatically calculate hash for new files that where moved by the mover from cache to array? is it possible to make the plugin calculate hash for file even if it is on cache and not on the array? I discovered that I have a lot of files without blake3 hashes despite '"Automatically protect new and modified files" option is enabled.

Thanks for your help. I'll try to ask tailscale also. nas-diagnostics-20230609-2323.zip

My logs are full of this kind of line: Jun 9 15:47:12 NAS tailscaled: 2023/06/09 15:47:07 wg: [rNaiD] - Failed to send handshake initiation: peer's node key has expired all my devices on my tailscale network have valid key and my unRAID server has Expiry disabled what does these errors mean?

Hi @binhex, I made my own docker image in order to get btrfs snapshot working corectly, it seems you need the user to run urbacksrv to be urbackup, ie do not change USER="urbackup" at the end of /etc/default/urbackupsrv, instead I use entrypoint.sh for re-writing uid and gid to map urbackup and nobody. feel free to give it a try if you want. entrypoint.sh Dockerfile

@binhex similar problem here using mullvad and 4.4.5-2-01. resolve by using 4.4.5-1-01 instead.

Hi! I'm facing a strange issue. in fact, i have a custom docker network supporting ipv6. radarr, sonarr and others are able to talk to each other using container name instead of ip, but binhex-qbittorrentvpn is unreachable. ping binhex-qbittorrentvpn from radarr and sonarr give me Addresse unreachable, unless I explicitly ask for ipv4 ping. even stranger, ping work briefly when I restart qbittorrent container... Any advise?