x0fflin3

hi any ideas how to run fan control on Terramaster F5-221? already done \boot\config\go: # sensors modprobe it87 force_id=0x8620 but did not see the fan arrays. clicking on fan detect there is nothing happen. i have replaced the original fans with noctuas, but them still to loud on 2000 pwm... root@BruRaid:~# sensors it8620-isa-0a20 Adapter: ISA adapter in0: 1.08 V (min = +0.59 V, max = +0.61 V) in1: 1.50 V (min = +1.97 V, max = +0.50 V) in2: 2.14 V (min = +0.58 V, max = +1.88 V) +5V: 4.27 V (min = +1.18 V, max = +3.50 V) in4: 2.18 V (min = +0.96 V, max = +1.24 V) in5: 2.26 V (min = +0.18 V, max = +1.60 V) in6: 420.00 mV (min = +0.40 V, max = +1.62 V) 3VSB: 480.00 mV (min = +0.60 V, max = +0.48 V) Vbat: 3.19 V temp1: +33.0°C (low = +52.0°C, high = -52.0°C) sensor = thermal diode temp2: +31.0°C (low = -113.0°C, high = -54.0°C) sensor = thermal diode temp3: +31.0°C (low = -12.0°C, high = -90.0°C) sensor = disabled temp4: +31.0°C temp5: +31.0°C temp6: +31.0°C intrusion0: ALARM acpitz-acpi-0 Adapter: ACPI interface MB Temp: +38.0°C (crit = +100.0°C) coretemp-isa-0000 Adapter: ISA adapter CPU Temp: +39.0°C (high = +105.0°C, crit = +105.0°C) Core 0: +38.0°C (high = +105.0°C, crit = +105.0°C) Core 2: +39.0°C (high = +105.0°C, crit = +105.0°C) root@BruRaid:~# sensors-detect # sensors-detect version 3.6.0 # System: retsamarret 000-F5221-FBA002-0001 [Default string] # Board: retsamarret Default string # Kernel: 5.15.43-Unraid x86_64 # Processor: Intel(R) Celeron(R) CPU J3355 @ 2.00GHz (6/92/9) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): yes Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): yes Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8613E Super IO Sensors' Success! (address 0xa20, driver `to-be-written') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): yes Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): yes Using driver `i2c-i801' for device 0000:00:1f.1: Broxton (SOC) Module i2c-dev loaded successfully. Next adapter: SMBus I801 adapter at f040 (i2c-0) Do you want to scan it? (yes/NO/selectively): yes Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Next adapter: i915 gmbus dpb (i2c-1) Do you want to scan it? (yes/NO/selectively): yes Client found at address 0x49 Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Analog Devices ADT7410/ADT7420'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP435'... No Probing for `National Semiconductor LM73'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Probing for `SMSC EMC1023'... No Probing for `SMSC EMC1043'... No Probing for `SMSC EMC1053'... No Probing for `SMSC EMC1063'... No Next adapter: i915 gmbus dpc (i2c-2) Do you want to scan it? (yes/NO/selectively): yes Next adapter: i915 gmbus misc (i2c-3) Do you want to scan it? (yes/NO/selectively): yes Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Driver `to-be-written': * ISA bus, address 0xa20 Chip `ITE IT8613E Super IO Sensors' (confidence: 9) Note: there is no driver for ITE IT8613E Super IO Sensors yet. Check https://hwmon.wiki.kernel.org/device_support_status for updates. Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): yes Copy prog/init/lm_sensors.init to /etc/init.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. Unloading i2c-dev... OK root@BruRaid:~#

boah hammer! tut tatsächlich! bekomme jetzt die CPU Temp angezeigt unabhöngig von Grafana in UNRAID und kann die Lüfter steuern! Muss nur noch verstehen wie die da belegt sind und der Fan Controller funktioniert. Danke, das erspart mir den ICUE Controller con Corsair.

nein, da hatte ich einen benchmark laufen auf cpu und gpu für temp test. hab noch keine direkten sensor fürs wasser aber vllt kommt einer kürze ein ICUE Controller, damit könnt ich die temp von Wasser auslesen und im Betrieb die Lüfter steuern. Die GPU zeigt mir im Leerlauf gerade 25°C, das Wasser wäre 3-4°C kühler.

Haben die auch. Das System hat eine wakü, vorne 3 Lüfter oben 2. Alle laufen mindestens mit 1000U. Die Lüfter pusten die Luft erst auf den Radiator, dann gehen sie an die hdds. Eventuell hätte mehr Sinn gemacht die Luft von innen nach außen zu saugen. Das Wasser halt sich bei 32°C. Verbaut sind aktuell in Summe 6 x 3.5hdd, zwei sind noch unten hinter der schwarzen Blende. Vorne 360mm kühler Block mit 3x2000U 120mm Lüftern und oben ein 240mm kühler mit 2x120mm Lüftern a 2000U Silent wings 3. Die obere Platte ist noch nicht angeschlossen, warte noch auf einen PCI sata Controller und es kommen noch noch zu den 2 nvme zwei weitere hinzu mit nochmal 3 weiteren SATA ssds.

das ist doof. so könnte ich die Lüfter wenigstens Steuern um die HDD's besser zu kühlen...wenn der parityCheck läuft werden die 57°C warm pwm controller mit autoFan wird nicht erkannt, das bringt keine Lösung.

perfekt, das Problem mit USB hat sich erledigt. bin über den Virt-Manager gegangen, hab alle Controller neu hinzugefügt, überflüssige entfernt, Tastatur wird jetzt richtig erkannt! Auch wenn der Name der GPU nicht richtig angezeigt wird, scheint es nun soweit richtig zu laufen. Wichtig wäre noch die Lüftersteuerung, dazu müsste das MSI DragonCenter auf das Mainboard zugreifen können. Mal sehen ob ich das richtige noch im IOMMU finde...hat wer einen Tipp wie die Group heißen kann?

ja hatte AMD genommen damit der Sound auch vom Rechner direkt kommt, habs auf beide Karten erweitert, NVIDIA & AMD) das habe ich ja oben erwähnt, ich weiss nicht weshalb mir der Name der GPU fehlt, wird von unraid nicht richtig erkannt. das Rom ist von meiner GPU mit angepassten Header, glaube ohne lief die nicht. teste ich nochmal genauer. nur zur Ergänzung die VM arbeitet auch als Workstation, hab direct attached auch am Tower die entsprechenden Peripheriegeräte.

macht das Sinn bei 2x4k Monitoren, mir sagt der Wert gerade nicht viel.

wenn ich die ausm iommu anwähle bekomme ich die vm nicht gestartet bzw so konfiguriert. und sieh an, bei dir wird die gpu auch mit richtigem model angezeigt.

Wie heiß werden die Platten aus dem backupsystem?

Moin, nutze Unraid als AllinOne Rechner. (Tower, Server, Nas) Hab die Tower VM soweit fertig bekommen dass auch die GPU durchgereicht wird an die VM. So richtig glücklich bin ich aber nicht, bei allen anderen Usern hat jeder das model stehen zur GPU, meine zeigt lediglich NVIDIA DEVICE an. #!/bin/bash echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind das läuft noch als Script, weiss allerdings nicht genau was es tut, aber es hat die vm mit der gpu zum laufen gebracht. Mein Wunsch wäre idealerweise die GPU mit mehreren VM's gleichzeitig zu teilen, wenn möglich. Dann bekomme ich die USB-Controller nicht durchgereicht, was kein großes Problem ist...würde die Corsair Tastatur richtig funktionieren. Die meint beim booten der VM den WIN Blocker zu aktivieren, zumindest leuchtet das Kontrolllämpchen wie'n Christbaum. Das perfide ist, dass die Suche in Start unter Windows nicht funktioniert, boote ich normal von der nvme tuts. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='36'> <name>Tower</name> <uuid>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>14</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='18'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='20'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='22'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='24'/> <vcpupin vcpu='8' cpuset='10'/> <vcpupin vcpu='9' cpuset='26'/> <vcpupin vcpu='10' cpuset='12'/> <vcpupin vcpu='11' cpuset='28'/> <vcpupin vcpu='12' cpuset='14'/> <vcpupin vcpu='13' cpuset='30'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/650e1c31-0cfa-6283-f5c1-906e28c18520_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='2D54SQ7T5S51'/> </hyperv> <kvm> <hidden state='on'/> </kvm> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='7' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/nvme-GIGABYTE_GP-ASM2NE6100TTTD_SN192608967199' index='3'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/nvme-INTEL_SSDPEKNW020T8_BTNH00360HPH2P0C' index='2'/> <backingStore/> <target dev='hdd' bus='virtio'/> <alias name='virtio-disk3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_860_EVO_500GB_S3Z2NB1K901351A' index='1'/> <backingStore/> <target dev='hde' bus='virtio'/> <alias name='virtio-disk4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </disk> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:f7:cc:ac'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-36-Tower/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='8'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='de'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2d' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/domains/unRAID_Settings/GPU_ROM/Meine_EVGARTX3080_fixed.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2f' slot='0x00' function='0x4'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0x0843'/> <address bus='1' device='10'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0x0a5b'/> <address bus='1' device='8'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc332'/> <address bus='1' device='7'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0a12'/> <product id='0x0001'/> <address bus='1' device='9'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1462'/> <product id='0x7c37'/> <address bus='3' device='2'/> </source> <alias name='hostdev6'/> <address type='usb' bus='0' port='5'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1b1c'/> <product id='0x1b3d'/> <address bus='1' device='11'/> </source> <alias name='hostdev7'/> <address type='usb' bus='0' port='6'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x2537'/> <product id='0x1081'/> <address bus='2' device='6'/> </source> <alias name='hostdev8'/> <address type='usb' bus='0' port='7'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x8087'/> <product id='0x0aa7'/> <address bus='1' device='5'/> </source> <alias name='hostdev9'/> <address type='usb' bus='0' port='9'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>