enect

Sorry, da hatte ich mich verschrieben... Ziel war und getestet hab ich nach der "Aufteilung" den D128 mit geladenen xe-Treiber an frigate zu geben (nicht den D130). Aber ich hab dann die Hardwarebeschleunigung in frigate nicht zum laufen bekommen, obwohl dazu auch nen bisschen was in der friagte docu steht. Nur mit i915 läuft es bei mir. Das i915 SR-IOV PlugIn hat bei mir bisher nicht sauber funktioniert. Aber gut, vielleicht muss ich das unter 7.3 nochmal testen. Hatte halt gehofft, mit dem Kernel 6.18 das PlugIn zu umgehen. Edit: Lese grad, dass SR-IOV im xe-treiber wohl gar nicht für die iGPUs gedacht ist und somit da meine Test-Fehlerquelle liegen kann.

Hab heute das Update auf 7.3 gemacht und i915.force_probe=!a780 xe.force_probe=a780 xe.max_vfs=2 getestet. Musste dann noch im go - file helfen. # SR-IOV VFs für den xe-Treiber erzeugen sleep 10 echo 2 > /sys/bus/pci/devices/0000:00:02.0/sriov_numvfs logger "SR-IOV: 2 VFs fuer Intel iGPU (xe) erfolgreich erzeugt" danach hatte ich das sichtbare ergebnis unter ls -l /dev/dri Aber ich bin auch im ersten Docker (frigate) gescheitert und konnte da die D130 nicht aktivieren. Er hat es nicht geschluckt... Keine Ahnung.

Danke das du deine Lösung postet, die in der Praxis -wie du selber schreibst- etwas umständlich ist. Ich schaffe es selbst noch nicht, auf 7.3 zu gehen und meine Tests zu machen... wäre aber jetzt auch davon ausgegangen, dass mit Kernel 6.18 und 14th Intel einiges besser wird. Hast du zufällig 915.force_probe=!a780 xe.force_probe=a780 xe.max_vfs=2 probiert, also inkl. dem Definieren der VF? Nach Reboot sollte man dann sehen, ob er die VFs bereit stellt ls -l /dev/dri Das Plex den xe nicht schluckt, ist natürlich ein anderes Thema. Ziel wäre schon, ohne das PlugIn klar zu kommen und dem 6.18 Kernel inkl. xe allein zu nutzen.

I haven't upgraded to 7.3 yet, but shouldn't the xe driver work now with 7.3 and kernel 6.18.28? That is, if I block 915 and force xe using the parameters 915.force_probe=!a780 xe.force_probe=a780 xe.max_vfs=2... If this is working, I should be able to see the expected result by running ls -l /dev/dri, and subsequently—in this example—assign a VF to the VM and another to Docker. Or am I overlooking something? Oh, in my case there's an Intel 14700 in the background...

Schau dir mal die iOS oder Android App "FileBrowser Professional" von stratospherix an. Kostet zwar ca. 15 EUR. Aber als ich von Synology auf Unraid umgestiegen bin, hat diese App fast alle Synolgy-Apps ersetz. Inkl. Bildbetrachtung, Sicherung der Bilder mit Routtinen usw... auch ein sehr guter Filebrowser.

ich nutze binhex-krusader zum entpacken. schau mal unter apps nach

I'm the guy with the script from the other thread. I searched and tested extensively... nothing worked if you want to use HDD temperatures as a trigger. I also tried modifying the IPMItools plugin... to no avail. The only thing is, my IPMI card from the mainboard has three temperature sensors. You could put one on an HDD and control it based on that. But that's inaccurate if you have many HDDs. I'd be happy to give you my current script, which has been refined over several months. Analyze it with AI and test it if you like. I'm very happy with it now, and after all this time, I have a lot of confidence in it. Fan_Control (at startup of array): Fan_Control Fan_Control_Secure_Mode (at stopping of array): Fan_Control_Secure_Mode

Nur zur Info. Hab mein Script mal hier vorsichtshalber gelöscht, weil ich einen gravierenden Nachteil gegenüber das existierende Plugin gefunden habe. Das PlugIn greift früh ein und erstellt die RAM Disk. Dann laufen auch andere Sachen fehlerfrei durch. Bei meinem gebastelten Script unter User Script entstehen Fehler in der GUI von user script. Er verliert die Zuordnung zu anderen Scripts und kann sie nicht mehr sauber verfolgen und leicht schlimmeres. Daher ist meine Lösung schrott und ich investiere keine Zeit, wenn jemand schon was funktionierndes gebastelt hat.

Oh OK. Kannst du mir bitte den Namen sagen? Wäre dann vermutlich komfortabler. Update... habs gefunden. ja shit dann... scheint wirklich genau das selbe zu sein. dann hab ich zeit verschwendet...

Just to be clear — these are my observations. I’ve had first-hand experience with this kind of problem: I owned an ASRock Rack ROMED8-2T/BCM and returned it for exactly these kinds of issues. Later I ran a Supermicro H12SSL-CT, which was stable but got scrapped due to high idle power (I even posted about that in the German forum). I recognized the situation in your case, wrote down my thoughts, and yes, I used AI to help phrase it in English. That doesn’t mean the insight isn’t mine — AI just helped shape it. This is reality now: tech evolves, tools assist, but the analysis is still human. Not everyone asking for help actually wants it, and that’s fine — just saying. Honestly, my lifetime is too short to argue about this kind of stuff, so I’m done with the topic.

I use AI for translation since I'm from Germany. But it's a brilliant response when someone wants to help. Life needs people like that... ungrateful.

Thanks for the update — that changes the picture. If PEG was already set and the system still initialized the BMC as the primary GPU, then it wasn’t a simple BIOS-priority issue. Many server boards with BMC ignore the PEG setting unless a secondary “Onboard/BMC VGA” or “Internal Graphics” toggle is disabled as well, so the behavior you saw is consistent with that. Blacklisting AST breaking the boot also confirms that the board was hard-wired to rely on the BMC framebuffer during POST/boot, so the ARC never became the active DRM device, regardless of driver forcing. Since replacing the motherboard and CPU fixed it, it strongly suggests a firmware/BIOS/BMC implementation problem on the previous board rather than an Unraid driver issue. In short: you didn’t do anything wrong — the previous board simply wouldn’t hand off primary GPU to the ARC under Linux, even with the correct settings.

Summary of your diagnostics: - The Aspeed BMC (AST) is currently bound as the primary GPU: /sys/class/drm/card0 -> driver ast. - The Intel Arc A310 (DG2) is present in lspci but has no kernel driver bound (Kernel driver in use: none). - xe and i915 modules are loaded but neither is bound to the Arc card, so /dev/dri only exposes the Aspeed device. Likely root cause: - The board boots with the Aspeed BMC as primary VGA device, preventing the Arc A310 from being initialized as the active DRM GPU. Immediate recommendations (in order): 1) BIOS: Set Primary Display / Init Display First to PCIe/PEG (disable "BMC/Aspeed as primary VGA"). Reboot and check lspci -k and /dev/dri. This is the cleanest fix. 2) If BIOS change is not available: try unbinding the AST driver and binding the Arc driver manually (SSH, root): - echo 0000:22:00.0 > /sys/bus/pci/drivers/ast/unbind # (replace with actual Aspeed PCI address) - echo 0000:2e:00.0 > /sys/bus/pci/drivers/xe/bind # (replace with Arc PCI address) Then check lspci -k -s 2e:00.0 and ls -l /dev/dri. # (replace with Arc PCI address) Useful checks to paste back if this doesn't work: - lspci -k -s 2e:00.0 # (replace with Arc PCI address) - ls -l /sys/class/drm/ - dmesg | egrep -i 'xe|i915|aspeed|ast|drm' Bottom line: It’s almost certainly just a BIOS configuration issue. The diagnostics don’t show a driver or kernel problem. The system is treating the Aspeed BMC as the primary GPU, so the Arc A310 never gets initialized or bound to the xe driver. Once the BIOS is set to use PCIe/PEG as the primary display, the Arc should load normally and show up under /dev/dri without any manual binding. Only if the BIOS cannot switch the primary GPU, the unbind/bind workaround is needed.

Yes – your diagnostics clearly show Machine Check Events (MCEs). That’s exactly what the Fix Common Problems plugin is warning you about. mce: [Hardware Error]: Machine check events logged [Hardware Error]: Corrected error, no action required. Fix Common Problems: Error: Machine Check Events detected on your server mcelog: ERROR: AMD Processor... Please use the edac_mce_amd module instead. What this means: These are corrected hardware errors reported by the CPU. The system didn’t crash, but it indicates a potential hardware issue that shouldn’t be ignored if it becomes frequent. On AMD systems, mcelog is basically unreliable and often throws useless messages — the Linux kernel recommends using the edac_mce_amd module instead. Most common causes: Too aggressive memory settings (EXPO/XMP) Slight system instability (RAM, CPU, PSU) Outdated BIOS with older AMD microcode Recommended steps: If EXPO/XMP is enabled → try disabling it for a while This alone fixes most MCE reports on AMD systems. Update BIOS Many AMD MCE issues are microcode bugs fixed in BIOS updates. Run a full Memtest86 overnight (4+ passes) If errors show up → RAM or memory controller issue. Check PSU quality & voltages Weak/unstable PSUs can trigger MCEs. Bottom line: Your server is not in immediate danger, but the CPU is reporting corrected hardware faults. Keep an eye on it. If these messages become more frequent, then it’s time to take action. Your system is running an AMD Ryzen 5 5600X. This CPU is known to occasionally report corrected Machine Check Events under Linux, especially when: EXPO/XMP memory profiles are enabled, BIOS is outdated, or the system is slightly undervolted/unstable. This isn’t unique to your hardware – it’s a common behavior on Zen 3 CPUs. Many users with 5600X/5800X/5900X/5950X see the same warnings when memory tuning is too aggressive or when the board’s early BIOS revisions had microcode issues.

Bin jetzt kein Experte, aber ich hatte mal ein sehr ähnliches Fehlerbild, als ich über powertop mittels autotune gearbeitet habe. Bei manuellen setzen über Tunables hab ich gemerkt, dass meine Netzwerkkarte (onboard) sich damit nicht vertragen haben. Sobald die "schlafen" gehen sollte, ist u.a. die Weboberfäche eingeschlafen und nicht mehr erreichbar gewesen. Das selbe auch über autotweak, wenn ich dort Ethernet angetastet habe. Vielleicht völlig an deinem Problem vorbei, aber vielleicht doch hilfreich...

Hi... Then please describe exactly what hardware your system is running. I don't think 14W is possible with the IMPI version.

@SimonF I, and apparently a few others, use the ASUS Pro WS W680-ACE IPMI board. Over the past few weeks, I've been tinkering with something to control the board's fans based on HDD temperatures. I outlined my approach here yesterday: I wanted to ask if you could take a look at it and see if there is a chance of finding a solution for the board within your plug-in or if it would be too much effort. A total of eight fans can be managed here. You can assign a fan curve to each fan. It's important to note that the BMC still processes the fan curve based on the CPU temperature. Therefore, I set the temperature value to 1°C and specify the same PWM value for all points on the curve – it's then flat. Of course, you then need to be able to select the right hardware for each fan, be it one or more HDDs or the CPU. The other "features" of my solution are listed in the linked post. My solution with the script works for me, but of course it would be nicer for me and certainly others if it could be solved more conveniently with a plug-in like yours. Maybe I've made you curious... PS: I tried inserting the JSON into your plugin, but unfortunately nothing happens then. "ASUS_W680_ACE": { "raw": "00 30 0e 04", "auto": "00 30 0e 00 00 00 00 00 00 00 00 00 00 00 00", "full": "00 30 0e 03 00 00 00 00 00 00 00 00 00 00 00", "fans": { "CHA_FAN1": "00", "CHA_FAN2": "01", "CHA_FAN3": "02", "CHA_FAN4": "03", "CHA_FAN5": "04", "CHA_FAN6": "05", "CHA_FAN7": "06", "CHA_FAN8": "07" } } }

Topic: Controlling Fans Based on HDD Temperatures with IPMI After looking around here and in the support thread for the “IPMI Tools” without finding anything useful for fan control based on HDD temperatures – specifically for the ASUS Pro WS W680-ACE IPMI – and after the “Dynamix System Temp” plugin (including drivers) didn’t help either, I’ve been doing a bit of experimenting lately. Conclusion: Using a few packages and “user script” you can build your own fan controller for this board… But first, maybe the most important bit upfront before I get into the details. At the beginning, I just couldn’t figure out the right IPMI command to change the fan/PWM settings. The manual wasn’t helpful, but eventually ASUS support came through and provided the info I needed. So for those of you who just want the quick answer on how to control things via IPMI, here’s the relevant bit straight from ASUS: “Please note that a FAN source that doesn’t physically exist can’t be activated or ‘created’ via IPMI either. But if you want to manually control, for example, an HDD fan, that’s basically possible via IPMI. Here are some basic commands to control fan modes: • Set fan mode to ‘Generic’: ipmitool raw 0x30 0x0e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 • Set fan mode to ‘Full Speed’: ipmitool raw 0x30 0x0e 0x03 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 • Set fan mode to ‘Custom’ (manual): Example for fan zone “0” with multiple temp/duty pairs – this would reach 100% fan speed at 80 °C: ipmitool raw 0x30 0x0e 0x04 0x00 0x28 0x32 0x32 0x41 0x3c 0x4b 0x46 0x55 0x50 0x64 Explanation of values (each pair is temp and fan speed %): • 0x28 = 40 °C → 0x32 = 50 % • 0x32 = 50 °C → 0x41 = 65 % • 0x3c = 60 °C → 0x4b = 75 % • 0x46 = 70 °C → 0x55 = 85 % • 0x50 = 80 °C → 0x64 = 100 % If you want to target a different fan zone, change the fourth value: • 0x00 = Zone 1 • 0x01 = Zone 2, etc.” Important: What this means is that you can’t just set a single PWM value per fan – you always have to define an entire fan curve. Also, keep in mind that once the BMC receives a fan curve via IPMI, it still needs a temperature input to decide what PWM value to use. Unfortunately, the BMC only has access to the CPU temperature and external physical sensors – no HDD temps. So if you want to set a fixed PWM value safely, you need to create a fan curve where all the temperature points lead to the same fan speed, set the trigger temperature to 1°C, and select the CPU as the source. That way, since the CPU is always at least 1°C, the curve will reliably apply the PWM value you specified. Now, I’ve got zero programming skills, so I couldn’t write a script myself to handle this (to control the fan PWM based on HDD temps). But hey, we live in great times – that’s what ChatGPT is for. So I started by explaining my setup to ChatGPT – focusing on my hardware. I’ve got a Supermicro SuperChassis 743TQ-903B-SQ, and it was important to know that on the ASUS BMC, CHA-FAN1 through CHA-FAN4 are connected to fans that cool the HDDs. FAN1 and FAN2 are directly for the HDDs, while FAN3 and FAN4 also help cool five more HDDs and provide airflow for the CPU. That led to this requirement: FAN1 and FAN2 should respond only to the HDD temperatures, while FAN3 and FAN4 should react to both HDD temps and the CPU package temp. I then defined fan curves for both the HDDs and the CPU, and each fan was assigned to the appropriate HDDs. I wanted to keep the number of required packages for the script as low as possible, and decided to go with freeipmi instead of ipmitool, since that's what the “IPMI Tools” package actually uses under the hood. That’s also why the commands in the script have been adapted for freeipmi. I installed the IPMI Tools package so I could monitor fan speeds and temperatures directly in the UNRAID dashboard. Required packages: ipmi-raw (freeipmi/IPMI Tools), smartctl, hdparm, sensors, iostat (from sysstat), awk, printf, head, wc, tail Step by step, I had ChatGPT add more and more features to the script… 1. HDD Activity Detection using iostat Only queries SMART temperature if a disk is actually reading or writing data. Prevents unnecessary SMART access during idle time, allowing drives to spin down as expected. 2. Spin-down Protection for HDDs Uses hdparm -C to check if a disk is in standby mode. If so, it skips temperature checks to avoid waking the drive unnecessarily — maintaining UNRAID’s spin-down behavior. 3. Correct SMART Temperature Extraction Reads the temperature from column 10 (RAW_VALUE) of the Temperature_Celsius SMART attribute. Avoids misinterpretation by ensuring accurate temperature parsing across all drive vendors. 4. Fan Speed Control Based on Temperature Custom fan curves: HDD zones use a stepped curve: 10 % / 25 % / 45 % / 85 % at increasing thresholds. CPU zones (CHA_FAN3+4) use 10 % / 35 % / 50 % / 80 % / 100 %. 5. Independent Control per Fan Zone (CHA_FAN1–4) Each fan zone is assigned a group of HDDs. Zones C and D additionally factor in CPU temperature in the control logic. 6. Change Detection (Delta Update) The script only sends an ipmi-raw command if the PWM value has changed since the last loop. Reduces IPMI traffic and log spam. 7. Failsafe Mechanism (IPMI Failure) If the ipmi-raw command fails, the script sends a failsafe PWM value of 60%. Logs whether the fallback succeeded or failed (e.g., due to a hung BMC). 8. Compact Log with Auto-Rotation Logs are written to RAM If the log exceeds 100 lines, it's trimmed to the last 50 lines. Each log entry includes: HDD temperature (or (all sleeping or inactive)) CPU temperature Target fan PWM Date and time 9. Optional Dry-Run Mode Set DRY_RUN=1 at the top of the script to simulate fan control without sending actual IPMI commands. 10. One-Time Dependency Check On startup, the script checks for required tools. If anything is missing, it logs the missing dependencies and exits gracefully. 11. Cooldown-Logik at idle/sleep After the last active access per fan zone, the last PWM value remains valid for 120s Gives the currently used HDDs some time to cool down Only then does the value fall back to DEFAULT_SLEEPING_HDD_SPEED 12. The script runs every 10 seconds. It is activated when the array is started via "User Scripts." For anyone who missed this, have fun playing with this information. The following script is my current version, which I've been testing casually for a week. So far, it's stable, and no errors have been detected. However, the script is for my setup and basically only works for me (fan and HDD/CPU allocation). But as I said, you can achieve a lot with ChatGPT... I'm open to suggestions if anyone has any ideas for improvement/features or sees a bug. #!/bin/bash INTERVAL=10 LOGFILE="/tmp/user.scripts/tmpScripts/Fan_Control_HDDs/log.txt" DRY_RUN=0 MIN_FAN_SPEED=10 DEFAULT_SLEEPING_HDD_SPEED=10 FAILSAFE_FAN_SPEED=60 AFTER_ACTIVITY_COOLDOWN=120 MAX_SAFE_HDD_TEMP=65 MAX_SAFE_CPU_TEMP=80 declare -A fan_disks fan_disks[A]="/dev/sda /dev/sdb /dev/sdc /dev/sdd" fan_disks[B]="/dev/sde /dev/sdf /dev/sdh /dev/sdg" fan_disks[C]="/dev/sdi /dev/sdj /dev/sdk /dev/sdl /dev/sdm" fan_disks[D]="/dev/sdi /dev/sdj /dev/sdk /dev/sdl /dev/sdm" declare -A fan_zone fan_zone[A]=0x00 fan_zone[B]=0x01 fan_zone[C]=0x02 fan_zone[D]=0x03 declare -A last_pwm declare -A last_active_time declare -A last_active_pwm log_echo() { echo "$1" >> "$LOGFILE" local line_count line_count=$(wc -l < "$LOGFILE" 2>/dev/null) if [[ "$line_count" -gt 100 ]]; then tail -n 50 "$LOGFILE" > "${LOGFILE}.tmp" && mv "${LOGFILE}.tmp" "$LOGFILE" fi } check_dependencies() { local missing=0 for cmd in ipmi-raw smartctl hdparm sensors iostat; do if ! command -v "$cmd" >/dev/null 2>&1; then log_echo "$(date '+%F %T') ❌ Dependency missing: $cmd" missing=1 fi done if (( missing )); then echo "Exiting due to missing dependencies." exit 1 fi } get_temp() { local dev=$1 [[ ! -e "$dev" ]] && echo "SKIP" && return local state state=$(hdparm -C "$dev" 2>/dev/null | awk '/drive state/ {print $4}') [[ "$state" == "standby" ]] && echo "SKIP" && return local io_activity io_activity=$(iostat -d -k -x "$dev" 1 2 | awk -v d=$(basename "$dev") ' $1 == d { count++; if (count == 2) print ($5 + $6) }') local io_whole io_whole=$(printf "%.0f" "$io_activity") if [[ "$io_whole" -gt 0 ]]; then smartctl -A "$dev" 2>/dev/null | awk ' /Temperature_Celsius|Temperature/ && NF >= 10 {print $10}' | head -n1 else echo "SKIP" fi } get_max_temp_for_fan() { local devices=($1) local max_temp=0 local any_awake=0 for dev in "${devices[@]}"; do [[ ! -e "$dev" ]] && continue temp=$(get_temp "$dev") if [[ "$temp" != "SKIP" && -n "$temp" && "$temp" -gt $max_temp ]]; then max_temp=$temp any_awake=1 fi done if (( any_awake == 0 )); then echo -1 else echo "$max_temp" fi } get_cpu_temp() { sensors 2>/dev/null | awk '/Package id 0:/ {print int($4)}' | head -n1 } cpu_fan_curve() { local t=$1 if (( t < 60 )); then echo 10 elif (( t < 70 )); then echo 35 elif (( t < 80 )); then echo 50 elif (( t < 90 )); then echo 80 else echo 100 fi } check_dependencies while true; do for fan in A B C D; do now=$(date +%s) devices="${fan_disks[$fan]}" hdd_temp=$(get_max_temp_for_fan "$devices") if [[ $hdd_temp -eq -1 ]]; then if [[ -n "${last_active_time[$fan]}" && $(( now - last_active_time[$fan] )) -lt $AFTER_ACTIVITY_COOLDOWN ]]; then final_speed=${last_active_pwm[$fan]} hdd_temp_display="(recent activity, cooling)" else final_speed=$DEFAULT_SLEEPING_HDD_SPEED hdd_temp_display="(all sleeping or inactive)" log_cooldown=1 fi else hdd_temp_display="${hdd_temp}°C" hdd_speed=$(( hdd_temp < 40 ? 10 : hdd_temp < 45 ? 25 : hdd_temp < 50 ? 45 : hdd_temp < 55 ? 85 : 85 )) final_speed=$hdd_speed last_active_time[$fan]=$now last_active_pwm[$fan]=$hdd_speed fi if [[ $fan == C || $fan == D ]]; then cpu_temp=$(get_cpu_temp) cpu_speed=$(cpu_fan_curve "$cpu_temp") final_speed=$(( final_speed > cpu_speed ? final_speed : cpu_speed )) final_speed=$(( final_speed < MIN_FAN_SPEED ? MIN_FAN_SPEED : final_speed )) else final_speed=$(( final_speed < MIN_FAN_SPEED ? MIN_FAN_SPEED : final_speed )) cpu_temp="N/A" fi # Emergency override if [[ "$cpu_temp" =~ ^[0-9]+$ ]] && (( cpu_temp >= MAX_SAFE_CPU_TEMP )) || (( hdd_temp >= MAX_SAFE_HDD_TEMP )); then final_speed=100 fi zone="${fan_zone[$fan]}" pwm_key="${zone}" prev="${last_pwm[$pwm_key]:--1}" if [[ "$final_speed" -ne "$prev" ]]; then last_pwm[$pwm_key]="$final_speed" timestamp=$(date '+%F | %T') log_msg="🚀 Set CHA_FAN$((fan_zone[$fan] + 1)) | HDD=$hdd_temp_display | CPU=$cpu_temp°C → Target=${final_speed}% | $timestamp" if [[ "$hdd_temp" -eq -1 && "${log_cooldown:-0}" -eq 1 ]]; then log_msg="⌛ Cooldown expired → $log_msg" unset log_cooldown fi log_echo "$log_msg" if (( DRY_RUN )); then log_echo "🧪 DRY-RUN: Would send to zone $zone → PWM $final_speed%" else hex_pwm=$(printf '0x%02x' "$final_speed") if ! ipmi-raw 0x00 0x30 0x0e 0x04 "$zone" \ 0x01 "$hex_pwm" 0x01 "$hex_pwm" 0x01 "$hex_pwm" 0x01 "$hex_pwm" 0x01 "$hex_pwm" > /dev/null; then log_echo "❌ IPMI failed → fallback to $FAILSAFE_FAN_SPEED%" hex_pwm_failsafe=$(printf '0x%02x' "$FAILSAFE_FAN_SPEED") ipmi-raw 0x00 0x30 0x0e 0x04 "$zone" \ 0x01 "$hex_pwm_failsafe" 0x01 "$hex_pwm_failsafe" 0x01 "$hex_pwm_failsafe" 0x01 "$hex_pwm_failsafe" 0x01 "$hex_pwm_failsafe" last_pwm[$pwm_key]="$FAILSAFE_FAN_SPEED" fi fi fi done sleep "$INTERVAL" done

Just a small comment from experience. I wouldn't buy the WD Red SN700 again. I use it primarily for Frigate clips. But this model generates a ton of PCI correction errors in the logs. Everything runs fine, but it's annoying. I had to disable the "feature". I use the WD SN850X for my cache. No problems and no error messages. However, I first updated the SN850X's firmware on my regular PC. So I prefer SN850x to SN700. I'm not a fan of your HDDs either. If you get six 4TB drives from that brand, it'll cost around €600. I'd recommend two Thoshiba MG10ACA20TE drives for the same price. They're fast and, in my opinion, quiet. This solution also consumes significantly less power overall.

Yes, I have been using this exact RAM (KSM48E40BD8KI-32HA) with my ASUS Pro WS W680-ACE IPMI for about 9 months. (2x 32GB). No problems and absolutely stable. I am very satisfied and can recommend it without reservation.

As a basic framework, I can recommend the following, which I use myself and am very satisfied with: ASUS Pro WS W680-ACE IPMI KSM48E40BD8KI-32HA i7-14700 Noctua NH-D12L You can use 8 HDDs with the board. You will also need an adapter for the additional HDDs. There are plenty of recommendations for this in the forum. There is also a long post here about the ASUS board that gives you lots of useful tips. With the case, you're looking at around €2,000.

To be on the safe side, you can install the drivers if you haven't already done so: https://unraid.net/community/apps?q=coral#r But I'm assuming it's your board with the M.2 Sata. The Coral TPU requires at least a PCIe Gen2 x1 interface.

You may want to read the data sheet for the ASUS board. Quote: Total supports 3 x M.2 slots and 8 x SATA 6Gb/s ports // 1 x SlimSAS Slot Support SlimSAS NVMe device (supports PCIe 4.0 x4 mode and up to 4 SATA devices) The SlimSAS port can be switched to SATA in the BIOS and you only need to buy the corresponding cable separately. The only advantage of the Supermicro is that IPMI is directly on the board. However, the fan control is worse with the Supermicro because it only has two zones. Personally, I can recommend Asus. I am very happy with it and had Supermicro before. Asus are also quicker with updates for BIOS and KVM. The latest microcode doesn't even seem to be available on the Supermicro website.

I had already reinstalled the container. But now, after uninstalling, I also deleted the folder under appdate and then reinstalled it. Now it's working again... I just have to reset the settings. Thanks again for your always quick response and your help.