Just so people know I got this working, with a monitoring bash file I found on this forum will have to find and book mark it.  
It writes out to a file,  then mounted that file in a nfs share and basically cat and echoed it back into proxmox

Used a cronjob for it like the below it runs every minute.

#!/bin/bash

dir="/mnt/PWM/"
nfs_server="x.x.x.x:/mnt/user/FANSHARE"
command_to_run="ls -l $dir"

while true; do
    if mountpoint -q $dir; then
        echo "NFS directory is already mounted. Running command..."
        # Replace the following line with the command you want to run when the NFS directory is mounted
        cat /mnt/PWM/pwm > /sys/class/hwmon/hwmon3/pwm1
        break
    else
        echo "NFS directory is not mounted. Attempting to mount..."
        mount $nfs_server $dir
        if [ $? -eq 0 ]; then
            echo "NFS directory successfully mounted. Running command..."
            # Replace the following line with the command you want to run when the NFS directory is mounted
            cat /mnt/PWM/pwm > /sys/class/hwmon/hwmon3/pwm1
            break
        else
            echo "Mount failed. Waiting for 30 seconds..."
            sleep 30
        fi
    fi
done
Asked chapgpt to write that for me.  I'm ok at reading scripting never been good at writing it.

21 hours ago, empty-handed-topping2304 said:

Looking for some help and not sure if its even possible.

I have a jonsbo n3 and just installed some pwm fans and replaced the jonsbo 3 pins ones with Artic 4 pin pwm fans.

My morherboard is the Asus Prime n100 it has 1 pwn connector, I bought an adapter so I could connect 3 fans to this 1 port.

I had'nt thought this fully through.

Unraid cannot see the pwm sensor and Proxmox cannot see the disks as the sata adapter is passed through to unraid.

I want to control the speed of the fans based on the temperature of the drives.

Is there anyway of passing the pwm sensor from proxmox into unraid.  Failing that pass the temperature back into proxmox to control the fans from there.

Server runs headless so havent had a chance to look at bios options yet.

Any advice would be greatly appreciated.

This question doesn't fit this thread. I would suggest you start a new thread, so the right people may see it.

@jbat66 thanks for the guide.

 

I’m curious why you suggest to not pass thru the hard drives directly and to instead create only large virtual drive. Would that not defeat the whole purpose of using of using unraid and its raid features?

 

You mentioned a performance hit but how bad is it really? If one of my drives gives out within this large virtual drive you have suggested to use, would that data not just be lost?

 

I’ve personally never used unraid but have decided to use it instead of truenas because I want to use a number of mixed sized drives which I understand can’t be done with truenas.

 

Thanks for your time.

During the boot process, after the samba initialization (Starting Samba:) I have 3 messages that I do not understand:

Starting mcelog daemon: /usr/sbin/mcelog --daemon
chmod: cannot access '/dev/dri': No such file or directory
logger: send message failed: Bad file descriptor

The system seems to be working just fine but I would like to know what are those extra messages in the console (that slow down the boot process a few seconds).

 

I'm using Proxmox v8.2, I'm not passing through any GPU or iGPU and these are my VM settings:





Btw, regarding the instructions on how to boot from the Unraid pendrive, I'm just passing through the USB Vendor/Device ID and in the boot options I select the USB and it works like a charm. I'm using Proxmox 8.2 though. Maybe the usb boot is something that wasn't available before.


edit: 

If I passthrough my Intel HD 4600 iGPU to the Unraid VM, the chmod: cannot access '/dev/dri': No such file or directory message goes away but the other two messages are still present.

edit 2:

I fixed those messages. The chmod: cannot access '/dev/dri': No such file or directory went away by simply deleting the Intel-GVT-g plugin, which I didn't even remember having (I haven't used Unraid in a while).

 

The message logger: send message failed: Bad file descriptor I think went away when I disabled "Mirror syslog to flash", but I'm not sure.

The remaining one, Starting mcelog daemon: /usr/sbin/mcelog --daemon, I still don't know what's about but I guess it's related to some plugin also.

Edited October 2, 20241 yr by s1l3nce
recent findings