OddMagnet

still got the problem, though it looks like it's not only spamming deletions now: Feb 16 12:39:43 OddNas avahi-daemon[17573]: Registering new address record for ADDRESS on br0.*. Feb 16 12:39:47 OddNas dhcpcd[1016]: br0: deleting address ADDRESS/64 Feb 16 12:39:47 OddNas avahi-daemon[17573]: Withdrawing address record for ADDRESS on br0. Feb 16 12:41:36 OddNas dhcpcd[1016]: br0: deleting address ADDRESS/64 Feb 16 12:42:44 OddNas avahi-daemon[17573]: Registering new address record for ADDRESS on br0.*.

By variables I meant that I replaced the same numbers in my logs with the same words, to anonymise my IPs Not sure where "dhcpcd" would be coming from then. I have these Plugins installed: Appdata Backup CA Mover Tuning Community Apps Compose.Manager Dynamix Active Streams File Manager S3 Sleep System Buttons System Information System Statistics System Temperature Enhanced Log Viewer File Activity Fix Common Problems Folder View Intel GPU TOP NerdTools Open Files Theme Engine Tips and Tweaks Unassigned Devices + Preclear Unraid Connect User Scripts I checked NerdTools and it isn't installed there (not even listed there).

When checking the logs, they're flooded with "deleting address". Here's a bit of those logs: Feb 11 04:44:52 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:45:07 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:45:58 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:49:18 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:49:23 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:49:27 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:54:59 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:55:04 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:57:44 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:57:45 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:57:47 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 04:58:19 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:07:30 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:08:16 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:16:08 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:16:12 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:19:04 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:19:05 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:19:23 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:19:28 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:22:06 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:22:10 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:22:12 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:22:15 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:22:16 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:22:32 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:26:29 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:26:33 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:26:37 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:27:44 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 05:59:12 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:07:32 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:09:39 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:09:46 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:12:53 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:13:06 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:13:10 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:13:15 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:14:10 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:14:14 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:14:18 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:20:05 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:27:44 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:33:40 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:35:04 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:35:42 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:38:00 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:38:05 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:47:41 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:51:17 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 06:57:44 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:01:46 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:03:42 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:03:46 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:03:51 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:10:01 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:10:05 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:10:10 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:13:42 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:21:23 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:21:28 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:27:44 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:27:45 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:33:49 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:42:11 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:47:17 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:53:00 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:54:09 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:54:13 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:54:18 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:54:28 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:55:06 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:57:08 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:57:13 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:57:16 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:57:44 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:57:45 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:58:26 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:58:30 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 07:58:35 Unraid-NAS dhcpcd[1016]: br0: deleting address [PART1]:[PART2]/64 Feb 11 08:00:04 Unraid-NAS kernel: vethbf49f2a: renamed from eth0 Feb 11 08:00:04 Unraid-NAS kernel: br-9a649b6f5d31: port 1(veth99ebabf) entered disabled state Feb 11 08:00:04 Unraid-NAS kernel: br-9a649b6f5d31: port 1(veth99ebabf) entered disabled state Feb 11 08:00:04 Unraid-NAS kernel: device veth99ebabf left promiscuous mode Feb 11 08:00:04 Unraid-NAS kernel: br-9a649b6f5d31: port 1(veth99ebabf) entered disabled state Feb 11 08:00:05 Unraid-NAS kernel: br-9a649b6f5d31: port 1(vethf6bba0f) entered blocking state Feb 11 08:00:05 Unraid-NAS kernel: br-9a649b6f5d31: port 1(vethf6bba0f) entered disabled state Feb 11 08:00:05 Unraid-NAS kernel: device vethf6bba0f entered promiscuous mode Feb 11 08:00:05 Unraid-NAS kernel: br-9a649b6f5d31: port 1(vethf6bba0f) entered blocking state Feb 11 08:00:05 Unraid-NAS kernel: br-9a649b6f5d31: port 1(vethf6bba0f) entered forwarding state Feb 11 08:00:05 Unraid-NAS kernel: eth0: renamed from veth732f06a Feb 11 08:00:05 Unraid-NAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethf6bba0f: link becomes ready I've redacted my IPV6 addresses. Couldn't find a tool for that, so I simply replaced parts of it by variables, where I saw them repeating ¯\_(ツ)_/¯ Here's what my settings look: Interface eth0 IPv6 address assignment: Automatic IPv6 address: [PART1]:[PART2] / 64 IPv6 default gateway: fe80::[GATEWAY-ADDRESS] IPv6 privacy extensions: Disabled IPv6 DNS server assignment: Automatic IPv6 DNS server: fd00::[GATEWAY-ADDRESS] IPv6 DNS server 2: [PART1][GATEWAY-ADDRESS] Desired MTU: 1500 Enable VLANs: No Interface Extra Current listening interfaces: br0 Include listening interfaces: -empty- Exclude listening interfaces: -empty- Routing Table ROUTE - GATEWAY - METRIC IPv4 default - 192.168.178.1 via br0 - 0 172.22.0.0/16 - br-9a649b6f5d31 - 0 192.168.178.0/24 - br0 - 1 IPv6 [PART1]::/64 - br0 - 1005 [OTHER-ADDRESS]::/64 - br0 - 1005 default - fe80::[GATEWAY-ADDRESS] via br0 - 1005

Okay, so since I‘m reaching C10 that should be the case for me as well. It sounds like after that there’s no difference compared to headless in terms of power savings?

I‘m confused, I assumed not plugging in any monitor would be running headless. Is there a difference?

Had to go a bit more complicated, since Unraid is kept in Memory. So I created the file /boot/rules/01-asrock-led.rules, then added commands to /boot/config/go so it'd copy and reload the rules. # Copy the rules file cp /boot/rules/01-asrock-led.rules /etc/udev/rules.d/ chmod 644 -R /etc/udev/rules.d/01-asrock-led.rules 2> /dev/null # reload udev rules udevadm control --reload-rules udevadm trigger Sadly this doesn't work though. Not sure what I'm missing I was missing the udevadm trigger 🤦‍♂️ I don't have USB devices plugged in, other than the USB for Unraid. The only other thing plugged in is my network cable. From what I was able to google "consoleblank" shouldn't make any difference is no screen is plugged in, right? After disabling the LED controller, I'm down to !!! 6W IDLE !!!, pretty fucking good I'd say I'm pretty much ~90% C10 Idle, is that something that can still be pushed? (I'm literally clueless, first time trying to build a DIY NAS ^^') Based on the device stats I think there isn't anything left to disable? The Device 1ed0:2283 seems to be a Non-Volatile memory controller, I assume that's for my SSD, so a no-no in terms of disabling

Hey @genesisdoeswhatnintendont, thanks so much for your guide, I followed it and am able to reach C10 now (mostly) and dropped down to 10W Idle. I have a couple of questions, since you have the exact same Mainboard that I do. Not sure if you're still around since your post was a year ago, but here's to hoping (not sure why I thought that, lol) Could you explain what those do exactly? I looked at the `setup_script_file`, but it's not quite clear to me. It looks like "LED MCU" disabled USB devices, so that's a no-no for me since I'm using Unraid I guess? "Native ASPM" disabled means that the BIOS handles ASPM, correct? If so that should be good for me as well? (already enabled it) "Discrete Bluetooth Interface" not sure if this applies to the AsRock H610m-itx. Does it use Bluetooth over the Wifi Antennas? Would that also disable Wifi? "Password protection of Runtime Variables" just means I could use that tool without having to set an admin password? @genesisdoeswhatnintendont, could I compare my BIOS settings with yours? Currently I'm still getting about 28% C2, which I'd like to eliminate as well if possible

Gonna try a couple more things in BIOS before giving this a try, will report back after that. Checked without it, sadly not the cause of my problems. (Or luckily I guess, since I don't need to send it back, lol)

Hey guys, I've followed the guide, but I can't reach better than C3 PKG states. Hoping to get some help here My System is: CPU: i3-13100 MB: AsRock H610m-itx RAM: Mushkin 2x32GB SSD: Teamgroup MP33 Pro 2TB I haven't installed HDDs yet, since I'm still waiting for my case, lol. (So I decided to dive into this topic while waiting xD) Not sure if this matters, but I've not created the Cache Pool with my SSD either. The iGPU driver however is installed. Current Idle Draw: 15W (I assume/hope this can still go lower) I've attached screenshots of my powertop idle stats, device stats and tunables, as well as the ASPM stats. Device Stats looks suspicious to me, since some devices are permanently at 100%? When checking the CPU frequency there are always some cores jumping to ~4GHz before going down to 800MHz again. Unraid WebGUI was not open, I only used the terminal to access Unraid. Additionally, here are my BIOS settings: CPU Config: Hyper Threading: Enabled Active P-Cores: All CPU C States Support: Enabled Enhanced Halt State: Enabled CPU C6 & C7 Support: Enabled CPU Package C State Support: Enabled CFG Lock: Disabled (couldn't find any real info on what this does ¯\_(ツ)_/¯ ) C6DRAM: Enabled AVX/AVX2: Enabled Intel Virtualization Technology: Enabled Hardware Prefetcher: Enabled Adjacent Cache Line Prefetch: Enabled Chipset Config: Primary Graphics Adapter: Onboard Above 4G Decoding: Enabled Clever Access Memory: Enabled VI-d: Enabled SR-IOV Support: Enabled DMI Link Speed: Gen4 PCIE1 Link Speed: Auto PCI Express Native Control: Enabled PCIE ASPM Support: L1 PCH PCIE ASPM Support: L1 DMI ASPM Support: Enabled PCH DMI ASPM Support: Enabled iGPU Multi Monitor: Disabled Intel® Ethernet Connection I219-V: Enabled Onboard HD Audio: Disabled Onboard WAN Device: Disabled Deep Sleep: Enabled in S4-5 Restore on AC/Power Loss: Power Off Restore Onboard LED Default: Disabled RGB LED: Off GNA Device: Disabled Storage Config: SATA Controller(s): Enabled SATA Mode Selection: AHCI Hybrid Storage Detection and Configuration Mode: Disabled SATA Aggressive Link Power Management: Enabled Hard Disk S.M.A.R.T: Enabled ACPI Config: Suspend to RAM: Auto (other choice was disabled) PS/2 Keyboard Wake Support: Disabled PCIE Devices Power On: Disabled I219 LAN Power On: Disabled RTC Alarm Power On: By OS USB Keyboard/Mouse Power On: Disabled USB Config Legacy USB Support: Enabled XHCI Hand-off: Disabled Lastly: I found this post on askubuntu.com, which was about the my exact MB, is that something I should look into? Don't want to go around installing Windows on my SSD and doing some potential dangerous stuff before asking here first

Based on the docs that should work as well (didn't test it yet) I guess that's probably more reasonably, to expect people like me to just set that variable

Since my project has grown to include quite a sizeable amount of containers I noticed that docker compose struggles with that. For context, I have a single "docker-compose.yml" which has includes to the sub-compose files that make up my project. Ideally I'd like to be able to just use that main file to start up the whole project. By default it tries to do everything in parallel, which makes it impossible for me to start my project from scratch. It's possible to use the --parallel option like this: docker compose --parallel 3 up That way docker compose can handle huge compose files or projects consisting out of a multitude of included sub-compose files Suggestion: would it be possible to add that as an option in the Docker Compose Manager settings?

Ah, I wasn't aware that that was a limitation of the compose command. Would be really cool if compose could also show extraction progress, so I know it's still working, just extracting something really slowly, lol

That's weird, when I do a docker pull some_image in the normal terminal I also get extraction progress

I'm currently using `Terminal`

I had my traefik configured to log to a file... 🤦‍♂️ New question, are there plans to show extraction progress in the UI as well? I thought that my compose-up was stuck when pulling Home Assistant (first time, haven't used that before) After restarting a couple of times I decided to try a manual `docker pull` and figured out that the extraction is just extremely slow.

Is the viewing of logs on a container basis bugged? Or am I doing something wrong? I have a stack with Traefik and Homepage, so nothing too fancy yet. When I try to check the logs for Traefik (clicking on Traefik's icon, then clicking "Logs"), I only get one line: time="2024-01-05T21:51:16+01:00" level=info msg="Configuration loaded from file: /etc/traefik/traefik.yml" When I check the log file from Traefik however, everything is logged as it should be.