1471

Thank you 👍

Just wondering, has anyone tried running 2025.04.13 (latest folderview2 in the app store) on Unraid 7.2? Or is it a case manually installing the 04.08.2025 for now? If so, any idea on a rough timeline for a app store release?

Anyone else having issues since the update 3 days ago? Using the forked version: https://github.com/freender/docker-intel-gpu-telegraf?tab=readme-ov-file 2025-09-13T06:42:39Z I! Loading config: /etc/telegraf/telegraf.conf 2025-09-13T06:42:39Z E! [telegraf] Error running agent: no outputs found, probably invalid config file provided 2025-09-13T06:43:07Z I! Loading config: /etc/telegraf/telegraf.conf 2025-09-13T06:43:07Z E! [telegraf] Error running agent: no outputs found, probably invalid config file provided

Just a heads up, if you're running the latest version of Telegraf (1.34.5-alpine), it seems to cause issues with the 'Ultimate Dashboard'. Until someone clever that me can work out what changes caused the issue, pinning to an older version works: Change from: telegraf:alpine To version: telegraf:1.34.4-alpine

Good spot, it is indeed, woooo! Will switch over later today. Thank you for your efforts keeping this plugin alive @VladoPortos

Well, this thread made the ‘Unraid newsletter’. Hopefully a bit of attention will help getting it into the App Store!

I've got an issue when the Unraid webpage is left open, over time the servers power usage slowly increases. Below is a screen show from a Tasmota smart plug in Home Assistant. You can see when having the webpage closed the power usage idles around 87W, then with the webpage open it starts steadily increasing. I've seen this rise to 110W before I noticed and closed the webpage. When the power usage increases, navigating to different tabs on the webpage also seems sluggish, taking a while to open a different tab etc. Seems others have the same issue, see post on the Unraid subreddit HERE. Issue wasn’t present on 6.12.14 and I’ve not made any significant changes to the system other than upgrading to 7.0.0. Only change has been updating a Server 2022 VM to Server 2025. I've also tried setting the fastusr flag, as per the 7.0.0 relaese notes, no change. I don't think this is the issue as wasnt seeing high flash writes and have plenty of RAM available (normal usage of 35GB out of 64GB total). Diagnostics attached. unraid-server-diagnostics-20250220-0636.zip

Thanks for that, works for me. I had previously been using an old version as a workaround, but your method is a much better solution. Repository telegraf:1.20.2-alpine Post arguments /bin/sh -c 'apk update && apk upgrade && apk add ipmitool && apk add smartmontools && telegraf'

Cool, i'll test when I update to 7.0 over the weekend and update this post with how it goes. Edit: yup, works fine using the latest slackware package.

Thanks @mgutt, Looks like the latest Slackware package is: powertop-2.15-i586-2 Which looks like the same version as you're using on your Github repo: powertop-2.15-x86_64-1.txz and the current version installed via Nerd Tools: powertop-2.15-x86_64-1_nerdtools.txz Looking at the Nerd Tools thread, looks like it might be dying for good this time.

Can I just check, is THIS still the recommended way to install powertop? mkdir /boot/extra cd /boot/extra wget https://github.com/mgutt/unraid-packages/raw/main/6.11.0/powertop-2.15-x86_64-1.txz I’ve previously installed Powertop using Nerd Tools but see it’s deprecated in Unraid 7.0.0.

Running a different set up to you, but I have the same issue with VM's. Can hit C8, but can't get any C State soon as I start a VM (Server 2022 + Home Assistant). Bit of info here:

I don't suppose anyone can run a little test for me? Are you able to hit any C States with just a Windows VM running (indeally Win Server and an intel CPU)? Wondering if the reason I can't get to any C state with a Win VM running is local to me or not.

Right then, I had a bit of time to do some testing earlier in the week, it seems like: Win Server 2022 VM's stops getting to C2 PCI Sata card stops C6 NVME / SSD's stops C8 Frst thing to look at is the VM issue, then look at the sata card as supports ASPM and shouldn't be causing problems. I'd be happy if I could get to C6 for now. Any help would be appreciated. Previous post earlier in this thread with server spec and configuration HERE for info and my testing notes below: _____________________________________________ Leaving powertop running for 2 mins before recording C state. Looking at Pkg(HW) only, CPU C states are fine. SERVER TESTING array on - No C state array off - C2 77% array on (VM off, docker on) - C2 21.5% array on (VM on, docker off) - No C state array on (VM Win on only, docker off) - No C state array on (VM HA on only, docker off) - C2 43.3% array on (VM off, docker off) - C2 54% NOTES: - Seems like the Win Server 2022 VM’s stopping the server from getting to C2 - With the Win VM off and getting to C2, power usage drops from an average of 95W to 75W (a 20W saving) THINGS REMOVED (array off) SATA Card - SSD removed - C2 40.6% + C6 47.9% SATA Card - SSD - NVME removed - C2 37.4% + C3 11.6 + C6 1.7% + C8 39.4% SATA Card - NVME removed - C2 27.2.6% + C6 57.5% SSD - NVME removed - C2 91.9% NOTES: - Seems like the SATA Card is stopping the server from getting to C6 and the SSD's or NVME's are stopping C8. - This should be fine as running the latest firmware available which supports ASPM TO TRY: - Create fresh Win11 VM and see if can get C2 with just that running - DONE - NO DIFFERENCE - Remove mapped drive in Win VM and turn off indexing? - DONE, NO DIFFERENCE - Update BIOS version to latest version - DONE, NO DIFFERENCE - Check firmware of card and maybe lower to recommended? - Set 'PCI native control' in BIOS to disabled (let the BIOS control ASPM)?

Thanks, yea probably the best option at this point. A job for next week.