Interstellar

Just noticed that when running this pre clear script that UnRAID keeps trying to put the disks to sleep every 15 minutes (as per my array settings). Not the end of the world, but it really shouldn't be attempting to spin down disks that are being pre-cleared. I've changed my Spindown delay to 60 mins whilst the disks pre clear. This comment suggests this is intended behaviour: I don't agree if that is the case...!

Yes I saw that, but I can’t have the server down too much otherwise the family get annoyed at the lack of internet. Not in a massive rush, it works and that’s good enough for now. 🤣

Have rebooted many times and it’s been spot on every time, thanks for the update 👍

Sweet. I shall get on the RC when it comes along

Recently upgraded to a i5-13500 hoping to isolate and passthrough the performance cores for a gaming VM leaving the eight(!) efficiency cores to deal with Dockers, UnRAID processes, etc... After a bit of faffing about I finally got my RX6600 vfio-binded and working (Error 43 was the problem... Resize BAR). However, I have a number of questions now that I can't find the answer to so you more knowledgable technical folk can explain the following. 1. When threads 2-11 (P-Core + HT 2-6) are Isolated, I am still able to use those cores in UnRAID (E.g. I can run Prime95 and that will use all 20 threads). When this happens obviously the performance of the VM goes through the floor, but what the actual problem is random processes still use those cores (even with Dockers pinned to the efficiency cores) causing games to stutter. I can see the cores waking up from C7 sleep (corefreq) when the VM is shutdown but I can't tell which process(es) they are. So my question here is, why when cores are isolated do certain processes still insist on using the isolated cores and is there any way of stopping it? 2. Core 0 - Passing through core 0 causes stuttering and poor performance which apparently is to be expected. So my question here is, is there any way of re-ordering the cores so the E-Cores come first and the P-Cores come second. It is a bit annoying having to sacrifice a P-core to Unraid when it has eight underutilised and more efficent E-Cores available...!! 3. An alternative would be to Upgrade the VM to W11 and then passthrough maybe two E-cores instead, however I am unsure (without spending time trying it) if the type of core is actually detectable by the VM such that the thread director can schedule tasks accordingly. The VM can't see the live status of the clock frequency in things like HWInfo, so how would it know if its a P or E-Core? Anyone shed some light on the above?

Is 6.12 running Kernal 6.1 yet? Want to try Resize BAR and that needs 6.1 at minimum

Having read through this topic it sounds like that Resize BAR sort-of works with AMD as long as you have kernel v6? My RX6600 with Resize BAR off in BIOS currently shows: lspci -vvvs 03:00.0 | grep BAR Capabilities: [200 v1] Physical Resizable BAR BAR 0: current size: 256MB, supported: 256MB 512MB 1GB 2GB 4GB 8GB BAR 2: current size: 2MB, supported: 2MB 4MB 8MB 16MB 32MB 64MB 128MB 256MB When I turn it on I get a Code 43 error in the VM. It'd be nice for it to work, get a few extra FPS, so I assume I need to wait for the kernel to be upgraded then add the xml changes?

Recently upgraded my motherboard and now I get this when I try and use the Fan Control software... <br /><b>Warning</b>: file_get_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon2/pwm1_enable): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>40</b><br /><br /><b>Warning</b>: file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon2/pwm1_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>42</b><br /><br /><b>Warning</b>: file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon2/pwm1_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br />/sys/devices/platform/nct6687.2592/hwmon/hwmon2/fan1_input After installing the ict6687 plugin I do have all the sensors and I can manually set the fan speed via the command line. nct6687-isa-0a20 Adapter: ISA adapter +12V: 12.02 V (min = +12.00 V, max = +12.05 V) +5V: 5.04 V (min = +5.03 V, max = +5.05 V) +3.3V: 3.35 V (min = +3.34 V, max = +3.35 V) CPU Soc: 616.00 mV (min = +0.16 V, max = +1.20 V) CPU Vcore: 662.00 mV (min = +0.66 V, max = +0.66 V) CPU 1P8: 0.00 V (min = +0.00 V, max = +0.00 V) CPU VDDP: 0.00 V (min = +0.00 V, max = +0.00 V) DRAM: 1.22 V (min = +0.23 V, max = +2.40 V) Chipset: 946.00 mV (min = +0.92 V, max = +0.95 V) CPU SA: 898.00 mV (min = +0.90 V, max = +0.90 V) Voltage #2: 1.54 V (min = +1.53 V, max = +1.54 V) AVCC3: 3.32 V (min = +3.32 V, max = +3.34 V) AVSB: 3.34 V (min = +3.34 V, max = +3.36 V) VBat: 1.06 V (min = +1.06 V, max = +1.06 V) Array Fan: 630 RPM (min = 596 RPM, max = 3174 RPM) Array Fan: 1532 RPM (min = 580 RPM, max = 1540 RPM) Array Fan: 1235 RPM (min = 0 RPM, max = 1301 RPM) CPU: +30.5°C (low = +27.5°C, high = +87.0°C) MB Temp: +33.5°C (low = +33.0°C, high = +39.5°C) VRM MOS: +32.0°C (low = +32.0°C, high = +45.5°C) PCH: +46.0°C (low = +46.0°C, high = +53.0°C) CPU Socket: +31.0°C (low = +30.5°C, high = +56.0°C) PCIe x1: +29.0°C (low = +29.0°C, high = +30.5°C) M2_1: +32.0°C (low = +31.5°C, high = +32.0°C) Searching this thread brings up the error but not the solution unless I'm being silly? There is no pwm_enable, so maybe that is why it is falling over? echo 255 > pwm1 for example, works. -r--r--r-- 1 root root 4096 Feb 2 22:08 fan1_input -r--r--r-- 1 root root 4096 Feb 2 22:09 fan1_label -r--r--r-- 1 root root 4096 Feb 2 22:08 fan1_max -r--r--r-- 1 root root 4096 Feb 2 22:08 fan1_min -r--r--r-- 1 root root 4096 Feb 2 22:08 fan2_input -r--r--r-- 1 root root 4096 Feb 2 22:09 fan2_label -r--r--r-- 1 root root 4096 Feb 2 22:08 fan2_max -r--r--r-- 1 root root 4096 Feb 2 22:08 fan2_min -r--r--r-- 1 root root 4096 Feb 2 22:08 fan3_input -r--r--r-- 1 root root 4096 Feb 2 22:09 fan3_label -r--r--r-- 1 root root 4096 Feb 2 22:08 fan3_max -r--r--r-- 1 root root 4096 Feb 2 22:08 fan3_min -r--r--r-- 1 root root 4096 Feb 2 22:08 fan4_input -r--r--r-- 1 root root 4096 Feb 2 22:09 fan4_label -r--r--r-- 1 root root 4096 Feb 2 22:08 fan4_max -r--r--r-- 1 root root 4096 Feb 2 22:08 fan4_min -r--r--r-- 1 root root 4096 Feb 2 22:08 fan5_input -r--r--r-- 1 root root 4096 Feb 2 22:09 fan5_label -r--r--r-- 1 root root 4096 Feb 2 22:08 fan5_max -r--r--r-- 1 root root 4096 Feb 2 22:08 fan5_min -r--r--r-- 1 root root 4096 Feb 2 22:08 fan6_input -r--r--r-- 1 root root 4096 Feb 2 22:09 fan6_label -r--r--r-- 1 root root 4096 Feb 2 22:08 fan6_max -r--r--r-- 1 root root 4096 Feb 2 22:08 fan6_min -r--r--r-- 1 root root 4096 Feb 2 22:08 fan7_input -r--r--r-- 1 root root 4096 Feb 2 22:09 fan7_label -r--r--r-- 1 root root 4096 Feb 2 22:08 fan7_max -r--r--r-- 1 root root 4096 Feb 2 22:08 fan7_min -r--r--r-- 1 root root 4096 Feb 2 22:08 fan8_input -r--r--r-- 1 root root 4096 Feb 2 22:09 fan8_label -r--r--r-- 1 root root 4096 Feb 2 22:08 fan8_max -r--r--r-- 1 root root 4096 Feb 2 22:08 fan8_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in0_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in0_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in0_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in0_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in10_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in10_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in10_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in10_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in11_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in11_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in11_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in11_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in12_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in12_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in12_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in12_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in13_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in13_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in13_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in13_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in1_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in1_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in1_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in1_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in2_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in2_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in2_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in2_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in3_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in3_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in3_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in3_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in4_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in4_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in4_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in4_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in5_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in5_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in5_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in5_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in6_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in6_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in6_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in6_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in7_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in7_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in7_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in7_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in8_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in8_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in8_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in8_min -r--r--r-- 1 root root 4096 Feb 2 22:08 in9_input -r--r--r-- 1 root root 4096 Feb 2 22:08 in9_label -r--r--r-- 1 root root 4096 Feb 2 22:08 in9_max -r--r--r-- 1 root root 4096 Feb 2 22:08 in9_min -r--r--r-- 1 root root 4096 Feb 2 22:08 name drwxr-xr-x 2 root root 0 Feb 2 22:22 power/ -rw-r--r-- 1 root root 4096 Feb 5 20:19 pwm1 -rw-r--r-- 1 root root 4096 Feb 5 20:14 pwm2 -rw-r--r-- 1 root root 4096 Feb 5 20:14 pwm3 -rw-r--r-- 1 root root 4096 Feb 2 22:22 pwm4 -rw-r--r-- 1 root root 4096 Feb 2 22:22 pwm5 -rw-r--r-- 1 root root 4096 Feb 2 22:22 pwm6 -rw-r--r-- 1 root root 4096 Feb 2 22:22 pwm7 -rw-r--r-- 1 root root 4096 Feb 2 22:22 pwm8 lrwxrwxrwx 1 root root 0 Feb 2 22:08 subsystem -> ../../../../../class/hwmon/ -r--r--r-- 1 root root 4096 Feb 2 22:08 temp1_input -r--r--r-- 1 root root 4096 Feb 2 22:08 temp1_label -r--r--r-- 1 root root 4096 Feb 2 22:08 temp1_max -r--r--r-- 1 root root 4096 Feb 2 22:08 temp1_min -r--r--r-- 1 root root 4096 Feb 2 22:08 temp2_input -r--r--r-- 1 root root 4096 Feb 2 22:09 temp2_label -r--r--r-- 1 root root 4096 Feb 2 22:08 temp2_max -r--r--r-- 1 root root 4096 Feb 2 22:08 temp2_min -r--r--r-- 1 root root 4096 Feb 2 22:08 temp3_input -r--r--r-- 1 root root 4096 Feb 2 22:08 temp3_label -r--r--r-- 1 root root 4096 Feb 2 22:08 temp3_max -r--r--r-- 1 root root 4096 Feb 2 22:08 temp3_min -r--r--r-- 1 root root 4096 Feb 2 22:08 temp4_input -r--r--r-- 1 root root 4096 Feb 2 22:08 temp4_label -r--r--r-- 1 root root 4096 Feb 2 22:08 temp4_max -r--r--r-- 1 root root 4096 Feb 2 22:08 temp4_min -r--r--r-- 1 root root 4096 Feb 2 22:08 temp5_input -r--r--r-- 1 root root 4096 Feb 2 22:08 temp5_label -r--r--r-- 1 root root 4096 Feb 2 22:08 temp5_max -r--r--r-- 1 root root 4096 Feb 2 22:08 temp5_min -r--r--r-- 1 root root 4096 Feb 2 22:08 temp6_input -r--r--r-- 1 root root 4096 Feb 2 22:08 temp6_label -r--r--r-- 1 root root 4096 Feb 2 22:08 temp6_max -r--r--r-- 1 root root 4096 Feb 2 22:08 temp6_min -r--r--r-- 1 root root 4096 Feb 2 22:08 temp7_input -r--r--r-- 1 root root 4096 Feb 2 22:08 temp7_label -r--r--r-- 1 root root 4096 Feb 2 22:08 temp7_max -r--r--r-- 1 root root 4096 Feb 2 22:08 temp7_min -rw-r--r-- 1 root root 4096 Feb 2 22:08 uevent

Agreed that board is not suitable for a 13900K. I'm getting one but running a i5-13500 on it (154W Turbo, apparently). 7 E-cores for UnRAID, 1 E-core for Opnsense, 6 P-cores for Windows 10 VM.

Happening for me too, has been for years now across all three last Mac OS releases and associated Safari versions. Disabled all my extensions, still the same thing. Have to use Chrome every time...

Still getting the issue where I have to manually install it after start. The error during boot and no Corefreq icon in settings: Jan 26 19:25:25 tower root: plugin: checking: /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz - MD5 Jan 26 19:25:25 tower root: plugin: skipping: /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz already exists Jan 26 19:25:25 tower root: plugin: running: /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz Jan 26 19:25:25 tower root: Jan 26 19:25:25 tower root: +============================================================================== Jan 26 19:25:25 tower root: | Installing new package /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz Jan 26 19:25:25 tower root: +============================================================================== Jan 26 19:25:25 tower root: Jan 26 19:25:25 tower root: Verifying package CoreFreq-2022.07.21.txz. Jan 26 19:25:25 tower root: Installing package CoreFreq-2022.07.21.txz: Jan 26 19:25:25 tower root: PACKAGE DESCRIPTION: Jan 26 19:25:25 tower root: Package CoreFreq-2022.07.21.txz installed. Jan 26 19:25:25 tower root: plugin: creating: /usr/local/emhttp/plugins/CoreFreq/README.md - from INLINE content Jan 26 19:25:25 tower root: plugin: running: anonymous Jan 26 19:25:29 tower root: Jan 26 19:25:29 tower root: ------ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR-------- Jan 26 19:25:29 tower root: ---Can't get latest CoreFreq version and found no local package!--- Jan 26 19:25:29 tower root: Jan 26 19:25:29 tower root: plugin: run failed: /bin/bash Jan 26 19:25:30 tower root: Executing hook script: post_plugin_checks Then after I try manually installing it again once the internet is back I get the Settings Icon and a blank page: Jan 26 19:27:59 tower root: plugin: running: anonymous Jan 26 19:27:59 tower root: plugin: creating: /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz - downloading from URL https://raw.githubusercontent.com/ich777/unraid-corefreq/master/packages/CoreFreq-2022.07.21.txz Jan 26 19:27:59 tower root: plugin: checking: /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz - MD5 Jan 26 19:27:59 tower root: plugin: running: /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz Jan 26 19:27:59 tower root: plugin: creating: /usr/local/emhttp/plugins/CoreFreq/README.md - from INLINE content Jan 26 19:27:59 tower root: plugin: running: anonymous Jan 26 19:28:04 tower root: plugin: corefreq.plg installed Then I have to remove and install it again and it finally works: Jan 26 19:29:20 tower root: plugin: running: anonymous Jan 26 19:29:20 tower root: plugin: corefreq.plg removed Jan 26 19:29:25 tower root: plugin: running: anonymous Jan 26 19:29:25 tower root: plugin: creating: /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz - downloading from URL https://raw.githubusercontent.com/ich777/unraid-corefreq/master/packages/CoreFreq-2022.07.21.txz Jan 26 19:29:25 tower root: plugin: checking: /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz - MD5 Jan 26 19:29:25 tower root: plugin: running: /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz Jan 26 19:29:25 tower root: plugin: creating: /usr/local/emhttp/plugins/CoreFreq/README.md - from INLINE content Jan 26 19:29:25 tower root: plugin: running: anonymous Jan 26 19:29:27 tower root: plugin: corefreq.plg installed Jan 26 19:29:37 tower emhttpd: cmd: /usr/local/emhttp/plugins/CoreFreq/include/test.sh Jan 26 19:29:38 tower kernel: corefreqk: loading out-of-tree module taints kernel. Jan 26 19:29:38 tower kernel: CoreFreq(3:-1:-1): Processor [ 06_9E] Architecture [Coffee Lake/S] CPU [6/6] Very easy for you to test this, boot your server without an active internet connection. Its 100% repeatable for me.

What’s the power usage in windows? it may just be with certain things happening you just can’t go into C2. what does corefreq-cli say for power?

I don't include those embedded type things - What I meant was you can’t go out and buy a ARM motherboard/CPU combo from Amazon and plug 4 SATA HDDs into them, which is what I meant. 👍 Edit: Seems there is the odd thing floating about... From 10 years ago..!: https://www.gigabyte.com/Enterprise/Server-Motherboard/MP30-AR0-rev-11 Also this is starting to look like something that you'd really run UnRAID on: https://en.t-firefly.com/product/industry/itx3588j But can't find it for sale anywhere even nearly a year later. So I'm going to stick with my statement that you can't currently buy anything that you'd want to install UnRAID on thus no business case.

Firstly, you're posting on a UnRAID forum. UnRAID is, at the core, a NAS. Hence you'd forgive the people who know it as NAS software assuming that you'd use it... as a NAS. It'd be interesting if anyone uses it as a non-NAS but I've not come across anyone doing so, I'm sure there are a few, but I'd guess less than a few %. Secondly, regarding Plex - Unless I'm transcoding/generating Thumbnails/etc Plex uses <1% on average. If Plex is using one-core 24/7 then you have something wrong. If you're regularly transcoding 4K for streaming then a GPU would be significantly faster and more efficient than a CPU. GTX1050/RX5600/RX6600 idle at a couple of watts for example and the latter certainly have the ability to transcode 4K H265. Thirdly, getting to your question - The NAS ARM hardware market is, frankly, non-existent. I'm not sure if there is any ARM NAS stuff out there outside of some very niche things. Hence UnRAID won't, until there is actual ARM NAS hardware available, bother to convert it over. Yes they have started working on Linux for AS, but is it a fully fledged, 100% performant and stable distro yet? I'm fairly sure the answer is no. Linux on ARM vs Linux on AS is a completely different kettle of fish. It'll be years before something like Ubuntu works natively on AS as well as it does on x86. So in summary: Zero current business case for ARM, let alone AS.

Post might be a bit late… but here goes anyway… This is going to be difficult to do a direct comparison so let’s do some basic calcs. All your HDDs and SSDs are somewhere around 0.5-1W idle. 15 of them, so let’s call that 8-10W A 1050Ti apparently uses 3-4W when idle, however we’d need to check if it is indeed idling so might be worth removing it to see what happens. Fans are probably using 1W each. Again can unplug them temporarily to get a reading. When I removed my SAS controller from my old server (consolidated 10 4TB drives into four 10TB drives) I dropped 10W, plus a further 6W from the drive consolidation (and 40!W when they were all spinning!) I’m going to guess the H310 won’t be far off that. So adding all that up.. 25-30W bringing you down to ~30W. You don’t state the PSU you’re using unless I’ve missed it, if it’s not a Titanium/Platinum the efficiency below 10% load could be as bad as 70%. That leaves the power draw of the Ryzen + Mobo at low 20s of watts. Add to the fact the GPU and LBA card will require PCI-E lanes to be switched on I can see the 20W reading being about right, given that the first Gen Ryzens really sucked idle power wise. My server (thanks to mgutts script) without the four port NIC idles at ~9-10W according to the UPS. That’s four 14TB drives, H310 motherboard, 16GB DDR4, 8600T, 1TB NVME, 550W Platinum PSU. So if you really want to lower the consumption, then sadly it’s Intel (I really wanted to go AMD but the idle power draw of early ryzens is poor) plus storage consolidation (to get rid of the LBA card). May half the draw then.

It seems to be that your requirements are far off what a NAS is expected to do. Talking about Bluetooth / iPhone integration, it’s a NAS, why would you need that? Perfectly possible to build a low power NAS to do the 4K transcoding bit. Won’t be as low power as a Mini but that’s one of the great things about AS.

Upgraded from 6.11.1 to 6.11.5 last night. No dramas. Everything working OK overnight.

Looking at those links it looks like they are talking about bridging NICs etc which may cause security concerns, that is not how mine is setup. I have two cores isolated, dedicated to the VM and the PCI-E NIC isolated and passed through to the VM, so it's not really as they are describing at all..! In any case, off topic..! Once installed, corefreq seems to work perfectly for me. I change the TDP limits from the UI which is very useful!

Yes only SATA. No SAS etc cards. I used to have a SAS card, can't remember which Highpoint card it was. A few years ago I used to have 8 odd 4TB drives hanging off it. Since upgrading to four 14TBs thus being able to ditch the card to only use internal SATA ports, I remember dropping a good 5W if not more when I removed it. Minecraft/Windows VMs are probably way more intensive. As powertop shows for cores 4/5, they are isolated and only used by my OpnSENSE VM and they are spending 60-70% of their time in C7, thus obviously not that intensive. corefreq-cli shows CPU Package power at about 4-5W with the VMs/Dockers running and 2-3W without them. As for iGPU, turns out something is installed. I think because maybe UnRAID includes them by default now. I don't recall installing them! Kernel driver in use: i915 Kernel modules: i915

Not sure why you'd think that. I've had it running on there for years. I did briefly have it running on a Thin Client alongside but then why have two devices running 24/7 instead of one? Also couldn't support full FTTP line speed unless I spent more £ than the server was actually worth so what's the point? (Plus another 5W of power draw...!) Next time I encounter the problem I will 👍

No idea - completely headless. None of my dockers need it as far as I'm aware, I don't pass it through to Plex for example. Don't even have the drivers installed - is it a problem its being used briefly? Up to 1.5% if I look now. Edit: Back to 0.3% Is there a way to find out what is using the GPU? I have about 15 dockers running and a OPNSense VM running on cores 4 and 5 (isolated), stopping all the dockers/VMs drops the average usage to low single digit CPU usage and drops 1-2W off the power.

DNS/IP/etc is fixed, it's just there is no internet until the VM starts. Plugins are installed before the VM starts/finishes booting up so it'll always fail this step. It then moves it into the "Failed to Install" tab of the plugins window. See log for what happens: Dec 4 19:42:53 tower root: plugin: installing: corefreq.plg Dec 4 19:42:53 tower root: Executing hook script: pre_plugin_checks Dec 4 19:42:53 tower root: plugin: running: anonymous Dec 4 19:42:53 tower root: plugin: checking: /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz - MD5 Dec 4 19:42:53 tower root: plugin: skipping: /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz already exists Dec 4 19:42:53 tower root: plugin: running: /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz Dec 4 19:42:53 tower root: Dec 4 19:42:53 tower root: +============================================================================== Dec 4 19:42:53 tower root: | Installing new package /boot/config/plugins/corefreq/CoreFreq-2022.07.21.txz Dec 4 19:42:53 tower root: +============================================================================== Dec 4 19:42:53 tower root: Dec 4 19:42:53 tower root: Verifying package CoreFreq-2022.07.21.txz. Dec 4 19:42:53 tower root: Installing package CoreFreq-2022.07.21.txz: Dec 4 19:42:53 tower root: PACKAGE DESCRIPTION: Dec 4 19:42:53 tower root: Package CoreFreq-2022.07.21.txz installed. Dec 4 19:42:53 tower root: plugin: creating: /usr/local/emhttp/plugins/CoreFreq/README.md - from INLINE content Dec 4 19:42:53 tower root: plugin: running: anonymous Dec 4 19:42:58 tower root: Dec 4 19:42:58 tower root: ------ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR-------- Dec 4 19:42:58 tower root: ---Can't get latest CoreFreq version and found no local package!--- Dec 4 19:42:58 tower root: Dec 4 19:42:58 tower root: plugin: run failed: /bin/bash Dec 4 19:42:58 tower root: Executing hook script: post_plugin_checks When you go to Settings, then corefreq, it is a blank page other than the normal header/footer. I tried installing it from CA, hit done, when to the settings page --> Blank Removed it from Plugins page, installed it via the plugins link instead --> Blank page again Removing it, reinstalling it again from CA and waiting more than 30 seconds after the "Post Plugins Check" line appears seems to allow it to complete whatever it needs to do to work as the normal page appeared for me after that. I did not that when removing it the second time it did say it wouldn't find a few things, which if the page/icons/etc weren't installed then that would explain the blank page. I.e. Maybe worth adding a check at the end of the script to make sure the page etc have actually been installed?

Having two issues with this plugin. First one is it fails to install on restart as it wants to download the package every time. Problem is my server runs OpnSENSE so it either needs to wait 5 minutes or it needs to store the package locally. Second one is that it takes a few attempts to install it and not get a blank page for its settings. No errors in syslog so difficult to see what is going on..!

So after mutt pointed me to this, I've had a go with powertop. To check BIOS settings requires connecting a monitor and I can't be bothered with that right now... Running --auto-tune gives be a 6W(!) drop from 30W to 24W... As expected my NIC prevents package C10, but the cores are going into C7 the majority of the time. Not done hpet=disable yet i5-8600T (50mV under-volt) 16GB DDR4 (non-ECC) H310CM-HDV/M.2 1TB M2 Intel Quad-Port NIC Four 14TB WD (Shucked) 320GB 2.5" (CCTV Stream) OPNSense VM running on cores 4/5 (isolated) Multiple Dockers include Home Assistant, Node Red, Plex, Grafana, InfluxDB, Telegraf, MairaDB, Mosquitto plus others... Pkg(HW) | Core(HW) | CPU(OS) 0 | | C0 active 6.7% | | POLL 0.0% 0.0 ms | | C1 0.2% 0.1 ms C2 (pc2) 6.7% | | C3 (pc3) 44.8% | C3 (cc3) 2.5% | C3 1.8% 0.1 ms C6 (pc6) 0.0% | C6 (cc6) 12.1% | C6 14.6% 0.5 ms C7 (pc7) 0.0% | C7 (cc7) 69.7% | C7s 0.1% 1.8 ms C8 (pc8) 0.0% | | C8 12.4% 0.9 ms C9 (pc9) 0.0% | | C9 0.3% 6.7 ms C10 (pc10) 0.0% | | | | C10 58.4% 5.7 ms | | C1E 4.0% 0.1 ms | Core(HW) | CPU(OS) 1 | | C0 active 7.5% | | POLL 0.0% 0.0 ms | | C1 0.7% 0.1 ms | | | C3 (cc3) 2.6% | C3 1.9% 0.1 ms | C6 (cc6) 8.4% | C6 12.3% 0.3 ms | C7 (cc7) 63.2% | C7s 0.1% 0.4 ms | | C8 8.5% 0.6 ms | | C9 1.5% 0.7 ms | | | | C10 58.6% 2.2 ms | | C1E 7.8% 0.1 ms | Core(HW) | CPU(OS) 2 | | C0 active 8.2% | | POLL 0.0% 0.0 ms | | C1 1.1% 0.0 ms | | | C3 (cc3) 1.7% | C3 1.3% 0.1 ms | C6 (cc6) 10.4% | C6 13.0% 0.3 ms | C7 (cc7) 62.5% | C7s 0.2% 1.2 ms | | C8 10.9% 0.6 ms | | C9 3.1% 1.1 ms | | | | C10 52.0% 2.3 ms | | C1E 9.2% 0.1 ms | Core(HW) | CPU(OS) 3 | | C0 active 6.9% | | POLL 0.0% 0.0 ms | | C1 0.7% 0.1 ms | | | C3 (cc3) 2.8% | C3 2.7% 0.1 ms | C6 (cc6) 9.4% | C6 13.3% 0.3 ms | C7 (cc7) 63.7% | C7s 0.0% 1.1 ms | | C8 7.3% 0.5 ms | | C9 1.0% 0.7 ms | | | | C10 59.0% 4.0 ms | | C1E 7.9% 0.1 ms | Core(HW) | CPU(OS) 4 | | C0 active 10.8% | | POLL 0.0% 0.0 ms | | C1 0.5% 0.0 ms | | | C3 (cc3) 4.2% | C3 2.5% 0.1 ms | C6 (cc6) 5.4% | C6 8.8% 0.2 ms | C7 (cc7) 67.1% | C7s 0.0% 0.0 ms | | C8 17.4% 0.7 ms | | C9 0.5% 3.6 ms | | | | C10 52.1% 4.9 ms | | C1E 6.3% 0.1 ms | Core(HW) | CPU(OS) 5 | | C0 active 13.9% | | POLL 0.0% 0.0 ms | | C1 1.0% 0.0 ms | | | C3 (cc3) 0.9% | C3 1.2% 0.1 ms | C6 (cc6) 4.3% | C6 5.5% 0.2 ms | C7 (cc7) 70.7% | C7s 0.0% 0.0 ms | | C8 6.9% 0.7 ms | | C9 2.5% 1.1 ms | | | | C10 62.9% 4.6 ms | | C1E 6.5% 0.1 ms | GPU | | | | Powered On 0.2% | | RC6 99.8% | | RC6p 0.0% | | RC6pp 0.0% | | | Will test over the next few weeks...!

2% above 5W, seems solid enough Will check, cores certainly spend a lot of time in C7, will restart my server tomorrow to see what powertop says. Maybe so, but I've run it with and without the card in, and it was a 4-5W change, so technically the contribution of the card is removed anyway. Isn't that a Gold rated PSU? Mine is Platinum so I'd hope its better Heavily stress tested this CPU, prime95 for 48 hours, various memory tests, and 90 days uptime all seems good at -50mV! Doesn't make my parity check take longer and I don't believe this is the case. There are low leakage CPUs (Mobile) and high leakage CPUs (Tend to go into high end desktop, i.e. K). The 8600T has an idle voltage lower than the 8600K I used to have (600mV against 700mV). It's very difficult to find idle values for memory power usage. Websites such as this show a marked change in power usage when you increase capacity: https://www.tomshardware.com/reviews/intel-core-i7-5960x-haswell-e-cpu,3918-13.html but likely that is under load. Ultimately you have more RAM, that is more memory that needs to be refreshed every x number of cycles, plus ECC which requires an additional die to store the parity information IIRC and then the memory controller in theory is working harder (albeit not at idle). How much those things add is the question... 11W seemed pretty damn good at the time Will have to check these details...! I still don't see how I'd get anywhere near your power draw though.