BarbaGrump

When trying to upgrade 7.2.4 -> 7.3-b2 on a server with just 4G of Ram, the initial plugin installation fails. Maybe some kind of check to see if Ram, and thus /tmp, is to small? plugin: installing: unRAIDServer.plg Executing hook script: pre_plugin_checks plugin: downloading: unRAIDServer.plg ... done plugin: downloading: unRAIDServer-7.3.0-beta.2-x86_64.zip ... 96% plugin: unRAIDServer-7.3.0-beta.2-x86_64.zip download failure: File I/O error Executing hook script: post_plugin_checks

Little late to the party… Im doing something similar. In my /boot/config/go: scp <proxmox-host>:/<path-to-enc-key-on-zfs-encrypted-fileset>/keyfile /root/keyfile

If you using ZFS, you can use sanoid/syncoid to replicate filesets to any other host with ZFS. I'm doing this. I running a PBS that is backuptarget for all vms/cts running on my Proxmox cluster, but also target for ZFS data(appdata mainly) from my virtual Unraid.

UPDATE: It works perfectly to passthrough ASM1166 to Unraid or any other host. I have enabled all ASPM-stuff in BIOS. The culprit is "powertop --auto-tune" settings. Again. See my post about this here. If you really wants to run this(on the F6-424 Max however, it does not really make a difference in power consumption) you have two alternatives: 1. Isolate the ASM1166 on the host. echo "options vfio-pci ids=1b21:1166" > /etc/modprobe.d/isolate-sata.conf echo "blacklist ahci" >> /etc/modprobe.d/pve-blacklist.conf update-initramfs -u 2. Skip the isolation steps, and run all commands produced by "powertop --auto-tune" instead, but excluding the ASM1166 part Below is the commands --auto-tune would have runned on my system(with 1 nic disabled) You can create a list for your own system with powertop -C powertop.csv && cat powertop.csv echo '0' > '/proc/sys/kernel/nmi_watchdog' echo '1500' > '/proc/sys/vm/dirty_writeback_centisecs' echo 'auto' > '/sys/bus/usb/devices/1-3/power/control' echo 'auto' > '/sys/bus/pci/devices/0000:00:14.2/power/control' echo 'auto' > '/sys/bus/pci/devices/0000:03:00.0/power/control' echo 'auto' > '/sys/block/sda/device/power/control' echo 'auto' > '/sys/bus/pci/devices/0000:00:1f.0/power/control' echo 'auto' > '/sys/bus/pci/devices/0000:02:00.0/power/control' echo 'auto' > '/sys/bus/pci/devices/0000:00:04.0/power/control' < This is the ASM1166 echo 'auto' > '/sys/bus/pci/devices/0000:01:00.0/power/control' echo 'auto' > '/sys/bus/pci/devices/0000:00:1f.5/power/control' echo 'auto' > '/sys/bus/pci/devices/0000:00:00.0/power/control' Run all commands above EXCEPT: echo 'auto' > '/sys/bus/pci/devices/0000:00:04.0/power/control'

I have Unraid 7.0.0-beta.4 running on Proxmox 8.2 with virtio, and I see no errors or having any issues. Running on a Terramaster f6-424 Max.

First: great write-up! I have been passing disks with no problems, sure I have to deal with smartctl and spindown on the Proxmoxhost. I am now SSD-only, but when I used spinning rust, I simply ran a ”hdparm -S60 /dev/disk/by-id/YOUR-PASSEDTHROGH-DISK-HERE” on Proxmox startup to make the passed disk spin down after 5 min. Worked like a charm

My posts are now ”complete” 🙂

This is part two of my article on getting Unraid 7 up and running on Proxmox on Terramaster F6-424 Max. See first part here! Getting Unraid 7 to work on Proxmox: My Initial passthrough config: /etc/kernel/cmdline: root=ZFS=rpool/ROOT/pve-1 boot=zfs intel_iommu=on iommu=pt pci=noaer I could probably remove pci=noaer since the BIOS allowed me to turn off Advanced Error Reporting per PCIe channel. /etc/modules: vfio vfio_iommu_type1 vfio_pci vfio_virqfd /etc/modprobe.d/i915.conf options i915 enable_fbc=1 enable_guc=3 /etc/modprobe.d/pve-blacklist.conf blacklist pcspkr Unraid VM-config: General: Name, Id OS: Do not use CD-ROM System: Machine=q35, BIOS=OVMF, Qemu Agent=X Disks: Your own preferences, But Im going for 1T, Discard=X, SSD emulation=X CPU: 8 cores, Type=Host Memory 16384, balloon=0 Then add Unraid USB, iGPU and ASM1166 SATA controller to the VM. After that...Hit Start. ...and nothing happens. Bummer! Ok. Lets kill the vm Drop to shell on your Proxmox-host and run rm /var/lock/qemu-server/lock-<YOUR-VM-ID>.conf qm stop <YOUR-VM-ID> To get things going, we need to isolate the iGPU and SATA-controller. lspci -nn 00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 04:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1166 Serial ATA Controller [1b21:1166] (rev 02) OK, so its 8086:46a8 and 1b21:1166 we want Run echo "options vfio-pci ids=8086:46a8,1b21:1166" > /etc/modprobe.d/vfio.conf echo "blacklist ahci" >> /etc/modprobe.d/pve-blacklist.conf echo "blacklist i915" >> /etc/modprobe.d/pve-blacklist.conf echo "blacklist xe" >> /etc/modprobe.d/pve-blacklist.conf update-initramfs -u -k all reboot Now try to start Unraid VM...Success for you as well, I hope. Well, not all went well... Im getting errors in Unraid dmesg regarding the GPU, but everything (eg hw-transcoding in Plex and Emby, Frigate detection etc.) seems to work just fine. And after shutting Unraid VM down and restart it, the SATA-disks does not show up in Unraid. The isolation of the SATA-controller works...I dont see any SATA-disks in Proxmox. Only after a powerdown/restart of the Proxmox host, disk are visible again. For now Im passing through the disks instead of the controller. This I cant solve. Edit after 2w: So...the backup solution was to passthrough the disks instead. I know Unraid wants full control over the disks, but I have now been running with all my disks passed through, and so far no problems. So, all in all, I'm very happy with the setup. It works very well, and I must say that for the price of the MAX, you got plenty of power to play with. I really recommends this piece of hardware, even though I'm still disapointed with the SATA-passthrough debacle.

Update: It seems that hw-transcoding on Plex works, even though the error above persists.

No, I dont. It works perfect with a Bookworm VM.

I'm trying to get Unraid 7 to work on Proxmox on a Terramaster F6-424 Max. The gpu present it self as: 00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) When I Passthrough the iGPU, I get the following in dmesg: Does anyone else see this, and maybe have a clue on whats going on? Not getting any errors when passing through the GPU to a Debian VM. [Sat Oct 26 16:40:12 2024] ------------[ cut here ]------------ [Sat Oct 26 16:40:12 2024] i915 0000:06:10.0: Platform does not support port C [Sat Oct 26 16:40:12 2024] WARNING: CPU: 5 PID: 1103 at drivers/gpu/drm/i915/display/intel_display.c:7426 assert_port_valid+0x46/0x56 [i915] [Sat Oct 26 16:40:12 2024] Modules linked in: i915(+) intel_rapl_common kvm_intel kvm iosf_mbi drm_buddy ttm video crct10dif_pclmul crc32_pclmul crc32c_intel wmi ghash_clmulni_intel sha512_ssse3 i2c_algo_bit sha256_ssse3 sha1_ssse3 drm_display_helper aesni_intel crypto_simd cryptd rapl drm_kms_helper drm input_leds led_class i2c_i801 virtio_net intel_agp backlight i2c_smbus intel_gtt ahci net_failover failover i2c_core virtio_console libahci agpgart button [Sat Oct 26 16:40:12 2024] CPU: 5 PID: 1103 Comm: udevd Tainted: G U 6.6.56-Unraid #1 [Sat Oct 26 16:40:12 2024] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 4.2023.08-4 02/15/2024 [Sat Oct 26 16:40:12 2024] RIP: 0010:assert_port_valid+0x46/0x56 [i915] [Sat Oct 26 16:40:12 2024] Code: 7f 08 8d 6e 41 4c 8b 67 50 4d 85 e4 75 03 4c 8b 27 e8 e2 4d fd e0 89 e9 4c 89 e2 48 c7 c7 09 70 91 a0 48 89 c6 e8 ee 87 94 e0 <0f> 0b 89 d8 5b 83 e0 01 5d 41 5c c3 cc cc cc cc 90 90 90 90 90 90 [Sat Oct 26 16:40:12 2024] RSP: 0018:ffffc90000de7aa8 EFLAGS: 00010282 [Sat Oct 26 16:40:12 2024] RAX: 0000000000000000 RBX: 000000000000001e RCX: 0000000000000003 [Sat Oct 26 16:40:12 2024] RDX: 0000000001cf00d0 RSI: 0000000000000003 RDI: 00000000ffffffff [Sat Oct 26 16:40:12 2024] RBP: 0000000000000043 R08: 0000000000000000 R09: ffff888101cf1320 [Sat Oct 26 16:40:12 2024] R10: 0000000000000001 R11: 0000000000aaaaaa R12: ffff888100f148a0 [Sat Oct 26 16:40:12 2024] R13: ffff888104271aa8 R14: ffff888100f420c0 R15: ffff888100f42000 [Sat Oct 26 16:40:12 2024] FS: 0000150546a21740(0000) GS:ffff88846fd40000(0000) knlGS:0000000000000000 [Sat Oct 26 16:40:12 2024] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [Sat Oct 26 16:40:12 2024] CR2: 000015054652e000 CR3: 00000001066ee000 CR4: 0000000000750ee0 [Sat Oct 26 16:40:12 2024] PKRU: 55555554 [Sat Oct 26 16:40:12 2024] Call Trace: [Sat Oct 26 16:40:12 2024] <TASK> [Sat Oct 26 16:40:12 2024] ? __warn+0x99/0x11a [Sat Oct 26 16:40:12 2024] ? report_bug+0xd9/0x153 [Sat Oct 26 16:40:12 2024] ? assert_port_valid+0x46/0x56 [i915] [Sat Oct 26 16:40:12 2024] ? handle_bug+0x3c/0x63 [Sat Oct 26 16:40:12 2024] ? exc_invalid_op+0x13/0x60 [Sat Oct 26 16:40:12 2024] ? asm_exc_invalid_op+0x16/0x20 [Sat Oct 26 16:40:12 2024] ? assert_port_valid+0x46/0x56 [i915] [Sat Oct 26 16:40:12 2024] ? assert_port_valid+0x46/0x56 [i915] [Sat Oct 26 16:40:12 2024] ? __pfx_intel_ddi_init+0x10/0x10 [i915] [Sat Oct 26 16:40:12 2024] intel_ddi_init+0xe5/0xd44 [i915] [Sat Oct 26 16:40:12 2024] ? __pfx_intel_ddi_init+0x10/0x10 [i915] [Sat Oct 26 16:40:32 2024] intel_bios_for_each_encoder+0x35/0x4d [i915] [Sat Oct 26 16:40:32 2024] intel_setup_outputs+0xaf/0x6f0 [i915] [Sat Oct 26 16:40:32 2024] intel_display_driver_probe_nogem+0x15f/0x1e1 [i915] [Sat Oct 26 16:40:32 2024] i915_driver_probe+0x721/0x9f7 [i915] [Sat Oct 26 16:40:32 2024] ? __pfx___driver_attach+0x10/0x10 [Sat Oct 26 16:40:32 2024] local_pci_probe+0x3d/0x81 [Sat Oct 26 16:40:32 2024] pci_device_probe+0x17c/0x1d0 [Sat Oct 26 16:40:32 2024] ? sysfs_do_create_link_sd+0x7a/0xab [Sat Oct 26 16:40:32 2024] really_probe+0x115/0x269 [Sat Oct 26 16:40:32 2024] __driver_probe_device+0xc0/0xf2 [Sat Oct 26 16:40:32 2024] driver_probe_device+0x1f/0x77 [Sat Oct 26 16:40:32 2024] __driver_attach+0xdc/0xf5 [Sat Oct 26 16:40:32 2024] bus_for_each_dev+0x7b/0xc2 [Sat Oct 26 16:40:32 2024] bus_add_driver+0xf4/0x1df [Sat Oct 26 16:40:32 2024] driver_register+0x9e/0xdc [Sat Oct 26 16:40:32 2024] i915_init+0x1f/0x7f [i915] [Sat Oct 26 16:40:45 2024] ? __pfx_i915_init+0x10/0x10 [i915] [Sat Oct 26 16:40:45 2024] do_one_initcall+0x80/0x1a4 [Sat Oct 26 16:40:45 2024] ? kmalloc_trace+0x43/0x52 [Sat Oct 26 16:40:45 2024] do_init_module+0x60/0x20d [Sat Oct 26 16:40:45 2024] __do_sys_init_module+0xbc/0xfd [Sat Oct 26 16:40:45 2024] do_syscall_64+0x57/0x7b [Sat Oct 26 16:40:45 2024] entry_SYSCALL_64_after_hwframe+0x78/0xe2 [Sat Oct 26 16:40:45 2024] RIP: 0033:0x1505471f09aa [Sat Oct 26 16:40:45 2024] Code: 48 8b 0d 61 a4 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 2e a4 0d 00 f7 d8 64 89 01 48 [Sat Oct 26 16:40:45 2024] RSP: 002b:00007fff22a98bc8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af [Sat Oct 26 16:40:45 2024] RAX: ffffffffffffffda RBX: 0000000000460b70 RCX: 00001505471f09aa [Sat Oct 26 16:40:45 2024] RDX: 000000000045bfd0 RSI: 0000000000690730 RDI: 0000150545e9e010 [Sat Oct 26 16:40:45 2024] RBP: 0000150545e9e010 R08: 0000000000000007 R09: 0000000000000006 [Sat Oct 26 16:40:45 2024] R10: 0000000000000071 R11: 0000000000000246 R12: 000000000045bfd0 [Sat Oct 26 16:40:45 2024] R13: 0000000000020000 R14: 00000000004616a0 R15: 0000000000000000 [Sat Oct 26 16:40:45 2024] </TASK> [Sat Oct 26 16:40:45 2024] ---[ end trace 0000000000000000 ]--- [Sat Oct 26 16:40:45 2024] i915 0000:06:10.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.29.2 [Sat Oct 26 16:40:46 2024] clocksource: Long readout interval, skipping watchdog check: cs_nsec: 1000724613 wd_nsec: 1000724617 [Sat Oct 26 16:40:57 2024] i915 0000:06:10.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3 [Sat Oct 26 16:40:58 2024] i915 0000:06:10.0: [drm] GT0: HuC: authenticated for all workloads [Sat Oct 26 16:40:59 2024] i915 0000:06:10.0: [drm] GT0: GUC: submission enabled [Sat Oct 26 16:40:59 2024] i915 0000:06:10.0: [drm] GT0: GUC: SLPC enabled [Sat Oct 26 16:41:00 2024] i915 0000:06:10.0: [drm] GT0: GUC: RC enabled [Sat Oct 26 16:41:01 2024] i915 0000:06:10.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by intel_gt_init+0x271/0x28c [i915] [Sat Oct 26 16:41:01 2024] BUG: kernel NULL pointer dereference, address: 0000000000000000 [Sat Oct 26 16:41:02 2024] #PF: supervisor write access in kernel mode [Sat Oct 26 16:41:03 2024] #PF: error_code(0x0002) - not-present page [Sat Oct 26 16:41:03 2024] PGD 1060d2067 P4D 1060d2067 PUD 1060d3067 PMD 0 [Sat Oct 26 16:41:04 2024] Oops: 0002 [#1] PREEMPT SMP NOPTI [Sat Oct 26 16:41:05 2024] CPU: 7 PID: 1103 Comm: udevd Tainted: G U W 6.6.56-Unraid #1 [Sat Oct 26 16:41:05 2024] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 4.2023.08-4 02/15/2024 [Sat Oct 26 16:41:06 2024] RIP: 0010:refcount_inc+0x5/0x28 [i915] [Sat Oct 26 16:41:07 2024] Code: 90 0f 1f 44 00 00 48 89 fe 48 8b 3d 32 eb 15 00 e9 21 ea bd e0 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 b8 01 00 00 00 <f0> 0f c1 07 85 c0 be 02 00 00 00 74 0c 8d 50 01 09 c2 79 0a be 01 [Sat Oct 26 16:41:08 2024] RSP: 0018:ffffc90000de7b08 EFLAGS: 00010246 [Sat Oct 26 16:41:09 2024] RAX: 0000000000000001 RBX: ffff888117e5cc00 RCX: 0000000000000dc0 [Sat Oct 26 16:41:10 2024] RDX: 0000000000000000 RSI: ffff888106a2c000 RDI: 0000000000000000 [Sat Oct 26 16:41:11 2024] RBP: 0000000000000000 R08: 00000000ffffffff R09: 0000000000000001 [Sat Oct 26 16:41:11 2024] R10: 0000000000046430 R11: 0000000000aaaaaa R12: 0000000000000000 [Sat Oct 26 16:41:12 2024] R13: 0000000000001000 R14: 0000000000000180 R15: ffff888100f42000 [Sat Oct 26 16:41:13 2024] FS: 0000150546a21740(0000) GS:ffff88846fdc0000(0000) knlGS:0000000000000000 [Sat Oct 26 16:41:14 2024] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [Sat Oct 26 16:41:14 2024] CR2: 0000000000000000 CR3: 00000001066ee000 CR4: 0000000000750ee0 [Sat Oct 26 16:41:15 2024] PKRU: 55555554 [Sat Oct 26 16:41:16 2024] Call Trace: [Sat Oct 26 16:41:17 2024] <TASK> [Sat Oct 26 16:41:17 2024] ? __die_body+0x1a/0x5c [Sat Oct 26 16:41:18 2024] ? page_fault_oops+0x329/0x376 [Sat Oct 26 16:41:19 2024] ? do_user_addr_fault+0x12d/0x48a [Sat Oct 26 16:41:20 2024] ? exc_page_fault+0xf9/0x116 [Sat Oct 26 16:41:20 2024] ? asm_exc_page_fault+0x22/0x30 [Sat Oct 26 16:41:21 2024] ? refcount_inc+0x5/0x28 [i915] [Sat Oct 26 16:41:22 2024] intel_context_init+0x57/0x14e [i915] [Sat Oct 26 16:41:23 2024] intel_context_create+0x2f/0x43 [i915] [Sat Oct 26 16:41:24 2024] intel_engine_create_pinned_context+0x1e/0xda [i915] [Sat Oct 26 16:41:24 2024] intel_pxp_init+0x17b/0x1ff [i915] [Sat Oct 26 16:41:25 2024] i915_driver_probe+0x74b/0x9f7 [i915] [Sat Oct 26 16:41:26 2024] ? __pfx___driver_attach+0x10/0x10 [Sat Oct 26 16:41:26 2024] local_pci_probe+0x3d/0x81 [Sat Oct 26 16:41:27 2024] pci_device_probe+0x17c/0x1d0 [Sat Oct 26 16:41:28 2024] ? sysfs_do_create_link_sd+0x7a/0xab [Sat Oct 26 16:41:29 2024] really_probe+0x115/0x269 [Sat Oct 26 16:41:29 2024] __driver_probe_device+0xc0/0xf2 [Sat Oct 26 16:41:30 2024] driver_probe_device+0x1f/0x77 [Sat Oct 26 16:41:31 2024] __driver_attach+0xdc/0xf5 [Sat Oct 26 16:41:31 2024] bus_for_each_dev+0x7b/0xc2 [Sat Oct 26 16:41:32 2024] bus_add_driver+0xf4/0x1df [Sat Oct 26 16:41:33 2024] driver_register+0x9e/0xdc [Sat Oct 26 16:41:33 2024] i915_init+0x1f/0x7f [i915] [Sat Oct 26 16:41:34 2024] ? __pfx_i915_init+0x10/0x10 [i915] [Sat Oct 26 16:41:35 2024] do_one_initcall+0x80/0x1a4 [Sat Oct 26 16:41:35 2024] ? kmalloc_trace+0x43/0x52 [Sat Oct 26 16:41:36 2024] do_init_module+0x60/0x20d [Sat Oct 26 16:41:36 2024] __do_sys_init_module+0xbc/0xfd [Sat Oct 26 16:41:37 2024] do_syscall_64+0x57/0x7b [Sat Oct 26 16:41:38 2024] entry_SYSCALL_64_after_hwframe+0x78/0xe2 [Sat Oct 26 16:41:38 2024] RIP: 0033:0x1505471f09aa [Sat Oct 26 16:41:39 2024] Code: 48 8b 0d 61 a4 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 2e a4 0d 00 f7 d8 64 89 01 48 [Sat Oct 26 16:41:40 2024] RSP: 002b:00007fff22a98bc8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af [Sat Oct 26 16:41:41 2024] RAX: ffffffffffffffda RBX: 0000000000460b70 RCX: 00001505471f09aa [Sat Oct 26 16:41:42 2024] RDX: 000000000045bfd0 RSI: 0000000000690730 RDI: 0000150545e9e010 [Sat Oct 26 16:41:42 2024] RBP: 0000150545e9e010 R08: 0000000000000007 R09: 0000000000000006 [Sat Oct 26 16:41:43 2024] R10: 0000000000000071 R11: 0000000000000246 R12: 000000000045bfd0 [Sat Oct 26 16:41:43 2024] R13: 0000000000020000 R14: 00000000004616a0 R15: 0000000000000000 [Sat Oct 26 16:41:44 2024] </TASK> [Sat Oct 26 16:41:45 2024] Modules linked in: i915(+) intel_rapl_common kvm_intel kvm iosf_mbi drm_buddy ttm video crct10dif_pclmul crc32_pclmul crc32c_intel wmi ghash_clmulni_intel sha512_ssse3 i2c_algo_bit sha256_ssse3 sha1_ssse3 drm_display_helper aesni_intel crypto_simd cryptd rapl drm_kms_helper drm input_leds led_class i2c_i801 virtio_net intel_agp backlight i2c_smbus intel_gtt ahci net_failover failover i2c_core virtio_console libahci agpgart button [Sat Oct 26 16:41:47 2024] CR2: 0000000000000000 [Sat Oct 26 16:41:47 2024] ---[ end trace 0000000000000000 ]---

Just One more question…which parms in Bios did you change? Or is above with default settings?

This is a thread(or actually two threads) to share experience and information regarding my latest project: virtulize Unraid(maybe 7.0) on PVE on a brand new Terramaster F6-424 Max that will replace my main pve-node. I will do this as a multipart post, and I will update posts as I go. My hope is that this can help others in the future. Thanks to @Piece that helped me with some hw-info! Pt.1 - Background, info and Proxmox setup Pt.2 - Unraid. Setup, Installation and configuration of Unraid. This part Is also published here on Unraid.net

That is really good results. I’ll be running unraid on proxmox with ~15 containers, but also ~10 vms and lxcs. All ssd/nvme.

How did it go with ASPM tests? I've always had "visual" problems on nasboxes(f4-424 pro, asustor 6704 etc) with recoverable errors but never "real" problems so I have just hidden the errors. Did you needed to ug ASM1166 FW, or is it recent? A Bummer that a FW-upgrade cant be done without Windows...

It is a 120mm Arctic fan. Not the most effective.

I've fixed that problem with black scotch-tape... 🙂

Interesting! Exactly this is my next adventure...to put proxmox on the AS6704T and move my unraid VM(and the rest of VMs) that runs on a DIY rig for the moment. Will get back with my findings. I did replace the Fan(se post #1) and that had effect on the temp. You hammer F5 to get to a menu att boot where you use tab to choose "settings". From there its a ordinary bios. Kernel panic...yikes! Is it Unraid VM that panics or is it Proxmox? I'm running Unraid under Proxmox(SATA-controller and GPU passed through), and its rock solid. My reason to step away from my much more powerfull DIY-rig(core i5 11500T) back to this nice AS6704T, is due to severe problems with the nic...the dreaded V225-I that craches under load dispite me trying every solution on the Internet.

It just showin "Starting up..." or something like that. I've disconnectad the display, so I dont remember exactly.

@independence Any updates on your adventures with the Asustor?

I will look into it...can never save to much cpu cycles -> lower power consumption 🙂

Thanx! I run all my apps on a share with the "only" option set for the cache 🙂

Really Awsome! Working perfect! One question...Is there a reason why the persistant storage (/ms-edge) by default maps to a disk rather than a share? i.e Data Dir: /mnt/cache_1tb/appdata/micrososft-edge/ whereas the share instead would be /mnt/user/appdata/microsoft-edge I changed to the share, and everything seems to work. Once again...thank you for your effort!

Damn that was fast! I'll give it at try pronto!

I understand the problem. Allthough its not the way containers is supposed to work... could one think of a 0.1 version where edge is kept updated from within the container(persistant storage)...the same way most nextcloud-container works? Or is that as complicated as the way you do this with the chromium?